Well, IDE scripts I haven't looked at all. So this very well might be possible there.

I just converted one of my apps to dynamic strings, from being one language only. It was hell of a work, but I did it. Now, I think I will not make any software again without using dynamic strings. This is just too cool. For example, I created my app in Icelandic (native) and English. Then I just exported dynamic strings for russian, sent it to a very good person, which then just sent me the file again with all translation work done.

Unfortunately I need to manually copy / paste them into the IDE myself, do to the bug i sent you. It is a lot of work. But is very well worth it. If for example you have tens of thousands of constants, I truly feel sorry for you, but I guess for now, and it probably won't be fixed in R4, we just need to do this. This is as boring job as they come by.

But like you said, you are able to export the whole module as XML, do a quick and dirty find replace, and then import it again. BUT TAKE BACKUPS before you do :)

Trausti


On 17.8.2006, at 12:34, Tobias Bußmann wrote:

Hi Trausti,
thanks for your quick replay.

Trausti Thor Johannsson wrote:
>> - in the 'build options' window I can set a Region and a Language.
>> For what is the Region? I've found nothing regarding this.
>
> This is for the old system.  No longer needed.

Okay - I don't know the 'old system'. So the 'Region' setting is de facto ignored now?

- Files created with Linuga 1.1 cannot be imported (error message in r2, crash in r3) only Lingua 1.0 works (but lacks of cause the improvements of 1.1) when will it be updated?
There is a bug ticket on this : http://www.realsoftware.com/ feedback/viewreport.php?reportid=vifkjpju

...is on my watch list, thx ;)

- The only way to change a bunch of constants to dyn / not dyn is to save as XML and do some ugly find / replace - right? do we have a way with IDE scripting?
Or do it in the IDE itself

Of course, but there are a lot...

- On OS X I'm happy with the dynamic Language selection, but in Windows I'm not. There is always this ugly 'Resources' Folder and no way to choose a language different from the OS (e.g. if the OS (on a Server) is in English language but I want to see my app in local language). I'd like to have a single .exe again - which is much more easy to distribute.
You need to go into Control Panel, Regional settings and choose a country, this works. But I agree, don't like the resources folder much, but then again, don't like windows much.

I don't like Win much as well, but I've to comply with the needs of my customers. I develop on OS X :)

- Would you support a Feature Request to add in the build options a switch 'build static language app' even if you have dynamic constants? Otherwise the language selector drop-down doesn't makes much sense to me anymore...
It is there, just don't choose dynamic strings, and it works.

Yes, but if I don't use dynamic strings at all, I cannot use Linuga. And the 'old' REALglot doesn't work anymore. So how to bring the tokens to the translator?

Currently I'm working the following way:
I'm using dynamic string constants and do my debug builds with them. For translation I pack a Win32 executable with its resource folder, lingua 1.0 and the .rbl language file in an zip and send it to the translator. Afterwards I import the edited .rbl Before I do a release build I export to XML, replace the dynamic strings by non-dynamic ones, import it again, do the build with static language and drop the XML project afterwards. Not very comfortable. I'd really like to automate this with an IDE script at least....

regards
Tobias

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to