custompropertysets

Ken Ray kray at sonsothunder.com
Mon Jun 24 10:04:18 EDT 2002


Ron,

In my experience, if you are going to use outside translators, you should
always keep your language data in an external file; either one that is
always referenced by the app, or one that is "imported" into the app once
and stored with the app. The reason for this is that outside translators (a)
shouldn't have access to the internal workings of your stacks (which they
would if you had to set custom properties for each object), and (b) it is
more likely that something will get missed and you'll have a nightmare of
finding what didn't get translated.

When I worked for Allegiant Technologies (the now-defunct publishers of
SuperCard), we had to translate a couple of things into German and it was a
nightmare getting things translated (and our German rep KNEW SuperCard!!!).

Just my $0.02,

Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/

----- Original Message -----
From: "Ron" <rbarber at yhb.att.ne.jp>
To: <use-revolution at lists.runrev.com>
Sent: Sunday, June 23, 2002 8:51 PM
Subject: Re: custompropertysets


> Greetings
>
> I am setting up an application that can display dialogs, menus etc in a
> variety of languages based on the user's choice. There seem to be several
> ways to go about this and I would appreciate input based on your
experience
> and insight. Klaus uses a text file and then reads in the whole file to a
> single userprop in the stack and then calls the needed item of that
userprop
> through judicious use of an itemdel. If I've understood Rob correctly, he
> doesn't use userprops at all in his multi-lingual app. (thanks guys for
your
> input)
>
> My thought is to set up a custompropertyset in the main stack for each
> language. Then set up a key for each necessary btn name, dialog etc. The
> keys would then be referenced on open cd or open wd of the substacks.
>
> This would avoid setting up custompropertysets and keys for each object
> (which seems redundant and difficult to maintain) and would not create
> another file to keep up with on the HD(easy enough to maintain but the
small
> possibility of having the file misplaced). But I wonder how hard my
approach
> would be to maintain and update/correct? Also, any memory issues
concerning
> reading the file after startup being better than including the data as
part
> of the app.?
>
> Thanks
> Ron
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the Use-livecode mailing list