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


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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

Subject: [OASIS Issue Tracker] Commented: (OFFICE-704) Public Comment:OpenDocument 1.2v7-02: Table of Contents

    [ http://tools.oasis-open.org/issues/browse/OFFICE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213#action_16213 ] 

Patrick Durusau commented on OFFICE-704:

Well, on one hand I am not unsympathetic to the concern voiced by Makoto and seconded by Dennis but ease of translation would always be judged relative to some target language. That is to say that some terms would be easier to translate into one target language than another and we would have to favor one language over another in order to judge the fitness of any term for its ease of translation.

My conclusion from that is having non-translatable terms for headings actually puts all target languages on an even footing and in fact allows them to map from one translation to another, insofar as they use supplemental text in addition to the untranslatable headings (mapping between the non-translatable headings). The question then becomes how consistent they are in their translations, something the ODF TC is uniquely not qualified to judge. 

If we have been inconsistent in our language usage (which would increase or even prevent a meaningful translation into any language), or if we have been unclear, ambiguous, or simply failed to define some case, those are all issues that should be raised for specific cases. 

The ODF Adoption TC could take on as a project producing versions of the TOC with added foreign language descriptors in various languages. Pick the top ten or so languages. That would make a nice offering along side the final versions of the various parts of ODF 1.2. 

But I have to agree with Michael here that the TC should close this issue unless we get something specific on a particular part of the text. 

Do note that in ODF 1.0 we did have prose text for headers that was, at least to me as an English speaker, not terribly descriptive nor intuitive. Nor would it have helped for most translations. The problem is that any terms we choose are going to be closer or farther away for any given person reading the text, depending upon their skill with the language and the technology. That was one of my motivations for suggesting the element/attribute names as headers. If you work with the format, at least those are recognizable across all languages of all developers working with the standard. 

> Public Comment: OpenDocument 1.2v7-02: Table of Contents
> --------------------------------------------------------
>                 Key: OFFICE-704
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-704
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: General
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Dennis Hamilton
>            Priority: Minor
>             Fix For: ODF 1.2
> Copied from office-comment list
> Original author: "Dennis E. Hamilton" <dennis.hamilton@acm.org> 
> Original date: 18 May 2008 07:45:09 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/200805/msg00031.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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