Classic Shell: Forum

I found two Failures in the PolicyDefinition files
1. Emtpy stringdefinition in ClassicStartMenu.adml us-US:
<string id="CSM_str_24"></string>
<string id="CSM_str_26"></string>

2. All Policydefinition should be in UTF-16 and not UTF-8, then it can be also translated into other languages with require UTF-16 e.g. German, French, etc.

Found a way to use it. Translated ADML MUST written in UTF-8 Format with local language Setting. Best use Notepad++
regards AlexJ

1) Yes, those two settings have a bug. It will be fixed in the next version.

2) You are mistaken about UTF-8. You are thinking of ANSI. UTF-8 can represent any language as UTF-16. It is just a different way of encoding the same characters.

3) At the moment I have no interest in localizing the ADML files. Currently the only localization mechanism is with a DLL and ADML files can't be in DLLs. You are free of course to localize them and share them, however keep in mind that because of the way the files are generated, it is unlikely your work will be compatible with the next version of the files.