I'd like to start a discussion about project templates in CafeTran. What are your wishes, needs etc.?
I'll kick off. Please add your comments and suggestions.
Templates? What a ridiculous idea.
This sounds very interesting & cool. In the end it could result to a kind of "create translation packages for colleagues" with TMs, Total recall extracts and TBs, and I do not think this is so odd.
But no invoicing, please. There are so many solutions and tools offering a supplementary invoicing option (including memoQ with its LT). I think most users have a good or near to perfect invoicing solution (personally I'D recommend GrandTotal for Mac or TO3000 for Windows users), and even with only an interface it will be nearly impossible to interact with them all (if there is not any related standard).
>But no invoicing, please.
Igor will be glad to hear that :).
Probably every user calculates differently, but perhaps other users would like a secondary field for word price of Translated segments too?
Come to think of it: I should probably have written:
But there should be the possibility to differentiate those from (or to unify them with) the general custom spelling dictionaries and the general non-translatables.
Project templates have been on my wish-list (you could almost make that demand-list with a single item, templates) since forever. Igor's answer to it was that "templates are quite complicated to code." If Igor calls something "quite complicated," it's probably friggin' impossible. Anyway, he solved part of the problem by including settings in the TMs themselves, by making it easy to select TMs (in the Menu and the DashBoard), and in a number of cases to recognise the language combination. Apart from re-using project files, that is. I'd still prefer templates, but I can live without them. Including "other file formats" (by now everybody should know what I mean...) is even more difficult, because they lack structured meta-data. Including them would require a Wizard rather than a template. Unless you'd want to create dozens of templates.
>But there should be the possibility to differentiate those from (or to unify them with) the general custom spelling dictionaries and the general non-translatables.
Indeed. There could be some dialogue box with checkboxes.
As a matter of fact I like this idea of separate spelling dictionaries and non-translatables lists so much, that I'd even welcome it in the Welcome screen. Though this may clutter this screen, of course.
Currently I'm very economic with my non-translatables, because the loading of the project is slowed down when I have a long list. Client-based non-translatables would provide a solution.