[Debian-handbook-translators] problem building PDF for id-ID
Andika Triwidada
andika at gmail.com
Fri Oct 30 01:25:58 GMT 2020
On Thu, Oct 29, 2020 at 9:03 PM Petter Reinholdtsen <pere at hungry.com> wrote:
>
> Build debian-handbook.pdf
> pdflatex failed
> te...:17367: TeX capacity exceeded, sorry [parameter stack size=10000].
> te...:17367: leading text: ...r,}\texttt{\ }\nolinkurl{workstation}/}
> Unexpected error occured
> Error: pdflatex compilation failed
>
Perfect! My bisection reach the same line containing 'workstation'. Thanks
Petter. It seems that some extra spaces matters.
Source string:
msgid "A system event is always signaled unless a rule in one of the
<filename>/etc/logcheck/ignore.d.{paranoid,server,workstation}/</filename>
directories states the event should be ignored. Of course, the only
directories taken into account are those corresponding to verbosity levels
equal or greater than the selected operation mode."
Error translation:
msgstr "Suatu kejadian sistem selalu diberi sinyal kecuali aturan di salah
satu dari direktori <filename>/etc/logcheck/ignore.d.{paranoid, server,
workstation}/</filename> menyatakan bahwa kejadian tersebut harus
diabaikan. Tentu saja, direktori yang diperhitungkan adalah hanya mereka
yang tingkat verbositasnya sama atau lebih dari mode operasi yang dipilih."
Ok translation:
msgstr "Suatu kejadian sistem selalu diberi sinyal kecuali aturan di salah
satu dari direktori
<filename>/etc/logcheck/ignore.d.{paranoid,server,workstation}/</filename>
menyatakan bahwa kejadian tersebut harus diabaikan. Tentu saja, direktori
yang diperhitungkan adalah hanya mereka yang tingkat verbositasnya sama
atau lebih dari mode operasi yang dipilih."
PDF builds fine now, only after turning some warning lines into fuzzy.
Merging id-ID/10_network-infrastructure.po >>
en-US/10_network-infrastructure.xml ->
tmp/id-ID/xml_tmp//10_network-infrastructure.xml
WARNING: Message missing from PO file, consider updating your POT and PO
files.
"\n<computeroutput>$ </computeroutput><userinput>vim
vars\n</userinput><computeroutput>$ </computeroutput><userinput>grep
EASYRSA vars\n</userinput><computeroutput>if [ -z \"$EASYRSA_CALLER\" ];
then\n# easyrsa. More specific variables for specific files (e.g.,
EASYRSA_SSL_CONF)\n#set_var EASYRSA \"${0%/*}\"\n#set_var EASYRSA_OPENSSL
\"openssl\"\n#set_var EASYRSA_OPENSSL \"C:/Program
Files/OpenSSL-Win32/bin/openssl.exe\"\n#set_var EASYRSA_PKI
\"$PWD/pki\"\n#set_var EASYRSA_DN \"cn_only\"\n#set_var EASYRSA_REQ_COUNTRY
\"FR\"\n#set_var EASYRSA_REQ_PROVINCE \"Loire\"\n#set_var EASYRSA_REQ_CITY
\"Saint-Étienne\"\n#set_var EASYRSA_REQ_ORG \"Falcot Corp\"\n#set_var
EASYRSA_REQ_EMAIL \"admin at falcot.com\"\n#set_var EASYRSA_REQ_OU
\"Certificate authority\"\n#set_var EASYRSA_KEY_SIZE 2048\n#set_var
EASYRSA_ALGO rsa\n#set_var EASYRSA_CURVE secp384r1\n#set_var
EASYRSA_CA_EXPIRE 3650\n#set_var EASYRSA_CERT_EXPIRE 1080\n#set_var
EASYRSA_CERT_RENEW 30\n#set_var EASYRSA_CRL_DAYS 180\n#set_var
EASYRSA_NS_SUPPORT \"no\"\n#set_var EASYRSA_NS_COMMENT \"Easy-RSA Generated
Certificate\"\n#set_var EASYRSA_TEMP_FILE
\"$EASYRSA_PKI/extensions.temp\"\n# when undefined here, default behaviour
is to look in $EASYRSA_PKI first, then\n# fallback to $EASYRSA for the
'x509-types' dir. You may override this\n#set_var EASYRSA_EXT_DIR
\"$EASYRSA/x509-types\"\n# EASYRSA_PKI or EASYRSA dir (in that order.) NOTE
that this file is Easy-RSA\n#set_var EASYRSA_SSL_CONF
\"$EASYRSA/openssl-easyrsa.cnf\"\n#set_var EASYRSA_REQ_CN
\"ChangeMe\"\n#set_var EASYRSA_DIGEST \"sha256\"\n#set_var EASYRSA_BATCH
\"\"\n$ </computeroutput>"
Merging id-ID/12_advanced-administration.po >>
en-US/12_advanced-administration.xml ->
tmp/id-ID/xml_tmp//12_advanced-administration.xml
WARNING: Message missing from PO file, consider updating your POT and PO
files.
"<computeroutput># </computeroutput><userinput>mdadm --create /dev/md0
--level=0 --raid-devices=2 /dev/sdb
/dev/sdc</userinput>\n<computeroutput>mdadm: Defaulting to version 1.2
metadata\nmdadm: array /dev/md0 started.\n#
</computeroutput><userinput>mdadm --query
/dev/md0</userinput>\n<computeroutput>/dev/md0: 8.00GiB raid0 2 devices, 0
spares. Use mdadm --detail for more detail.\n#
</computeroutput><userinput>mdadm --detail
/dev/md0</userinput>\n<computeroutput>/dev/md0:\n Version : 1.2\n
Creation Time : Tue Jun 25 08:47:49 2019\n Raid Level : raid0\n
Array Size : 8378368 (7.99 GiB 8.58 GB)\n Raid Devices : 2\n
Total Devices : 2\n Persistence : Superblock is persistent\n\n
Update Time : Tue Jun 25 08:47:49 2019\n State : clean \n
Active Devices : 2\n Working Devices : 2\n Failed Devices : 0\n
Spare Devices : 0\n\n Chunk Size : 512K\n\nConsistency Policy :
none\n\n Name : mirwiz:0 (local to host debian)\n
UUID : 146e104f:66ccc06d:71c262d7:9af1fbc7\n Events : 0\n\n
Number Major Minor RaidDevice State\n 0 8 32
0 active sync /dev/sdb\n 1 8 48 1
active sync /dev/sdc\n# </computeroutput><userinput>mkfs.ext4
/dev/md0</userinput>\n<computeroutput>mke2fs 1.44.5
(15-Dec-2018)\nDiscarding device blocks: done
\nCreating filesystem with 2094592 4k blocks and 524288 inodes\nFilesystem
UUID: 413c3dff-ab5e-44e7-ad34-cf1a029cfe98\nSuperblock backups stored on
blocks: \n 32768, 98304, 163840, 229376, 294912, 819200, 884736,
1605632\n\nAllocating group tables: done
\nWriting inode tables: done \nCreating journal
(16384 blocks): done\nWriting superblocks and filesystem accounting
information: done \n\n# </computeroutput><userinput>mkdir
/srv/raid-0</userinput>\n<computeroutput>#
</computeroutput><userinput>mount /dev/md0
/srv/raid-0</userinput>\n<computeroutput># </computeroutput><userinput>df
-h /srv/raid-0</userinput>\n<computeroutput>Filesystem Size Used
Avail Use% Mounted on\n/dev/md0 7.9G 36M 7.4G 1%
/srv/raid-0\n</computeroutput>"
WARNING: Message missing from PO file, consider updating your POT and PO
files.
"<computeroutput># </computeroutput><userinput>mkfs.ext4
/dev/vg_normal/lv_backups</userinput>\n<computeroutput>mke2fs 1.44.5
(15-Dec-2018)\nDiscarding device blocks: done
\nCreating filesystem with 3140608 4k blocks and 786432 inodes\nFilesystem
UUID: b9e6ed2f-cb37-43e9-87d8-e77568446225\nSuperblock backups stored on
blocks: \n 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208\n\nAllocating group tables: done
\nWriting inode tables: done \nCreating journal
(16384 blocks): done\nWriting superblocks and filesystem accounting
information: done \n\n# </computeroutput><userinput>mkdir
/srv/backups</userinput>\n<computeroutput>#
</computeroutput><userinput>mount /dev/vg_normal/lv_backups
/srv/backups</userinput>\n<computeroutput># </computeroutput><userinput>df
-h /srv/backups</userinput>\n<computeroutput>Filesystem
Size Used Avail Use% Mounted on\n/dev/mapper/vg_normal-lv_backups 12G
41M 12G 1% /srv/backups\n#
</computeroutput><userinput>[...]</userinput>\n<computeroutput>[...]\n#
</computeroutput><userinput>cat
/etc/fstab</userinput>\n<computeroutput>[...]\n/dev/vg_critical/lv_base
/srv/base ext4 defaults 0 2\n/dev/vg_critical/lv_files /srv/files
ext4 defaults 0 2\n/dev/vg_normal/lv_backups /srv/backups ext4
defaults 0 2</computeroutput>"
WARNING: Message missing from PO file, consider updating your POT and PO
files.
"<computeroutput># </computeroutput><userinput>xl
list</userinput>\n<computeroutput>Name
ID Mem VCPUs State Time(s)\nDomain-0
0 1894 2 r----- 63.5\n# </computeroutput><userinput>xl
create /etc/xen/testxen.cfg</userinput>\n<computeroutput>Parsing config
from /etc/xen/testxen.cfg\n# </computeroutput><userinput>xl
list</userinput>\n<computeroutput>Name
ID Mem VCPUs State Time(s)\nDomain-0
0 1505 2 r----- 100.0\ntestxen
13 1024 0 --p--- 0.0</computeroutput>"
WARNING: Message missing from PO file, consider updating your POT and PO
files.
"<computeroutput>root at mirwiz:~# </computeroutput><userinput>lxc-console -n
testlxc\n</userinput><computeroutput>Debian GNU/Linux 9 testlxc console
\n\ntestlxc login:
</computeroutput><userinput>root</userinput><computeroutput>\nPassword:
\nLinux testlxc 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19)
x86_64\n\nThe programs included with the Debian GNU/Linux system are free
software;\nthe exact distribution terms for each program are described in
the\nindividual files in /usr/share/doc/*/copyright.\n\nDebian GNU/Linux
comes with ABSOLUTELY NO WARRANTY, to the extent\npermitted by applicable
law.\nroot at testlxc:~# </computeroutput><userinput>ps
auxwf</userinput>\n<computeroutput>USER PID %CPU %MEM VSZ RSS
TTY STAT START TIME COMMAND\nroot 1 0.0 0.2 56736 6608 ?
Ss 09:28 0:00 /sbin/init\nroot 32 0.0 0.1 46096 4680
? Ss 09:28 0:00 /lib/systemd/systemd-journald\nroot 75
0.0 0.1 67068 3328 console Ss 09:28 0:00 /bin/login --\nroot
82 0.0 0.1 19812 3664 console S 09:30 0:00 \\_ -bash\nroot
88 0.0 0.1 38308 3176 console R+ 09:31 0:00 \\_ ps
auxwf\nroot 76 0.0 0.1 69956 5636 ? Ss 09:28 0:00
/usr/sbin/sshd -D\nroot at testlxc:~# </computeroutput>"
Merging id-ID/14_security.po >> en-US/14_security.xml ->
tmp/id-ID/xml_tmp//14_security.xml
WARNING: Message missing from PO file, consider updating your POT and PO
files.
"There are two types of chains: <emphasis>base chains</emphasis> and
<emphasis>regular chains</emphasis>. A base chain is an entry point for
packets from the networking stack. Base chains are registered into the
Netfilter hooks, i.e. they see packets flowing through the TCP/IP stack. On
the other hand a regular chain is not attached to any hook so it does not
see any traffic. But it may be used as a jump target for better
organization of the rules."
WARNING: Message missing from PO file, consider updating your POT and PO
files.
"<computeroutput># </computeroutput><userinput>iptables-save >
iptables-ruleset.txt\n</userinput><computeroutput>#
</computeroutput><userinput>iptables-restore-translate -f
iptables-ruleset.txt\n</userinput><computeroutput>\n# Translated by
iptables-restore-translate v1.8.2 on Thu Jul 18 10:39:33 2019\nadd table ip
filter\nadd chain ip filter INPUT { type filter hook input priority 0;
policy accept; }\nadd chain ip filter FORWARD { type filter hook forward
priority 0; policy drop; }\nadd chain ip filter OUTPUT { type filter hook
output priority 0; policy accept; }\nadd chain ip filter DOCKER\nadd chain
ip filter DOCKER-ISOLATION-STAGE-1\nadd chain ip filter
DOCKER-ISOLATION-STAGE-2\nadd chain ip filter DOCKER-USER\nadd rule ip
filter FORWARD counter jump DOCKER-USER\nadd rule ip filter FORWARD counter
jump DOCKER-ISOLATION-STAGE-1\nadd rule ip filter FORWARD oifname
\"docker0\" ct state related,established counter accept\nadd rule ip filter
FORWARD oifname \"docker0\" counter jump DOCKER\nadd rule ip filter FORWARD
iifname \"docker0\" oifname != \"docker0\" counter accept\nadd rule ip
filter FORWARD iifname \"docker0\" oifname \"docker0\" counter accept\nadd
rule ip filter DOCKER-ISOLATION-STAGE-1 iifname \"docker0\" oifname !=
\"docker0\" counter jump DOCKER-ISOLATION-STAGE-2\nadd rule ip filter
DOCKER-ISOLATION-STAGE-1 counter return\nadd rule ip filter
DOCKER-ISOLATION-STAGE-2 oifname \"docker0\" counter drop\nadd rule ip
filter DOCKER-ISOLATION-STAGE-2 counter return\nadd rule ip filter
DOCKER-USER counter return\nadd table ip nat\nadd chain ip nat PREROUTING {
type nat hook prerouting priority -100; policy accept; }\nadd chain ip nat
INPUT { type nat hook input priority 100; policy accept; }\nadd chain ip
nat POSTROUTING { type nat hook postrouting priority 100; policy accept;
}\nadd chain ip nat OUTPUT { type nat hook output priority -100; policy
accept; }\nadd chain ip nat DOCKER\nadd rule ip nat PREROUTING fib daddr
type local counter jump DOCKER\nadd rule ip nat POSTROUTING oifname !=
\"docker0\" ip saddr 172.17.0.0/16 counter masquerade\nadd rule ip nat
OUTPUT ip daddr != 127.0.0.0/8 fib daddr type local counter jump
DOCKER\nadd rule ip nat DOCKER iifname \"docker0\" counter return\n#
Completed on Thu Jul 18 10:39:33 2019\n#
</computeroutput><userinput>iptables-restore-translate -f
iptables-ruleset.txt > ruleset.nft\n</userinput><computeroutput>#
</computeroutput><userinput>nft -f
ruleset.nft\n</userinput><computeroutput># </computeroutput><userinput>nft
list ruleset</userinput><computeroutput>\ntable ip filter {\n chain INPUT
{\n type filter hook input priority 0; policy accept;\n }\n\n chain FORWARD
{\n type filter hook forward priority 0; policy drop;\n counter packets 0
bytes 0 jump DOCKER-USER\n counter packets 0 bytes 0 jump
DOCKER-ISOLATION-STAGE-1\n oifname \"docker0\" ct state related,established
counter packets 0 bytes 0 accept\n oifname \"docker0\" counter packets 0
bytes 0 jump DOCKER\n iifname \"docker0\" oifname != \"docker0\" counter
packets 0 bytes 0 accept\n iifname \"docker0\" oifname \"docker0\" counter
packets 0 bytes 0 accept\n }\n\n chain OUTPUT {\n type filter hook output
priority 0; policy accept;\n }\n\n chain DOCKER {\n }\n\n chain
DOCKER-ISOLATION-STAGE-1 {\n iifname \"docker0\" oifname != \"docker0\"
counter packets 0 bytes 0 jump DOCKER-ISOLATION-STAGE-2\n counter packets 0
bytes 0 return\n }\n\n chain DOCKER-ISOLATION-STAGE-2 {\n oifname
\"docker0\" counter packets 0 bytes 0 drop\n counter packets 0 bytes 0
return\n }\n\n chain DOCKER-USER {\n counter packets 0 bytes 0 return\n
}\n}\ntable ip nat {\n chain PREROUTING {\n type nat hook prerouting
priority -100; policy accept;\n fib daddr type local counter packets 0
bytes 0 jump DOCKER\n }\n\n chain INPUT {\n type nat hook input priority
100; policy accept;\n }\n\n chain POSTROUTING {\n type nat hook postrouting
priority 100; policy accept;\n oifname != \"docker0\" ip saddr 172.17.0.0/16
counter packets 0 bytes 0 masquerade\n }\n\n chain OUTPUT {\n type nat hook
output priority -100; policy accept;\n ip daddr != 127.0.0.0/8 fib daddr
type local counter packets 0 bytes 0 jump DOCKER\n }\n\n chain DOCKER {\n
iifname \"docker0\" counter packets 0 bytes 0 return\n }\n}\ntable ip
mangle {\n chain PREROUTING {\n type filter hook prerouting priority -150;
policy accept;\n }\n\n chain INPUT {\n type filter hook input priority
-150; policy accept;\n }\n\n chain FORWARD {\n type filter hook forward
priority -150; policy accept;\n }\n\n chain OUTPUT {\n type route hook
output priority -150; policy accept;\n }\n\n chain POSTROUTING {\n type
filter hook postrouting priority -150; policy accept;\n
}\n}\n</computeroutput>"
Merging id-ID/90_derivative-distributions.po >>
en-US/90_derivative-distributions.xml ->
tmp/id-ID/xml_tmp//90_derivative-distributions.xml
WARNING: Message missing from PO file, consider updating your POT and PO
files.
"Linux Mint is a (partly) community-maintained distribution, supported by
donations and advertisements. Their flagship product is based on Ubuntu,
but they also provide a “Linux Mint Debian Edition” (LMDE), which is based
on Debian Stable with a few backports. LMDE is available for both 32 and
64-bit. In both cases, the initial installation involves booting a live DVD
or a live USB storage device."
Raphael, any idea why there are those 'missing from PO file' warnings?
Regards,
Andika
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-handbook-translators/attachments/20201030/90046856/attachment-0001.html>
More information about the Debian-handbook-translators
mailing list