W3C home > Mailing lists > Public > public-tt@w3.org > June 2003

RE: TT Req (translation markup)

From: <Johnb@screen.subtitling.com>
Date: Mon, 30 Jun 2003 11:09:56 +0100
Message-ID: <11E58A66B922D511AFB600A0244A722E094048@NTMAIL>
To: Luke-Jr@cox.net, glenn@xfsi.com
Cc: public-tt@w3.org
Luke, Glenn, et al

Actually this may be an important issue.
It may be desirable to allow inline markup within a TT document that marks
sections of the text for specific purposes. I have in mind the XLIFF <mrk>
element.

The specification for XLIFF can be found at:
http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm

The mrk element has an mtype attribute

<mrk mtype/>

where the recommended values for the mtype attribute are as follow 

(this list is not exhaustive  and reference should be made to the XLIFF
specification):
- abbrev = abbreviation, acronym, etc.
- datetime = date or time information.
- name = proper or common name.
- phrase = sub-sentence level.
- protected = text that should remain untouched during the process.
- term = one or more words of a terminology entry.

Some examples of a text element using mrk markup are shown below:
<text id="T2" class="Charlie">Afternoon, <mrk mtype="abbrev">Dr</mrk>. <mrk
mtype="name">Sparrow</mrk>.</text>
<text id="T27" class="Sir Lancelot">I don't want <mrk mtype="protected"
xml:lang="en-us">garbage</mrk> on my car.</text>

The first example illustrates the use of the mrk element to identify an
abbreviation and a proper name that would probably require special
processing by a machine translation system. In the second example the mrk
element protects the word 'garbage' from machine translation  thus this
word should remain as 'American English' regardless of any translation of
the remainder of the surrounding text.

Is there any reason why TT format would prohibit or prevent the use of such
markup?

regards 
John Birch

The views and opinions expressed are the author's own and do not necessarily
reflect the views and opinions of Screen Subtitling Systems Limited.


> -----Original Message-----
> From: Luke-Jr [mailto:Luke-Jr@cox.net]
> Sent: 26 June 2003 00:11
> To: Glenn A. Adams; public-tt@w3.org
> Subject: Re: TT Req
> 
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> That is just an example of what the format would need to 
> support as far as 
> disabling/enabling specific portions of the timed text. It's 
> not really 
> translating-specific, but I couldn't think of any other use 
> for timed text. 
> =p
> 
> On Wednesday 25 June 2003 02:13 pm, Glenn A. Adams wrote:
> > I'm afraid I'm still not following you. What does 
> translation have to do
> > with timed text?
> >
> > G.
> >
> > > -----Original Message-----
> > > From: Luke-Jr [mailto:Luke-Jr@cox.net]
> > > Sent: Wednesday, June 25, 2003 1:32 AM
> > > To: public-tt@w3.org
> > >
> > > Oh, and a part I forgot... It should also be configurable at
> > > the level so one can choose whether or not to translate
> > > proper nouns (names, places, etc) and to include
> > > untranslatable stuff (For example, the Japanese -kun, -san, -chan,
> > > - -sama, etc).
> > >
> > > On Wednesday 25 June 2003 05:20 am, Luke-Jr wrote:
> > > > Basicly, those settings would cause English subtitles to be
> > >
> > > displayed
> > >
> > > > for all Japanese audio, songs, or images. In addition, it
> > >
> > > would enable
> > >
> > > > karaoke for all songs in the English/Roman characters 
> and also in
> > > > their native characters (if Japanese, it would use Japanese
> > > > characters; if Korean, it would use Korean, etc)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
> 
> iD8DBQE++joKZl/BHdU+lYMRAooYAJ47igf7OwxHW8sm23nSKK2pR+ZukwCeNJDk
> szGJDNxIiac5zdJcF2N/Rhw=
> =cvIt
> -----END PGP SIGNATURE-----
> 
> 
Received on Monday, 30 June 2003 10:08:55 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:23:59 UTC