Hello Peter,
Thank you for your code snippet. I see the problem. I agree that this behavior is not correct. Our developers will continue working on this issue. You will be automatically informed of our progress. Please accept our apologies for the inconvenience. In the meantime, please use the following workaround:
[C#]public class DXSpellCheckerLocale2 : SpellCheckerLocalizer { public override string GetLocalizedString(SpellCheckerStringId id) { switch (id) { case SpellCheckerStringId.Msg_FinishCheck: return "Rechtschreibprüfung abgeschlossen"; default: break; } return base.GetLocalizedString(id); } }
Thanks,
Alessandro.
Hello Alessandro,
Thank you for your workaround!
We're trying to roll-out our update in the next few days (or weeks - depending on the bugs ;-)), so it would be nice to have the SpellChecker localized.
Can you maybe tell me the expected releasedate of v2012.1 or v2011.1.9 (if the bug is fixed in these versions), so I can plan our release-schedule?
Thank you!
Peter
Hello Peter,
Please accept my sincere apologies for the delay in responding. I cannot tell you precisely when we release new versions because the development cycle depends on a number of factors, so any personal estimate can be misleading. However, everything looks very promising... Please stay tuned to our announcements.
Thanks,
Alessandro.
Is your intention to post an answer to your own question?
- If so, then proceed.
- If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
- If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.
Facebook
Twitter
Google+