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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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


Subject: RE: [xliff] Possible additional optional attribute for helping word-count


Mtg: This needs to be discussed later.



>  -----Original Message-----
> From: 	Yves Savourel [mailto:ysavourel@translate.com] 
> Sent:	Tuesday, April 16, 2002 2:09 PM
> To:	xliff@lists.oasis-open.org
> Subject:	[xliff] Possible additional optional attribute for helping
> word-count
> 
> Hi,
> 
> Related to the topic of counting, there is one aspect where we could add
> an attribute to help tool process the text more efficiently.
> 
> Currently when processing a <source> or a <target> element there is no way
> to know how an inline code such as <bpt>, or <x/> should affect the word
> breaking. While the majority of original codes are most likely not to be
> seen as separator (.e.g. <b>...</b> in HTML) a few are word breaker (e.g.
> <br/>).
> 
> It may be useful to have an additional optional attribute in <bpt>, <it>,
> <ph>, <g/>, <x/>, <bx/>, and <ex/> to indicate whether the code should be
> considered a word separator or not.
> 
> Something like word-break="yes|no" (or 'wb' to keep with the short name
> tradition). The default would be "no". For example:
> 
> <source>Line one<ph id="1" wb="yes">\n</ph>Line two</source>
> 
> 
> Cheers,
> -yves
> 


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


Powered by eList eXpress LLC