Agenda 22 May 2006 DITA Translation subcommittee meeting

["JoAnn Hackos" <joann.hackos@comtech-serv.com>]

Hello Everyone,

I'm calling in at 8 am from San Francisco. JoAnn

Agenda for Monday 22 May 2006

11:00 am - 12:00 am Eastern Standard Team (-5 GMT)

DITA Technical Committtee teleconference

USA Toll Free Number: 866-566-4838

USA Toll Number: +1-210-280-1707

PASSCODE: 185771

Roll Call

Approve Minutes from 15 May 2006 (enclosed for those who are not TC

members)

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

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

This link goes to the subcommittee home page rather than directly to the minutes. Please link to the minutes yourselves.

I have attached a Word document with the minutes.

Old Business:

Review Don's comments on indexing

New Business:

Discuss the second item on handling inline elements properly (alt text, footnote, draft comment, required element). Please pay particular attention to defining how the authors should handle this.n //Was this discussed last week?//

Storage of boilerplate text
       Boilerplate text is often kept in one or more .dita files used as a source for conrefs across a document set. How hsould authors / implementors / processors deal with multiple sets of boilerplate files automatically?  DocBook names every file containing generated text with a language entension (two letter only), including English.  A similar scheme, but probably with locale, not just country, would work for DITA documents as well.

If possible, continue with the next best practice in Nancy's list.

JoAnn

 

JoAnn T. Hackos, PhD
President
Comtech Services, Inc.
710 Kipling Street, Suite 400
Denver CO 80215
303-232-7586
joann.hackos@comtech-serv.com

 

 

Best Practices Translation SC.doc

--- Begin Message ---

• From: "Gershon L Joseph" <gershon@tech-tav.com>
• To: <dita-translation@lists.oasis-open.org>,<mambrose@sdl.com>,<pcarey@lexmark.com>,<rfletcher@sdl.com>,<bhertz@sdl.com>,"Richard Ishida" <ishida@w3.org>,<tony.jewtushenko@productinnovator.com>,"Lieske, Christian" <christian.lieske@sap.com>,"Jennifer Linton" <jennifer.linton@comtech-serv.com>,"Munshi, Sukumar" <Sukumar.Munshi@lionbridge.com>,"Charles Pau" <charles_pau@us.ibm.com>,<dpooley@sdl.com>,"Reynolds, Peter" <Peter.Reynolds@lionbridge.com>,"Felix Sasaki" <fsasaki@w3.org>,"Yves Savourel" <ysavourel@translate.com>,"Dave A Schell" <dschell@us.ibm.com>,"Bryan Schnabel" <bryan.s.schnabel@tek.com>,<Howard.Schwartz@trados.com>,<kara@ca.ibm.com>
• Date: Wed, 17 May 2006 06:13:58 -0600

Title: [dita-translation] DITA Translation Subcommittee Meeting Minutes: 15 May 2006

Best Regards,
Gershon

---
Gershon L Joseph
Member, OASIS DITA and DocBook Technical Committees
Director of Technology and Single Sourcing
Tech-Tav Documentation Ltd.
office: +972-8-974-1569
mobile: +972-57-314-1170
http://www.tech-tav.com

DITA Translation Subcommittee Meeting Minutes: 15 May 2006

(Recorded by Gershon Joseph <gershon@tech-tav.com>)

The DITA Translation Subcommittee met on Monday, 15 May 2006 at 08:00am PT
for 60 minutes.

1.  Roll call

Present: Don Day, Gershon Joseph, Kara Warburton, Kevin Farwell, Robert Anderson, 
    David Walters, Nancy Harrison

Regrets: JoAnn Hackos, Andrzej Zydron, Rodolfo Raya

2.  Accepted the minutes[1] of the previous meeting.
    Moved by Gershon, seconded by Don, no objections.

3.  Old Business:

    a.  Review Nancy's revision of the indexing best practice enclosed.

4.  New Business:

    a.  Discuss the second item on handling inline elements properly (alt text, 
        footnote, draft comment, required element). Please pay particular 
        attention to defining how the authors should handle this.

        DONE.

    b.  If possible, continue with the next best practice in Nancy's list.

        Don: Index entries are for in-situ index entries; <keyword> should be 
        used for index terms that apply to the entire topic.

        "If appropriate, the index entry should contain the range of text to be indexed"
        - This refers to page ranges. The index term is defined 
            inside the index marker. Start range should be at beginning of start 
            block (i.e., parent block element); end range markup should be at end 
            of end block element.
        - Tools should implement range from start of start element containing 
            the start index marker to end of end element that contains the end 
            index marker, regardeless of the location of the start and end markers.
        ACTION (from previous meeting) JoAnn to provide example markup

        "The author should insert -- where ???"
        - Put them where it's logical in the source document.

        "When these elements are encountered, the tool should interpret the 
        location of the container element for the inline element as the parent 
        element of the element. ???"
        - We don't have anything to say here, remove this sentence.

        "Well-configured XLIFF-based tools do this automatically"
        Change to: In generaral, XLIFF-based translation tools can be 
        configured to do this automatically.

        Agenda item for next week:
        What other best practices do we need to discuss? e.g. maximize usage 
        of conref (reusable blocks)...
 
Meeting adjourned at 09:00am PT.

---

[1] http://lists.oasis-open.org/archives/dita-translation/200605/msg00006.html

--- End Message ---