RE: Using ITS to provide quality directive

Ján

I have huge respect for Felix so anything he suggests is worth investigation! J

I think he’s referring to the use of the Unicode BCP 47 T Extension of the Locale Data Markup Language<http://unicode.org/reports/tr35/#t_Extension> which I know very little about. As a Unicode Technical Standard it’s got to be worth a look.

Phil


Phil Ritchie
Chief Technology Officer | Vistatec
Vistatec House, 700 South Circular Road,
Kilmainham, Dublin 8, Ireland.

@|from|displayname|@ | @|from|title|@ | VistaTEC
VistaTEC House, 700 South Circular Road, Kilmainham, Dublin 8, Ireland.
Tel: +353 1 416 8000
Email: @|from|mail|@ | www.vistatec.com | ISO 9001 | EN 15038
         
Expert Leadership in Global Content Solutions

Tel: +353 1 416 8000 | Direct: +353 1 416 8024
Email: phil.ritchie@vistatec.com
www.vistatec.com | ISO 9001 | ISO 13485 | EN 15038
Vistatec
Think Global
FacebookLinkedInTwitterGoogle Plus
From: Ján Husarčík [mailto:jan.husarcik@gmail.com]
Sent: 06 January 2017 15:25
To: Phil Ritchie <phil.ritchie@vistatec.com>
Cc: public-i18n-its-ig@w3.org
Subject: Re: Using ITS to provide quality directive

Hello Phill,
thanks a lot for the suggestion. Maybe it would be worth considering a data category for providing various directives for quality, style and other possible attributes for translation in next version of ITS.
What do you think about using Locale Filter data category as proposed by Felix in different thread:

<div its-locale-filter-list="*-t-t0-und" its-locale-filter-type="include">
   <p>For machine translation.</p>
</div>

where "*-t-t0-und"means: machine translation into a target language, target language is undefined:

<ldmlBCP47>
    <version number="$Revision: 11914 $" />
    <keyword>
        <key extension="t" name="t0" description="Machine Translation:
        Used to indicate content that has been machine translated, or a request for a particular type of machine translation of content.
        The first subfield in a sequence would typically be a 'platform' or vendor designation." since="21.0.2">
            <type name="und" description="The choice of machine translation is not specified. Used when the only information known (or requested) is that the text was machine translated." since="21.0.2" />
        </key>
    </keyword>
</ldmlBCP47>

Thanks,
Jan

On Thu, Jan 5, 2017 at 1:14 PM, Phil Ritchie <phil.ritchie@vistatec.com<mailto:phil.ritchie@vistatec.com>> wrote:

Ján

I don’t think there is a defined category specifically for that. The Localization Quality Issue<https://www.w3.org/TR/its20/#lqissue> and Localization Quality Rating<https://www.w3.org/TR/its20/#lqrating> were intended to express quality assessments rather than requirements. The Localization Note<https://www.w3.org/TR/its20/#locNote-datacat> would be a generic way of communicating requirements.

Phil


Phil Ritchie

Chief Technology Officer

 |

Vistatec



Vistatec House, 700 South Circular Road,
Kilmainham, Dublin 8, Ireland.

Tel:

+353 1 416 8000<tel:+353%201%20416%208000>

 |

Direct:

+353 1 416 8024<tel:+353%201%20416%208024>


Email:

phil.ritchie@vistatec.com<mailto:phil.ritchie@vistatec.com>


www.vistatec.com<http://www.vistatec.com>

 |

ISO 9001

 |

ISO 13485

 |

EN 15038



[Vistatec]<http://www.vistatec.com>

Think Global

[Facebook]<https://www.facebook.com/vistatec>

[LinkedIn]<http://www.linkedin.com/company/vistatec>

[Twitter]<https://twitter.com/Vistatecglobal>

[Google Plus]<https://plus.google.com/+VistatecGlobal/posts>





From: Ján Husarčík [mailto:jan.husarcik@gmail.com<mailto:jan..husarcik@gmail.com>]
Sent: 04 January 2017 16:41
To: public-i18n-its-ig@w3.org<mailto:public-i18n-its-ig@w3.org>
Subject: Using ITS to provide quality directive

Hello,

is there a way to use ITS markup to describe the desired level of translation quality in source document?

For example:
<p class="machine">Lorem ipsum dolor sit amet</p>
<p clsss="human">consectetur adipiscing elit</p>

The Provenance data category describes already translated content. How to provide such directive in source?

Thanks in advance.
Jan

Received on Friday, 6 January 2017 17:00:01 UTC