Japanese PDF layout issues
Posted: Thu Sep 21, 2017 3:59 pm
Hi,
Our Japanese translators are unhappy about the PDF layout for the Japanese language. For example, we have serious issues with improper line breaks, probably due to the fact that there are normally no empty spaces in Japanese, but I'm just guessing here.
Example: the following text block breaks the first line at an improper character (the line should at least include the first character on the next line and the following comma)
• 「Text」ダイアログを開くには、オプションエディターを開---------------------------------|<--line end is here
き、「Text」セクションで「Text」ボタンをクリックします。
Other example:
プログラムツリーにウィンドウフォーカスが設定されていない場 <-- There should be no linebreak here.
合、[A]、、[C]、[D] のキーを使用してプログラムツリー内を移動できます。
Apart from the fact that we should justify the paragraphs for proper Japanese layouting, we don't know why this happens. We use a proper Japanese font (Meiryo [TTF]). Could this be an issue with Apache FOP?
I've already tried out Noto Sans CJK, an OTF which seems to work with the latest Apache FOP version, but the issues remain.
Is there a workaround for this, or has anybody else come across this issue?
Thanks,
Christina
Our Japanese translators are unhappy about the PDF layout for the Japanese language. For example, we have serious issues with improper line breaks, probably due to the fact that there are normally no empty spaces in Japanese, but I'm just guessing here.
Example: the following text block breaks the first line at an improper character (the line should at least include the first character on the next line and the following comma)
• 「Text」ダイアログを開くには、オプションエディターを開---------------------------------|<--line end is here
き、「Text」セクションで「Text」ボタンをクリックします。
Other example:
プログラムツリーにウィンドウフォーカスが設定されていない場 <-- There should be no linebreak here.
合、[A]、、[C]、[D] のキーを使用してプログラムツリー内を移動できます。
Apart from the fact that we should justify the paragraphs for proper Japanese layouting, we don't know why this happens. We use a proper Japanese font (Meiryo [TTF]). Could this be an issue with Apache FOP?
I've already tried out Noto Sans CJK, an OTF which seems to work with the latest Apache FOP version, but the issues remain.
Is there a workaround for this, or has anybody else come across this issue?
Thanks,
Christina