OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (OFFICE-4030) Bottom to top, left to right writing direction


    [ https://issues.oasis-open.org/browse/OFFICE-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=78193#comment-78193 ] 

Patrick Durusau commented on OFFICE-4030:
-----------------------------------------

Regina commented on the email list:

*****

we need a decision about the way to go.
Problem is that the OOXML text vertical types "vert" and "vert270"
cannot be expressed in ODF and simple enabling bt-lr from XSL (as in
the proposal) does not solves the problem.

*****

To capture my response on the mailing list, so we don't have to hunt for it:
I'm assuming the following types (from the fifth edition) are at issue:

*****20.1.10.83 ST_TextVerticalType (Vertical Text Types)*****

eaVert (Vertical Text Type Enum ( East Asian Vertical )) A special
version of vertical text, where some fonts are displayed as if rotated
by 90 degrees while some fonts (mostly East Asian) are displayed vertical.

horz (Vertical Text Type Enum ( Horizontal )) Horizontal text. This
should be default.

mongolianVert (Vertical Text Type Enum ( Mongolian Vertical )) A special
version of vertical text, where some fonts are displayed as if rotated
by 90 degrees while some fonts (mostly East Asian) are displayed
vertical. The difference between this and the eastAsianVertical is the
text flows top down then LEFT RIGHT, instead of RIGHT LEFT

vert (Vertical Text Type Enum ( Vertical )) Determines if all of the
text is vertical orientation (each line is 90 degrees rotated clockwise,
so it goes from top to bottom; each next line is to the left from the
previous one).

vert270 (Vertical Text Type Enum ( Vertical 270 )) Determines if all of
the text is vertical orientation (each line is 270 degrees rotated
clockwise, so it goes from bottom to top; each next line is to the right
from the previous one).

wordArtVert (Vertical Text Type Enum ( WordArt Vertical )) Determines if
all of the text is vertical ("one letter on top of another").

wordArtVertRtl (Vertical WordArt Right to Left) Specifies that vertical
WordArt should be shown from right to left rather than left to right.

**********

Reading the definitions, yes, enabling bt-lr from XSL doesn't solve the
problem of peculiar definitions in OOXML but it would solve the issue
for such languages more generally. At least until more guidance is
issued from the W3C on rendering of CJK languages in texts.

Noting that eaVert and montolianVert are too vague to be meaningfully
mapped, "where some fonts are displayed as if rotated by 90 degrees
while some fonts (mostly East Asian)" makes no sense. I have no way to
know or specify "some fonts."

As far as vert top-bottom, left to right and vert270 bottom-top, right
to left, should we take guidance from 7.29 Writing-mode-related
Properties, 
[https://www.w3.org/TR/xsl/#writing-mode-related]
 (XSL 1.1)
and not invent new terminology for it?

Thinking that if we add writing-style elements sufficient to define
character styles (perhaps within the standard) that represent common
character orientations, leaving odd cases to user to define, wouldn't
that give a target for mapping OOXML vert and vert270?

Realize the present proposal may be inadequate but if the larger issue
is solving style mappings from OOXML, let's gather those requirements up
and define them.
So clearly the present proposal is inadequate.

I am moving the present "proposal" to description and leaving proposal blank until we have a full proposal for consideration by the TC.

Â

> Bottom to top, left to right writing direction
> ----------------------------------------------
>
>                 Key: OFFICE-4030
>                 URL: https://issues.oasis-open.org/browse/OFFICE-4030
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: New Feature
>          Components: Paragraph
>            Reporter: Andras Timar
>            Priority: Minor
>             Fix For: ODF 1.4
>
>




--
This message was sent by Atlassian Jira
(v8.3.3#803004)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]