By *can* I meant that I do not believe the specification says *must be*, it clearly says things like “commonly used.”
As stated in the spec, there are two ways one can format documents in Korean:
a) space/punctuation-based line ending rules only or
b) using space/punctuation and syllable-breaking rules
It makes no indication that either is wrong. It is a preference (not mandatory).
RenderX likely chooses “b” because “b” has been acceptable in all cases (at least you are first to report it) and “a” would most certainly be incorrect for justified text.
I do not believe you can change this behavior in any way, this is core to the engine itself. And in fact, even if one could change it, it would be required to change it line by line, para/table-cell entry by another as if you have justified text anywhere, you would need to use “b”. Now, perhaps this is because your translators are the ones pointing this out.
Note the two rules they have and they do not make a distinction whether one or the other is correct. They merely tell you that if you have “b”, do not use ragged right layout, use justified text. Otherwise use “a”. They certainly do not state “b” is wrong.
Kevin
From: Daniel Boughton [mailto:daniel.r.boughton@rrd.com]
Sent: Monday, August 11, 2014 1:03 PM
To: Kevin Brown; RenderX Community Support List
Subject: Re: [xep-support] Re: Line breaking rules for Korean.
Kevin:
Just wondering what you meant by "Korean *can* be set with only breaks at spaces." Is that something that is currently available or something that could be implemented in a future release?
On Mon, Aug 11, 2014 at 2:22 PM, Kevin Brown <kevin@renderx.com> wrote:
I think there are two schools/options and the use of the words “only valid” is … well … not valid.
Korean *can* be set with only breaks at spaces. However, this should be (and never is) used with justification as it would lead to terrible results.
I believe it is optional to allow breaking only at spaces, not “only valid”.
You would note text like this in the Unicode Line Breaking standard … note the use of “commonly” and not the use of “mandatory”:
“Korean makes use of both styles of line break. When Korean text is justified, the second style is commonly used, even for interspersed Latin letters. But when ragged margins are used, the Western style (relying on spaces) is commonly used instead, even for ideographs.”
At any rate, I have forwarded the request into our team for additional comments.
Kevin Brown
Executive Vice President, Sales & Marketing RenderX, Inc.
(650) 327-1000 <tel:%28650%29%20327-1000> Direct
(650) 328-8008 <tel:%28650%29%20328-8008> Fax
(925) 395-1772 <tel:%28925%29%20395-1772> Mobile
skype:kbrown01
kevin@renderx.com
sales@renderx.com
From: Xep-support [mailto:xep-support-bounces@renderx.com] On Behalf Of Simcha Gralla
Sent: Monday, August 11, 2014 12:18 PM
To: RenderX Community Support List
Subject: [xep-support] Re: Line breaking rules for Korean.
That doesn't sound like the rules as I learned them. Most Korean documents can break between all Hangul characters with the exception that there are characters defined to not be left alone at the start or end of the line. Among other places describing this, there's <http://msdn.microsoft.com/en-us/goglobal/bb688158.aspx#EED> http://msdn.microsoft.com/en-us/goglobal/bb688158.aspx#EED
Simcha Gralla
IBM Authoring Tools development
Brookfield, CT
Daniel Boughton <daniel.r.boughton@rrd.com> wrote on 2014-08-11 14:59:44:
> From: Daniel Boughton <daniel.r.boughton@rrd.com>
> To: RenderX Community Support List <xep-support@renderx.com>
> Date: 2014-08-11 15:00
> Subject: [xep-support] Line breaking rules for Korean.
> Sent by: "Xep-support" <xep-support-bounces@renderx.com>
>
> XEP currently groups Chinese, Japanese, and Korean together in it's
> line-breaking rules. Our translation team is telling us the Korean
> should be treated differently than Chinese and Japanese and that it
> is only valid to break at space characters.
>
> I was wondering if anyone else out there has encountered this, and
> how you have handled it using XEP.
>
> Thanks
> --
> __________________________________________________________________________________
> Daniel Boughton | Technical Analyst | RR Donnelley
> 655 Brighton Beach Rd | Menasha, WI 54952
> Office: 920.751.7603 | Cell: 920.450.3581 | Fax: 920..751.7686
> daniel..r.boughton@rrd.com
> http://www.rrdonnelley.com
> !DSPAM:87,53e916e310101584813245!
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html
-- __________________________________________________________________________________ Daniel Boughton | Technical Analyst | RR Donnelley 655 Brighton Beach Rd | Menasha, WI 54952 Office: 920.751.7603 | Cell: 920.450.3581 | Fax: 920.751.7686 <http://inside.rrd.net/insiderrd/pages/google/rrd_google_signature.aspx> daniel.r.boughton@rrd.com <http://www.rrdonnelley.com/> http://www.rrdonnelley.com
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html
Received on Mon Aug 11 20:47:35 2014
This archive was generated by hypermail 2.1.8 : Mon Aug 11 2014 - 20:47:36 PDT