-
- 24,544 Posts
Great tool.
I thought I’d mention that some language strings might have one or more placeholders in them. Those shouldn’t be translated. It might be worth checking them.
This what I need. Thanks.
zaenal.lokamaya
In the first post I have added new attachment
checkLexicon_2.1.1.zip, which contain workaround for comparing placeholders inside lexicons strings.
Please try it and let me know if it works according to your assumptions.
Thanks for suggestion to BobRay.
-
- 271 Posts
It seems that the attachment was lost.
Anybody can share it again?
There is some problem with attachements in the forum, so I have updated first post and add link to external source for check lexicon tool.
Enjoy it.
-
- 24,544 Posts
BTW, I've just created a different kind of tool called LexiconHelper. It's for add-on developers and It looks for lexicon strings in code files and compares them to the strings in a language file. It reports keys missing from the language file, empty keys in the language file, and orphans in the language file.
Best of all, the "keys missing from language file" output can be pasted into the language file, so all you need to do is fill in the strings.
I hope to release it soon.
Is checkLexicon working also for Revo 2.2?
Thanks
As of June 25, 2014, we have adopted
Crowdin as the translation tool and method for MODX Revolution. You can find
all the details here but this new tool automatically tracks changes, can have a vast number of translation submitters and includes in-context translation for those with access to our live, online translation install of Revo at MODX Cloud.
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub