AW: [All] high level use cases not yet ready to publish, please have another look - LibreOffice/init/Sebastian -

Hi Christian,

Unfortunately I have no valid user rights to modify the WIKI.  (Having a W3C account but not being in a W3C working group).
Can you please change the high level wiki entry for us to:
2.17.1 Description
The tool - ILO - ITS for Libre Office Writer Extension (ILO)  allows the use of a subset of ITS 2.0 in an open source word processing software (Libre Office).

  *   The tool - ]init[ ITS Libre Office Writer Extension (IILOW)- allows the use of a subset of ITS 2.0 in an open source word processing software (Libre Office).
  *   Capabilities include:

  1.  Tagging phrases and terms as "not to translate" (translate)
  2.  Tagging words for a specific locale only (locale filter)
  3.  Providing additional information for the translator (localization note)
  4.  Tagging words as "term" (terminology)

  *   The Libre Office extension and its software packages allows users to

  1.  Load ITS 2.0 annotated XML files (ODT, XLIFF)
  2.  Visualize ITS 2.0 metadata in the WYSIWYG editor of Libre office
  3.  Edit text related to the chosen subset of ITS 2.0 meta data
  4.  Save and export the text and including ITS 2.0 markup into the original file format (ODT, XLIFF)

2.17.2 Data category usage

  *   Terminology - One or several words can be marked up as a "term"
  *   Translate - Mark content as "to translate" and "not to translate"
  *   Localization Note - Pass a message (information, alert) to human agents (such as translators)
  *   Locale Filter - Limit content to specific locales
2.17.3 More Information and Implementation Status/Issues
ILO uses OKAPI capabilities for XLIFF handling and will be available in April 2013. The use of ILO will be presented on the 12th of March 2013 in Rome. The results of ILO development will be given back to the public domain under the open licenses LGPL V3 (same as Libre Office).
Thank you in advance,
Sebastian
PS: I thought it is a high level view on the thing so I did not provide too much details. If you will need them, of course, here they are:

  *   Detailed:
  *   Running software: Libre Office Writer 3.6.X
  *   Source code: Java
  *   General documentation: Installation guide, Developer's guide

Von: Lieske, Christian [mailto:christian.lieske@sap.com]
Gesendet: Montag, 4. März 2013 10:27
An: Sklarß, Sebastian (init)
Cc: public-multilingualweb-lt@w3.org
Betreff: RE: [All] high level use cases not yet ready to publish, please have another look - LibreOffice/init/Sebastian -

Hi Sebastian,

While editing the section on "Word Processing" the following specific questions came up. Hopefully, it is alright to contact you with them ...


1.      Did I revise the "description" properly?


2.      Did I revise the "data category use" properly?


3.      Do you have information for the following?

  *   Detailed:
  *   Running software:
  *   Source code:
  *   General documentation:
Thanks in advance for your help.

Of course, you are welcome to modify my current draft to come up with an enhanced version:

http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_level_summary#ITS_2.0_in_word_processing_software

Cheers,
Christian

From: Felix Sasaki [mailto:fsasaki@w3.org]
Sent: Saturday, February 16, 2013 2:34 AM
To: public-multilingualweb-lt@w3.org<mailto:public-multilingualweb-lt@w3.org>
Subject: [All] high level use cases not yet ready to publish, please have another look

Hi all, esp. Christian,

I had a brief look at
http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_level_summary
and I think this is not yet ready even for a first public working draft.

I won't point to specific sections here, but please have another look at "your" section with the following in mind:

- Don't mention something that is not in the spec anymore, e.g. "Disambiguation". Call this "Text Analysis Annotation".
- The "More Information and Implementation Status/Issues" sections are extremely heterogenous. Please, re-write them following this simple pattern taken from ENLASO:


[

Tool: Okapi Framework (ENLASO).

  *   Detailed slides at http://tinyurl.com/8tmg49d
  *   Running software: http://code.google.com/p/okapi/downloads/list
  *   Source code: http://code.google.com/p/okapi/source/browse/
  *   General documentation: http://www.opentag.com/okapi/wiki/
]

- Don't just "list" data categories. Describe their benefit in your implementation.
- Use a simple & sweet language style like e.g. in
http://www.w3.org/International/multilingualweb/lt/wiki/Use_cases_-_high_level_summary#Simple_Machine_Translation


The document should be a *high level* overview. Currently it has 20 pages - that's too long. We can provide details & more text in other publications.

NOTE for the EC project folks: this document is an important part for us to raise awareness for Rome and to give input for the Luxembourg review. Please invest the time to take above considerations into account.

Please, do that by Tuesday EOB 19 February.

Christian, what are your thoughts on editing this and making this ready for publication, also in terms fo timing.

Best,

Felix