[openbeostranslationkit] Re: Structured Text Translation

Mike Wilber wrote: 
I think we should decide what we want the user/Applications to be able to
do with the new Text Translation system and worry about the implementation
details after. There is so much that one can do with XML, HTML, PDF and
This is always a problem - sometimes thinking a wee bit ahead, might save us a whole lot of work. However I agree - the most important thing, is to have the actual user in mind.


What might a user want to do with XML, HTML, PDF or plain text data? Do
they want to simply look at the end result? Would they rather see the
source code? Do they want to edit it, then save it as
the same type? Do they want to save the data as a table of database
records? Are they only interested in the pictures used in the document? If
there is scripting code embedded, do they want to be able to execute or
examine the code? Would they want to see a PDF document as plain text
data?
IMO we should only concentrate on full translation of a document. The above statment, would imply that the PSD translator should ask the user which layer he wants. It doesn't - it just merges all layers and present that.
Whether or not the format being translated to or not, is up to the translator - it will just ditch embedded objects or javascript code, if it is converting into another format whcih doesn't support this...

I should be in the openbeostranslationkit channel soon, but I want to see
if there are any new jobs posted today first.
wee company :)


Other related posts: