[xliff] Fw: [xliff-comment] XLIFF and resizing information

["Matthew.Lovatt" <Matthew.Lovatt@oracle.com>]



 

----- Original Message -----

From: Mark Levins/Ireland/IBM

To: Tony Jewtushenko

Cc: Matthew.Lovatt

Sent: Monday, January 06, 2003 4:45 PM

Subject: Fw: [xliff-comment] XLIFF and resizing information

Hi Tony,

I think we should address Nikolai's mail below and add it to the agenda for the next meeting. I also think his issues fit in with what Matt wants with 'reformatting'.

My own initial ideas around this are around adding the following elements, <font>, <coord>, <css-style>, <style> and <exstyle> as optional children of <source> and <target>. Adding these elements would address all of the other data that may be changed during the course of translating/localizing an XLIFF document and would also address the current inadequacy of XLIFF for non-textual translation as outlined in Nikolai's mail below.

In each of these new elements, when a child of a <source>, the 'reformat' attribute could be used to determine whether or not the information may be changed as part of the translation process.
We could also further define <coord> with child elements <x>, <y>, <width> and <height> or <x1>, <y1>, <x2> and <y2> for greater flexibility and let each of these also have the ability to specify formatability through the 'reformat' attribute.

I don't currently have time to formally draft any of this into schema or a concrete example but maybe it could form the basis for further discussion. Please let me know what you think.

Regards,

---

Mark Levins
IBM Software Group | Dublin Software Laboratory | Airways Industrial Estate | Cloghran | Dublin 17 | Ireland
Phone: +353 1 7046676 | IBM Tie Line 166676

---

----- Forwarded by Mark Levins/Ireland/IBM on 01/06/2003 04:11 PM -----

Nikolai Tsepalov <nikolait@earthlink.net>

12/21/2002 08:41 PM

To	xliff-comment@lists.oasis-open.org
cc
Subject	[xliff-comment] XLIFF and resizing information

Hi All,

 

I’m trying to understand how XLIFF should handle resizing information.

Let’s take for instance Windows resource dialog with NO caption and two controls, label and edit box. 

 

IDD_DIALOG1 DIALOG DISCARDABLE  0, 0, 96, 28

STYLE WS_POPUP | WS_CAPTION | WS_THICKFRAME

FONT 8, "MS Sans Serif"

BEGIN

    EDITTEXT        IDC_EDIT1,35,7,53,14,ES_AUTOHSCROLL

    LTEXT           "Label:",IDC_STATIC,13,9,23,8

END

 

All of them should be resized and only label should be translated.

 

With label I have no question: <trans-unit>contains text to translate in <source> element, coordinates in coord attribute.

Localized text locates in <target> element and Localized coordinates in <target>‘s coord attribute.

 

Edit box has no text to translate. What should I do? Create <source> and <target> elements with no text?

 

Dialog is grouping element and also has no text to translate. So logically dialog's coordinates go to <group>’s coord attribute,

but where locale version of dialog coordinates should be located? According to specification <group> should not have <target> node.

If I have to create additional translation unit to hold locale version of group's coordinates, that looks very inelegant.

 

In general, in my opinion <group> and <trans-unit> have a lot in common,

may be better to combine them together in one element and add some attribute like ‘container=true’?

 

Please let me know, especially in you have information about some RC <-> XLIFF converter.

 

Thanks,

Nikolai.