2. Beyond Linux From Scratch 11.3
3. introduction_important_locale-issues
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:>=translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	Breaks Multibyte Characters	Casse les caractères multi-octets
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	Breaks Multibyte Characters	Quebra Caracteres Multi Byte
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	The Program Breaks Multibyte Characters or Doesn't Count Character Cells Correctly	The Program Breaks Multibyte Characters or Doesn't Count Character Cells Correctly
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	The Program Breaks Multibyte Characters or Doesn't Count Character Cells Correctly	Le programme casse les caractères multi-octets ou ne compte pas bien les cellules de caractères
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	The Program Breaks Multibyte Characters or Doesn't Count Character Cells Correctly	O Aplicativo Quebra Caracteres Multi Byte ou Não Conta Células de Caracteres Corretamente
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	Severity: High or critical	Severity: High or critical
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	Severity: High or critical	Sévérité : haute ou critique
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	Severity: High or critical	Gravidade: Alta ou crítica
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	Many programs were written in an older era where multibyte locales were not common. Such programs assume that C "char" data type, which is one byte, can be used to store single characters. Further, they assume that any sequence of characters is a valid string and that every character occupies a single character cell. Such assumptions completely break in UTF-8 locales. The visible manifestation is that the program truncates strings prematurely (i.e., at 80 bytes instead of 80 characters). Terminal-based programs don't place the cursor correctly on the screen, don't react to the "Backspace" key by erasing one character, and leave junk characters around when updating the screen, usually turning the screen into a complete mess.	Many programs were written in an older era where multibyte locales were not common. Such programs assume that C "char" data type, which is one byte, can be used to store single characters. Further, they assume that any sequence of characters is a valid string and that every character occupies a single character cell. Such assumptions completely break in UTF-8 locales. The visible manifestation is that the program truncates strings prematurely (i.e., at 80 bytes instead of 80 characters). Terminal-based programs don't place the cursor correctly on the screen, don't react to the "Backspace" key by erasing one character, and leave junk characters around when updating the screen, usually turning the screen into a complete mess.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	Many programs were written in an older era where multibyte locales were not common. Such programs assume that C "char" data type, which is one byte, can be used to store single characters. Further, they assume that any sequence of characters is a valid string and that every character occupies a single character cell. Such assumptions completely break in UTF-8 locales. The visible manifestation is that the program truncates strings prematurely (i.e., at 80 bytes instead of 80 characters). Terminal-based programs don't place the cursor correctly on the screen, don't react to the "Backspace" key by erasing one character, and leave junk characters around when updating the screen, usually turning the screen into a complete mess.	De nombreux programmes ont été écrits à une époque plus ancienne où les locales multi-octets n'étaient pas courantes. De tels programmes supposent que les types de données C "char", qui sont un octet, peuvent être utilisés pour stocker des caractères uniques. De plus, ils supposent que n'importe quelle séquence de caractères est une chaîne valide et que chaque caractère occupe une seule cellule de caractère. De telles suppositions échouent complètement dans les locales UTF-8. La conséquence évidente est que le programme tronque les chaînes de façon prématurée (c'est-à-dire aux octets 80 au lieu des caractères 80). Les programmes basés sur le terminal ne placent pas bien le curseur à l'écran, ne réagissent pas à la touche « Effacement » en effaçant un caractère et laissent les mauvais caractères affichés lors du rafraîchissement de l'écran, transformant généralement l'écran en désordre complet.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	Many programs were written in an older era where multibyte locales were not common. Such programs assume that C "char" data type, which is one byte, can be used to store single characters. Further, they assume that any sequence of characters is a valid string and that every character occupies a single character cell. Such assumptions completely break in UTF-8 locales. The visible manifestation is that the program truncates strings prematurely (i.e., at 80 bytes instead of 80 characters). Terminal-based programs don't place the cursor correctly on the screen, don't react to the "Backspace" key by erasing one character, and leave junk characters around when updating the screen, usually turning the screen into a complete mess.	Muitos aplicativos foram escritos em uma era mais antiga onde locales multi Byte não eram comuns. Tais aplicativos assumem que o tipo de dados "char" do C, que é um Byte, pode ser usado para armazenar caracteres únicos. Além disso, eles assumem que qualquer sequência de caracteres é uma sequência de caracteres válida e que cada caractere ocupa uma célula única de caractere. Tais presunções quebram completamente em locales UTF-8. A manifestação visível é a de que o aplicativo trunca sequências de caracteres prematuramente (isto é, em oitenta (80) Bytes, em vez de oitenta (80) caracteres). Os aplicativos baseados em terminal não colocam o cursor corretamente na tela; não reagem à tecla "Backspace" apagando um caractere; e deixam caracteres inúteis ao atualizar a tela, geralmente transformando a tela em uma completa bagunça.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	Fixing this kind of problems is a tedious task from a programmer's point of view, like all other cases of retrofitting new concepts into the old flawed design. In this case, one has to redesign all data structures in order to accommodate to the fact that a complete character may span a variable number of "char"s (or switch to wchar_t and convert as needed). Also, for every call to the "strlen" and similar functions, find out whether a number of bytes, a number of characters, or the width of the string was really meant. Sometimes it is faster to write a program with the same functionality from scratch.	Fixing this kind of problems is a tedious task from a programmer's point of view, like all other cases of retrofitting new concepts into the old flawed design. In this case, one has to redesign all data structures in order to accommodate to the fact that a complete character may span a variable number of "char"s (or switch to wchar_t and convert as needed). Also, for every call to the "strlen" and similar functions, find out whether a number of bytes, a number of characters, or the width of the string was really meant. Sometimes it is faster to write a program with the same functionality from scratch.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	Fixing this kind of problems is a tedious task from a programmer's point of view, like all other cases of retrofitting new concepts into the old flawed design. In this case, one has to redesign all data structures in order to accommodate to the fact that a complete character may span a variable number of "char"s (or switch to wchar_t and convert as needed). Also, for every call to the "strlen" and similar functions, find out whether a number of bytes, a number of characters, or the width of the string was really meant. Sometimes it is faster to write a program with the same functionality from scratch.	La correction de ce type de problème est une tâche pénible du point de vue d'un programmeur, comme tout cas de modernisation d'un design défectueux par de nouveaux concepts. Dans ce cas, il faut concevoir de nouveau toutes les structures de données pour s’accommoder du fait qu'un caractère complet peut s'étendre sur un nombre variable de « char » (ou basculer sur wchar_t et convertir au besoin). Pour chaque utilisation des fonctions « strlen » et équivalent, il faut aussi trouver ce que veut vraiment dire un nombre d'octets, de caractères ou la largeur de la chaîne. Il est parfois plus rapide d'écrire un programme ayant la même fonctionnalité en partant de zéro.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	Fixing this kind of problems is a tedious task from a programmer's point of view, like all other cases of retrofitting new concepts into the old flawed design. In this case, one has to redesign all data structures in order to accommodate to the fact that a complete character may span a variable number of "char"s (or switch to wchar_t and convert as needed). Also, for every call to the "strlen" and similar functions, find out whether a number of bytes, a number of characters, or the width of the string was really meant. Sometimes it is faster to write a program with the same functionality from scratch.	Corrigir esses tipos de problemas é uma tarefa tediosa, a partir de um ponto de vista do(a) programador(a), semelhante a todos os outros casos de retro adequar conceitos novos no projeto falho antigo. Nesse caso, deve-se reprojetar todas as estruturas de dados para a finalidade de acomodar ao fato de que um caractere completo possivelmente abranja um número variável de "char"s (ou alternar para wchar_t e converter conforme necessário). Também, para cada chamada à "strlen" e funções similares, descobrir se um número de Bytes; um número de caracteres; ou a largura da sequência de caracteres realmente foi declarada. Ocasionalmente, é mais rápido escrever um aplicativo com a mesma funcionalidade desde o zero.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	Among BLFS packages, this problem applies to <xref linkend="xine-ui"/> and all the shells.	Among BLFS packages, this problem applies to <xref linkend="xine-ui"/> and all the shells.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	Among BLFS packages, this problem applies to <xref linkend="xine-ui"/> and all the shells.	Au sein des paquets de BLFS, ce problème s'applique à<xref linkend="xine-ui"/> et tous les shells.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	Among BLFS packages, this problem applies to <xref linkend="xine-ui"/> and all the shells.	Entre os pacotes do BLFS, esse problema se aplica ao <xref linkend="xine-ui"/> e a todos os shells.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	Incorrect Manual Page Encoding	Incorrect Manual Page Encoding
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	Incorrect Manual Page Encoding	L'encodage des pages de manuel est incorrect
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	Incorrect Manual Page Encoding	Codificação Incorreta da Página de Manual
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	The Package Installs Manual Pages in Incorrect or Non-Displayable Encoding	The Package Installs Manual Pages in Incorrect or Non-Displayable Encoding
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	The Package Installs Manual Pages in Incorrect or Non-Displayable Encoding	Le paquet installe des pages de manuel dans un encodage incorrect ou non affichable
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	The Package Installs Manual Pages in Incorrect or Non-Displayable Encoding	O Pacote Instala as Páginas de Manual em Codificação Incorreta ou Não Exibível
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	Severity: Low	Severity: Low
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	Severity: Low	Sévérité&nbsp;: basse
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	Severity: Low	Gravidade: Baixa
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	LFS expects that manual pages are in the language-specific (usually 8-bit) encoding, as specified on the <ulink url="&lfs-root;/chapter08/man-db.html">LFS Man DB page</ulink>. However, some packages install translated manual pages in UTF-8 encoding (e.g., Shadow, already dealt with), or manual pages in languages not in the table. Not all BLFS packages have been audited for conformance with the requirements put in LFS (the large majority have been checked, and fixes placed in the book for packages known to install non-conforming manual pages). If you find a manual page installed by any of BLFS packages that is obviously in the wrong encoding, please remove or convert it as needed, and report this to BLFS team as a bug.	LFS expects that manual pages are in the language-specific (usually 8-bit) encoding, as specified on the <ulink url="&lfs-root;/chapter08/man-db.html">LFS Man DB page</ulink>. However, some packages install translated manual pages in UTF-8 encoding (e.g., Shadow, already dealt with), or manual pages in languages not in the table. Not all BLFS packages have been audited for conformance with the requirements put in LFS (the large majority have been checked, and fixes placed in the book for packages known to install non-conforming manual pages). If you find a manual page installed by any of BLFS packages that is obviously in the wrong encoding, please remove or convert it as needed, and report this to BLFS team as a bug.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	LFS expects that manual pages are in the language-specific (usually 8-bit) encoding, as specified on the <ulink url="&lfs-root;/chapter08/man-db.html">LFS Man DB page</ulink>. However, some packages install translated manual pages in UTF-8 encoding (e.g., Shadow, already dealt with), or manual pages in languages not in the table. Not all BLFS packages have been audited for conformance with the requirements put in LFS (the large majority have been checked, and fixes placed in the book for packages known to install non-conforming manual pages). If you find a manual page installed by any of BLFS packages that is obviously in the wrong encoding, please remove or convert it as needed, and report this to BLFS team as a bug.	LFS s'attend à ce que les pages de manuel soient dans l'encodage spécifique à la langue (en général 8-bit), comme indiqué sur la <ulink url="&lfs-root;/chapter08/man-db.html">page Man DB de LFS</ulink>. Cependant, certains paquets installent des pages de manuel traduites dans l'encodage UTF-8 (comme avec Shadow qui a déjà été traité), ou des pages de manuel dans des langues non présentes dans la table. Tous les paquets BLFS n'ont pas fait l'objet d'une évaluation de leur respect des exigences de LFS (la grande majorité a été vérifiée et des corrections ont été mises dans le livre pour les paquets connus pour installer des pages de manuel non conformes). Si vous trouvez une page de manuel installée par un paquet BLFS qui est dans un mauvais encodage, merci de la supprimer ou de la convertir selon vos besoins et de le signaler à l'équipe BLFS comme un bogue.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	LFS expects that manual pages are in the language-specific (usually 8-bit) encoding, as specified on the <ulink url="&lfs-root;/chapter08/man-db.html">LFS Man DB page</ulink>. However, some packages install translated manual pages in UTF-8 encoding (e.g., Shadow, already dealt with), or manual pages in languages not in the table. Not all BLFS packages have been audited for conformance with the requirements put in LFS (the large majority have been checked, and fixes placed in the book for packages known to install non-conforming manual pages). If you find a manual page installed by any of BLFS packages that is obviously in the wrong encoding, please remove or convert it as needed, and report this to BLFS team as a bug.	O LFS espera que as páginas de manual estejam na codificação específica para o idioma (geralmente oito (08) bits), conforme especificado na <ulink url="&lfs-root;/chapter08/man-db.html">página Man DB do LFS</ulink>. Entretanto, alguns pacotes instalam as páginas de manual traduzidas na codificação UTF-8 (por exemplo, o Shadow já tratou); ou páginas de manual em idiomas que não estão na tabela. Nem todos os pacotes do BLFS foram auditados para conformidade com as exigências colocadas no LFS (a quase totalidade foi verificada e correções colocadas no livro para os pacotes conhecidos por instalar páginas de manual não conformes). Se você encontrar uma página de manual instalada por quaisquer dos pacotes do BLFS que obviamente esteja na codificação errada, [então], por favor, remova-a ou converta-a conforme necessário e informe isso para a equipe do BLFS como um defeito.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	<literal>#!/bin/sh # Begin checkman.sh # Usage: find /usr/share/man -type f | xargs checkman.sh for a in "$@" do # echo "Checking $a..." # Pure-ASCII manual page (possibly except comments) is OK grep -v '.\\"' "$a" | iconv -f US-ASCII -t US-ASCII >/dev/null 2>&amp;1 \ &amp;&amp; continue # Non-UTF-8 manual page is OK iconv -f UTF-8 -t UTF-8 "$a" >/dev/null 2>&amp;1 || continue # Found a UTF-8 manual page, bad. echo "UTF-8 manual page: $a" >&amp;2 done # End checkman.sh </literal>	<literal>#!/bin/sh # Begin checkman.sh # Usage: find /usr/share/man -type f | xargs checkman.sh for a in "$@" do # echo "Checking $a..." # Pure-ASCII manual page (possibly except comments) is OK grep -v '.\\"' "$a" | iconv -f US-ASCII -t US-ASCII >/dev/null 2>&amp;1 \ &amp;&amp; continue # Non-UTF-8 manual page is OK iconv -f UTF-8 -t UTF-8 "$a" >/dev/null 2>&amp;1 || continue # Found a UTF-8 manual page, bad. echo "UTF-8 manual page: $a" >&amp;2 done # End checkman.sh </literal>
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	<literal>#!/bin/sh # Begin checkman.sh # Usage: find /usr/share/man -type f | xargs checkman.sh for a in "$@" do # echo "Checking $a..." # Pure-ASCII manual page (possibly except comments) is OK grep -v '.\\"' "$a" | iconv -f US-ASCII -t US-ASCII >/dev/null 2>&amp;1 \ &amp;&amp; continue # Non-UTF-8 manual page is OK iconv -f UTF-8 -t UTF-8 "$a" >/dev/null 2>&amp;1 || continue # Found a UTF-8 manual page, bad. echo "UTF-8 manual page: $a" >&amp;2 done # End checkman.sh </literal>	<literal>#!/bin/sh # Begin checkman.sh # Usage: find /usr/share/man -type f | xargs checkman.sh for a in "$@" do # echo "Checking $a..." # Pure-ASCII manual page (possibly except comments) is OK grep -v '.\\"' "$a" | iconv -f US-ASCII -t US-ASCII >/dev/null 2>&amp;1 \ &amp;&amp; continue # Non-UTF-8 manual page is OK iconv -f UTF-8 -t UTF-8 "$a" >/dev/null 2>&amp;1 || continue # Found a UTF-8 manual page, bad. echo "UTF-8 manual page: $a" >&amp;2 done # End checkman.sh </literal>
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	<literal>#!/bin/sh # Begin checkman.sh # Usage: find /usr/share/man -type f | xargs checkman.sh for a in "$@" do # echo "Checking $a..." # Pure-ASCII manual page (possibly except comments) is OK grep -v '.\\"' "$a" | iconv -f US-ASCII -t US-ASCII >/dev/null 2>&amp;1 \ &amp;&amp; continue # Non-UTF-8 manual page is OK iconv -f UTF-8 -t UTF-8 "$a" >/dev/null 2>&amp;1 || continue # Found a UTF-8 manual page, bad. echo "UTF-8 manual page: $a" >&amp;2 done # End checkman.sh </literal>	<literal>#!/bin/sh # Início checkman.sh # Uso: find /usr/share/man -type f | xargs checkman.sh for a in "$@" do # echo "Verificando $a..." # Página de Manual ASCII puro (possivelmente exceto comentários) está OK grep -v '.\\"' "$a" | iconv -f US-ASCII -t US-ASCII >/dev/null 2>&amp;1 \ &amp;&amp; continue # Página de Manual não UTF-8 está OK iconv -f UTF-8 -t UTF-8 "$a" >/dev/null 2>&amp;1 || continue # Encontrada uma Página de Manual UTF-8, ruim. echo "Página de Manual UTF-8: $a" >&amp;2 done # Fim checkman.sh </literal>
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	You can easily check your system for any non-conforming manual pages by copying the following short shell script to some accessible location, <placeholder type="screen" id="0"/> and then issuing the following command (modify the command below if the <command>checkman.sh</command> script is not in your <envar>PATH</envar> environment variable):	You can easily check your system for any non-conforming manual pages by copying the following short shell script to some accessible location, <placeholder type="screen" id="0"/> and then issuing the following command (modify the command below if the <command>checkman.sh</command> script is not in your <envar>PATH</envar> environment variable):
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	You can easily check your system for any non-conforming manual pages by copying the following short shell script to some accessible location, <placeholder type="screen" id="0"/> and then issuing the following command (modify the command below if the <command>checkman.sh</command> script is not in your <envar>PATH</envar> environment variable):	Vous pouvez facilement vérifier le respect par toutes les pages de manuel de votre système en copiant le petit script shell suivant à un endroit accessible, <placeholder type="screen" id="0"/> puis en exécutant la commande suivante (modifiez la commande ci-dessous si le script <command>checkman.sh</command> n'est pas dans votre variable d'environnement <envar>PATH</envar>)&nbsp;:
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	You can easily check your system for any non-conforming manual pages by copying the following short shell script to some accessible location, <placeholder type="screen" id="0"/> and then issuing the following command (modify the command below if the <command>checkman.sh</command> script is not in your <envar>PATH</envar> environment variable):	Você pode verificar facilmente o seu sistema para quaisquer páginas de manual não conformes, copiando o seguinte script curto de shell para algum local acessível, <placeholder type="screen" id="0"/> e, então, emitindo o seguinte comando (modifique o comando abaixo se o script <command>checkman.sh</command> não estiver na sua variável de ambiente <envar>PATH</envar>):
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	<userinput>find /usr/share/man -type f | xargs checkman.sh</userinput>	<userinput>find /usr/share/man -type f | xargs checkman.sh</userinput>
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	<userinput>find /usr/share/man -type f | xargs checkman.sh</userinput>	<userinput>find /usr/share/man -type f | xargs checkman.sh</userinput>
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	<userinput>find /usr/share/man -type f | xargs checkman.sh</userinput>	<userinput>find /usr/share/man -type f | xargs checkman.sh</userinput>
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — English	Note that if you have manual pages installed in any location other than <filename class='directory'>/usr/share/man</filename> (e.g., <filename class='directory'>/usr/local/share/man</filename>), you must modify the above command to include this additional location.	Note that if you have manual pages installed in any location other than <filename class='directory'>/usr/share/man</filename> (e.g., <filename class='directory'>/usr/local/share/man</filename>), you must modify the above command to include this additional location.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — French	Note that if you have manual pages installed in any location other than <filename class='directory'>/usr/share/man</filename> (e.g., <filename class='directory'>/usr/local/share/man</filename>), you must modify the above command to include this additional location.	Remarquez cependant que si vous avez des pages de manuel installées ailleurs que dans <filename class='directory'>/usr/share/man</filename> (comme dans <filename class='directory'>/usr/local/share/man</filename>), vous devez modifier la commande ci-dessus pour inclure cet emplacement supplémentaire.
	Beyond Linux From Scratch 11.3/introduction_important_locale-issues — Portuguese (Brazil)	Note that if you have manual pages installed in any location other than <filename class='directory'>/usr/share/man</filename> (e.g., <filename class='directory'>/usr/local/share/man</filename>), you must modify the above command to include this additional location.	Observe que, se você tiver páginas de manual instaladas em qualquer outro local que <filename class='directory'>/usr/share/man</filename> (por exemplo, <filename class='directory'>/usr/local/share/man</filename>), [então] você precisa modificar o comando acima para incluir esse local adicional.

• 2 / 2
  / 2