[OASIS Issue Tracker] Commented: (OFFICE-3356) Public Comment:Please standardize "Line Start Prohibition Rule"

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/OFFICE-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21831#action_21831 ] 

Dennis Hamilton commented on OFFICE-3356:
-----------------------------------------

I nosed around and note that there are Unicode Characters that may be adaptable to these purposes, especially NO-BREAK SPACE, WORD JOINER, and ZERO WIDTH NO-BREAK SPACE:

U+0083 NO BREAK HERE (a control whose function is apparently defined in ISO/IEC IS 6429:1992 and may not be related to layout)
U+00A0 NBSP, NO-BREAK SPACE
U+2060 WORD JOINER (the recommended way of doing this, if a non-breaking space can't be used and if U+FEFF is undesirable)
U+FEFF ZERO WIDTH NO-BREAK SPACE (the historical way of doing this, although not to be used on the front of a stream (where it is a byte-order-mark)

In this way, it would be up to a word-processor that was adapted to conventions of a particular language to insert the appropriate marks.  This would allow the text to be rendered properly even by an application that does not support such entry and is not designed to implement correct markup from its editing.

> Public Comment: Please standardize "Line Start Prohibition Rule"
> ----------------------------------------------------------------
>
>                 Key: OFFICE-3356
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3356
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Needs Discussion, Public Review, Text
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Robert Weir 
>            Priority: Blocker
>             Fix For: ODF 1.2 CD 06
>
>
> Copied from office-comment list
> Original author: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp> 
> Original date: 16 Aug 2010 09:49:25 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/201008/msg00004.html
> Text copied for convenience in searching JIRA (note that Unicode may be garbled):
> """
> Open Office appear to support "line-start prohibition rule", and even
> allows document authors to specify which character is prohibited.
> This rule is considered very important in Japan, China, Taiwan, and
> Korea.
> http://www.w3.org/TR/2009/NOTE-jlreq-20090604/#en-subheading2_1_7
> If you explicitly specify which character is prohibited, the following
> is generated by OO.o as part of setting.xml.
>       <config:config-item-map-indexed config:name="ForbiddenCharacters">
>         <config:config-item-map-entry>
>           <config:config-item config:name="Language" config:type="string">ja</config:config-item>
>           <config:config-item config:name="Country" config:type="string">JP</config:config-item>
>           <config:config-item config:name="Variant" config:type="string"/>
>           <config:config-item config:name="BeginLine" config:type="string"
>             >!%),.:;?]}¢°’”‰′″℃、。ã€...〉》」』ã€'〕ぁぃã...ぇぉっゃã‚...ょゎ゛゜ゝゞァィゥェォッャュョヮヵヶ・ーヽヾ！ï¼...），．：；？］｝｡｣､･ｧｨｩｪｫｬｭｮｯｰﾞﾟ¢</config:config-item>
>           <config:config-item config:name="EndLine" config:type="string"
>             >$([Â¥{£¥‘“〈《「『【ã€"＄（［｛｢£￥</config:config-item>
>         </config:config-item-map-entry>
> However, their semantics is not at all described in ODF 1.0.  It is not 
> described in the current draft of ODF 1.2 either.  Please standardize
> them.  Otherwise, ODF 1.2 does not contribute to interoperability 
> of Japanese text.
> """

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira