summaryrefslogtreecommitdiff
path: root/man/es/man1/dos2unix.htm
diff options
context:
space:
mode:
Diffstat (limited to 'man/es/man1/dos2unix.htm')
-rw-r--r--man/es/man1/dos2unix.htm67
1 files changed, 61 insertions, 6 deletions
diff --git a/man/es/man1/dos2unix.htm b/man/es/man1/dos2unix.htm
index d85a74e..fc5d154 100644
--- a/man/es/man1/dos2unix.htm
+++ b/man/es/man1/dos2unix.htm
@@ -2,12 +2,12 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
-<title>dos2unix 7.2 - Convertidor de archivos de texto de formato DOS/Mac a Unix y viceversa</title>
+<title>dos2unix 7.3 - Convertidor de archivos de texto de formato DOS/Mac a Unix y viceversa</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
-<link rev="made" href="mailto:root@localhost" />
+<link rev="made" href="mailto:ASSI@cygwin.nonet" />
</head>
-<body style="background-color: white">
+<body>
@@ -23,6 +23,7 @@
<li><a href="#Codificaciones">Codificaciones</a></li>
<li><a href="#Conversion">Conversion</a></li>
<li><a href="#Marca-de-orden-de-bytes">Marca de orden de bytes</a></li>
+ <li><a href="#Unicode-file-names-on-Windows">Unicode file names on Windows</a></li>
<li><a href="#Ejemplos-Unicode">Ejemplos Unicode</a></li>
</ul>
</li>
@@ -143,6 +144,50 @@
<p>Establece el modo de conversi&oacute;n, Donde CONVMODE puede ser: <i>ascii</i>, <i>7bit</i>, <i>iso</i>, <i>mac</i> siendo ascii el valor por defecto.</p>
</dd>
+<dt id="D---display-enc-ENCODING"><b>-D, --display-enc ENCODING</b></dt>
+<dd>
+
+<p>Set encoding of displayed text. Where ENCODING is one of: <i>ansi</i>, <i>unicode</i>, <i>utf8</i> with ansi being the default.</p>
+
+<p>This option is only available in dos2unix for Windows with Unicode file name support. This option has no effect on the actual file names read and written, only on how they are displayed.</p>
+
+<p>There are several methods for displaying text in a Windows console based on the encoding of the text. They all have their own advantages and disadvantages.</p>
+
+<dl>
+
+<dt id="ansi"><b>ansi</b></dt>
+<dd>
+
+<p>Dos2unix&#39;s default method is to use ANSI encoded text. The advantage is that it is backwards compatible. It works with raster and TrueType fonts. In some regions you may need to change the active DOS OEM code page to the Windows system ANSI code page using the <code>chcp</code> command, because dos2unix uses the Windows system code page.</p>
+
+<p>The disadvantage of ansi is that international file names with characters not inside the system default code page are not displayed properly. You will see a question mark, or a wrong symbol instead. When you don&#39;t work with foreign file names this method is OK.</p>
+
+</dd>
+<dt id="unicode"><b>unicode</b></dt>
+<dd>
+
+<p>The advantage of unicode (the Windows name for UTF-16) encoding is that text is usually properly displayed. There is no need to change the active code page. You may need to set the console&#39;s font to a TrueType font to have international characters displayed properly. When a character is not included in the TrueType font you usually see a small square, sometimes with a question mark in it.</p>
+
+<p>When you use the ConEmu console all text is displayed properly, because ConEmu automatically selects a good font.</p>
+
+<p>The disadvantage of unicode is that it is not compatible with ASCII. The output is not easy to handle when you redirect it to another program or a file. Redirection to a file does not give a correct UTF-16 file.</p>
+
+</dd>
+<dt id="utf8"><b>utf8</b></dt>
+<dd>
+
+<p>The advantage of utf8 is that it is compatible with ASCII and when you redirect it to a file you get a proper UTF-8 file. You need to set the console&#39;s font to a TrueType font. With a TrueType font the text is displayed similar as with the <code>unicode</code> encoding.</p>
+
+<p>The disadvantage is that when you use the default raster font all non-ASCII characters are displayed wrong. Not only unicode file names, but also translated messages become unreadable. On Windows configured for an East-Asian region you may see a lot of flickering of the console when the messages are displayed.</p>
+
+<p>In a ConEmu console the utf8 encoding method works well.</p>
+
+</dd>
+</dl>
+
+<p>The default encoding can be changed with environment variable DOS2UNIX_DISPLAY_ENC by setting it to <code>unicode</code> or <code>utf8</code>.</p>
+
+</dd>
<dt id="f---force"><b>-f, --force</b></dt>
<dd>
@@ -275,7 +320,7 @@
<p>Cuando el archivo de entrada es UTF-16 y se usa la opci&oacute;n <code>-u</code>, se escribir&aacute; un BOM UTF-16.</p>
-<p>No utilice esta opci&oacute;n cuando la codificaci&oacute;n de salida sea distinta de UTF-8 o UTF-16. V&eacute;ase tambi&eacute;n la secci&oacute;n UNICODE.</p>
+<p>No utilice esta opci&oacute;n cuando la codificaci&oacute;n de salida sea distinta de UTF-8, UTF-16 o GB18030. V&eacute;ase tambi&eacute;n la secci&oacute;n UNICODE.</p>
</dd>
<dt id="n---newfile-ARCHIVO_DE_ENTRADA-ARCHIVO_DE_SALIDA"><b>-n, --newfile ARCHIVO_DE_ENTRADA ARCHIVO_DE_SALIDA ...</b></dt>
@@ -486,6 +531,12 @@
<p>Dos2unix y unix2dos escriben siempre BOM cuando se usa la opci&oacute;n <code>-m</code>.</p>
+<h2 id="Unicode-file-names-on-Windows">Unicode file names on Windows</h2>
+
+<p>Dos2unix has optional support for reading and writing Unicode file names in the Windows Command Prompt. That means that dos2unix can open files that have characters in the name that are not part of the default system ANSI code page. To see if dos2unix for Windows was built with Unicode file name support type <code>dos2unix -V</code>.</p>
+
+<p>There are some issues with displaying Unicode file names in a Windows console. See option <code>-D</code>, <code>--display-enc</code>. The file names may be displayed wrongly in the console, but the files will be written with the correct name.</p>
+
<h2 id="Ejemplos-Unicode">Ejemplos Unicode</h2>
<p>Convertir de Windows UTF-16 (con una BOM) a Unix UTF-8:</p>
@@ -510,7 +561,7 @@
<p>GB18030 es totalmente compatible con Unicode y puede considerarse como formato de transformaci&oacute;n Unicode. Como ocurre con UTF-8, GB18030 es compatible con ASCII. GB18030 tambi&eacute;n es compatible con la p&aacute;gina de c&oacute;digos de Windows 936, tambi&eacute;n conocida como GBK.</p>
-<p>En Unix/Linux los archivos UTF-16 se convierten a GB18030 cuando la codificaci&oacute;n local se establece en GB18030. Tenga en cuenta que esto s&oacute;lo funcionar&aacute; si se establece la ubicaci&oacute;n en China. Por ejemplo en una configuraci&oacute;n local English British la conversi&oacute;n <code>en_GB.GB18030</code> de UTF-16 a GB18030 no funcionar&aacute;, pero en una configuraci&oacute;n local China <code>zh_CN.GB18030</code> s&iacute; lo har&aacute;.</p>
+<p>En Unix/Linux los archivos UTF-16 se convierten a GB18030 cuando la codificaci&oacute;n local se establece en GB18030. Tenga en cuenta que esto s&oacute;lo funcionar&aacute; si la configuraci&oacute;n local es soportada por el sistema. Utilice <code>locale -a</code> para obtener el listado de configuraciones regionales admitidas.</p>
<p>Use la opci&oacute;n <code>-ul</code> o <code>-ub</code> para convertir un archivo UTF-16 sin BOM.</p>
@@ -574,7 +625,11 @@
<p>Use dos2unix en combinaci&oacute;n con los comandos find(1) y xargs(1) para convertir recursivamente archivos de texto contenidos en un &aacute;rbol de directorios. Por ejemplo para convertir todos los archivos .txt en el &aacute;rbol de directorios debajo del directorio actual escriba:</p>
-<pre><code> find . -name *.txt |xargs dos2unix</code></pre>
+<pre><code> find . -name &#39;*.txt&#39; |xargs dos2unix</code></pre>
+
+<p>In a Windows Command Prompt the following command can be used:</p>
+
+<pre><code> for /R %G in (*.txt) do dos2unix &quot;%G&quot;</code></pre>
<h1 id="INTERNACIONALIZACIN">INTERNACIONALIZACI&Oacute;N</h1>