mquinson / po4a Goto Github PK

"The amount of entries differ between files: Y is not X"

msgid ""
"How to compile Bash for more than one kind of system from the same source "
"tree."
msgstr ""
"C@'omo compilar Bash para m@'as de un tipo de sistema desde el mismo @'arbol "
"de fuentes."

For the addenda to work, it is better to have short lines (so that the 
translator can choose between which ones to put there addenda). 
The Sgml module does so since the bug #263300, in Debian.

the po-debiandoc tool writes the PO-file header in the generated
SGML file (enclosed in , of course), so that these
useful informations are contained in this file.
It would be really nice if po4a-translate did something similar.

(Reported by Denis on the mailing list)

1107d64
Invalid po file doc/src/some/file.po:
'LC_ALL' is not recognized as an internal or external command,
operable program or batch file.

@url{https://example.org,
example}

@itemize
@item See @url{https://example.org,
example}
@end itemize

@itemize
@item See @url{https://example.org,
@c ===========================================================================
@c
@c This file was generated with po4a. Translate the source file.
@c
@c ===========================================================================
@c Adapted from http://www.gnu.org/philosophy/philosophy.html.
@c See <https://lists.gnu.org/archive/html/guix-devel/2016-01/msg00425.html>,
@c for a discussion of what follows.
@c See <https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html>.
@c TODO: It would be good with badges on the website that tracks these
@c branches.  Or maybe even a status page.
@c Debbugs bug: https://debbugs.gnu.org/db/15/15361.html
example} @end itemize @example git clone
https://git.savannah.gnu.org/git/guix.git @end example When building Guix
from a checkout, the following packages are required in addition to those
mentioned in the installation instructions (@pxref{Prérequis}).  @itemize

If you translate a PO file into some language
using iso8859-1, but forget to precise the charset in the
header of the PO file, and don't give the charset to
po4a-update either, then po4a-update proceeds to remove all
accentuated characters from the file.

I am not sure what the best way to handle this would be;
presumably, one could do some heuristic ("there are many
strange characters in there, probably this isn't ascii") and
ask for confirmation that you do actually want to filter out
strange characters. Fact is, most of the time you won't want
to.

A related problem: when the master document's charset is not
ascii, po4a-updatepo seems to happily ignore the PO's
charset specification and change it (to UTF-8 in my case,
which I am not sure where it comes from, as I think the
input document was iso-8859-1 just like the PO), along with
all the characters in the PO. In other words, po4a-update
silently:
- changes the charset I have specified in the PO
- changes all the non-ascii characters in some way
("in some way", because I don't think it ended up in UTF-8
either).

I'm so in love with French accents right now.

#. type: Attribute 'lang' of: <html>
#: _site/en/about.html:2 _site/en/archive.html:2 _site/en/contact.html:2
#: _site/en/index.html:2 _site/en/posts/2015-08-12-spqr.html:2
#: _site/en/posts/2015-10-07-rosa-rosa-rosam.html:2
#: _site/en/posts/2015-11-28-carpe-diem.html:2
#: _site/en/posts/2015-12-07-tu-quoque.html:2
msgid "en"
msgstr "ru"
#...
#. type: Content of: <html><body><main><h1>
#: _site/en/archive.html:23
msgid "Archives"
msgstr "Архив"
#...
#. type: Content of: <html><body><footer>
#: _site/en/about.html:33 _site/en/archive.html:49 _site/en/contact.html:28
#: _site/en/index.html:59 _site/en/posts/2015-08-12-spqr.html:41
#: _site/en/posts/2015-10-07-rosa-rosa-rosam.html:43
#: _site/en/posts/2015-11-28-carpe-diem.html:41
#: _site/en/posts/2015-12-07-tu-quoque.html:43
msgid ""
"Site proudly generated by <a href=\"http://jaspervdj.be/hakyll\">Hakyll</a>"
msgstr ""
"Сайт создан с помощью <a href=\"http://jaspervdj.be/hakyll\">Hakyll</a>"
=item DOCBOOKDIR

Similar to XMLDIR but only used to prepare the translated DocBook files. If
your package wants to use .sgml files, please discuss how these should be
built on the po4a-devel mailing list.

 # pattern to find the .docbook files
 DOCBOOKDIR=""

if [ -n "$XMLDIR" ]; then
	for file in $XMLDIR/*.xml; do
		LOCAL=`basename $file`
		wrap_langs "[type:docbook]" "$file" "\$lang:$XMLDIR/\$lang/$LOCAL"
	done
fi
if [ -n "$DOCBOOKDIR" ]; then
	for file in $DOCBOOKDIR; do
		LOCAL=`basename $file`
		wrap_langs "[type:docbook]" "$file" "\$lang:$BASEDIR/\$lang/$LOCAL"
	done
fi

Title: Some title
Date: Some date

lorem ipsum ...

foo bar baz ...

It would be nice if I could mark some paragraphs as untranslatable.

For example, say I have a docbook flie that lists a number of file paths
as part of the documentation. These paths (like ~/.cache) show up to 
be translated, but I don't want them to be.

Maybe some format-specific comment that po4a understands? 
In the docbook example, the paragraph being preceded by 
 or something.

You are right, that would be nice. The parser can cope with 
comments only if they are embedded within a paragraph, 
which means that in XML one has to write 
<para>Foo bar</para> 
to have this comment printed into PO files.
One could indeed define special comments, e.g. 
<para>Foo bar</para> to have a paragraph 
copied verbatim into translated documents. Note that these comments 
will not be removed from translated documents, I believe that this is fine.

You can test by editing Locale/Po4a/Xml.pm like this: replace
if ($translate ne "")
by
if ($translate ne "" && !(defined($comments) && $comments =~ m/^\s*po4a:\s*ignore/s))
I will commit this change unless you report problems with it.

That would be fine. I'd also be interested in similar syntax for man pages too.

Just for the record, this feature is now implemented in the man module 
(see section "Hiding text from po4a" from Locale::Po4a::Man(3pm))

Just to be sure: in which modules would you need this feature, Michael?

Implementing it in Sgml may be particularly challenging so I'd prefer 
not to do that if you don't really need it. Is it enough if it works in Man?

Thanks for your patience,

As the title says, the Xml module does not wrap the generated 
document, even if asked to by the -w flag.

# Remove HTML test, which does no longer pass
# and probably should be removed upstream, too.
override_dh_auto_test:
    rm t/09-html.t

msgid ""
"How to compile Bash for more than one kind of system from the same source tree."
msgstr ""
"C@'omo compilar Bash para m@'as de un tipo de sistema desde el mismo @'arbol de "
"fuentes."

* Compilando para M@'ultiples Arquitecturas::  C@'omo compilar Bash para 
                                                 m@'as de un tipo de sistema 
                                                 desde el mismo @'arbolde 
                                                 fuentes.

ifdef::stalenotes[]

parse...po4a::asciidoc: Impossible d'analyser la liste d'attributs : []

Complex regular subexpression recursion limit (32766) exceeded at
/usr/share/perl5/Locale/Po4a/TeX.pm line 697

    # detect \begin and \end (if they are not commented)
    if ($buffer =~ /^((?:.*?\n)?                # $1 is
                      (?:[^%]                   # either not a %
                        |                       # or
                         (?<!\\)(?:\\\\)*\\%)*? # a % preceded by an odd nb of \
                     )                          # $2 is a \begin{ with the end of the line
                      (${RE_ESCAPE}(?:begin|end)\{.*)$/sx
        and length $1) {
        my ($begin, $end) = ($1, $2);
        my ($t1, $t2) = ("", "");
        if (is_closed($begin)) {
            ($t1, @env) = translate_buffer($self, $begin, $no_wrap, @env);
            ($t2, @env) = translate_buffer($self, $end,   $no_wrap, @env);

            print STDERR "($t1$t2,@env)\n"
                if ($debug{'translate_buffer'});
            return ($t1.$t2, @env);
        }
    }

#.  ANY additional lines in the script cause a pdf rendering problem
#. type: Content of: <sect1><screen><userinput><literal>
msgid ""
"<userinput>cat &gt; version-check.sh &lt;&lt; \"EOF\" <literal>#!/bin/bash # "
"Simple script to list version numbers of critical development tools export "
"LC_ALL=C bash --version | head -n1 | cut -d\" \" -f2-4 MYSH=$(readlink -f /"
"bin/sh)  echo \"/bin/sh -&gt; $MYSH\" echo $MYSH | grep -q bash || echo "
"\"ERROR: /bin/sh does not point to bash\" unset MYSH echo -n \"Binutils: \"; "
"ld --version | head -n1 | cut -d\" \" -f3- bison --version | head -n1 if [ -"
"h /usr/bin/yacc ]; then echo \"/usr/bin/yacc -> `readlink -f /usr/bin/yacc`"
"\"; elif [ -x /usr/bin/yacc ]; then echo yacc is `/usr/bin/yacc --version | "
"head -n1` else echo \"yacc not found\" fi bzip2 --version 2&gt;&amp;1 &lt; /"
"dev/null | head -n1 | cut -d\" \" -f1,6- echo -n \"Coreutils: \"; chown --"
"version | head -n1 | cut -d\")\" -f2 diff --version | head -n1 find --"
"version | head -n1 gawk --version | head -n1 if [ -h /usr/bin/awk ]; then "
"echo \"/usr/bin/awk -&gt; `readlink -f /usr/bin/awk`\"; elif [ -x /usr/bin/"
"awk ]; then echo awk is `/usr/bin/awk --version | head -n1` else echo \"awk "
"not found\" fi gcc --version | head -n1 g++ --version | head -n1 ldd --"
"version | head -n1 | cut -d\" \" -f2- # glibc version grep --version | head -"
"n1 gzip --version | head -n1 cat /proc/version m4 --version | head -n1 make "
"--version | head -n1 patch --version | head -n1 echo Perl `perl -V:version` "
"python3 --version sed --version | head -n1 tar --version | head -n1 makeinfo "
"--version | head -n1 # texinfo version xz --version | head -n1"
msgstr ""

#. type: Content of: <sect1><screen>
#: lfs-en/chapter02/hostreqs.xml:211
#, no-wrap
msgid ""
"echo 'int main(){}' &gt; dummy.c &amp;&amp; g++ -o dummy dummy.c\n"
"if [ -x dummy ]\n"
"  then echo \"g++ compilation OK\";\n"
"  else echo \"g++ compilation failed\"; fi\n"
"rm -f dummy.c dummy</literal>\n"
"EOF\n"
"\n"
"bash version-check.sh</userinput>"
msgstr ""

+ perl Build.PL installdirs=vendor
DEBUG util.py:499:  Created MYMETA.yml and MYMETA.json
DEBUG util.py:499:  Creating new 'Build' script for 'po4a' version '0.54'
DEBUG util.py:499:  + ./Build
DEBUG util.py:499:  Created META.yml and META.json
DEBUG util.py:497:  BUILDSTDERR: Unknown format type: pod.
DEBUG util.py:497:  BUILDSTDERR: List of valid formats:
DEBUG util.py:497:  BUILDSTDERR:   - asciidoc: AsciiDoc format.
DEBUG util.py:497:  BUILDSTDERR:   - dia: uncompressed Dia diagrams.
DEBUG util.py:497:  BUILDSTDERR:   - docbook: DocBook XML.
DEBUG util.py:497:  BUILDSTDERR:   - guide: Gentoo Linux's XML documentation format.
DEBUG util.py:497:  BUILDSTDERR:   - ini: INI format.
DEBUG util.py:497:  BUILDSTDERR:   - kernelhelp: Help messages of each kernel compilation option.
DEBUG util.py:497:  BUILDSTDERR:   - latex: LaTeX format.
DEBUG util.py:497:  BUILDSTDERR:   - man: Good old manual page format.
DEBUG util.py:497:  BUILDSTDERR:   - pod: Perl Online Documentation format.
DEBUG util.py:497:  BUILDSTDERR:   - rubydoc: Ruby Documentation (RD) format.
DEBUG util.py:497:  BUILDSTDERR:   - sgml: either DebianDoc or DocBook DTD.
DEBUG util.py:497:  BUILDSTDERR:   - texinfo: The info page format.
DEBUG util.py:497:  BUILDSTDERR:   - tex: generic TeX documents (see also latex).
DEBUG util.py:497:  BUILDSTDERR:   - text: simple text document.
DEBUG util.py:497:  BUILDSTDERR:   - wml: WML documents.
DEBUG util.py:497:  BUILDSTDERR:   - xhtml: XHTML documents.
DEBUG util.py:497:  BUILDSTDERR:   - xml: generic XML documents (see also docbook).
DEBUG util.py:497:  BUILDSTDERR:   - yaml: YAML documents.
DEBUG util.py:497:  BUILDSTDERR: Died at Po4aBuilder.pm line 161.
DEBUG util.py:497:  BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.zBgf15 (%build)
DEBUG util.py:497:  BUILDSTDERR:     Bad exit status from /var/tmp/rpm-tmp.zBgf15 (%build)
DEBUG util.py:499:  RPM build errors:
DEBUG util.py:640:  Child return code was: 1
INFO util.py:556:  EXCEPTION: [Error()]

List Header
* item 1
* item 2
* item 3

... That's why the PO files produced by the po-debiandoc module
contain the following header:

 #
 #  ADVISES TO DEVELOPERS:
 #    - you do not need to manually edit POT or PO files.
 #    - this file contains the translation of your debconf templates.
 #      Do not replace the translation of your program with this !!
 #        (or your translators will get very upset)
 #
 #  ADVISES TO TRANSLATORS:
 #    If you are not familiar with the PO format, gettext documentation
 #     is worth reading, especially sections dedicated to this format.
 #    For example, run:
 #         info -n '(gettext)PO Files'
 #         info -n '(gettext)Header Entry'
 #
 #    Some information specific to po-debconf are available at
 #            /usr/share/doc/po-debconf/README-trans
 #         or http://www.debian.org/intl/l10n/po-debconf/README-trans
 #

$ cat <<EOF > code.md
\`\`\`bash
one
two
three
\`\`\`
EOF

$ po4a-gettextize --format text --option markdown --master code.md --po code.po

$ cat code.po
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2019-05-05 00:18+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <[email protected]>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. type: Code fence info string
#: code.md:1
#, no-wrap
msgid "bash"
msgstr ""

#. type: Plain text
#: code.md:1
#, no-wrap
msgid ""
"one\n"
"\n"
"two\n"
"\n"
"three\n"
"\n"
msgstr ""

$ cat code.po
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2019-05-05 00:18+0900\n"
"PO-Revision-Date: 2019-05-05 00:27+0900\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <[email protected]>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. type: Code fence info string
#: code.md:1
#, no-wrap
msgid "bash"
msgstr "bash"

#. type: Plain text
#: code.md:1
#, no-wrap
msgid ""
"one\n"
"\n"
"two\n"
"\n"
"three\n"
"\n"
msgstr ""
"one\n"
"\n"
"two\n"
"\n"
"three\n"
"\n"

po4a-translate --format text --option markdown --master code.md --po code.po --localized localized_code.md

```bash
one

two

three

```

$ cat code.po
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2019-05-05 00:18+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <[email protected]>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

#. type: Code fence info string
#: code.md:1
#, no-wrap
msgid "bash"
msgstr ""

#. type: Plain text
#: code.md:1
#, no-wrap
msgid ""
"one\n"
"two\n"
"three\n"
msgstr ""

```bash
one
two
three
```

/opt/local/bin/perl5.26 Build.PL installdirs=core --config cc="/usr/bin/clang" --config ld="/usr/bin/clang"
WARNING: the following files are missing in your kit:
	META.yml
Please inform the author.

Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'po4a' version '0.53'

If you want to handle a file being in another directory, all included ones are
not found because they are searched in the current directory instead of 
where the master file is.

Could this be fixed together with the generalized way to include files for all the 
modules?

Could be hacked in the meanwhile ;)

po4a po4a.conf
documentation_administrator.tex:64: (po4a::tex)
               Unbekannte Umgebung: »lstlisting«

register_generic_command("menu,{_}");
register_generic_command("lstlisting,{}");

mquinson / po4a Goto Github PK

po4a's People

Contributors

Stargazers

Watchers

Forkers

po4a's Issues

To reproduce

Expected result

Environment info

Recommend Projects

Recommend Topics

Recommend Org