On Thu, Jul 4, 2013 at 3:12 AM, Marguerite Su wrote:

Let's simplify it:

eg: the first page of the doc has content:

openSUSE 12.3 Start-Up 7 04, 2013

Where can I replace the text "Start-Up" to eg:

openSUSE 12.3 上手指南 7 04, 2013

This bug is because when generating the localized xml, it uses "en/xml/entity-decl.ent" instead of "$lang/xml/entity-decl.ent", so the real names that macros point to are always English. A quick fix is to make soft links.

PS:

I find the way to get all the "translator-credits" out from all POs.

Now I'm working on testing and make scripts.

Later I'll commit it to 50-tools, XD

It's done. I'm testing it in zh_CN branch. -- To unsubscribe, e-mail: opensuse-doc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-doc+owner@opensuse.org

Hi, Frank, On Thu, Jul 4, 2013 at 9:52 PM, Frank Sundermeyer wrote:

...

There're more suitable/readable names in Chinese, so I want to replace them.

this is resolved, correct?

Ja!

...

It is possible that some kind guys writing some perl scripts to extract the translator credits in every po, generate a new xml, and integrate it into our existing documentation?

I've never worked with -po files so far, but I am willing to try this. Where are your .po files located and what parts need to be extracted?

my po files here: http://svn.opensuse.org/svn/opensuse-doc/trunk/documents/distribution/zh_CN/... And I wanted to extract from eg: systemd.xml.zh_CN.po msgid "translator-credits" msgstr "2013, 玛格丽特 · 苏 " to 2013, 玛格丽特 · 苏 <ulink url="mailto:marguerite@opensuse.org"/> Currently I'm using shell script to do this: http://svn.opensuse.org/svn/opensuse-doc/trunk/documents/distribution/zh_CN/... But because I use `tail -1`, so my script can only extract the last one who added his name to the msgstr...so I think other powerful scripting language may do a lot better but it's out of my ability... Thanks Marguerite -- To unsubscribe, e-mail: opensuse-doc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-doc+owner@opensuse.org

On Thu, 4 Jul 2013 22:22:40 +0800 Marguerite Su wrote: Hi Marguerite,

...

...

It is possible that some kind guys writing some perl scripts to extract the translator credits in every po, generate a new xml, and integrate it into our existing documentation?

Attached is a shell script that, sort of, does what you want--based on the existing data. The biggest problem with your .po files is the inconsistency of the Translators data. Some translator credits are added as comments at the beginning of the file, whereas others are mentioned in the "translator-credits" section. Combination of both exists, too. The "translator credit" section contains the data in a number of varieties that makes them difficult to parse (there are even two different commas!). Single authors also entered their credits differently from file to file (there are, for example, nine different credits from yourself ;-)). Interestingly, there is almost no occurrence of multi-line data in the "translator-credits" section. (a fact I made use of). The fact that the data is inconsistent also makes the msggrep output useless for your purpose. It typically looks like this:

msggrep -K -e 'translator-credits' po/zypper.xml.zh_CN.po # # Translators: # , 2013. # Guo Yunhe , 2013. msgid "" msgstr "" "Project-Id-Version: opensuse-manuals\n" "POT-Creation-Date: 2013-03-17 02:02+0800\n" "PO-Revision-Date: 2013-03-02 03:36+0000\n" "Last-Translator: guoyunhebrave \n" "Language-Team: Chinese (China) (http://www.transifex.com/projects/p/opensuse-" "manuals/language/zh_CN/)\n" "Language: zh_CN\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n"

#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2 #: zypper.xml:0(None) msgid "translator-credits" msgstr "Sign Guo Yunhe " Parsing that output is not much different from parsing the complete .po file, therefore I did not make use of it. My script focuses on the "translator-credits" (ignoring the comments) and tries unify the existing variants - just a quick hack that allows you to quickly make use of the data without having to do too much manual work. This version assumes that multiple entries occur on one line and are separated by ";" - that is the case in all but three files. It converts all usable data to <member>2012, 玛丽苏 <ulink url="mailto:i@marguerite.su"/></member> which allows you to just Cut & Paste it into a <simplelist>. The output can easily be changed by adjusting the script. Errors and missing data is reported at STDERR--that will hopefully help fixing the data. To run it, go to the po/ and run the script like this: extract-translators.sh 2>translator_errors.txt | sort -u That will put the data on STDOUT (sorted, with duplicates removed) and the errors to translator_errors.txt. For better results, the translator data needs to be cleaned up (at least the comments from the top of the files need to be moved to the "translator-credits" section). And as long as there is no way or tool that lets you properly extract the "translator-credits" section from the .po file, I suggest to put the data in one line separated by a RECORD_DELIMITER (see line 4 in the script). Hope this helps. -- Regards Frank Frank Sundermeyer, Technical Writer, Documentation SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0, Fax: +49-911-7417755; http://www.opensuse.org/ SUSE Linux Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) "Reality is always controlled by the people who are most insane" Dogbert