Scratch wrote:
Ummmm... tool? Was considering notepad. Are there tools to populate these translation XML files?
oh my.
I don't think there should be too many keys to search through because I'm going to implement S.Corfield's suggestion of returning a struct for an entire page's content. So I would reference translation by: #ContactUsPage.PageTitle#, #ContactUsPage.BodyText#, etc.
yes, we pump each language/locale into an application scope struct, usually logically separated (higher level than a page so you can get some key re-use). but the start-up time for xml will be slower than rb--if you're not seeing this it's simply because your i18n apps aren't big enough yet. in any case, this is a very mild issue compared to the fact that you don't have a set of translation tools to manage this process. things are going to spiral out of control, especially if you have to go to domain experts who don't give a rat's behind about xml, etc. for translations.
---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
