Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Add to Dictionary with special charachters won't work - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Mon Apr 8th, 2013 09:22 am
PM Private Upload Quote Reply
DelphiDev
Member
 

Joined: Mon Jan 21st, 2013
Location:  
Posts: 12
Status: 
Offline
Hey there,

with the release of our software just around the corner and me having to check >15000 translation strings for spelling errors I frequently use "Add to dictionary" to hide translations from my filtered view.

There seems to be a bug as to how Sisulizer handles entries in its Dictionary that contain special characters.

I added strings like "file(s)", "client(s)", "*.zip" to Sisulizer's dictionary and yet those still show up as spelling errors.

When I right-click the translation column and select "Edit custom dictionary" the abovementioned strings are there but they are not recognized as being "correct" by Sisulizer.

Is there a way to fix this?

Thanks,

Greg

Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 8th, 2013 09:40 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 2009
Status: 
Offline
Hi Greg,

I guess that you using the default Polar spell checker. It has some issues with non-trivial text such as "file(s)".

You better use Hunspell spell checker. It can correctly handle this kind of text. You can download an OpenOffice dictinary (that uses Hunspell) from here

http://extensions.services.openoffice.org/dictionary

Install it and make sure that the installed spell checker is higher in the list that Polar. That way Sisulizer will use it.

Ilkka

Attachment: Untitled.png (Downloaded 11 times)



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 8th, 2013 09:50 am
PM Private Upload Quote Reply
DelphiDev
Member
 

Joined: Mon Jan 21st, 2013
Location:  
Posts: 12
Status: 
Offline
Thank you, Ilkka. This really helped me!
I appreciate your super fast support!

Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 8th, 2013 10:13 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3835
Status: 
Offline
Polar spell checker is imperfect, but this is third party component, so we can't improve. Unfortunately, we can't include Hunspell spellchecker directly to installer, because GPU license doesn't allow on this. However, Sisulizer users can manually download,  install and use this module.

Best,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 8th, 2013 10:18 am
PM Private Upload Quote Reply
DelphiDev
Member
 

Joined: Mon Jan 21st, 2013
Location:  
Posts: 12
Status: 
Offline
One thing that came to my mind: is it possible that Sisulizer computes strings preceded or followed by a special character as being misspelled? Although I installed Hunspell dictionaries I still get way too many supposed spelling errors like "(Command" or "deprecated)". Neither "Command" nor "deprecated" are misspelled (obviously not), yet Sisulizer marks them as being misspelled because of preceding or following special characters. Sisulizer also offers me to add "(Command" to the dictionary, that's why I came up with the idea that Sisulizer seems to have a weird behavior here?

Back To Top PM Private Upload Quote Reply

 Posted: Mon Apr 8th, 2013 10:40 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3835
Status: 
Offline
Currently Sisulizer treat word in bracket e.g. "(Sisulizer)" as correct, but words only with preceded or followed by single bracket char e.g. "(Sisulizer software)" are recognized as mistakes. Also words with added sufix in brackets e.g. "file(s)" are also recognized as mistake. I'll ask our R&D if possible is  possible implementing option for ignoring ALL bracket characters.

Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 12:25 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Add to Dictionary with special charachters won't work



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize