Once you start internationalizing stuff like info and unit counters, you are basically making a new module. No one is going to want to download a 50 MB international version of a module when the single language version is 2 MB.
Focus on the application elements (e.g. Rotate Clockwise, Delete, Clone, etc). -z On Mar 3, 2007, at 3:30 AM, Joel Uckelman wrote: > Thus spake "David Stanaway": > > The tricky bit is when you make layout assumptions based on how > the (en) > > text looks, and when that get displayed in another perhaps more > verbose in > > some instances locale, things get cut off, or distorted. > > Oh, that is aside from keeping the translations synced... > > Tokens which are rendered by VASSAL are an interesting issue for > translation. > One one hand, there are a lot of tokens which I could see people > wanting > in their native language---I'm guessing that these would be > informational > markers for the most part, things like "Rauch" on Smoke counters. > On the > other hand, there are also a lot of tokens which have text which > shouldn't > be translated, mainly text for names. I don't think anyone wants a DAK > token which says "GAC" on it instead. > > As for text alignment, that's tricky. Germanic languages are less > verbose > on average than Romance languages, for example; I'd expect this to be > a problem in a Spanish translation of a module originaly done in > English, > say. Maybe what we need is a way to substitute images as well as > strings, > for those cases when the token needs a different layout in the target > language. > > -- > J. > >
