Are you saying they should simply run a seperate set of RBs in their own farcry application to handle any globalised customisations, and leverage the existing utilities in the code base?
if by "globalised customisations" you mean "globalized customizations", yes ;-) if this stuff is specific to some install, then let it stay there & be their responsibility.
I meant more indicate a generic set of labels in the existing RBs people could leverage rather than build more labels.
good luck w/that ;-)
actually having a "commonly used rb" tends to slow development down w/complex apps, folks are always wondering which key is in what rb. it only pays off if you can get complete logical separation or the keys are used in specific/discrete chunks of code. forcing developers to jump back & forth & to remember trivial details like that is going to get something large & heavy tossed at you.
There appear to be a lot of RB entries -- but I assume this is a result of having built FarCry with one language without being careful about the
there are so many rb entries because you have so many labels/text chunks and because english is so freaking precise. i did a bit of normalization but i didn't want to change any meanings that i thought were non-trivial. and it kind of rolls out into the localizations if you're not careful. better to be verbose now then have to come back & add stuff just to satisfy some farsi-language needs. besides farcry's rb is kind of smallish, we have apps with a dozen or so rb that are 3x-4x in size.
I'll put up the PDF you sent through when I get a chance. Any more documentation gratefully received ;)
well the link to the rbManager tutorial would be a good idea. btw that's changed (ibm re-organized all of their icu/icu4j sites when they released 3.2):
http://www-306.ibm.com/software/globalization/icu/rbmanager.jsp
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
