Jump to content
Focx

Punctuation and justification in Japanese text

Recommended Posts

I'm currently trying to work with a Japanese text in two justified columns, which means there are bound to be many lines. Now, for some reason punctuation gets not treated as such, but gets bumped into the next line as if it were an ordinary character (see example). I've tried playing around with optical alignment to no avail and am a bit lost. Am I missing something or is this related to some quirk with Japanese?

Thanks in advance!

 

1233453683_ScreenshotofAffinityPublisherBeta(2019-05-0617-31-37).png.e3d16afa30d216a8659696869ffbeb06.png

Share this post


Link to post
Share on other sites
On 5/6/2019 at 10:35 AM, Focx said:

Am I missing something or is this related to some quirk with Japanese?

One quirk in Chinese (like your sample): every character, punctuation included, takes the same space. Like monospace fonts did in old typewriters. In your screenshot it appears not to work for ", 1", so it might be an issue with the used font. With for instance Songti SC there is more space between "," and "1":

2090213971_asianchinesesongticomma.jpg.cee66a2a44cb5a478692c4e8be30989b.jpg

Unfortunately it does not solve your issue completely, cause there should not be a line break before a comma. That's a difficulty reported already:

or here, too:
https://forum.affinity.serif.com/index.php?/topic/75274-missing-asian-punctuation-support/&do=findComment&comment=393325


macOS 10.12.6,  Macbook Pro 15" + Eizo 24"

Share this post


Link to post
Share on other sites

Concerning line breaks with narrow text frames AfPub behaves different to, for instance, InDesign:
Whereas in AfPub a line break may happen any time and allows to – simply by narrowing the frame width – one char per line, InDesign would just not show the text but overflow instead if the frame gets too narrow for its words, numbers included.

AfPub   vs.   InDesign:

1272051553_linebreaksafpub.jpg.003edc3a0392861ecdbcf082fc95235b.jpg    331766230_linebreaksindesign.jpg.03fb74a327655f0e4f7f22e912e21bc8.jpg


macOS 10.12.6,  Macbook Pro 15" + Eizo 24"

Share this post


Link to post
Share on other sites

Thanks for letting me know thomaso, it would be great to get that fixed. I agree, it's the line break before the comma that's the issue, because it happens regardless of whether there's a number after the comma or whether I use western or Japanese commas (, or 、).

Share this post


Link to post
Share on other sites
8 minutes ago, Focx said:

it's the line break before the comma that's the issue,

In your screenshot I see missing space, too. Between comma and 1950. – That might get fixed by yourself with another font.

p.s.: Chinese here, not Japanese ;)


macOS 10.12.6,  Macbook Pro 15" + Eizo 24"

Share this post


Link to post
Share on other sites

I tried adding a space behind a normal comma but it didn't change anything. Then I tried a full-width comma + space and it worked -- but not in another case in the same document. There I was able to fix it using the "spacing" -> "tighten more" function. Seems like a nice workaround!

Share this post


Link to post
Share on other sites
9 hours ago, Focx said:

Seems like a nice workaround!

In proper Chinese fonts both punctuation and syllable glyphs have same width ('Advance width').
(different to numbers, they are latin/arabic)

So such a workaround with manually added white spice to influence the apparence on (western) screen, can get risky if your layout file goes to China for text control or print production.


macOS 10.12.6,  Macbook Pro 15" + Eizo 24"

Share this post


Link to post
Share on other sites

Serif seem to be somewhat aware of this issue, but thus far have not found the urge and/or manpower to fix it.

For the time being, the lack of proper support for CJK punctuations/typesetting renders all Affinity products unusable to Asian/CJK users for any work that involves significant amounts of CJK textual content.

Cheers.

Share this post


Link to post
Share on other sites

FYI, most of software that can handle Asian text have an option to turn on/off Asian rule.
Dev team doesn't need to make them work in non-Asian language.
Asian users will turn on these feature explicitly when they need.
So it should be turned off by default.
Then it won't be confusing nor become a problem to non-Asian users.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.