Profile

Forgot to mention, the ULI stuff is sentence level only. I personally think we should stay away from standardizing XLIFF segmentation behavior and let the data drive the appropriate behavior where the users see fit. I don't know if that's what you meant below though. From: "Schnabel, Bryan S" ...

Another source of exception is http://unicode.org/uli/trac/changeset/48 from Unicode Consortium. The exception data is mostly based on dbPedia ( http://www.dbpedia.org ) with vetting from IBM and Microsoft. The implementation is included in ICU 53 as tech preview and will be released as part of main ...

This looks good, the only observation is that unlike Unicode, there is always some change/addition to the standard, XLIFF may not and need not update as rapidly. Unless we have a major theme (that benefits most of the participants) to focus on for the next few years, this may not be as easy ...

Sorry, forgot to include the PDF: From: Helena S Chapman/San Jose/IBM To: xliff@lists.oasis-open.org Date: 04/30/2014 12:18 PM Subject: Fw: Please find a pdf attached. FYI. I received this by the way of Unicode Consortium recently. Feel free to agree or disagree with my resposne. I do have a question ...