Re: [xliff] RE: a future use for XLIFF?

I think this is a good use case  that I would call

dev-English->proper-English

dev-languageX->proper-langaugeX

But IMHO this use case is well covered with the current spec.

It can be done in full compliance, as BCP 47 allows for usage of private language tags.

And this really IS a source & target situation. You actually do not need to add anything, because it is a separate roundtrip that does not have specific feature requirements.

However there is a similar but different group of use cases that LRC/SOLAS has been trying to push, which is attractive mainly for companies who have their whole resource cycle in XLIFF such as Oracle. BTW XLIFF as full content life-cycle format was one of 2.0 considered features, proposed by Christian, but dropped because we failed to find a champion for it after Christian left the TC.

I see two main use cases in this group

1) Source pre-editing for MT

2) Continuous source quality assurance as part of the full XLIFF content cycle

And this I think would need a module to allow for it in an interoperable way

Cheers

dF

Dr. David Filip

=======================

LRC | CNGL | LT-Web | CSIS

University of Limerick, Ireland

telephone: +353-6120-2781

cellphone: +353-86-0222-158

facsimile: +353-6120-2734

mailto: 

On Thu, Sep 5, 2013 at 11:30 PM, Kevin O'Donnell <> wrote:

Thanks for sharing Bryan. I think it’s definitely a good use case for XLIFF. I’ve seen similar examples where “dev English” was ‘localized’ into “content writer English” using proto-localization techniques.

 

From:  [mailto:]
On Behalf Of Schnabel, Bryan S

Sent: Thursday, September 5, 2013 2:54 PM

To: 

Subject: [xliff] a future use for XLIFF?

 

Interesting thing happened at the office today . . .

 

One of my colleagues approached me with a problem (I’ll paraphrase). “I need to send a file to somebody who wants to suggest editorial changes to a few of our web pages. Can we export our web pages to word processor file, spreadsheet, or
 some simple XML format?”

 

Since we use a Web CMS, and do not have static pages, there really was no easy way I could think of. Doing a view source, then saving to file, then opening with a word processor resulted in way too much clutter.

 

So just for the fun of it, I used our Drupal XLIFF module and exported a few XLIFF files, and sent them.

 

My colleague was delighted. “What a wonderful format! We can leave the source text intact, and enter our suggestions in the target field! Perfect!”

 

Could this be a future XLIFF 2.X module someday? XLIFF without the L?