FW: Whitepaper is ready for review

Title: Message

Hello 
all,

 

I 
updated the XLIFF 1.2 White Paper, along with input from those who volunteered 
to help, solicited at previous TC meetings.  

 

I took 
an initial pass, and Rodolfo provided some very good feedback.  I 
incorporated all of his suggestions.  But I was not able to update the list 
of applications supporting XLIFF in section 7.  This needs to be done, but 
I'm of the opinion that we could go ahead and ask the TC to approve the chairs 
to request a ballot for approval of XLIFF 1.2 as an OASIS standard (and the 
final updates to the White Paper could happen along the 
way).

 

Please 
feel free to offer suggestions to improve the White Paper.  I will raise 
the idea of initiating the OASIS ballot at the next TC meeting (October 16), and 
see if I can get Mary to check our readiness beforehand.

 

Thanks,

 

Bryan

 

  

  
-----Original Message-----
From: Rodolfo M. Raya 
  [mailto:] 
Sent: Thursday, September 27, 2007 
  7:11 AM
To: Schnabel, Bryan S
Cc: 
  ; 
  
Subject: Re: Whitepaper is ready for review 
  (RE: Whitepaper: Localisationvs. Localization)

On Tue, 
  2007-09-25 at 13:22 -0700,  wrote: 
  Hello 
    all, 
  
  I finally finished 
    bringing the whitepaper up-to-speed to work for XLIFF 1.2.  
    

Hi Bryan,

Thanks for updating the 
  white paper. I'm sure it required a lot of work.

Here are my initial 
  comments on the updated version:

OASIS has a new logo. The white-paper 
  has the old one in its front page.

The introduction makes me think that 
  XLIFF is only useful for software localisation. Although it may have started 
  as a project to simplify software localisation, it has evolved and is 
  perfectly usable in general translations, including any kind of documentation. 
  Notice that the charter in page 3 mentions that XLIFF specifications "support the entire localization process, and support common 
  software and document data formats and mark-up languages". A 
  paragraph explaining this achievement maybe important for the 
  introduction.

I think that it would be important to add a paragraph at 
  the end of section 2.4 mentioning that XLIFF 1.2 was approved as Committee 
  Specification in May 2007.

There are now many commercial and open 
  source filters that allow transforming different formats to XLIFF and back. A 
  list of document formats that can be translated using XLIFF maybe useful in 
  sections 4 or 5. The following document types are some of the formats that can 
  be directly processed using XLIFF:

  
    
Software Localisation: 
    
      
Windows C/C++ Resources (RC) 
      
Windows .NET Resources (ResX) 
      
Java .Properties 
      
Portable Objects (PO/POT) 
      
Binary resources (.exe and .dll) 
      
JavaScript/EcmaScript 
      
International Components of Unicode (ICU) Resource Bundle 
      
Oracle Business Applications 

    
Documentation: 
    
      
HTML 
      
FrameMaker (MIF) 
      
Adobe InDesign (INX) 
      
Microsoft Office 2007 
      
OpenDocument (OpenOffice/StarOffice) 
      
Rich Text Format (RTF) 
      
Generic XML 

    
Specialised XML Filters: 
    
      
DocBook 
      
DITA 
      
XHTML 
      
xml:tm 
      
Microsoft Word 2003 ML 

I'm sure that there 
  are more, but the above list is a good start to show that XLIFF can be used in 
  multiple scenarios. 

The list of applications supporting XLIFF in 
  section 7 is quite outdated. I can do some research and provide additional 
  information.

A link to latest specification should be added to the 
  appendix and probably to some of the initial sections.

These are the 
  basic details that may deserve attention. Hope these comments 
  help.

Best regards,
Rodolfo

OFF TOPIC:  the 
  TC charter may need a review and update.

  
    
    

      --
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.