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: Re: [office] Text Object position


Florian Reuter wrote On 11/30/05 19:00,:
> Hi David,
>>>> I have a suggestion for an improvement in the way we specify the 
>>>> position of text objects (or even drawing objects in general).
>>>> What about saving their position (svg:x and svg:y) as redundant 
>>>> information, for applications that don't implement all the 
>>>> positioning capabilites of e.g. OOWriter?If the application reading 
>>>> this doesn't implement centering of inline elements
>>>> in paragraphs, the text box will be wrongly placed. Can we specify 
>>>> that the
>>>> initial application should save the x and y (relative to the page 
>>>> topleft corner),
>>>> so that less-advanced applications and conversion filters know where 
>>>> to place it?
> First I liked the idea, because its technically very easy to implement
> this feature.
> But thinking a little about this issue I would like to suggest a
> different way to approach the "high sophisticated layout mechanisms" in
> OpenDocument.
> Speaking from the point of a user we have an application A, which
> supports layout feature f and an application B, which doesn't. When
> writing the coordinates of f to the file, B could display the position
> of f correctly, but B is still not able to e.g. save it, modify it,
> recalculating it. In general I think writing the coordinates of f to the
> file will only delay the user problems.

Another problem is that the position of a text box may depend on other 
features that an application may support or not. If an application for 
instance does not support certain line spacing options, then the text may be 
distributed to pages differently than in the application that stored the 
position. For a paragraph anchored text box using a page position may than 
lead to an entirely wrong result.

And there in another problem: What happens if an application does not 
calculate the position of text boxes at all, for instance because it does not 
display the document to the user?


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