[OASIS Issue Tracker] Commented: (OFFICE-1599) Editor Note: Section17.224 draw:text-areas

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

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

Patrick Durusau commented on OFFICE-1599:
-----------------------------------------

OK, now I think I see the problem. 

The draw:areas attribute appears on a <draw:enhanced-geometry> element. The <draw:enhanced-geometry> element specifies the outline of a custom shape (being a child of a <draw:custom-shape> element. 

If there is no draw:areas attribute, then text is place in whatever shape has been defined by the <draw:enhanced-geometry> element.

OK, but the draw:areas attribute can define one or more text areas.

If one text area: Text, whether vertical or not, appears in the text area.

If two text areas, horizontal text in first area, vertical text in the second area. 

Question: How are styles associated with the respective text areas to determine whether the text is horizontal or vertical? (Assuming that it is via draw styles that such information is being passed.)

Second question: Since more than two text areas can be defined, is any vertical text always in the second text area? How would I assign text to a third or fourth text area?



> Editor Note: Section 17.224 draw:text-areas

> --------------------------------------------
>
>                 Key: OFFICE-1599
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1599
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>             Fix For: ODF 1.2
>
>
> Transcribed from ODF_Revised_Editorial_Notes_27May2009.odt
> Original author: Patrick Durusau
> Section 17.224 draw:text-areas
> Ed. Note As defined, the attribute is inconsistent and incomplete. It starts by saying we define a list of text areas. Then it says what happens if a second text area is present. Then we define how to define a text area. As a string? So, we don't have a list, or at least no mechanism for one, possibly assume up to two text areas, and don't define what values define a text area. 
> Sven Jacobi says:
> textareas::= textareasequence? 
> textareasequence ::= textarea ( ' '+ textareasequence )* 
> textarea::= position ' '+ position ' '+ position ' '+ position 
> position::= formula | modifier | number 
> formula::= '?' name 
> modifier::= '$' integer 
> number::= sign? float | sign? integer 
> float::= fractional exponent? | integer exponent 
> fractional::= integer? '.' integer | integer '.' 
> exponent::= ( 'e' | 'E' ) sign? integer 
> sign::= '+'| '-' 
> integer::= [0-9]+ 
> name ::= [^ ]+ 
> Patrick: Yes, but the prose requires:
> "If a second text area is available it is used for vertical text." 
> Noting that the first text area being for horizontal text is only by implication. 
> Nor it is clear how more than two areas (assuming the regex were extended to include what is said in the prose) are to be positioned. 
> If this is meant to simply specify the position of one or more text areas in some defined coordinate space (represented by a <draw:enhanced-geometry> element) then why don't we simply say that? 
> Sven Jacobi further replies: 
> "If text in a shape is drawn and there is no draw:text-areas element, then entire area of the shape is used. 
> If the draw:text-areas element is available, then with one exception the first text area is used. And this is the 
> exception, if the text is verical and if a second text area is available, the second text area is used. 
> I am not sure if it is sensible do to specify a limitation of 2 rectangles, I thought it is sufficient without." 

-- 
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