Source strings

24 Strings 100%
Browse Translate
716 Words 100%
4,996 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
24 716 4,996
All strings Browse Translate Zen
24 716 4,996
Read-only strings Browse Translate Zen
2 85 559
Strings with any failing checks Browse Translate Zen
2 85 559
Failing check: Multiple failing checks Browse Translate Zen

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.0
Last remote commit Add Portuguese (Brazil) BLFS 5a031b636f
Julien Lepiller authored 11 months ago
Last commit in Weblate Translated using Weblate (Greek) 56f209073a
User avatar Greekforce1821 authored a year ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-0/index/
File mask lfs/*/chapter01/askforhelp.po
Translation file Not available
Last change Sept. 1, 2023, 5:52 a.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,900,209
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
a month ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 24 716 4,996
Translated 100% 24 100% 716 100% 4,996
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 24 100% 716 100% 4,996
Failing checks 8% 2 11% 85 11% 559
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 24 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
MarAprMayJunJulAugSepOctNovDecJanFeb

Quick numbers

716
Hosted words
24
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Source string added
An excellent article about asking for help on the Internet is available online at <ulink url="http://catb.org/~esr/faqs/smart-questions.html"/>. Read this document, and follow the hints. Doing so will increase the likelihood of getting the help you need.
a year ago
User avatar None

Source string added
This is not enough information to diagnose the problem, because it only notes that something went wrong, not <emphasis>what</emphasis> went wrong. The entire section, as in the example above, is what should be saved because it includes the command that was executed and all the associated error messages.
a year ago
User avatar None

Source string added
<computeroutput>make [2]: *** [make] Error 1</computeroutput>
a year ago
User avatar None

Source string added
In this case, many people would just include the bottom section:
a year ago
User avatar None

Source string added
<computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\"
-DLIBDIR=\"/mnt/lfs/usr/lib\"
-DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
-g -O2 -c getopt1.c
gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o
expand.o file.o function.o getopt.o implicit.o job.o main.o
misc.o read.o remake.o rule.o signame.o variable.o vpath.o
default.o remote-stub.o version.o opt1.o
-lutil job.o: In function `load_too_high':
/lfs/tmp/make-3.79.1/job.c:1565: undefined reference
to `getloadavg'
collect2: ld returned 1 exit status
make[2]: *** [make] Error 1
make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
make: *** [all-recursive-am] Error 2</computeroutput>
a year ago
User avatar None

Source string added
Both the screen output and the contents of various files are useful in determining the cause of compilation problems. The screen output from the <command>configure</command> script and the <command>make</command> run can be helpful. It is not necessary to include the entire output, but do include all of the relevant information. Here is an example of the type of information to include from the <command>make</command> screen output.
a year ago
User avatar None

Source string added
Compilation Problems
a year ago
User avatar None

Source string added
If something goes wrong while running the <command>configure</command> script, review the <filename>config.log</filename> file. This file may contain errors encountered during <command>configure</command> which were not printed to the screen. Include the <emphasis>relevant</emphasis> lines if you need to ask for help.
a year ago
User avatar None

Source string added
Configure Script Problems
a year ago
User avatar None

Source string added
Deviating from this book does <emphasis>not</emphasis> mean that we will not help you. After all, LFS is about personal preference. Being up-front about any changes to the established procedure helps us evaluate and determine possible causes of your problem.
a year ago
Browse all translation changes