W3C home > Mailing lists > Public > public-i18n-its-ig@w3.org > October 2008

Re: decorator batch in bash

From: Felix Sasaki <fsasaki@w3.org>
Date: Tue, 21 Oct 2008 15:08:00 +0900 (JST)
Message-ID: <1425.>
To: Syd_Bauman@Brown.edu
Cc: public-i18n-its-ig@w3.org

> I will make only a few minutes, if any, of the call tomorrow (daughter
> has an orthodontist appt).
>> > Personally, I'd like to have the program give me the option of
>> > where to put the output file, too, but I wanted to make sure that
>> > was in line with the group's desires first.
>> good point, we can change that for the windows batch files too.
> Check. Let's put that on the tings-to-do list.
>> Good point. I have added an explanation to
>> http://www.w3.org/International/its/wiki/ITS_Translate_Decorator#Example_input_and_output
>> at the bottom, could you check if it makes things clearer?
> Yes, much clearer. I am a bit curious, though. Why is itsTve
>   attribute itsTve { "yes" | "no" }
> rather than
>   attribute itsTve { xsd:boolean }

there is no specific reason for that, both should work fine.

> ?
> I've tested the ITS Translate Decorator on the example/input.xml using
> the new front-ends, and it seems to work just fine. (There are
> warnings from Saxon about the intermediate XSL, but I presume those
> are expected.)


>>     * If there are translatable attributes at an element node, that node
>>       has an *itsTva* attribute which lists the names of these
>>       attributes, seperated by '#'. Attributes whose name is not listed
>>       as part of *itsTva* are not translatable.
> The values of itsTva= I am getting are flanked, not separated, by '#'.
> I.e., I'm seeing a "#title#" where I would have expected "title" or
> "title#".

Yes, that's true. We can change that as well.

> How does the ITS Translate Decorator compare with Sebastian's
> "Spritser"?[1]

See in the wiki
"The XSLT-based "decoration" approach was pioneered by Spritser, a general
ITS 1.0 implementation provided by Sebastian Rahtz (Oxford University). "

The translate decorator is a simplified implementation of what Spritser
offers. It's only advantage: easy of use and a very specific use case. One
question we have to think about is how to go on from here (Christian might
remember this ;) ): write more decorators (e.g. "within text" decorator),
or make more documentation about Spritser and replace the Translate
decorator with it. I think both are fine and are rather a question of
time, e.g. Sebastians time.

Received on Tuesday, 21 October 2008 06:08:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:11:27 UTC