OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita-translation message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: DITA Translation Subcommittee Meeting Minutes: 22 May 2006

Best Regards,

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
DITA Translation Subcommittee Meeting Minutes: 22 May 2006

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

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

1.  Roll call

    Present: Rodolfo Raya, JoAnn Hackos, Don Day, Gershon Joseph, Chris Wong, 
        Yves Savourel, Kevin Farwell, Patrick Klaassen

    Regrets: Andrzej Zydron, Felix Sasaki, Robert Anderson

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

3.  Old Business:

3a  Review Don's comments on indexing
    Don clarified his comment in last week's minutes on index term inside <keywords>
    Index entry in <keywords> should be processed as index term at beginning 
    of referenced topic.

4.  New Business:

4a  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 should authors / 
        implementers / processors deal with multiple sets of boilerplate files 
        automatically?  DocBook names every file containing generated text 
        with a language extension (two letter only), including English.  A 
        similar scheme, but probably with locale, not just country, would work 
        for DITA documents as well.
    Best practice focused on authors working with file system (no CMS) and let
        CMS vendors deal with implementation under their architecture.
    For multilingual documents, each language should reside in a separate 
        folder (or at least a separate topic)
    For single language document going to translation, there should be a
        parallel folder structure for each language, so that relative paths 
        and filenames are maintained across all languages of the content.
    ACTION for everyone with use cases to document the use cases and send to 
    the list for design.

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

Next meeting on 5 June 2003!!!

Meeting adjourned at 09:00am PT.


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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]