MHonArc v2.5.0b2 -->
















xliff message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: HTML Profile - restype values




From: "Yves Savourel" <ysavourel@translate.com>
To: "XLIFF Main List" <xliff@lists.oasis-open.org>
Date: Thu, 18 Mar 2004 11:21:04 -0700






Hi everyone,

Bryan and I thought we could work more efficiently if we were posting
directly some of the question we are running into while working on the
HTML->XLIFF representation.

So, we'll start a few threads. Here is the first:


======================================== QUESTION:

What should be the restype values of HTML content?

--- HTML Source Example:

<p>Text</p>

--- Discussion:

While some parts of HTML content have corresponding restype values in the
current XLIFF 1.1 (for examnple: table, row, etc. there are many others that
do not, and there are cases where the current values are not enough (e.g.
h1, h2, h3, etc. cannot be all mapped to 'heading'?).

So, what could be a solution for the attribute values not supported?

--- Possible Solutions:

A) Come up witha new attribute (using the extension point) of a new
namespace that would allows us to create a whole list of HTML-specific info:

<trans-unit id='1' xlfhtm:type='h1'>
....</trans-unit>

But then XLIFF's restype would be unused.

B) Define a list of extended values for restype, following a logcal pattern.
For example, something like:

x-html-nameofelement[-nameofattribute]

that will give you:

restype='x-html-p'
restype='x-html-p-title'
restype='x-html-img-alt'
restype='x-html-h1'
...

But then should we use that mechanism too for the HTML parts that do have a
match in the current restype values? For example: restype='x-html-table' or
restype='table'

















[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]