July 2010 - Devel - Po4a List Archives

by intrigeri

Hi, there is a tiny inconsistency in the way po4a writes PO headers. When it creates a PO file, it writes in there: "Content-Transfer-Encoding: ENCODING" ... on the other hand, at other times, e.g. when updating a PO file, this header field is replaced by: "Content-Transfer-Encoding: ENCODING\n" This is probably only annoying for VCS repositories history, e.g. when using a multi-lingual ikiwiki[1] thanks to the po plugin[2] I wrote, that heavily uses po4a. In this case, this tiny inconsistency triggers a double commit of PO files when a page is added to the wiki. This bug was reported by Joey Hess: http://ikiwiki.info/bugs/po:_double_commits_of_po_files/ The attached one-line patch fixes this "bug". It would be pretty nice if it was applied on time to be shipped in Squeeze. [1] http://ikiwiki.info [2] http://ikiwiki.info/plugins/po/ Bye, thanks for po4a! -- intrigeri <intrigeri(a)boum.org> | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr-fingerprint.asc | Did you exchange a walk on part in the war | for a lead role in the cage?

13 years, 7 months

2
5
0 / 0

Preparation of the next po4a 0.40.1 release

by Denis Barbier

Hello, As told during the preparation of po4a 0.40, I would like to propose a longer string freeze for 0.40.1, but also to release 0.40.1 as soon as possible. I will try to release po4a 0.40.1 on Wednesday, 25th August around 20:00 UTC. That sounds reasonable, but not very exciting; in order to make this experience funnier, I will leave on vacation very soon and do not know whether I will read mails ;-) Omar, can you please send calls for translations as you did with 0.40? First set a string freeze date with David, I do not know if all the stylistic changes in English documentation he proposed have been applied. if you will not have time, can you please explain how to proceed so that someone else can do this job? Thanks in advance. Denis

13 years, 8 months

4
13
0 / 0

Question about xml -> pot with po4a - from ADempiere ERP community

by Peanut Blake

Dear all, I am from ADempiere open source ERP. I am using po4a for translation. Thank you very much for your good work! Now I meet trouble need your help. I have one xml file like: <row id="103" trl="Y"> <value column="Name" original="Minutes">Minutes</value> <value column="UOMSymbol" original="m " pot-remark="Short form of 'Minutes'. Don't translate @@ID-103@@.">m @@id-103@@</value> </row> I want to convert to POT file like: #. Content of: <id-103><Name> #, no-wrap msgid "Minutes" msgstr "" #. Content of: <id-103><UOMSymbol> #. Short form of 'Minutes'. Don't translate @@ID-103@@. #, no-wrap msgid "m @@id-103@@" msgstr "" I have two questions: 1. How to put remark in xml to POT? for example, put "pot-remark="Short form of 'Minutes'. Don't translate @@ID-103@@."" to "#. Short form of 'Minutes'. Don't translate @@ID-103@@." 2. How to put id & column in xml to POT? for example, put id="103" column="Name" to #. Content of: <id-103><Name> Does po4a already provide such functions? Thank you! Peanut Blake from ADempiere ERP community

13 years, 8 months

2
2
0 / 0

Re: [Po4a-devel] When and how can we migrate out of CVS and WML ?

by David Prévot

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Le 30/07/2010 05:38, Petter Reinholdtsen a écrit : > [Craig Small] >> The problem with replacing WML is; what do you replace it with? and >> will it bring any real benefit? > > What about using XHTML and po4a to handle translations using .po > files? The original english versions would be written in XHTML, > translators would work on .po files, and the site could be generated > regularly or when the source or .po files changes. > > For an english XHTML page index.html.en, this command will generate a > .pot file: > > po4a-gettextize -M UTF-8 -f xhtml -m index.html.en -p index.pot FWIW, po4a can handle WML directly, but may need some more testing in order to handle every document on the site. Anyway, I'm BCCing the po4a-devel list in order to eventually gather more accurate comment about this. Cheers David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkxTVS0ACgkQ18/WetbTC/p14wCfVZ+iqnygmjyoG7ebQkFq2PJF qckAn11AbRiVmjjdWwo20H+x1gWd5PII =FdSC -----END PGP SIGNATURE-----

13 years, 9 months

1
0
0 / 0

[po4a-Bugs][311647] Allow marking some paragraphs/phrases as not-for-translation

by po4a-bugs＠alioth.debian.org

Bugs item #311647, was changed at 2009-05-03 10:04 by Michael Terry You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=311647&gro... Status: Open Priority: 3 Submitted By: Michael Terry (mterry-guest) Assigned to: Nobody (None) Summary: Allow marking some paragraphs/phrases as not-for-translation Category: None Group: None Resolution: None Initial Comment: 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. ---------------------------------------------------------------------- Comment By: Michael Terry (mterry-guest) Date: 2010-07-29 14:14 Message: That would be fine. I'd also be interested in similar syntax for man pages too. ---------------------------------------------------------------------- Comment By: Denis Barbier (barbier-guest) Date: 2010-07-29 09:39 Message: 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. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=311647&gro...

13 years, 9 months

1
0
0 / 0

[po4a-Bugs][301268] Feature request : po4a-statistics

by po4a-bugs＠alioth.debian.org

Bugs item #301268, was changed at 2005-03-17 22:27 by Denis Barbier You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=301268&gro... >Status: Closed Priority: 3 Submitted By: Jean-Michel Pouré (jmpoure-guest) Assigned to: Nobody (None) Summary: Feature request : po4a-statistics Category: None Group: None >Resolution: Wont Fix Initial Comment: It would nice if a perl script could output statistics: translated (with %), untranslated (with %), fuzzy (with %). The results should be available in several formats, including HTML. ---------------------------------------------------------------------- >Comment By: Denis Barbier (barbier-guest) Date: 2010-07-29 16:00 Message: Sorry, but that would open a can of worms, people will want to customize output. To print statistics, you can run: for f in *.po; do printf "$f: "; msgfmt --statistics -o /dev/null $f; done For HTML, see the gen_translations function in https://alioth.debian.org/scm/viewvc.php/po4a/html-build-upload.sh?view=m... ---------------------------------------------------------------------- Comment By: Martin Quinson (mquinson) Date: 2005-05-10 20:15 Message: connecté user_id=10600 What kind of stats? The one of the po file? it's msgformat job, I think. The one of the document? po4a-translate does so, with the -v flag. Would you mind explaining a bit more? Thanks, Mt. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=301268&gro...

13 years, 9 months

1
0
0 / 0

[po4a-Bugs][304394] Unexpected escaped chars in the po

by po4a-bugs＠alioth.debian.org

Bugs item #304394, was changed at 2007-04-30 14:24 by Denis Barbier You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=304394&gro... >Status: Closed Priority: 3 Submitted By: Nobody (None) Assigned to: Nicolas FRANÇOIS (nekral-guest) Summary: Unexpected escaped chars in the po Category: None Group: None >Resolution: Invalid Initial Comment: Hi, It seems that the "\n*" are replaced by " *" (where * is not a wildcard). The bug is visible in the removed 0.30 series, don't know for other release. ---------------------------------------------------------------------- >Comment By: Denis Barbier (barbier-guest) Date: 2010-07-29 15:42 Message: No reply from bug reporter, I am closing this bug. ---------------------------------------------------------------------- Comment By: Nicolas FRANÇOIS (nekral-guest) Date: 2007-08-08 14:08 Message: Hello, Could you provide a test file, and indicate which module you used? Thanks in advance ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=304394&gro...

13 years, 9 months

1
0
0 / 0

[po4a-Bugs][311647] Allow marking some paragraphs/phrases as not-for-translation

by po4a-bugs＠alioth.debian.org

Bugs item #311647, was changed at 2009-05-03 16:04 by Denis Barbier You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=311647&gro... Status: Open Priority: 3 Submitted By: Michael Terry (mterry-guest) Assigned to: Nobody (None) Summary: Allow marking some paragraphs/phrases as not-for-translation Category: None Group: None Resolution: None Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: Denis Barbier (barbier-guest) Date: 2010-07-29 15:39 Message: 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. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=311647&gro...

13 years, 9 months

1
0
0 / 0

[po4a-Bugs][300622] automatic classification of docbook tags

by po4a-bugs＠alioth.debian.org

Bugs item #300622, was changed at 2004-04-06 23:07 by Denis Barbier You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=300622&gro... >Status: Closed Priority: 3 Submitted By: Martin Quinson (mquinson-guest) Assigned to: Nobody (None) Summary: automatic classification of docbook tags Category: None Group: None >Resolution: Fixed Initial Comment: [This was #6454 from Savannah] *** fgouget repported *** Here's the problem: the 'command' DocBook tag can be used either inline, or in a tag that does not contain text, e.g. 'cmdsynopsis'. Because of the latter case I had put 'command' in the 'translate' category. But this causes 'The <command>ls</> command prints the directory contents.' to generate: msgid "The" msgstr "" msgid "ls" msgstr "" msgid "command prints the directory contents." msgstr "" The above is too hashed out to be translated. I can fix this by moving the 'command' tag to the 'ignore' category. And it still works if I put it into a 'cmdsynopsis' tag. But then we rely on 'cmdsynopsis' being in the 'indent' category. Is this the right thing to do? How does one determine in which category to put tags? **** mquinson answered **** Yes, this is bad. I did move command to ignore, and cmdsynopsis is already in the indent list. I'll release 0.15.4 soon. I'd really like to know how to determine automatically in which category fall each tag. That would allow me to write an automatic dtd parser determining this, and getting rid of the manual determination. By the way, it would allow the use of this module with all existing dtd for free. For example, HTML could be translated that way, which is not the case for now. I have no idea about that right now, and too few time to investigate the issue. If you want to do this, I would be more than pleased to help you if I can, and integrate it when it works. If you don't want, we have to fix the list manually together. I'll do as many releases as needed to get that list right if you choose the second option. *** fgouget answered *** I'm willing to go for the second route (using the Wine doc as the testbed) and maybe determine an algorithm for classifying the tags (I'll leave the implementation as an exercise<g>). But could you check, complete and correct the following categories description? * empty Tags that cannot contain text or other tags. * verbatim Tags in which the text layout, spaces and new-lines, is important. Such text should not be reformated before being put in po format. * translate Tags containing text to be translated. When po4a-gettextize finds such a tag it will cut short the current text, if any, and put it in an msgid, and then start a new msgid entry with the text contained inside the tag to be translated. (maybe that's a bug, should the po4a-gettextize be different when inside #PCDATA stuff? It would make sense to ignore all tags in that case in DocBook, maybe not in other dtds?) This means inline tags must not be put in this category as it would otherwise cut text mid-sentence, making them impossible to translate. Difference with indent??? * section Tags that cannot contain text to be translated but can contain other tags. I believe these tags cannot appear inside tags that are translatable, such as tags in the translate and indent categories. What's the point? * indent Indented tags? Indented where? What's this indentation for? Difference with section and especially translate? * ignore These tags are ignored and left in the stream of text to be translated. Inline tags must be put in this category so that they don't cause po4a-gettextize to split text mid-sentence. If an ignore tag is not in an inline context, then if its parent is in the translate or indent category then it will be put straight in the stream of text to be translated. Otherwise? *** mquinson answered *** Ok, I'll try to document this in the Sgml.pm documentation. It will give us a base of discution ;) In short, translate=indent in the current code (and I don't remember why I introduced indent); section is different so that the source of the translated document looks better. But this module is so old that I can recall wrong ;) ---------------------------------------------------------------------- >Comment By: Denis Barbier (barbier-guest) Date: 2010-07-29 15:14 Message: I agree with Jordi, and as Locale::Po4a::Docbook is there now (well, for a long time already), I am closing this bug. ---------------------------------------------------------------------- Comment By: Jordi Vilalta (jvprat-guest) Date: 2004-08-09 23:31 Message: Logged In: YES user_id=10156 In the Xml module, the same tag can be inline (it can be conditional, depending on into which tag it is) and translatable (if it isn't inside another translatable tag). Also, the Xml module handles all the tags as they were in the "ignore" category, and then you say which ones you want to treat in a different way. I think this can be enough in this case. If true, when a Xml-derived DocBook module appears, this bug could be closed. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=300622&gro...

13 years, 9 months

1
0
0 / 0

Preparation of the next po4a 0.40 release

by Denis Barbier

Hello, I would like to release po4a 0.40 next week (on July, 27th) to fix several bugs. Here are the current status of the translations: Translations of the binaries: af: 22t 30f 133u ar: 1t 184u bn: 4t 8f 173u ca: 143t 14f 28u cs: 179t 5f 1u de: 179t 5f 1u eo: 180t 4f 1u es: 185t et: 84t 31f 70u eu: 179t 5f 1u fr: 185t he: 3t 9f 173u hr: 30t 16f 139u id: 129t 24f 32u it: 133t 22f 30u ja: 185t kn: 33t 32f 120u ko: 20t 12f 153u ku: 4t 8f 173u nb: 51t 40f 94u nl: 20t 15f 150u oc: 4t 20f 161u pl: 185t pt: 179t 5f 1u pt_BR: 41t 33f 111u ru: 185t sl: 6t 17f 162u sv: 180t 4f 1u uk: 4t 18f 163u uz: 5t 7f 173u vi: 180t 4f 1u zh_CN: 14t 8f 163u zh_HK: 16t 24f 145u You can find the PO files in: http://alioth.debian.org/scm/viewvc.php/po4a/po/bin/?root=po4a Translations of the man pages: ca: 798t 170f 511u es: 1479t fr: 1318t 3f 158u it: 279t 125f 1075u ja: 1461t 5f 13u pl: 1461t 5f 13u ru: 401t 6f 1072u You can find the PO files in: http://alioth.debian.org/scm/viewvc.php/po4a/po/pod/?root=po4a Denis

13 years, 9 months

4
22
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Devel July 2010