Re: decorator batch in bash

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 }
?


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#". 

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


Notes
-----
[1] http://tei.oucs.ox.ac.uk/Oxford/ITS/

Received on Tuesday, 21 October 2008 02:52:00 UTC