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] Working Draft - explicit statement on inheritance

Hi Yves,

I wonder if we are lacking an explicit statement about inheritance
in the XLIFF WD. I am thinking along the lines of the statements
in XML 1.0 related to 'xml:space' and 'xml:lang' (sth. like 'valid
for all subelements as well unless overridden').


I want to set a kind of default for the maximum length of a trans-unit.


 <group maxwidth="255">
  <trans-unit id="1" resname="news2" restype="button" maxwidth="50">
   <source xml:lang="DE-DE">Drucktaste</source>
  <!-- ... other <trans-unit> would inherit the maxwidth
  defined for <group> -->


This approach only works if inheritance really applies.

-----Original Message-----
From: Yves Savourel [mailto:ysavourel@translate.com]
Sent: Freitag, 12. Juli 2002 21:50
To: XLIFF list
Subject: [xliff] Working Draft

Hi everyone,

Here is an updated version of the working draft for 1.1. The zip file
includes the schema for the core and the values.

I didn't include the proposal for <reformat> nor <tool> in it yet.

I'm still looking into how to allow extending attribute values. I suppose
you can define your own list of types and import the pre-defined one, but
that is akward for validation. It would be nice to fine a way to have to
change only imported files, so the reference to the main XSDs would remain
the same regardless whether or not you have your own extension.
I hope some of you have ideas for this, because I can see I'm running out...

Have a great week-end

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

Powered by eList eXpress LLC