|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Several suggestions about new features for the Sisulizer
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Several suggestions about new features for the Sisulizer
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page:   1 2 |
|
|||||||||||||||
| Several suggestions about new features for the Sisulizer - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Jaakko and Ilkka, Thank you for implementing ignore "&" prefix character option in search and filter features, but I’ve next idea about ampersand characters. Do you think about option for ignore this character in Translate duplicate? If you interest my proposal, I suggest following additional settings for this feature: - possibility of changing status translated duplicate with not matched character “&”(for example for fully matched duplicate is “auto translated", for duplicate with not matched “&” character could be “Best guess”), - option for adding missing ampersand characters to begin translated strings - user always can quick and easy fix incorrectly hotkeys characters by validation feature. I propose also Identical solution for Translation Memory - I think it is may be first step to “fuzzy matching” feature anticipated to the Sisulizer 2. Have a nice day, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
We will implement that. regards, Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, I have one idea for undo feature in SL. For safety my translated data in projects I save often my project during work, but unfortunately, the undo buffer is cleared after it, and I can not find my last changes. I suggest a bit another solution for undo feature. Do you think about using “ring buffer” to undo feature? This overwrites the oldest item if the capacity is reached. Additional, I propose possibility for set up buffer size (number of undo steps) by user. Best wishes, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello friends, Lately I translated two INI files (I don’t like this way implementation of Multilanguage to applications, but unfortunately many software now use it), and both original files contained bugs (duplicate of context). The Sisulizer during scanning displayed error message “List index out of bounds” and stopped scan, but after comparing partially created contents of scanned file in visual editor with contents of original file opened in text editor I found, and fixed bugs. Do you think about adding new additional message to output pane contains information about line number with error or line number with information about last correctly scanned line? This information allow users quick find similar problems in original file. If you interest my suggestion, I can send incorrect INI files for you. Best regards Janusz Last edited on Sat Mar 10th, 2007 12:01 am by Janusz Grzybek ____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Ilkka.Siikanen Administrator
|
In next build the undo buffer will not be cleared during saving the project Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, I’ve one note about feature “Duplicate Translations Fund”. Sometimes I can’t to choose translation, if appear this dialog during using feature “Translate using Translation Engine”. Probably, contents of neighboring rows or form appearance in visual editor could be help me to choose best translation from dialog “Duplicate Translations Fund”. Do you think about adding new option "Show row" to this dialog, for showing row and node in sheet and visual editor? Dialog “Duplicate Translations Fund” don’t have to lose activity during using potential feature “Show row”, will do to add to dialog window Minimize button, which improve preview highlighted row in sheet and visual editor. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, I’ve one small idea for HTML editor. Sometimes translated html files are placed in others directories than original or have other names, often translated web site has completely different directories structure, and translator need to change most internal links on web site. The Sisulizer has option for displaying A href attribute, but manually edition of hyperlinks is not comfortable and additional during manually edition user can make mistakes in edited links. Do you think about adding to sheet in the HML editor special dialog for hyperlink items with option for selection targeted file of hyperlink? Best Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Siikanen Administrator
|
At this point the sturcture of translated HTML-files must be identical with original. In the version 2.0 it is possible to edit href-values. regards, Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
“At this point the sturcture of translated HTML-files must be identical with original.” For this reason I use following method of work: - First, I change structure of original website (directories structure, file names etc.) - After that, I change links in the UltraEdit . This editor has possibility of changing these same links in many files at once. The Sisulizer also is very good tool for this action, because feature Translate Duplicates also change at once all these same links in project. - For changing others elements of websites (e.g. CSS or new elements not exists in original) I use Macromedia DreamWeaver. - For localization all translatable elements I use the Sisulizer. Below is example of website localized with the Sisulizer: Original website: http://www.axandra.com Website files are put in 5 separated directories (5 independent domain names) Translated website (to Polish): http://www.axandra.pl Contents of all independent directories was transferred to subdirectories in main directory of localized website (for example contents of the http://www.axandra-link-popularity-tool.com domain was transferred to http://www.axandra.pl/ARELIS subdirectory. Additional, some links are still pointed to http://www.axandra.com. Above website was my first big website localized with the Sisulizer, and during my work I found out that the Sisulizer is very good tool for localization of websites  !“In the version 2.0 it is possible to edit href-values.” Thanks! Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Do you think about adding support for MSI files? Some other software localization tools supports MSI installer files, for example The Passolo. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Yes. We will implement this in Sisulizer 2.0 Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, I am now very busy, but I try in all evenings to find moment for think about, how to make life of our developers hard:P Jaakko wrote in this topic about implementation online spell checking to version 2 of the Sisulizer, but some improvements could to be implemented earlier. 1. Do you think about adding exclude list for common special characters and strings, like &, \n, \r or html tags? 2. Unfortunately, main dictionary SpellPL.lex (I use the Sisulizer mainly to Polish localization of software) is imperfect, and spell checker in the Sisulizer recognize many common Polish words as mistakes, for this reason pane of validation after spell checking can contains hundreds of incorrect results, and this feature is permanently not useful with Polish language. This situation could be changed after adding possibility of managing custom dictionary in the spell checker feature. I don’t know how the Sisulizer works with the Polar Spell Checker, because the Polar Spell Checker is third part component in the Sisulizer, maybe, possible is filtering strings before spell checking, or filtering of results for the Validation pane? Adding above features can significantly improve spell checking in the Sisulizer. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:10 pm | Page: 1 2 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Several suggestions about new features for the Sisulizer | |
Sisulizer software localization tool - Three simple steps to localize
