Breezy

Browsing Norwegian Bokmal translation

  1. Series trunk
  2. Template “brz”
  3. Norwegian Bokmal (nb)
Don't show this notice anymore
Before translating, be sure to go through Launchpad Translators instructions and Norwegian Bokmal guidelines.
2521 → 2530 of 2550 results First • • • Last
2521.
Patterns containing square brackets or spaces should be
surrounded in quotes to ensure they are correctly parsed.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in en/help_topics/rules.txt:39
2522.
authentication Information on configuring authentication
basic Basic commands
branches Information on what a branch is
bugs Bug tracker settings
checkouts Information on what a checkout is
configuration Details on the configuration settings available
conflict-types Types of conflicts and what to do about them
content-filters Conversion of content into/from working trees
criss-cross Information on criss-cross merging
current-formats Current storage formats
debug-flags Options to show or record debug information
diverged-branches How to fix diverged branches
env-variables Environment variable names and values
eol Information on end-of-line handling
files Information on configuration and log files
formats Information on choosing a storage format
git Using Bazaar with Git
global-options Options that control how Breezy runs
glossary Glossary
hooks Points at which custom processing can be added
launchpad Using Bazaar with Launchpad.net
location-alias Aliases for remembered locations
log-formats Details on the logging formats available
missing-extensions What to do when compiled extensions are missing
other-formats Experimental and deprecated storage formats
patterns Information on the pattern syntax
repositories Basic information on shared repositories.
revisionspec Explain how to use --revision
rules Information on defining rule-based preferences
standalone-trees Information on what a standalone tree is
standard-options Options that can be used with any command
status-flags Help on status flags
sync-for-reconfigure Steps to resolve "out-of-sync" when reconfiguring
topics Topics list
url-special-chars Special character handling in URLs
urlspec Supported transport protocols
working-trees Information on working trees
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in en/help_topics/topics.txt:1
2523.
Special character handling in URLs
==================================
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in en/help_topics/url-special-chars.txt:1
2524.
Bazaar allows locations to be specified in multiple ways, either:
(no translation yet)
Located in en/help_topics/url-special-chars.txt:4
2525.
* Fully qualified URLs
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in en/help_topics/url-special-chars.txt:6
2526.
* File system paths, relative or absolute
There are leading/trailing spaces here. Each one represents a space character. Enter a space in the equivalent position in the translation.
(no translation yet)
Located in en/help_topics/url-special-chars.txt:8
2527.
Internally brz treats all locations as URLs. For any file system paths
that are specified it will automatically determine the appropriate URL
representation, and escape special characters where necessary.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in en/help_topics/url-special-chars.txt:10
2528.
There are a few characters which have special meaning in URLs and need careful
handling to avoid ambiguities. Characters can be escaped with a % and a hex
value in URLs. Any non-ASCII characters in a file path will automatically be
urlencoded when the path is converted to a URL.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in en/help_topics/url-special-chars.txt:14
2529.
URLs represent non-ASCII characters in an encoding defined by the server, but
usually UTF-8. The % escapes should be of the UTF-8 bytes. Bazaar tries to be
generous in what it accepts as a URL and to print them in a way that
will be readable.
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in en/help_topics/url-special-chars.txt:19
2530.
For example, if you have a directory named '/tmp/%2False' these are all valid
ways of accessing the content (0x2F, or 47, is the ASCII code for forward slash)::
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
(no translation yet)
Located in en/help_topics/url-special-chars.txt:24
2521 → 2530 of 2550 results First • • • Last

This translation is managed by Launchpad Norwegian translators, assigned by Launchpad Translators.

You are not logged in. Please log in to work on translations.

No-one has contributed to this translation yet.