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.
<!-- Normal layout: --> <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,
Hi,
On Thursday 21 January 2010 Yasuhiko Kamata wrote:
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.
That sounds very good! :-)
[...]
Validation (make validate) and PDF creation (make pdf) finished with no error.
That's a good start. :-)
But some sorts of tagged texts in PDF were displayed with blank. These are "guimenu", "replaceable", and "xref" (referenced text).
Do you use FOP or XEP for creating the PDF? I guess, it's FOP, right?
In addition, some characters of these texts can be displayed normally if the character is ASCII (alphabets, numbers, etc.).
Does the fonts contain the characters? You can open the font in FontForge (same package name, lower case).
So I think this problem was caused by some font setting. However, no font settings seems to be exist in susedoc except above.
There are font setting for XEP and FOP, but the latter is not tested enough.
Hope this is a start to narrow down the problem. Thanks for your translation efforts! :-)
Tom
Hello,
But some sorts of tagged texts in PDF were displayed with blank. These are "guimenu", "replaceable", and "xref" (referenced text).
Do you use FOP or XEP for creating the PDF? I guess, it's FOP, right?
Yes, I'm now using FOP. XEP is not installed.
In addition, some characters of these texts can be displayed normally if the character is ASCII (alphabets, numbers, etc.).
Does the fonts contain the characters? You can open the font in FontForge (same package name, lower case).
Yes, they can be opened by fontforge.
(for IPAPMincho) $ fontforge /usr/share/fonts/truetype/ipamp.otf (for IPAPGothic) $ fontforge /usr/share/fonts/truetype/ipagp.otf (for IPAGothic) $ fontforge /usr/share/fonts/truetype/ipag.otf
Basic Latin (like U+0041), Hiragana/Katakana (Japanese fundamental characters; like U+3042, U+30A2), CJK Unified Ideographs (also called "Kanji"; like U+4E00) were displayed as expected.
So I think this problem was caused by some font setting. However, no font settings seems to be exist in susedoc except above.
There are font setting for XEP and FOP, but the latter is not tested enough.
Ok, I'll try with XEP later.
Thanks,
Hi,
On Friday 22 January 2010 Yasuhiko Kamata wrote:
But some sorts of tagged texts in PDF were displayed with blank. These are "guimenu", "replaceable", and "xref" (referenced text).
Do you use FOP or XEP for creating the PDF? I guess, it's FOP, right?
Yes, I'm now using FOP. XEP is not installed.
I've checked out your SVN repository and tested it with XEP. Some graphic files were missing, but that's ok as you concentrate on the text.
At first, I had some problems with an "out of memory error". Luckily I could solve it with an export XEP_MEMORY="-Xmx1100m". After this the PDF was created without errors.
You can see the results here: http://www.suse.de/~toms/opensuse-man-ja/opensuse-html-xep.pdf (It takes some time to synchronize.)
If you don't mind, I would like to suggest some improvements in your SVN repository:
1. Rename the ENV file ENV-opensuse-html as it is misleading. For example, something like ENV-opensuse is probably enough. This applies also to the directory. Maybe it is even better to move all the contents in it one level higher and remove the directory alltogether. But this is just an idea, maybe you want to structure it further.
2. Use separate ENV files to make it easier to build only Quick Starts, User Guide or Administration Guide. The above PDF contains 1836 pages and on slower computers it takes ages. On computers with less memory it will probably fail.
3. In some xml/book*.xml files, there is an attribute lang="en". This should be lang="ja", but I guess, I already know that. :)
Apart from that it is a good start! Keep on moving! :-)
[...]
(for IPAPMincho) $ fontforge /usr/share/fonts/truetype/ipamp.otf (for IPAPGothic) $ fontforge /usr/share/fonts/truetype/ipagp.otf (for IPAGothic) $ fontforge /usr/share/fonts/truetype/ipag.otf
Basic Latin (like U+0041), Hiragana/Katakana (Japanese fundamental characters; like U+3042, U+30A2), CJK Unified Ideographs (also called "Kanji"; like U+4E00) were displayed as expected.
Ok, that looks good. I've used the Sazanami fonts (package sazanami-fonts).
[...]
Tom
Hello,
On Fri, 22 Jan 2010 09:10:33 +0100 Thomas Schraitle thomas.schraitle@suse.de wrote:
I've checked out your SVN repository and tested it with XEP. Some graphic files were missing, but that's ok as you concentrate on the text.
At first, I had some problems with an "out of memory error". Luckily I could solve it with an export XEP_MEMORY="-Xmx1100m". After this the PDF was created without errors.
You can see the results here: http://www.suse.de/~toms/opensuse-man-ja/opensuse-html-xep.pdf (It takes some time to synchronize.)
Oh, that's great! Surely problems which appears on FOP disappeared; I can see texts as expected.
So I'll use XEP instead of FOP from now.
If you don't mind, I would like to suggest some improvements in your SVN repository:
- Rename the ENV file ENV-opensuse-html as it is misleading. For
example, something like ENV-opensuse is probably enough. This applies also to the directory. Maybe it is even better to move all the contents in it one level higher and remove the directory alltogether. But this is just an idea, maybe you want to structure it further.
- Use separate ENV files to make it easier to build only Quick
Starts, User Guide or Administration Guide. The above PDF contains 1836 pages and on slower computers it takes ages. On computers with less memory it will probably fail.
- In some xml/book*.xml files, there is an attribute lang="en". This
should be lang="ja", but I guess, I already know that. :)
Thank you for advice. SVN repository is now under constructing; I'll arrange the structure later (after 50% completion or so).
Thanks,
Hi,
On Friday 22 January 2010 Yasuhiko Kamata wrote:
[...]
You can see the results here: http://www.suse.de/~toms/opensuse-man-ja/opensuse-html-xep.pdf (It takes some time to synchronize.)
Oh, that's great!
:-)
Surely problems which appears on FOP disappeared; I can see texts as expected.
So I'll use XEP instead of FOP from now.
XEP is a commercial application. There is also a Personal Edition, but it prints a logo in the bottom of the page.
I think, it must also work for FOP, but at the moment, our stylesheets are a bit untested as we use XEP internally.
If you don't mind, I would like to suggest some improvements in your SVN repository: [...]
Thank you for advice. SVN repository is now under constructing; I'll arrange the structure later (after 50% completion or so).
Whatever fits best do your needs. It was just an idea. Do whatever you want/need. :-)
Tom
Hello,
At length, translation of manuals (to Japanese) is now reached a milestone. Current status is follows:
Translation completed: * Quickstarts (Install, KDE, GNOME, AppArmor) * Startup * Reference * KDE user guide * GNOME user guide
NOT yet translated (now in working): * Application guide * Security guide
These translations are based on 11.3-6.1.1 version. (from openSUSE 11.3 update repository)
Could you create a translation tree (ja) on opensuse-doc SVN at berlios.de and grant me a write permission? (I'll commit translations afterwards)
Language: Japanese (ja) My account: belphegor
Thanks and best regards,
On Dec 13, 10 15:51:55 +0900, Yasuhiko Kamata wrote:
Translation completed:
- Quickstarts (Install, KDE, GNOME, AppArmor)
- Startup
- Reference
- KDE user guide
- GNOME user guide
NOT yet translated (now in working):
- Application guide
- Security guide
This is great news. Thank you for very much for the translation effort!
Could you create a translation tree (ja) on opensuse-doc SVN at berlios.de and grant me a write permission? (I'll commit translations afterwards)
Language: Japanese (ja) My account: belphegor
trunk/documents/distribution/ja has been set up, but I am unsure if I did the permissions correctly. You should have write access there. Please ping me if it does not work yet.
cheers, JW-
On Mon, 13 Dec 2010 12:38:48 +0100 Juergen Weigert jw@suse.de wrote:
trunk/documents/distribution/ja has been set up, but I am unsure if I did the permissions correctly. You should have write access there. Please ping me if it does not work yet.
Thanks for creation. I've now committed the latest translation (rev. 2179).
So I want them to become available via a RPM package (opensuse-manuals_ja-nnn.rpm). What can I do?
Thanks,
Hi,
On Monday 13 December 2010 Yasuhiko Kamata wrote:
At length, translation of manuals (to Japanese) is now reached a milestone. Current status is follows:
Translation completed:
- Quickstarts (Install, KDE, GNOME, AppArmor)
- Startup
- Reference
- KDE user guide
- GNOME user guide
NOT yet translated (now in working):
- Application guide
- Security guide
This is really great news!
These translations are based on 11.3-6.1.1 version. (from openSUSE 11.3 update repository)
Could you create a translation tree (ja) on opensuse-doc SVN at berlios.de and grant me a write permission? (I'll commit translations afterwards)
This works already and I could update my ja directory. Thanks, awesome work!
Just to give you a small tip: It's also possible to build a specific book, for example, one of the Quick Starts. I would recommend to copy the ENV-opensuse-* files from the en directory to ja. This makes it faster to work with the files instead of just the whole set. :)
Hi,
On Monday 13 December 2010 Yasuhiko Kamata wrote:
Translation completed: [...] Could you create a translation tree (ja) on opensuse-doc SVN at berlios.de and grant me a write permission? (I'll commit translations afterwards)
I've created also an image directory for you. It contains the subdirectory src with the different graphic formats. You can just fill them with Japanese screenshots.
On Mon, 13 Dec 2010 13:33:38 +0100 Thomas Schraitle toms@suse.de wrote:
I've created also an image directory for you. It contains the subdirectory src with the different graphic formats. You can just fill them with Japanese screenshots.
Thanks, I'll work for taking Japanese version of screenshots.
Just to give you a small tip: It's also possible to build a specific book, for example, one of the Quick Starts. I would recommend to copy the ENV-opensuse-* files from the en directory to ja. This makes it faster to work with the files instead of just the whole set. :)
Ok, copied and committed.
Best regards,
-
Juergen Weigert -
Thomas Schraitle -
Thomas Schraitle -
Yasuhiko Kamata