As I had some 1.5 translation done and in process of translation I found it convenient to empty untranslated strings I needed a bit of code altering for my purposes (to show and count empty strings as untranslated). Thanks to Ifan's prompt response pointing me to right places in code I managed to do it. For those who would like to do the same:
in
com_fftranslation/helper.php (line 128 nn)
Code:
} else if ($v!='') {
if($v!=$ref_strings[$k]) {
$file['changed']++;
}
} ...
in
com_fftranslation/views/edit.php (line 68 nn)
Code:
} else if ($v['edit'] == '') {
$row->ref = $v['ref'];
$row->refshow = htmlspecialchars($v['ref']);
$row->cb = '';
$row->style = ';border-left:solid red 2px;padding-left:2px';
} ...
I still find some inconveniences in the way component handles counting translated vs untranslated.
Problem with counting 'unchanged' strings: In many cases of languages using Latin alphabet some strings stay the same which doesn't mean they are untranslated.
I don't understand how it chooses that file translation is complete. Maybe something is wrong at my side but it automatically turns files that have 84% (176/209) to complete. I think it counts unchanged strings as translated after all.
Said all this, maybe it would be better to clear all fields which are the same as in reference files and count only empty ones as untranslated. These strings which will stay the same as in reference file are usually one word strings so it is easy to copy them in process of translation. With this method we can get exact number of translated strings and no confusion. It would also enable beter groupworking if component 's multireplace tool would skip replacing combos with empty definitions. It should then keep in memory all possible replacements for open files and apply them if definitions are left empty.
What do You think?
Other minor things:
It seems that select all doesn't work in files view.
I can't save preferences in Moz 1.7.13 (Gecko/20060414). I worked it out by altering default values in editor.
It also would be great to be able to decide if 'same KEY=String combos' should be replaced in other files when saving current document, not globally.
SAME_KEY=Same string combos which could be translated in many files at once are mostly repeated in Front End against Administrator, does the component handle it? (by now in case it doesn't I copied administrator files (reference and translation) into site folder with altered names)
_________________
Proud
Polish Joomla! Team Member > http://www.joomla.plHardcore Translator
Joomla! Translation Coordination Team
Jobs in IT:
http://www.workita.com
