Dictionary object utf-8 or alternative?

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • Hi there. I think i've got a bug with the extension “Dictionary” I can't get it to load a list of Spanish words. When checking that the word exists in the dictionary, it has problems with words that have accentuation or some special character (like vacío, día, etc) so I assume it is a formatting error (UTF-8).
    Exactly the same thing happened to me with the spellcheck extension. I don't want to use an array to check the 700,000+ possible Spanish words. What alternative can you think of? Thanks in advance

    • New
    • Official Post

    Hi there. I think i've got a bug with the extension “Dictionary” I can't get it to load a list of Spanish words. When checking that the word exists in the dictionary, it has problems with words that have accentuation or some special character (like vacío, día, etc) so I assume it is a formatting error (UTF-8).
    Exactly the same thing happened to me with the spellcheck extension. I don't want to use an array to check the 700,000+ possible Spanish words. What alternative can you think of? Thanks in advance

    I tested here with a French dictionary, it worked after I did this:

    The French dictionary was in an UTF8 CSV file, I converted it to ANSI (with Notepad++, Encoding / Convert to ANSI) and then set the Language property of the application to French (in the About tab). I suppose it should work this way with Spanish too. The Language option in the app properties allows you to define the language used by non Unicode extensions like the Dictionary object: Fusion converts the Unicode strings it passes to these extensions to ANSI using the language defined in this property.

  • I tested here with a French dictionary, it worked after I did this:

    The French dictionary was in an UTF8 CSV file, I converted it to ANSI (with Notepad++, Encoding / Convert to ANSI) and then set the Language property of the application to French (in the About tab). I suppose it should work this way with Spanish too. The Language option in the app properties allows you to define the language used by non Unicode extensions like the Dictionary object: Fusion converts the Unicode strings it passes to these extensions to ANSI using the language defined in this property.

    Hi there. Thanks you for your reply. It worked. I didn't know about the language option behaviour. I know it's an old extension but it still is a much faster and economic way to run that task.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!