- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Feb 2017 17:47:02 +0000
- To: public-i18n-archive@w3.org
r12a has just created a new issue for https://github.com/w3c/clreq:
== How does line start/end overflow work for romanised phonetic
annotations? ==
The following is my understanding of the jLReq rules for dealing with
situations where an annotation would otherwise protrude outside a
line start or end. Are the Chinese rules the same or different? (In
either case, it would be useful to say something in cLReq, i think.)
---
_Is the annotation longer than the base text?_
NO There’s no problem to solve here. Stop.
YES Carry on.
_Is the annotation wanting to extend beyond the line start or end?_
NO You need to use rules about overhang, rather than
these. Stop.
YES Carry on.
_You have two choices:_
1. FLUSH Both annotation and base are aligned with line end.
The annotation is aligned with the start of the base (_katatsuke_).
2. OFFSET The base is moved away from the line end. The
annotation is aligned with the middle of the base (_nakatsuke_).
In either case, the bit of the annotation that overflows the base on
the inside of the line will need to be positioned relative to the
adjacent base characters using the rules for overhang (which are
described elsewhere).
_Did you choose FLUSH when there are multiple base characters for the
annotation (ie. group ruby)?_
NO You’re ok. Stop.
YES You should spread out the base characters, using equal
amounts of space.
Please view or discuss this issue at
https://github.com/w3c/clreq/issues/128 using your GitHub account
Received on Wednesday, 15 February 2017 17:47:09 UTC