December 2010 - openSUSE Documentation

[opensuse-doc] Acess on Berlios SVN
by Luiz Fernando Ranghetti 28 Dec '10

28 Dec '10

Hi guys, Could someone grant me acess on berlios SVN, specially in the to be created pt_BR folder? Regards, Luiz -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

3 8

[opensuse-doc] JFYI: openSUSE 11.4 project has been started
by Frank Sundermeyer 27 Dec '10

27 Dec '10

Hi, today I have started the openSUSE 11.4 documentation project by setting properties and adjusting the set at https://svn.berlios.de/svnroot/repos/opensuse-doc/trunk/documents/distribut… The last "11.3 revision" in SVN is 2277--it will be released as an online update for 11.3 soon. This revision is also copied to the tags directory in SVN, see https://svn.berlios.de/svnroot/repos/opensuse-doc/tags/documents/openSUSE_1… If you are still translating 11.3 manuals, please either use this tag or trunk revision 2277 for checking out the English sources. -- 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: Markus Rex, HRB 16746 (AG Nuernberg) "Reality is always controlled by the people who are most insane" Dogbert -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

1 0

[opensuse-doc] Just a little question
by Luiz Fernando Ranghetti 27 Dec '10

27 Dec '10

Hi guys! Just a little question: Now that we move to berlios and I see some translations being made (ja, ru, hu) how the corrections are propagated to the translated xmls? For example: yast-repair was dropped from openSUSE and the en xmls where corrected today: http://svn.berlios.de/wsvn/opensuse-doc/trunk/?op=revision&rev=2272&peg=2272 How this change (or any other) will be propagated to its counterparts on ja, hu, etc? Will be some automatic way or translate teams should make a diff from time to time and include the changes by hand? Regards, Luiz -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

2 2

[opensuse-doc] KDE Booklet
by Javier Llorente 16 Dec '10

16 Dec '10

Hi list-mates, Some people at KDE (upstream) are almost done writing the official KDE Booklet. I have asked one of the authors what format they are using and he replied InDesign. Well, how could .po files be generated for an easier translation? I have never used InDesign. He also asked for alternatives. Luiz (elchevive) told me that Thomas (toms) recommended him http://www.syntext.com/products/serna-free/ (a free xml editor) a long time ago. Thanks, -- Javier Llorente

4 4

[opensuse-doc] questions for susedoc (Japanese fonts in susedoc)
by Yasuhiko Kamata 13 Dec '10

13 Dec '10

Hello all, We're now trying to translate the opensuse_manual to Japanese in beriOS.de (http://developer.berlios.de/projects/opensuse-man-ja/) This translation effort is about 25 percent completed. So I've planned to generate a PDF file from them. Before making, I've modified /usr/share/susedoc/xslt/common/l10n/ja.xml as follows for IPA fonts.  <l:gentext key="fop1.body.font.family" text="IPAPMincho,FreeSerif"/> <l:gentext key="fop1.sans.font.family" text="IPAPGothic,FreeSans"/> <l:gentext key="fop1.monospace.font.family" text="IPAGothic,FreeMono"/> <l:gentext key="fop1.symbol.font.family" text="IPAPGothic,Symbol"/> <l:gentext key="fop1.callout.unicode.font" text="IPAPGothic"/> ("fop1.pocket.*", "xep.*", and "xep.pocket.*" was also modified like above) After modification, run as follows. $ cd trunk/opensuse-html $ source ENV-opensuse-html $ make validate $ make pdf Validation (make validate) and PDF creation (make pdf) finished with no error. But some sorts of tagged texts in PDF were displayed with blank. These are "guimenu", "replaceable", and "xref" (referenced text). In addition, some characters of these texts can be displayed normally if the character is ASCII (alphabets, numbers, etc.). So I think this problem was caused by some font setting. However, no font settings seems to be exist in susedoc except above. How do I fix it? Cheers, -- Yasuhiko Kamata E-mail: belphegor(a)belbel.or.jp -- To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-doc+help(a)opensuse.org

4 11