Yes, I can see where
<g> could be interpreted as containing only non-translatable codes.
I based my use of
them on the HTML profile document (see below).
I’ve copied the rest
of the XLIFF cmte for their input.
Should the HTML
profile be revised to use bpt/ept instead of <g> for inline
cases, inline elements are very well suited to be mapped to <g>. The
value of their
ctype attribute should be a
concatenation of '
x-html-' and the name of the
element (in lowercase). For example:
<b> would be
<p>In Portland, Oregon one may
<i>ski</i> on the mountain, <b>wind surf</b> in the
gorge, and <i>surf</i> in the ocean, all on the same
<source xml:lang='en'>In Portland,
Oregon one may <g id='i1' ctype='x-html-i'>ski</g> on the
mountain, <g id='i1' ctype='bold'>wind surf</g> in the gorge, and
<g id='i1' ctype='x-html-i'>surf</g> in the ocean, all on the same
M. Raya [mailto:email@example.com]
Sent: Monday, March 06, 2006 7:01
Subject: Re: How to
translate text within G tags?
As far as I know,
<g> elements contain inline codes, not translatable
>From the specs: http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm#g
Generic group placeholder - The
<g> element is used to
replace any inline code of the original document that has a beginning and an
end, does not overlap other paired inline codes, and can be moved within its
parent structural element.
To me, this means that <g> is
used to wrap moveable inline code and for "inline code" I understand tags
inherent to the formatting of the document, i.e. "\i" and "\i0" to mark start
and end of italics in RTF or "<i>" and "</i>" for the same purpose
in HTML. IMO, only the formatting portion can be enclosed in <g>. Notice
that <g> cannot contain any <sub> element with translatable text
In your example I would enclose the text "no need to download
again in a <bpt>/<ept> pair.
According to the introduction
of the specs, XLIFF "borrows" elements from TMX and you can read a clear
example of handling italics in TMX at http://www.lisa.org/standards/tmx/tmx.html#ContentMarkup_Rules
you consider <g> as a black box with translatable text that can be
moved, the translatable text that it contains may end at any location in the
translated segment. The result can be horrible.
Think on RTF documents
that when converted to XLIFF contains tags in the middle of a word in the
source text. Most of the times those tags are originated in change tracking
and signal the correction of a spelling error. Translators usually place those
tags at the end of the segment or after the corresponding word in their
translations but never in the middle of the equivalent word in the target
language. This is the typical use case for <g> tags.
On Mon, 2006-03-06 at 17:20 -0500, Doug Domeny
with the XLIFF Editor, I couldn’t find a way to translate text between
How would a
translator translate the phrase “not need to download
state="needs-translation">Before you can use
eWebEditPro, it must be downloaded into your browser. When you click the
Now</g>button at the bottom of
this page, eWebEditPro will be automatically downloaded and installed. This
process may take several minutes depending on the speed of your network
connection. Once downloaded, eWebEditPro will <g
ctype="italic">not need to
download again</g> unless upgrading to a
+1 603 594-0249
The information in this e-mail is
intended strictly for the addressee, without prejudices, as a
confidential document. Should it reach you, not being the
addressee, it is not to be made accessible to any other
unauthorised person or copied, distributed or disclosed to any
other third party as this would constitute an unlawful act under
certain circumstances, unless prior approval is given for its
transmission. The content of this e-mail is solely that of the
sender and not necessarily that of Heartsome.