|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Customized dictionary data are saved at source level
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Customized dictionary data are saved at source level
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page: 1 2   |
|
|||||||||||||||
| Customized dictionary data are saved at source level - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
jbueno25 Member
|
The words added to customized dictionary are saved in a source node in the slp file. It's a problem when source is excluded or removed, because those words are ignored in spell checking. For example, a translator adds "myWord" (in "mySource" source) to dictionary, and this word is added to "otherSource" node: <source class="TNetAssemblySource" name="otherSource" ...> ... <spelldata> <dictionary> <item>myWord</item> </dictionary> </spelldata> </source> All rows (for all sources) with word "myWord" was correctly checked. When "otherSource" is excluded/removed/etc, Sisulizer shows spell errors in rows with word "mySource". Juancho.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Juancho, This can be configured under Tools - General - Spelling & Grammar. Since this is not a bug I move this post to Usage. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello,This can be configured under Tools - General - Spelling & Grammar. Option "Tools" menu > "General" > "Spelling & Grammar" tab > "Default custom dictionary location" > "Save dictionary to a standalone file" is global setting and all new projects will be use this settings for all translation languages. If you don't want change this setting, you can use alternative solution: Right click on translation language column header > click "Language properties" from context menu > "Spelling" tab > "Custom dictionary location" > "Save dictionary to … file". This setting is applied only to selected language of specified project, while all new project use still custom dictionary setting from "Spelling & Grammar" tab of "General Settings". Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jbueno25 Member
|
I configure "Save dictionary to the project file" and the words are added to the project. Those words are applied to all project. This is right. The problem appears when I exclude a source, then close Sisulizer and then open same project. All words added to excluded source node (in slp file) aren't applied to spellcheck and all rows with those words are marked as erroneous. 1) Create a project with 2 sources, SourceA and SourceB. In my case, there are .Net assemblies. Both sources have next original string: "Searche". This word is not found in english dictionary. Then, in those rows appears an spell error. 2) Add "Seache" to dictionary. Then, spell errors dissapears. 3) Exclude the source. To locate what source to exclude, save the project and locate (in slp file) the source when a spelldata node with "Searche" item. 4) Save and close Sisulizer. 5) Open the project. The unique "Seache" row showed has an spell error... and: 6) Include the source. 7) Reopen sisulizer. Both rows are right.... Juancho. (In this configuration window I can use a standalone file, but this file is not sent to translator when slmake creates a SLE package, for example. Then, I can't use a standalone file)
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jbueno25 Member
|
Hi, Janusz. I tried your second solution and it solves my problem. I had to delete the absolute paths of the SLD files in General options | Spelling & Gramar tab (see figure 0001), but now I have one dictionary for project and language. Before, I had tried a lot of combinations of this parameters. I can't find some way to send the customized dictionary with the translator and, later, to import his changes (new words added). Is this possible? Juancho. I think that initial problem reported in this topic is an strange behavior  Attachment: 0001.png (Downloaded 71 times)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, I’m surprised a bit this issue, because Sisuslizer spell checker data are saved at first level XML node in project, and for this reason these data should be independent from source nodes and removing or excluding sources shouldn’t have influence on spell checking data. You can to see it on below screenshot. I performed your test described above, but I can’t reproduce your issue, that is, custom dictionary data leaved in project after removing source. Could you send to me your SLP via “Private Upload” button? I’d like check issue with your project. Best regards, Janusz Attachment: screen.png (Downloaded 70 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello,I can't find some way to send the customized dictionary with the translator and, later, to import his changes (new words added). Is this possible? The best solution is saving custom dictionary to project, but if you have problem with this solution (I’ll test this issue again, but later, because now I’m a bit busy), you can include standalone custom dictionary file to exchange package in 6th step of Exchange Wizard. BTW: SLD files are plain text files and you can edit it in any text editor. Best regards, Janusz Attachment: screen.png (Downloaded 64 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Juancho, Hmm... I checked issue with your test scenario, your project and SLO files and I’ve got again correct result, that is, custom dictionary data was saved to first XML node level and existed still after removing your source. Could you revert your custom dictionary settings to saving data in project file and check it again? Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jbueno25 Member
|
Please, I need help. I can't configure it... In Vista, solution in post 5 doesn't works. When I close and open Sisulizer, the absolute path reappears... I did a fresh installation of Sisulizer in other machine. I can't configure standalone files in proyect folder:
Save dictionary to "SpellESP.sld" file
My configuration is lost. Sisulizer use dictionary in Sisulizer folder.C:\Program Files\Sisulizer 2008\SpellESP.sld I will store dictionaries in project file. Juancho.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
You can select only in Column language properties, if custom dictionary will be saved to project file or to custom dictionary file specified in General settings. You can’t set up many different paths to custom dictionary file for selected language. You can use only absolute path for spell checker components in general settings, because: - For spell checker components required is registration in Windows system - Spell checker libraries are third party components - Saving custom dictionary to different directory than Sisulizer installation directory (XP), User directory (on Vista) could cause paths issues with relative paths. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jbueno25 Member
|
Sorry, I was wrong. I understood that it could be done. I've been using separate files for two weeks without problems but now I need to exchange them with the translator. Now, I'm using Hunspell dictionaries and dictionaries in project file, but the original error reported in this topic still happens. Thanks for your help, Janusz. Juancho.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
In generally, standalone file is useful, if you want use one custom dictionary file for all your projects. It give you one centralized custom dictionary on your PC for all your projects, but this is not good solution, if you want exchange custom dictionaries with your translators. Saving custom dictionary to project file is good solution, if you want exchange custom dictionaries with your translators, but it doesn’t create centralized custom dictionary on your PC for all your projects. In your case, best solution is saving custom dictionary to project file, so we should find some solution for reproduce your issue. Unfortunately, now I need go out from my office, but I’ll try find tomorrow some way for reproduce your problem. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Juancho, Could you tell me if you resolved your issue with Sisulizer reinstalling (library registration)? You sent project file, but without translations and with empty custom dictionary content. I can’t reproduce issue, because when I added new entries to custom dictionary Sisulizer (on my PC) saves it in correctly place in project. Could you send to us your incorrectly working project file, but with custom dictionary entries added to project on your PC? Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
jbueno25 Member
|
>Could you tell me if you resolved your issue with Sisulizer reinstalling (library registration)? No, I didn't resolve this issue installing or reinstalling Sisulizer. I tried to install in a clean machine, reinstall it, reinstall in my test machine... > Could you send to us your incorrectly working project file, but with custom dictionary entries added to project on your PC? I send you a project with a source (Systen.Printing.dll) and two words in "en" and "es" dictionaries:
Could you reproduce this behaviour? Juancho.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
If I add a word In Original column, Sisulizer stores it in a source node; if I add a word in Spanish column, it's stored in document node, out of a source node. Exactly. Custom dictionary data for originals aren’t assigned to language (look on spelldata syntax in SLP file), but to source, and for this reason spelldata tag content is saved in project file as source class sub-node.
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
No, I didn't resolve this issue installing or reinstalling Sisulizer. I tried to install in a clean machine, reinstall it, reinstall in my test machine... I’ll forward your bug report to our developers. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
jbueno25 Member
|
>Exactly. Custom dictionary data for originals aren’t assigned to >language (look on spelldata syntax in SLP file), but to source, and for > this reason spelldata tag content is saved in project file as source >class sub-node. Ok. Then, there are no errors. It's right behavior, because I'm checking Original column!!!!! The only question I have is (see first post): >The words added to customized dictionary are saved in a source node > in the slp file. It's a problem when source is excluded or removed, > because those words are ignored in spell checking. It's an strange behaviour. Isn't it? I found a way to solve it: add a column with original language (en); right click on Original column header > click "Language properties" from context menu > "Spelling" tab and change "Spell Checker" to "Use 'en' spell checker". Then, Sisulizer stores all words in the "spelldata lang=en" node, out of source node. It solves my problem!!!!!! Now, I have other issues:
I'm grateful for your help (thanks for your patience), Juancho
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
This configuration is not saved in slp project. I have to configure original column spellchecker everytime I load the project Thank you for found it. I forwarded already information about this bug to our R&D. When I remove the english column... all words dissapears. (This is not important). This is normal. If you use saving custom dictionary to project, Sisulizer remove dictionary when you remove selected language from project, because dictionary is dedicated only for this project, so if you remove language, dictionary for this language is useless. If you would like share custom dictionary with other projects, you should use custom dictionary as standalone file. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Janusz Grzybek wrote: Thank you for found it. I forwarded already information about this bug to our R&D. I fixed this in build 290. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Jaakko implemented to build 290 custom dictionary export/import feature (to/from ANSI text files or XML files). Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 09:23 pm | Page: 1 2 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Customized dictionary data are saved at source level | |
Sisulizer software localization tool - Three simple steps to localize
