MantisBT - TestLink
View Issue Details
0002244TestLinkLocalizationpublic2009-03-18 06:462009-04-05 00:42
1.8 RC 5 
FF 3.06
0002244: CZ localization
I've attached complet CZ localization for RC5. BTW who is the owner of czech localization? There have to be one at least for coordination and check of vocabulary consistency.

Anyway I propose to change the way how the the language strings are converted. Currently, there is the conversion (via iconv) done each time, no matter if the source strings are in the same code page. Because I have significant problems with iconv (strings were cut before local specific chars, or local specific chars changed to questionmark), I did following changes in order to display the localized strings:

in file lang_api.php

old definition on row 67:

$the_str = iconv($TLS_STRINGFILE_CHARSET,TL_TPL_CHARSET,$loc_str);
new definition on row 67:

    $the_str = iconv($TLS_STRINGFILE_CHARSET,TL_TPL_CHARSET,$loc_str);;
    $the_str = $loc_str;

Because the problem with iconv and mb, have you think about replacement or enhancement? I would like to cooperate on implementation of convertcharset class ( [^]) as an alternative to iconv. Are you interested?
No tags attached.
zip (41,657) 2009-03-18 06:46
Issue History
2009-03-18 06:46mirosvadNew Issue
2009-03-18 06:46mirosvadFile Added:
2009-03-18 06:46mirosvadBrowser => FF 3.06
2009-03-18 06:46mirosvadPHP Version => 5.2.3
2009-03-18 20:13mhavlatNote Added: 0005898
2009-03-18 20:13mhavlatAssigned To => mhavlat
2009-03-18 20:13mhavlatSeveritymajor => text
2009-03-18 20:13mhavlatStatusnew => assigned
2009-03-19 05:12mirosvadNote Added: 0005903
2009-03-22 16:59mhavlatNote Added: 0005939
2009-03-30 06:16mirosvadNote Added: 0006062
2009-03-30 16:26mhavlatStatusassigned => resolved
2009-03-30 16:26mhavlatFixed in Version => 1.8.0
2009-03-30 16:26mhavlatResolutionopen => fixed
2009-03-30 16:26mhavlatNote Added: 0006064
2009-04-05 00:42mhavlatStatusresolved => closed

2009-03-18 20:13   
Hello Miro,
you added two things.
Czech strings: I will add your contribution to 1.8.1. There is not establish owner yet. I personally have minimal experience in Czech testing terminology. I considered to create some vocabulary document to define it. However I miss wider contacts with Czech testing authorities (if any exist).

Charset conversion: Could I ask to create a new record? I didn't experienced in this area. So I would like others to analyse the problem.

Thank you.
2009-03-19 05:12   
Hi Martin,

I think that we can consider ISTQB which have czech subsidiary as a testing authority. They have on english site glossary. As far as I look around there have to be probably czech equivalent. I send an email to ISTQB representative for czech and slovak republic. So we will see. Currently I have the syllabus for ISTQB certification so we can use that as the baseline anyway.

To be honest, as I work for international company we use rather english wording even in czech documents. :-) My qualification for translation is therefore based on texts from trainings and other internet sources :-) BTW current translation in RC5 for testcase is wrong. ;-) The previous one "Testovaci pripad" was correct.

For the proposed changes I will log new issue as you suggested.
2009-03-22 16:59   
I added the localization on both 1.8 branch and head. I run update script and new 135 definition was added into strings.txt. I localized some of them (but not all) :-(

Please, Let me know about response from TSTQB guys. I wonder.
2009-03-30 06:16   
Hi Martin,

alright there is another chapter from never ending story (the translation) :-)) I've got a reply from CASTB (Czech and Slovak testing board) So far they have slovak translation of glossary. They are currently working on czech one. You can find it here I will take the current translation from CSV Head and go through the rest of definitions without translation.

Anyway, I think that ISTQB glossary and their syllabus would be a good start point for any who will do the translation in any language (even for english one) Dont you think?
2009-03-30 16:26   
Great! I definitely agree to be compliant with they glossary. I did sometimes correction to this standard (in English), but not all of course.
Feel free to report also inconsistency in English terminology. Thanks.

I'm going to close this thread (for change log evidence). Please create a new record for next contribution or points. Thanks a lot. Anyway I hope that we will stay in touch.