Source strings

47 Strings 100%
Browse Translate
1,537 Words 100%
10,291 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
47 1,537 10,291
All strings Browse Translate Zen
47 1,537 10,291
Read-only strings Browse Translate Zen
1 80 520
Strings with any failing checks Browse Translate Zen
1 80 520
Failing check: Ellipsis Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
x_lib_glslang 0 0 0 0 1 0 0
x_lib_cairo 0 0 0 0 1 0 0
postlfs_virtualization_qemu-bridge-kernel 0 0 0 0 0 0 0
x_lib_at-spi2-core 0 0 0 0 0 0 0
x_lib_kimageannotator 0 0 0 0 1 0 0
x_lib_qt5-components 0 0 0 0 1 0 0
x_lib_gtksourceview 0 0 0 0 0 0 0
x_lib_tepl 0 0 0 0 1 0 0
x_lib_qt5-alternate 0 0 0 0 0 0 0
xfce_xfce 0 0 0 0 0 0 0
Browse all components

Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch 12.1
Last remote commit Add pt_BR translation e751a3b16e
Julien Lepiller authored yesterday
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-1/index/
File mask blfs/*/introduction/important/locale-issues.po
Translation file Not available
Last change None
Last author None
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 47 1,537 10,291
Translated 100% 47 100% 1,537 100% 10,291
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 47 100% 1,537 100% 10,291
Failing checks 2% 1 5% 80 5% 520
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 47 changes 0 changes 0 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

1,537
Hosted words
47
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
+100%
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. 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.
2 months ago
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. English
<userinput>find /usr/share/man -type f | xargs checkman.sh</userinput>
2 months ago
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. 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):
2 months ago
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. 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>
2 months ago
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. 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.
2 months ago
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. English
Severity: Low
2 months ago
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. English
The Package Installs Manual Pages in Incorrect or Non-Displayable Encoding
2 months ago
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. English
Incorrect Manual Page Encoding
2 months ago
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. English
Among BLFS packages, this problem applies to <xref linkend="xine-ui"/> and all the shells.
2 months ago
User avatar None

Source string added

  1. Beyond Linux From Scratch 12.1
  2. introduction_important_locale-issues
  3. 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.
2 months ago
Browse all translation changes