Browsing Spanish translation

Don't show this notice anymore
Before translating, be sure to go through Ubuntu Translators instructions and Spanish guidelines.
21082117 of 2380 results
2108.
If you have binary files that do not contain a null byte though, be
sure to add ``eol = exact`` rules for those as well. You can do this
by giving more explicit patterns earlier in the rules file. For example::
There are line breaks here. Each one represents a line break. Start a new line in the equivalent position in the translation.
Si tiene archivos binarios que no contienen un byte nulo, esté
seguro de añadir la regla «eol = exact». Puede hacer eso
dando reglas específicas antes de ello en el archivo rules. Por ejemplo::
Translated and reviewed by Paco Molinero
Located in en/help_topics/eol.txt:45
2109.
[name *.png]
eol = exact
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/eol.txt:49
2110.
If your working tree is on a network drive shared by users on different
operating systems, you typically want to force certain conventions for
certain files. In that way, if a file is created with the wrong line
endings or line endings get mixed during editing, it gets committed
correctly and gets checked out correctly. For example::
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/eol.txt:55
2111.
[name *.bat]
eol = crlf
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/eol.txt:61
2112.
[name *.sh]
eol = lf
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/eol.txt:64
2113.
If you take the care to create files with their required endings, you can
achieve *almost* the same thing by using ``eol = exact``. It is slightly
safer to use ``lf`` and ``crlf`` though because edits accidentally
introducing mixed line endings will be corrected during commit for files
with those settings.
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/eol.txt:70
2114.
If you have sample test data that deliberately has text files with mixed
newline conventions, you can ask for those to be left alone like this::
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/eol.txt:76
2115.
[name test_data/]
eol = exact
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/eol.txt:79
2116.
Note that ``exact`` does not imply the file is binary but it does mean
that no conversion of end-of-lines will be done. (Bazaar currently relies
of content analysis to detect binary files for commands like ``diff``.
In the future, a ``binary = true`` rule may be added but it is not
supported yet.)
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/eol.txt:85
2117.
If you have an existing repository with text files already stored using
Windows newline conventions (``crlf``), then you may want to keep using that
convention in the repository. Forcing certain files to this convention
may also help users who do not have rules configured. To do this, set
``eol`` to one of the values below.
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/eol.txt:91
21082117 of 2380 results

This translation is managed by Ubuntu Spanish Translators, assigned by Ubuntu Translators.

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

Contributors to this translation: Adolfo Jayme Barrientos, Andrés Margffoy, Dani Moncayo, Diego Islas Ocampo, Eduardo Alberto Calvo, Emilio Hidalgo Simon, Jaime Ernesto Mora, Jelmer Vernooij, Jorge Luis Granda, Jose Luis Tirado, Kathleen Perez, Lucio, Miguel Angel del Olmo, Monkey, Nacho Perea, Pablo Rubianes, Paco Molinero, Simona Cana, VPablo, Víctor Fernández, calabero111, pescamillam, psamuel.