From: Tatsuya K. <tat...@ma...> - 2002-05-05 06:33:37
|
Hi Max, >> ... it took me several hours to figure out that I can't put: > >> - user.d2wmodel in a framework (the correct answer is d2w.d2wmodel) > > Ouch! I've wanted to add for a long time the ability to load any > *.d2wmodel files just like eomodels. I somehow started to believe that I could use both file names. I don't know why. > Wow that is a *lot* of work. Thank you so much. Travis and I have been > working on the website and the PowerPoint presentation for most of > today. Seems to be coming together pretty well. Sounds great! I'm looking forward to watching the video of the Stepwise session. >> Basically, I've done localizing with the followings: >> >> - Login Page (Main) >> - MenuHeader >> - HomePage, with the language selector >> - entity names (for all pages) >> - property names (for all pages) >> - message for ERDEditPasswordConfirm >> - part of validation messages I started to realize that there are still lots of work to make app completely localized, e.g I localized entity names for _manipulatedEntityName in MenuHeader but D2W pages still bear the English names under title banner. Also, buttons are still English too. But I think this is almost enough for the presentation. (Please see the attached screenshot.) By the way, I have to work on English property names; I used ERDLocalizedAssignment for all property names of entities, but I only put corresponding Japanese translations and left English part blank (because they don't need translations.) However, the current implementation of ERDLocalizedAssignment doesn't capitalize words while displayNameForProperty does. e.g. With displayNameForProperty: targetRelease -> Target Release Current localizableAssignment: targetRelease -> targetRelease I'm going to post a separate email with the list of changes. Thanks, Tatsuya -- Tatsuya Kawano New York, NY 10016 United States |