For performance reasons I decided to keep keys case sensitve.
The easy way is to make all upper case, following a convention used on constants in c#, c++
l Uppercase ”A..Z” is Required, Yes
l Numbers ”0..9” are allowed, Yes
l No other symbols out standard 127 ascii codes.
l UnderLine ”_” is allowed. Yes… easy to separate names or words
l DASH ”-” is allowed. Yes… easy to separate names or words even if I would keep only one convention (underline for separate, dash only where it is proper, like in culture name)
l Space cause troubles, replace with _
l Brackets allowed only if make sense
l Dot ”.” is NOT allowed. Or better is used to separate assemblies so it has a special meinig: it separate a prefix eg: Ecommerce.MY_KEY if the key is in ECommerce assembly (no dll) (in assembly name lower case are allowed).
l LowerCase ”a..z” is NOT allowed in key names (see before)
I hope his is all you need… If you need other just ask again.
Thanks for you effort on this.
Emmanuele De Andreis
Internet Solutions Provider
[mailto:email@example.com] Per conto di yiming
Inviato: venerdì 17 dicembre 2004 18.40
A: 'manudea'; firstname.lastname@example.org; email@example.com
Oggetto: [Rainbowportal-localization] advise needed for key revise
My work about resx key revise is going to be done.
Now I need your advise for following issue.
Please Answer it for me.
How Do I Work:
1. I had revised all the following keys, Is there any other Keyword I should working on with?
l find by "TextKey"
l find by "Localize.GetString"
l find by ".EnglishName" and "_baseSettings.Add", They’re for Settings Caption
l find by ".Description" and "_baseSettings.Add", They’re for the “?” description icon
l find by "_baseSettings.Add", for those keys without EnglishName specified.
l find by ".ErrorMessage" or "ErrorMessage="
l find by "ERROR_" or "_ERROR"
l Reviewed every Module, and their setting pages, add/edit pages with AutoLearn
2. I didn’t / or partially working on following issues:
l Control values/items, ex: Edit/Dropdown/List/CheckBox
l Caption/text in modules(ascx/aspx/cs) which are not using Esparentus
l Dynamic keys: those keys which set/get with expressions, not directly.
l keys with country code: these keys often used by expressions.
There are some directory under
“DeskTopModules”, some of them are not default installed.
I do something about them, tell me if there’s something else I should do:
l Include and test their keys like other modules: LDAPUserProfile, SignInLdap
l Keys Under this are EXCLUDED: OneFileModule.
l These Paths are searched with keyword above, but not tested: Admin, DateTextBox, Register, Workflow
Answer This For Me
Rule of TextKey Names, Now
Please answer them for me , Manu
I will correct invalid keys by the rule of your answer.
l (Y/N) Uppercase ”A..Z” is Required, Yes or No?
l (Y/N) Numbers ”0..9” are allowed, Yes or No?
l (Y/N) UnderLine ”_” is allowed. Y/N?
l --(Following characters I found in keys, I assumed they’re wrong)
l (Y/N) LowerCase ”a..z” is NOT allowed. Y/N?
l (Y/N) Space ” ” is NOT allowed. Y/N?
l (Y/N) DASH ”-” is NOT allowed. Y/N? (Notice: Culture code has “-“, like: zh-TW)
l (Y/N) Dot ”.” is NOT allowed. Y/N?
l (Y/N) Brackets ”()” is NOT allowed. Y/N?
I will give you:
5. The complete key list I revised.
6. Invalid keys will be modified.
7. Some modified code for let the TextKey work property(like the previous one)
8. A List of modules which are not globalized yet.
9. Some minor issues I haven’t resolved yet.
Please Give me the answers.