On Saturday 12 September 2009 14:00:53 Osamu Aoki wrote: > Hi, > > On Wed, Sep 09, 2009 at 08:49:12AM +0200, Noel David Torres Taño wrote: > > On Tuesday 08 September 2009 14:49:09 Osamu Aoki wrote: > > > Hi, > ... > > > * One proper way is to use "addendum" > > > explained in po4a(7). ("man 7 po4a"). (I never done this. I am > > > thinking to do this soon to add translators in appendix.) > > Did you read this document? > ... Readed it, but my brain can not always stop thinking in the old ways. > > > These are great ideas, I thought about them and I'm using the second > > in my temptative translation. But I was asking about if it possible to > > have something like a new paragraph not in the original XML. > > "addendum" is the way. > > > Would it be legal to do something like this? > > You mean "Would it be wise to do something like this?" Was asking about XML correctness, I know it leads to unmaintenable translations. > > > msgstr "Here, the main part of the greeting message can be customized > > by editing the \"<literal>/etc/motd.tail</literal>\" > > file.</screen><paragraph>The two english paragraphs state that the > > Debian GNU/Linux system consists of free software and comes with > > ABSOLUTELY NO WARRANTY. The first line is generated from the system > > information using \"<literal>uname > > -snrvm</literal>\".</paragraph><screen>" > > It probably builds OK if tags were OK. (You suggestion seems to be > broken but I did not check throughly.) > > But forcing this kind of "TRICK" to work in the source makes source very > unmaintainable and thus unwise. If you really need to do this, you > should use "addendum". Otherwise, inserting unmatched tags inside PO is > bad idea and I really wish translator to avoid using such tricks. > > > Or maybe, to avoid the empty <screen> at end, to do it at start of the > > NEXT paragraph, though ideal way may be having a NEW EMPTY paragraph > > in original which can be filled by translators. > > "addendum" will let you do properly. Please read "man 7 po4a". > > > ...just trying to provide a second cent. > > Yes, I understand. > > Clean and readable source is the best way to keep long document to be > usable even when it goes through next revision and someone else to fix > problem associated with it. Agree 100% > > Osamu > > Noel
Description: This is a digitally signed message part.