HTML localization is very simple in Sisulizer because it is visual, safe and it uses segmentation. Sisulizer extracts the visual HTML data and adds them to the project. When creating localized file Sisulizer creates an identical copy of the original HTML file except it contains is in the target language.
In some case several HTML tags should be translated as a single entry. For example you might have text data that contains formatting tags. The following tag contains a plain text:
<p>Finland is the most northern country in the world</p>
If you want to underline the the word most you might store the data in the following way:
<p>Finland is the <u>most northern</u> country in the world</p>
This will break the sentence in three different parts: "Finland is the ", "most" and " country in the world". To translate them separately is impossible or at least very hard. This is why Sisulizer embeds the formatting tags inside a translation unit (e.g. row). When editing the translation Sisulizer shows visually the inline tags. This makes it easy to produce similarly formatted translations.
In many cases HTML contains paragraphs that contains several sentences. In such case Sisulizer by default breaks the paragraphs into segments. Each segment is one translation gentry and it appears on its own row. Segmentation makes translation easier and it also makes reuse of translations much more useful.
By default Sisulizer scans (and localizes) only those strings that have been marked to be localized. For example if you have the following code:
str = "Hello world";
Sisulizer does not scan it unless you tag it. A tag is a slz comment on the same line as the string.
str = "Hello world"; //slz
You can change the scan logic opposite: to make Sisulizer to scan everything except tagged ones. In this case you have to use noslz tag.
str = "This is not localized"; //noslz
No matter what your tag mode is you can always use slz tag to give information about strings.
Information/include tag is used to pass string properties to the project. The syntax is
<comment><tag>[comment string|attribute]... attribute=MaxChars=mc|MaxPixels=mp|Expression="expression"
where comment is the single line comment character (e.g. "//"), tag is a tag string (e.g. slz), mc is the maximum length of the translation in characters, mp is the maximum length of the translation is pixels, and expression is the combined string expression.
The following line has an include tag that makes Sisulizer to scan the string.:
str = "Hello world"; //slz
The following line has an information tag that contains a comment ("Clicking this button opens on-line help") and sets the maximum length to 300 pixels:
str = "Click Help to get more information"; //slz MaxPixels=300 Clicking this button opens on-line help
Shows translated HTML 100% WYSIWYG.
Sisulizer's HTML directory contains HTML samples.