Looking at iLocalize, I have am a little annoyed that the trial doesn’t allow you to save projects. I prefer time limited but otherwise uncrippled software, as it gives you a better chance of evaluation. Also, I have one question (assuming you have used iLocalize yourself):
It seems that translators have to use iLocalize as well as the developer. How does that work? Presumably each translator does not need to buy their own version, or the developer is not expected to buy as many copies as he has translators?
The mighty developer sends the application to the poor translator who imports it to ilocalize. The poor translator does what is neccesary to get the beast translated and exports only the translation. iLocalize exports a file which the poor translator sends to the mighty developer. The mighty developer imports the received file to iLocalize - voila, end of story. And they lived happily…
Ups, got carried away there.
So, yes, everybody needs iLocalize. In fact it is quite easy to work with it, my brother is working for a software company so I could use his version. I do wonder what will happen if somebody translates ‘OK’ to something like ‘Agreeable’. Isn’t there a limit on how many characters a translation can have?
Besides iLocalize; using plain nibtool works as well, just not as comfortable - and comes free with the developer tools…
EDIT:
Just out of morbid curiosity I tried iLocalize and BlueTecs LocalizationManager. To sum it up: translation is mostly boring.
The tools are quite nice and so on - but in the end it might be less work to open each of the nib-file directly in Interface Builder. Too many problems with the length of the strings do require quite a lot tweaking - nothing disastrous, more tedious, mind you - insofar someone is probably better of in using bluetecs localizer and IB afterwards.
Keith, I promise you go nuts if you rearrange the UI elements for more than two languages within a single week.
But then - two thirds of Scrivener got a translation here… so I personally am satisfied
Were are your projects of translation now ? I can also give a hand for a french translation, if you give the appropriate and technical informations to do it
I’m ready to do a german translation. When the time has come you may contact me: m.juengling at mac.com
Can somebody please post a little FAQ on how to use the Aplle dev. tools to translate a software? I would like to do some exercises before get in with Scrivener.
Thanks a lot to the developer for considering a translated version!
It was fun to read your translation suggestions, by the way. I’ve just been working on some German-to-English translation (Mozart family letters). Puts me in a kind of hypersensitive hair-splitting mode. Pleasantly dizzying to pick my head up out of the 18th century and puzzle about 21st century computerspeak for a minute.
Puah! Sounds like you’re a translator? And your work isn’t funny at all with Mozart. Your first language is german? If not, respect! Ok, of course, if it is, respect too
Maybe we will see a 18th century version of Scrivener…
I’ve just downloaded Scrivener and within a few minutes I knew where my new novel would evolve. I still haven’t been able to buy it (my new mac ate my credit card).
For the moment the only thing I could ask for was to use the program in my native language. It doesn’t bother much to use English programs in other fields (I also do cover design for books in English Photoshop and play English Simcity), but when writing is concerned you want a harmony between your text, your thinking and of course, your software. So I’m up for the Turkish translation as soon as the translations begin.
All the best,
Diren
Istanbul
PS: Bought Scrivener a few days after this message.
All development effort has gone into 1.1 to ensure that Scrivener is compatible with Leopard. After that, I’ll be thinking about localising - but not until autumn at the earliest. For the next few weeks, I’m enjoying a holiday and I’m also going to try to get some writing done and actually use Scrivener myself.
Best,
Keith
Polish translation is ready, but… it’s impossible to translate toolbars (main menu, preferences…). However I transated strings, toolbars are still in english.
Some translations not affect to application (see: )
Sorry I didn’t reply to this sooner - I certainly meant to. Thank you so much for doing the Polish translation - much appreciated. Unfortunately there are a few minor interface changes in 1.1 so it will require a little updating.
For things such as menu items and interface items that are not embedded into code but rather in interface files, you need the developer tools installed (available on the OS X CD). But more than that, I need to set up in Scrivener different language .lproj files. There is other stuff I have to do my end to make sure that the language changes depending on user settings, too, and this is why I haven’t undertaken asking the kind volunteers who have said they will translate to do so yet (especially knowing that the interface has some minor changes coming).
I’m afraid I won’t be ready to start supporting translation of Scrivener into other languages for a little while yet, but when I am ready I will be very grateful for your Polish translation.
Interface changes? - No problem, translation for 1.08 is ready.
But Developer Tools not always are helpful (toolbars again). I’ll be waiting for 1.1 and I’ll translate Tutorials.
Thanks for your answer!
Marek
[Koledzy z Polski, jak tu któryś trafi, jeśli ktoś chce testować tłumaczenie Scrivenera - a przyda się - niech pisze do mnie! >>> yorick77 (maupka) gmail . com]
