RE: Updated script for intro video

Thank you Arle, I really appreciate.

 

WICS tools are great; I think that we will do a lot with this further down
the line, so please mention WICS project.

 

I would be very grateful if Logrus would be mentioned as well, but WICS is
already good.

 

Regards,

Serge

 

 

 

 

From: Arle Lommel [mailto:arle.lommel@dfki.de] 
Sent: Monday, November 04, 2013 11:45 AM
To: Serge Gladkoff
Cc: Olaf-Michael Stefanov; Stephan Walter; Multilingual Web LT Public List
Public List; Nieves Sande
Subject: Re: Updated script for intro video

 

Hi Serge,

 

For the intro video, that would be too much text, but I’ll make sure that
WICS is mentioned onscreen and with functionality in the prose.

 

We’ll be working on the script today so it will be added.

 

Best,

 

Arle

 

 

On 2013 Nov 3, at 19:39 , Serge Gladkoff <sgladkoff@logrus.ru> wrote:





Hello Arle,

 

I wonder if you can add the following to the script:

 

In its WICS (Work In Context System) project Logrus has developed standalone
visualization tools to preview simply in browser ITS 2.0 metadata embedded
in HTML5, XML and XLIFF files which can be used on any step of the
localization process regardless of the tools used on various steps.

 

We have completed project and delivered code and report to DFKI.

 

Regards,

Serge Gladkoff

Logrus International

 

 

 

 

From: Arle Lommel [mailto:arle.lommel@dfki.de] 
Sent: Friday, November 01, 2013 12:56 PM
To: Olaf-Michael Stefanov
Cc: Stephan Walter; Multilingual Web LT Public List Public List; Nieves
Sande
Subject: Re: Updated script for intro video

 

I like this. I’ll work with this as the “hook” then.

 

-Arle

 

On 2013 Oct 31, at 19:35 , Olaf-Michael Stefanov < <mailto:olaf@stefanov.at>
olaf@stefanov.at> wrote:






Hello Stephan, hi all,

 

I strongly support your point, Stephan, and also definitely prefer you
intro.

 

It gets to the real point of ITS-2.0 in a much more direct way, for those we
want to attract, those not hitherto involved in its development.

 

olaf-michael

 

 

Sent from my Samsung Galaxy Note.
Von meinem Samsung Galaxy Note gesendet.




-------- Original message --------
From: Stephan Walter < <mailto:stephan.walter@cocomore.com>
stephan.walter@cocomore.com> 
Date: 2013/10/31 10:27 (GMT+01:00) 
To: Arle Lommel < <mailto:arle.lommel@dfki.de>
arle.lommel@dfki.de>,Multilingual Web LT Public List Public List <
<mailto:public-multilingualweb-lt@w3.org> public-multilingualweb-lt@w3.org> 
Cc: Nieves Sande < <mailto:nieves.sande@dfki.de> nieves.sande@dfki.de> 
Subject: AW: Updated script for intro video 




Hi all,

 

somehow I’m not so sure about the introduction. I think this doesn’t really
point out the benefits of ITS 2.0 sufficiently. The problem of handling
structured formats and not breaking them is not really what we solve, is it?

 

I think we should try to find something less technical that focusses more on
why it’s good to have all  the metadata and why it’s good to have it where
you can have it with ITS 2.0.

 

Maybe a bit like this:

 

“

Every translator knows: Translation is not just about the text. You need to
know a lot more to decide whether German Eiweiß should be translated as
protein or egg white, whether monster is an internet job platform or an
imaginary creature, or that Yellow Submarine should not be translated at
all. There’s also important procedural information if you work
professionally, like delivery deadlines, translator’s names etc.

ITS 2.0 identifies the most important categories of such information and
defines them as translation metadata. And if you work with structured
formats (XML or HTML5) it allows you to encode this metadata exactly where
it is most useful: Within the document, together with the sentences and
expressions that need to be translated. Since ITS 2.0 is a W3C standard, it
integrates smoothly with  these formats and there’s already a number of
tools that support it (with more to come).

”

 

What do you think?

 

Best

Stephan

 

Von: Arle Lommel [ <mailto:arle.lommel@dfki.de> mailto:arle.lommel@dfki.de] 
Gesendet: Mittwoch, 30. Oktober 2013 12:04
An: Multilingual Web LT Public List Public List
Cc: Nieves Sande
Betreff: Updated script for intro video

 

Hi all,

 

I’ve updated the script with the feedback received so far. Nieves or Felix
will lead discussion of it today since I cannot join the call due to other
meetings. One note is that all implementations mentioned in here really need
to be described in the Implementation Wiki because we will link to
information there in the video description. The wiki can then link to other
resources, but we need to use it as the central repository of resources
rather than individual pages all over the place. So if you have not added
information on your implementation to the wiki, please do so.

 

-Arle

 

[Introduction]

Structured content in XML or HTML poses special challenges for translation
processes. Dealing with these formats has required expert knowledge and they
are easily broken without it. The W3C’s new Internationalization Tag Set
2.0, or ITS 2.0, standard provides mechanisms to add information to XML and
HTML5 files to support more sophisticated and robust translation and
localization processes and to simplify use of these powerful formats.

 

Why Should You Use ITS 2.0?

If you work with XML or HTML5, ITS offers a number of compelling advantages:

 

1. ITS 2.0 give you more control. ITS 2.0 lets you control whether content
is translated, give instructions to translators, provide information about
terminology, and give guidance to automated processes about how to handle
content.

 

2. ITS 2.0 simplifies management processes and lowers costs. By ensuring
that localization resources are included in content and linked to the exact
spot where they are needed, project management effort and cost and errors
are reduced and processes can be simplified. Case studies have shown cost
reductions of between 15–40% and time savings of 30–60% depending on the
technologies used.

 

3. ITS 2.0 improves localization quality. ITS 2.0 includes comprehensive
markup for domain or subject matter, terminology, and translation quality
assessment. It also provides a way for tools to “sign” their work and lets
machine translation tell you how confident it is in its results. These
features allow you to design smart processes that improve quality up front
and focus efforts to identify and deal with problems.

 

How Can You Use ITS 2.0?

ITS 2.0 is designed to be easy to use. You can use as little or as much of
it as you need to. Support for ITS 2.0 is available in authoring tools like
Drupal [mention Cocomore onscreen], Apache Jackrabbit [mention Adobe
onscreen], and LibreOffice [mention ]init[ onscreen]. It is also central to
open-source tools like the Okapi Framework [mention ENLASO/Okapi/VistaTEC
onscreen] and ITS Tool package [mention Shaun McCance/ITS Tool onscreen] for
localization and LanguageTool [mention Daniel Naber/LanguageTool onscreen]
for language quality checking. HTML5 files using ITS 2.0 can be validated
using the validator.nu [mention validator.nu onscreen] service and work
seamlessly in modern browsers. ITS 2.0 provides advanced functionality in
localization infrastructures and real-time web publishing systems [mention
Linguaserve and GBC Server and Atlas RT onscreen]. Machine translation
systems [mention CNGL and Lucy] and text analytics packages [mention IJS
Enrycher] are increasingly adopting ITS 2.0 as well as a way to make their
results more accessible and usable. It is also designed to work well with
major standards like XLIFF.

 

Because ITS 2.0 has a low barrier to entry and is designed to work with your
existing processes, you can start gaining benefit from it without having to
completely retool existing processes, and as more and more tools support ITS
2.0 the benefits available will only increase.

 

Shown onscreen is a list of implementations of ITS 2.0 as of November 2013.
For more information on these implementations and how you can leverage them,
please visit the ITS 2.0 wiki or view our other videos.