path: root/docs/_locale/de_DE/LC_MESSAGES/documentation.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2021, VyOS maintainers and contributors
# This file is distributed under the same license as the VyOS package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: VyOS 1.4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-10-21 12:01+0200\n"
"PO-Revision-Date: 2022-10-21 09:55+0000\n"
"Language-Team: German (Germany) (https://www.transifex.com/vyos/teams/155110/de_DE/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: de_DE\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#: ../../documentation.rst:7 94964c95ff7d439ea652112198572568
msgid "Write Documentation"
msgstr ""

#: ../../documentation.rst:9 3b7e55144593453a9a26923fe4af07fd
msgid ""
"We encourage every VyOS user to help us improve our documentation as we have"
" a deficit like most software projects.  This not only helps you when "
"reading but also everyone else."
msgstr ""

#: ../../documentation.rst:13 95e4fdf1bb5446b4a518da55d6d852c6
msgid ""
"If you are willing to contribute to our documentation this is the definite "
"guide how to do so."
msgstr ""

#: ../../documentation.rst:16 ededc47dd4c042239dbf608c66f954dd
msgid ""
"In contrast to submitting code patches, there is no requirement that you "
"open up a Phabricator_ task prior to submitting a Pull-Request to the "
"documentation."
msgstr ""

#: ../../documentation.rst:20 782eaae7a5d644e19bad45e9076af20e
msgid ""
"VyOS documentation is written in reStructuredText and generated to Read the "
"Docs pages with Sphinx, as per the Python tradition, as well as PDF files "
"for offline use through LaTeX. We welcome all sorts of contributions to the "
"documentation. Not just new additions but also corrections to existing "
"documentation."
msgstr ""

#: ../../documentation.rst:25 efa2880fb8334caa872042aa612c65e6
msgid ""
"The documentation source is kept in the Git repository at "
"https://github.com/vyos/vyos-documentation and you can follow the "
"instructions in the README.md_ to build and test your changes."
msgstr ""

#: ../../documentation.rst:29 3969612f13a74092ba456e01b5f2775b
msgid ""
"You can either install Sphinx (and TeX Live for PDF output) and build the "
"documentation locally, or use the Dockerfile_ to build it in a container."
msgstr ""

#: ../../documentation.rst:33 f12c9bd0789146b6927342b50643b789
msgid "Guidelines"
msgstr ""

#: ../../documentation.rst:35 55bbc87304e44ad9a7ce2d2125f95ab0
msgid ""
"There are a few things to keep in mind when contributing to the "
"documentation, for the sake of consistency and readability."
msgstr ""

#: ../../documentation.rst:38 fae514909a9b46119242e33379c9b632
msgid ""
"Take a look at the :doc:`/documentation` page for an intricate explanation "
"of the documentation process."
msgstr ""

#: ../../documentation.rst:41 28fc3fcc02a348798eb126a224e07041
msgid "The following is a quick summary of the rules:"
msgstr ""

#: ../../documentation.rst:43 b3f38a7e7223447bae8c02e06cc0e102
msgid ""
"Use American English at all times. It's always a good idea to run your text "
"through a grammar and spell checker, such as `Grammarly`_."
msgstr ""

#: ../../documentation.rst:45 13aaa37cf1cc4b719eb5c155e51e8d2e
msgid "Don't forget to update ``index.rst`` when adding a new node."
msgstr ""

#: ../../documentation.rst:46 77b3380c330e4182b2f2d66a05d011ee
msgid ""
"Try not to exceed 80 characters per line, but don't break URLs over this."
msgstr ""

#: ../../documentation.rst:47 6077a30ed5bd40bbbd999618b230c28c
msgid ""
"Properly quote commands, filenames and brief code snippets with double "
"backticks."
msgstr ""

#: ../../documentation.rst:48 45b676374e4e454db5a6ea24fdd17982
msgid "Use literal blocks for longer snippets."
msgstr ""

#: ../../documentation.rst:49 e4f4d4a80c574b07920f54618feae6b9
msgid "Leave a newline before and after a header."
msgstr ""

#: ../../documentation.rst:50 d28915a162f64416a195a7adf1bec625
msgid "Indent with two spaces."
msgstr ""

#: ../../documentation.rst:51 84be4f78516a420e96766acf956dd013
msgid "When in doubt, follow the style of existing documentation."
msgstr ""

#: ../../documentation.rst:53 5bc1e63a78604c78937ba4206c484dc4
msgid ""
"And finally, remember that the reStructuredText files aren't exclusively for"
" generating HTML and PDF. They should be human-readable and easily perused "
"from a console."
msgstr ""

#: ../../documentation.rst:58 c5a11ac11c5745db83c5c2ed36a826ae
msgid "Forking Workflow"
msgstr ""

#: ../../documentation.rst:60 e1378b2863b0470ca1efa1708ba17e18
msgid ""
"The Forking Workflow is fundamentally different from other popular Git "
"workflows. Instead of using a single server-side repository to act as the "
"\"central\" codebase, it gives every developer their own server-side "
"repository. This means that each contributor has not one, but two Git "
"repositories: a private local one and a public server-side one."
msgstr ""

#: ../../documentation.rst:66 5e9cb792bac94393907571454d1afb34
msgid ""
"The main advantage of the Forking Workflow is that contributions can be "
"integrated without the need for everybody to push to a single central "
"repository. Developers push to their own server-side repositories, and only "
"the project maintainer can push to the official repository. This allows the "
"maintainer to accept commits from any developer without giving them write "
"access to the official codebase."
msgstr ""

#: ../../documentation.rst:73 b1bfb8e5fc444b75ab56aa02da7cd2ce
msgid ""
"Updates to our documentation should be delivered by a GitHub pull-request. "
"This requires you already have a GitHub account."
msgstr ""

#: ../../documentation.rst:76 62c01f88d8f445b9a839710637474afa
msgid ""
"Fork this project on GitHub https://github.com/vyos/vyos-documentation/fork"
msgstr ""

#: ../../documentation.rst:78 bf808d9ed35b472abbed287c8254caba
msgid ""
"Clone fork to local machine, then change to that directory ``$ cd vyos-"
"documentation``"
msgstr ""

#: ../../documentation.rst:81 c5b19341bfbb49ef85f13de91dcf407e
msgid ""
"Install the requirements ``$ pip install -r requirements.txt`` (or something"
" similar)"
msgstr ""

#: ../../documentation.rst:84 52e056f411734c0a813394727352608c
msgid ""
"Create a new branch for your work, use a descriptive name of your work: ``$ "
"git checkout -b <branch-name>``"
msgstr ""

#: ../../documentation.rst:87 ffb8f5590f774000aa35721b83755e09
msgid ""
"Make all your changes - please keep our commit rules in mind "
"(:ref:`prepare_commit`). This mainly applies to proper commit messages "
"describing your change (how and why). Please check out the documentation of "
"Sphinx-doc_ or reStructuredText_ if you are not familiar with it. This is "
"used for writing our docs. Additional directives how to write in RST can be "
"obtained from reStructuredTextDirectives_."
msgstr ""

#: ../../documentation.rst:94 b3679b2330164a859572ce47a0514187
msgid ""
"Check your changes by locally building the documentation ``$ make "
"livehtml``. Sphinx will build the html files in the ``docs/_build`` folder. "
"We provide you with a Docker container for an easy-to-use user experience. "
"Check the README.md_ file of this repository."
msgstr ""

#: ../../documentation.rst:99 7aefe7e395d648c9bcb4c6de629ab9bd
msgid ""
"View modified files by calling ``$ git status``. You will get an overview of"
" all files modified by you. You can add individual files to the Git Index in"
" the next step."
msgstr ""

#: ../../documentation.rst:103 15e596bb33174be49011b2652294c899
msgid ""
"Add modified files to Git index ``$ git add path/to/filename`` or add all "
"unstaged files ``$ git add .``. All files added to the Git index will be "
"part of you following Git commit."
msgstr ""

#: ../../documentation.rst:107 dc4cf1b118b34639aa4af512d4a97ea3
msgid ""
"Commit your changes with the message, ``$ git commit -m \"<commit "
"message>\"`` or  use ``$ git commit -v`` to have your configured editor "
"launched. You can type in a commit message. Again please make yourself "
"comfortable without rules (:ref:`prepare_commit`)."
msgstr ""

#: ../../documentation.rst:112 edffb9d383bd4e318339a50b23882152
msgid ""
"Push commits to your GitHub project: ``$ git push -u origin <branch-name>``"
msgstr ""

#: ../../documentation.rst:114 36ab7ea3abbc42bbbba40116858ea614
msgid ""
"Submit pull-request. In GitHub visit the main repository and you should see "
"a banner suggesting to make a pull request. Fill out the form and describe "
"what you do."
msgstr ""

#: ../../documentation.rst:118 93fc93da17a5470f8d2d27aea68c4f4e
msgid ""
"Once pull requests have been approved, you may want to locally update your "
"forked repository too. First you'll have to add a second remote called "
"`upstream` which points to our main repository. ``$ git remote add upstream "
"https://github.com/vyos/vyos-documentation.git``"
msgstr ""

#: ../../documentation.rst:123 4cf28b23ad054e3e8bfb11d3f231d1d7
msgid "Check your configured remote repositories:"
msgstr ""

#: ../../documentation.rst:133 a99b75cb10e541be9c348b4c2f470942
msgid ""
"Your remote repo on Github is called ``origin``, while the original repo you"
" have forked is called ``upstream``. Now you can locally update your forked "
"repo."
msgstr ""

#: ../../documentation.rst:143 ece87fc5565e4380a6d9d86faee1b2cf
msgid ""
"If you also want to update your fork on GitHub, use the following: ``$ git "
"push origin master``"
msgstr ""

#: ../../documentation.rst:147 96a770c0c6344caf9990a995a0dce07f
msgid "Style Guide"
msgstr ""

#: ../../documentation.rst:150 ce35171d5abb48f38c630ab183f5d17f
msgid "Formating and Sphinxmarkup"
msgstr ""

#: ../../documentation.rst:153 180aa5aeaeab4b03b70442e407ef004c
msgid "TOC Level"
msgstr ""

#: ../../documentation.rst:155 c5a0e8a7d6bb401f9c8db6e86a9ddd25
msgid "We use the following syntax for Headlines."
msgstr ""

#: ../../documentation.rst:180 18e9696b72734c4a9447589baff11d98
msgid "Cross-References"
msgstr ""

#: ../../documentation.rst:182 afb0da1b9c6b467a97e3ecd28f161264
msgid ""
"A plugin will be used to generate a reference label for each headline. To "
"reference a page or a section in the documentation use the ``:ref:`` "
"command."
msgstr ""

#: ../../documentation.rst:186 782d82e3d77242c5b8702dbe9ad9015c
msgid ""
"For example, you want to reference the headline **VLAN** in the "
"**ethernet.rst** page. The plugin generates the label based on the headline "
"and the file path."
msgstr ""

#: ../../documentation.rst:190 0d809507de9d426fac3b363898ccfb3d
msgid "``:ref:`configuration/interfaces/ethernet:vlan``"
msgstr ""

#: ../../documentation.rst:192 ad8171eeebd649238dcbb3a710dc5b7e
msgid "to use an alternative hyperlink use it this way:"
msgstr ""

#: ../../documentation.rst:194 479178da660e48a2921a96eab1814a4c
msgid "``:ref:`Check out VLAN<configuration/interfaces/ethernet:vlan>``"
msgstr ""

#: ../../documentation.rst:197 480b006d02b84e9a9702e1b54df9f9a2
msgid "handle build errors"
msgstr ""

#: ../../documentation.rst:199 98ea702ff805489bb7c3e7ea3b7ae917
msgid ""
"The plugin will warn on build if a headline has a duplicate name in the same"
" document. To prevent this warning, you have to put a custom link on top of "
"the headline."
msgstr ""

#: ../../documentation.rst:229 ead0a9ff4939478098a747a716aa97fd
msgid "Address space"
msgstr ""

#: ../../documentation.rst:231 679cf6c2fc774666b795be27e4ce079c
msgid ""
"Note the following RFCs (:rfc:`5737`, :rfc:`3849`, :rfc:`5389` and "
":rfc:`7042`), which describe the reserved public IP addresses and autonomous"
" system numbers for the documentation:"
msgstr ""

#: ../../documentation.rst:235 0611f1bd52a24b328cc8b2dd66e293f9
msgid "``192.0.2.0/24``"
msgstr ""

#: ../../documentation.rst:236 104be7c19ff3491e8bc325953aee1c8a
msgid "``198.51.100.0/24``"
msgstr ""

#: ../../documentation.rst:237 942a3d760bec48bfbaae6c1f0a8c113d
msgid "``203.0.113.0/24``"
msgstr ""

#: ../../documentation.rst:238 c62d58ea9cfa4a35821ba38bc92a9be2
msgid "``2001:db8::/32``"
msgstr ""

#: ../../documentation.rst:239 5fd11e6dabd04b95948f356979d12992
msgid "16bit ASN: ``64496 - 64511``"
msgstr ""

#: ../../documentation.rst:240 5bf414c887514d96b320efda0fc286da
msgid "32bit ASN: ``65536 - 65551``"
msgstr ""

#: ../../documentation.rst:241 f5b33645b8124b638f771776a404f0ff
msgid "Unicast MAC Addresses: ``00-53-00`` to ``00-53-FF``"
msgstr ""

#: ../../documentation.rst:242 a32298f007de4b95a1df392ca3bb0a51
msgid "Multicast MAC-Addresses: ``90-10-00`` to ``90-10-FF``"
msgstr ""

#: ../../documentation.rst:244 a666a88a512b4e24a774ae53412b8597
msgid "Please do not use other public address space."
msgstr ""

#: ../../documentation.rst:248 4d2d64f1a6ba4bbcbc1c9eda933f1ed9
msgid "Line length"
msgstr ""

#: ../../documentation.rst:250 03a4e439a9674a11aacaaacca502c43c
msgid "Limit all lines to a maximum of 80 characters."
msgstr ""

#: ../../documentation.rst:252 176a3ee3983d42b0bf163974c82f4d30
msgid ""
"Except in ``.. code-block::`` because it uses the html tag ``<pre>`` and "
"renders the same line format from the source rst file."
msgstr ""

#: ../../documentation.rst:257 a5ac440b498648d68fbd6b166d70285c
msgid "Autolinter"
msgstr ""

#: ../../documentation.rst:259 f13fcca1cecc455984fd6ecca63cb04c
msgid ""
"Each GitHub pull request is automatically linted to check the address space "
"and line length."
msgstr ""

#: ../../documentation.rst:262 cf7badd6f7624ebe8fabfd43921e0362
msgid ""
"Sometimes it is necessary to provide real IP addresses like in the "
":ref:`examples`. For this, please use the sphinx comment syntax ``.. "
"stop_vyoslinter`` to stop the linter and ``.. start_vyoslinter`` to start."
msgstr ""

#: ../../documentation.rst:268 3f9fdf47afcc4766b5024f4a5d9f92f9
msgid "Custom Sphinx-doc Markup"
msgstr ""

#: ../../documentation.rst:270 d81442f618624c9a9e6d631d76f9cf9c
msgid ""
"Custom commands have been developed for writing the documentation. Please "
"make yourself comfortable with those commands as this eases the way we "
"render the documentation."
msgstr ""

#: ../../documentation.rst:275 20a6bc0a50b34f608dd1a94b48235e21
msgid "cfgcmd"
msgstr ""

#: ../../documentation.rst:277 91902cd7f0bf46efa8aecd511ddd6fd5
msgid ""
"When documenting CLI commands, use the ``.. cfgcmd::`` directive for all "
"configuration mode commands. An explanation of the described command should "
"be added below this statement. Replace all variable contents with <value> or"
" something similar."
msgstr ""

#: ../../documentation.rst:282 a833a4416f634f5597b56c19514ac476
msgid ""
"With those custom commands, it will be possible to render them in a more "
"descriptive way in the resulting HTML/PDF manual."
msgstr ""

#: ../../documentation.rst:292 d8b6168aee0a46c0ac1d563f5de13f10
msgid "For an inline configuration level command, use ``:cfgcmd:``"
msgstr ""

#: ../../documentation.rst:299 445c9bd2dcc948088d46b8e6c1571665
msgid ""
"To extract a defaultvalue from the XML definitions add a ``:defaultvalue:`` "
"to ``.. cfgcmd::`` directive. To have this feature locally, the vyos-1x "
"submodule must be initialized before. Please be aware to not update the "
"submodule in your PR."
msgstr ""

#: ../../documentation.rst:314 f1d07cc20de04b2782a21eb9749b2646
msgid "opcmd"
msgstr ""

#: ../../documentation.rst:316 6e2d006837434db3b020592720f8d3b6
msgid ""
"When documenting operational level commands, use the ``.. opcmd::`` "
"directive. An explanation of the described command should be added below "
"this statement."
msgstr ""

#: ../../documentation.rst:319 bd92a75286674617842d1fa6858d4a9b
msgid ""
"With those custom commands, it is possible to render them in a more "
"descriptive way in the resulting HTML/PDF manual."
msgstr ""

#: ../../documentation.rst:328 270866faefbe4632884dbf5a930adf40
msgid "For an inline operational level command, use ``:opcmd:``"
msgstr ""

#: ../../documentation.rst:335 3429ba857fc24422ad11b75497fefd3a
msgid "cmdinclude"
msgstr ""

#: ../../documentation.rst:337 00849875c2cd4d2e891a37f401f8158a
msgid ""
"To minimize redundancy, there is a special include directive. It includes a "
"txt file and replace the ``{{ var0 }}`` - ``{{ var9 }}`` with the correct "
"value."
msgstr ""

#: ../../documentation.rst:346 4b978dc344d24f4a8e1369fc6563ed76
msgid "the content of interface-address.txt looks like this"
msgstr ""

#: ../../documentation.rst:373 2ad81153f30a4d9c92ffaca186a6f298
msgid "vytask"
msgstr ""

#: ../../documentation.rst:375 3e3f4bdb039a49359509f677749cd471
msgid ""
"When referencing to VyOS Phabricator Tasks, there is a custom Sphinx Markup "
"command called ``vytask`` that automatically renders to a proper Phabricator"
" URL. This is heavily used in the :ref:`release-notes` section."
msgstr ""

#: ../../documentation.rst:385 06e68cff507c410a9ce2f9b302b354b6
msgid "Page content"
msgstr ""

#: ../../documentation.rst:387 78abdcd7186c46d2b9bc5c0027f6ae6b
msgid ""
"The documentation has 3 different types of pages. The same kind of pages "
"must have the same structure to achieve a recognition factor."
msgstr ""

#: ../../documentation.rst:390 04e865df23e4415a929390a0f17edf33
msgid ""
"All RST files must follow the same TOC Level syntax and have to start with"
msgstr ""

#: ../../documentation.rst:399 49f1322f7fbb4d398926ae2c552de75b
msgid "Configuration mode pages"
msgstr ""

#: ../../documentation.rst:401 6674bad9eb4c45af81673c89d768f06b
msgid ""
"The configuration mode folder and the articles cover the specific level of "
"the commands. The exact level depends on the command. This should provide "
"stability for URLs used in the forum or blogpost."
msgstr ""

#: ../../documentation.rst:405 e1f15b8d4b7f44ca8446fd7d94c17ab2
msgid "For example:"
msgstr ""

#: ../../documentation.rst:407 c3236f51d7844beb9864e651a2a38dd3
msgid "``set firewall zone`` is written in ``firewall/zone.rst``"
msgstr ""

#: ../../documentation.rst:408 d06871e602cd4ebca42768151b6f53fd
msgid "``set interfaces ethernet`` is written in ``interfaces/ethernet.rst``"
msgstr ""

#: ../../documentation.rst:410 1dcc48cf2c9f47d982ef6d909824ef85
msgid ""
"The article starts with a short introduction about the command or the "
"technology. Please include some helpful links or background information."
msgstr ""

#: ../../documentation.rst:413 c0e3c76ac5a0432fa664ffaa22245ad9
msgid ""
"An optional section follows. Some commands have requirements like compatible"
" hardware (e.g. Wifi) or some commands you have to set before. For example, "
"it is recommended to set a route-map before configuring BGP."
msgstr ""

#: ../../documentation.rst:417 906906edc5b1476e8e90e47ef6a8cf24
msgid ""
"In the configuration part of the page, all possible configuration options "
"should be documented. Use ``.. cfgcmd::`` described above."
msgstr ""

#: ../../documentation.rst:420 e90cb08881db48a1b9ba29d026bd5bf9
msgid ""
"Related operation command must be documented in the next part of the "
"article. Use ``::opcmd..`` for these commands."
msgstr ""

#: ../../documentation.rst:423 4f7507f8857d4f61a750aae5e4d19a83
msgid ""
"If there some troubleshooting guides related to the commands. Explain it in "
"the next optional part."
msgstr ""

#: ../../documentation.rst:427 efd1894eba394a22a9f1b636f7cb6339
msgid "Operation mode pages"
msgstr ""

#: ../../documentation.rst:429 116d1678c2ca4e3cb9c760595291ded3
msgid ""
"Operation mode commands that do not fit in a related configuration mode "
"command must be documented in this part of the documentation."
msgstr ""

#: ../../documentation.rst:432 c98b393f766f42808e78d0e60c62b5e9
msgid ""
"General concepts for troubleshooting and detailed process descriptions "
"belong here."
msgstr ""

#: ../../documentation.rst:436 88fdcd3b3dcf4161ba5c4bc51922b688
msgid "Anything else"
msgstr ""

#: ../../documentation.rst:438 54c4ece207164ff3ab5a1a18245f68e9
msgid ""
"Anything else that is not a configuration or an operation command has no "
"predefined structure."
msgstr ""