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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-inline message

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


Subject: Requirement #13


Hi everyone,

To keep up our nice progress forward, let try to discuss #13 by email:

The current wording is:


"Should be able to represent a flow of text that, in the original format, was stored has a nested flow

For example, the value of the HTML ALT attribute is stored in the IMG tag that can be withing a paragraph:

<p>Click here: <img alt='OK' src='ok.png'/>.</p>

Another example: in ODF a footnote is stored at the location where the footnote reference is display when publishing."


I would propose few changes, something like:


"Must be able to represent separately different flows of text when, in the original format, they are mixed together.

Example 1: In DITA a footnote is stored at the location where it is referred to:

<p>Palouse horses<fn>A Palouse horse is the same as an Appaloosa.</fn> have spotted coats.</p>

This p element contains two separate flows: "Palouse horses have spotted coats" and "A Palouse horse is the same as an Appaloosa."

Example 2: The value of the HTML ALT attribute is stored in the IMG tag and can be within a paragraph:

<p>Click here: <img alt='OK' src='ok.png'/>.</p>


Cheers,
-ys




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