DITA Translation Subcommittee Agenda -- 19 February 2007

Hi Folks!.

Agenda for 
Monday  19 February 
2007

11:00 am - 12:00 am Eastern 
Standard Team DITA Technical Committee teleconference 

USA Toll Free Number: 866-566-4838 
USA Toll 
Number:

+1-210-280-1707

PASSCODE: 
185771

1) Roll Call

2) Accept Minutes 
from 5 February 2007

http://www.oasis-open.org/apps/org/workgroup/dita-translation/<http://ww

w.oasis-open.org/apps/org/workgroup/dita-translation/>

Attached for guests and 
observers.

3)  Review open action 
items

    3.1 
ACTION: Gershon to investigate whether he can use a client's samples.

        
CONTINUED. (client is awaiting legal OK)

    3.2 ACTION: Gershon and Don will present the 
approved best practices on
        
indexing and Translation Memory as committee drafts for approval by the 
DITA
        Technical 
Committee.

        
ON HOLD (until DITA TC closes 1.1 spec)

    3.3 ACTION: Everyone to review the document JoAnn 
posted on 13 November
        (subject: 
Document from Christian Lieske).

        
CONTINUED [we hope to discuss next week]

    3.4 ACTION: Don to raise glossary work item at the 
TC after the 1.1 draft to
        see if 
it needs its own subcommittee.

        
ON HOLD (until DITA TC closes 1.1 spec)

    3.5 ACTION: JoAnn will contact Carol Geyer to 
discuss the possibility of a 
        
maintenance mode for the committee.

        
CONTINUED 

4) Returning 
business: 

4.1 Review the new draft of the Multi-language Best Practice (Nancy Harrison) 

4.2 Review Andrzej 
Zydron's OAXAL proposal. 

4.3 Review Robert Anderson's 
response on the lang attribute. (see attached 
email) 

5) New 
business:

Continue discussion of a new charter for the committee 
going forward. 

Review Christian 
Lieske's 
article.

JoAnn T. Hackos, PhD
President
Comtech Services, 
Inc.
710 Kipling 
Street, Suite 400
Denver CO 80215
303-232-7586


 

 

OAXAL V1.0.zip

--- Begin Message ---

From: "Robert D Anderson" <>

To: "JoAnn Hackos" <>

Date: Wed, 14 Feb 2007 01:01:49 -0700

Title: Re: Notes on the language attribute

Hi JoAnn,

I've updated the xml:lang attribute description to point to RFC 4646

instead of both ISO-3166 and RFC 3066. It looks like the new RFC 4646

encompasses both of the older ones.

The language reference had a single example, of "es-es". I've shortened

this to "es", based on the comments on our referenced page that the

shortest possible value should be used. Their example is that "ja" should

always be used in favor of "ja-JP", except in those cases where you must

indicate that this is Japanese as spoken in Japan.

In terms of case - the RFC 4646 actually mandates that the case does not

matter. From section 2.1 of the RFC:

   The tags and their subtags, including private use and extensions, are

   to be treated as case insensitive: there exist conventions for the

   capitalization of some of the subtags, but these MUST NOT be taken to

   carry meaning.

That's followed by a few examples, such as one to show the equivalence of "

mn-Cyrl-MN" and "mN-cYrL-Mn". They do recommend that you follow the

conventions set forth in 4646, but they take pains to indicate that this is

only a recommendation. So, I've left off any discussion of case in the

attribute description.

Thanks-

Robert D Anderson

IBM Authoring Tools Development

Chief Architect, DITA Open Toolkit

(507) 253-8787, T/L 553-8787

                                                                          

             "JoAnn Hackos"                                               

             <joann.hackos@com                                            

             tech-serv.com>                                             To

                                       Robert D                           

             02/05/2007 01:26          Anderson/Rochester/IBM@IBMUS       

             PM                                                         cc

                                       <>              

                                                                   Subject

                                       Notes on the language attribute    

                                                                          

                                                                          

                                                                          

                                                                          

                                                                          

                                                                          

Hello Robert,

Rodolfo had some feedback for us today at the Translation Subcommittee

meeting. He noted in Nancy Harrison's sample multi-language topics that we

are not using the lang attribute correctly. According to the latest

standards document, the country is in lower case and the locale is in upper

case. There is also a new value for script to indicate, for example, that

Russian is written using Latin or Cyrillic characters.  ru-cyr-RU;

ru-lat-RU

He points you to the W3C article that is already referenced in the Language

Specification. It has pointers to the new standard. He also mentions that

these are new rules taking the place of ad-hoc labeling of country and

locale.

Are there any examples in the Lang Spec or the Arch Spec that show the

language? If so, they should be corrected according to the new rules.

JoAnn

JoAnn T. Hackos, PhD

President

Comtech Services, Inc.

710 Kipling Street, Suite 400

Denver CO 80215

303-232-7586



--- End Message ---