<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1688946848;
mso-list-template-ids:-1169396300;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I think there are two schools/options and the use of the words “only valid” is … well … not valid.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Korean *<b>can</b>* be set with only breaks at spaces. However, this should be (and never is) used with justification as it would lead to terrible results.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I believe it is optional to allow breaking only at spaces, not “only valid”.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>You would note text like this in the Unicode Line Breaking standard … note the use of “commonly” and not the use of “mandatory”:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>“</span>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.”<span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>At any rate, I have forwarded the request into our team for additional comments.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>Kevin Brown<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>Executive Vice President, Sales & Marketing RenderX, Inc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>(650) 327-1000 Direct<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>(650) 328-8008 Fax<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>(925) 395-1772 Mobile<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'>skype:kbrown01<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'><a href="mailto:kevin@renderx.com">kevin@renderx.com</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'><a href="mailto:sales@renderx.com">sales@renderx.com</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:#1F497D'><a href="http://www.renderx.com">http://www.renderx.com</a> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Xep-support [mailto:xep-support-bounces@renderx.com] <b>On Behalf Of </b>Simcha Gralla<br><b>Sent:</b> Monday, August 11, 2014 12:18 PM<br><b>To:</b> RenderX Community Support List<br><b>Subject:</b> [xep-support] Re: Line breaking rules for Korean.<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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 </span><a href="http://msdn.microsoft.com/en-us/goglobal/bb688158.aspx#EED"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>http://msdn.microsoft.com/en-us/goglobal/bb688158.aspx#EED</span></a><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Simcha Gralla<br>IBM Authoring Tools development<br>Brookfield, CT</span><o:p></o:p></p><p class=MsoNormal><br><tt><span style='font-size:10.0pt'>Daniel Boughton <<a href="mailto:daniel.r.boughton@rrd.com">daniel.r.boughton@rrd.com</a>> wrote on 2014-08-11 14:59:44:</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><br><tt>> From: Daniel Boughton <<a href="mailto:daniel.r.boughton@rrd.com">daniel.r.boughton@rrd.com</a>></tt></span><br><tt><span style='font-size:10.0pt'>> To: RenderX Community Support List <<a href="mailto:xep-support@renderx.com">xep-support@renderx.com</a>></span></tt><br><tt><span style='font-size:10.0pt'>> Date: 2014-08-11 15:00</span></tt><br><tt><span style='font-size:10.0pt'>> Subject: [xep-support] Line breaking rules for Korean.</span></tt><br><tt><span style='font-size:10.0pt'>> Sent by: "Xep-support" <<a href="mailto:xep-support-bounces@renderx.com">xep-support-bounces@renderx.com</a>></span></tt><br><tt><span style='font-size:10.0pt'>> </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> XEP currently groups Chinese, Japanese, and Korean together in it's </tt><br><tt>> line-breaking rules. Our translation team is telling us the Korean </tt><br><tt>> should be treated differently than Chinese and Japanese and that it </tt><br><tt>> is only valid to break at space characters.</tt></span><br><tt><span style='font-size:10.0pt'>> </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> I was wondering if anyone else out there has encountered this, and </tt><br><tt>> how you have handled it using XEP.</tt></span><br><tt><span style='font-size:10.0pt'>> </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> Thanks</tt></span><br><tt><span style='font-size:10.0pt'>> -- </span></tt><br><tt><span style='font-size:10.0pt'>> __________________________________________________________________________________</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> Daniel Boughton | Technical Analyst | RR Donnelley</tt><br><tt>> 655 Brighton Beach Rd | Menasha, WI 54952 </tt><br><tt>> Office: 920.751.7603 | Cell: 920.450.3581 | Fax: 920..751.7686</tt><br><tt>> <a href="mailto:daniel..r.boughton@rrd.com">daniel..r.boughton@rrd.com</a></tt><br><tt>> <a href="http://www.rrdonnelley.com">http://www.rrdonnelley.com</a></tt></span><br><tt><span style='font-size:10.0pt'>> </span></tt>!DSPAM:87,53e916e310101584813245! <o:p></o:p></p></div></body></html>