I like the language editor as it is. Does exactely what it should do. There are some very annoying bugs however (text without variable-name). I'm still trying to find out what happens (so no bug reported yet). So I would like some reliability added.....
Thnx
Boudewijn.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I filed a RFE some time ago about some simpler way to get only the messages that is not already tranlslated. Some of the files there are quit a few lines and it is sometimes hard to find the line when it is in the middle. Maybe if you could choose in the Edit utility all or "not translated" lines. Otherwise a like the tool.
I have also have does random bugs talk about before. I haven't succeeded in geting the bugs to repet themeselfes in any predictable way
Best regards
Patrik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I didn't forget that RFE.
But as there were some other problems to be solved I have not found the time to implement this yet :-(
But normally also now it should not be such a problem, because the new messages are highlighted in red and can be found by just scrolling down the window.
bye, Kurt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Showing only the not-translated lines would be nice, but what about changed messages? I sometimes see them appear in the changelog, so I suppose the translators should do something with those messages too?
Boudewijn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think this is a point the developers should have an eye on.
Every time an adding to the english language files is made or a change on the content of a message of those files this should be added to the changelog.txt.
It should also be added to the changelog.txt if general changes to all language files are made.
For the changes I did to the language files and didn't write into the changelog.txt I want to say:
Mea culpa!
bye, Kurt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wasn't telling you off for not mentioning changes in the log :-) If they were missing, I hadn't noticed it yet!
What I meant was that it would be great to see changes too in the editor, showing in green or whatever, so we can (if neccesary) adjust the translation.
Bye
Boudewijn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Concerning the random bugs in the language editor, I can say that some of the bugs I encountered (perhaps all), was caused by false conditions in the language files.
The last time I encountered bugs, they were caused by the brute-force security handling of the html-entities and other special-chars, and as such I wouldn't blame it on the language-tool.
Best regards,
Arne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm losing track again... :-(
From Kurt I understand that the editor can handle any string and any character. Can you tell me some more about those "false conditions"?
Thnx
Boudewijn.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
and then I turned to manually doing the translations in a text-editor. At that time my main goal was to get the translations done, and therefore I didn't preserve any faulty conditions, and I didn't go into further investigations.
Still, the conditions created by the brute-force replacements probably created different conditions in different language files, and since I was using html-entities I may have encountered different conditions in my language files from what you have encountered in your language file.
At that time you said:
> One way or another the file contained a text with
> no variable name.
I too encountered that problem when trying to translate the new help_text.da.php, but since this happened at the same time when the other "brute force" problems happened, I simply blamed it on the "brute-force" method and did the rest of the translation in a text-editor.
I didn't encounter this problem again, and I don't blame it on the language tool. But then again, I don't expect the language tool to be able handle unforeseen problems in the language files. I do expect the language tool to handle everything correctly, which is feed to the language files using the language-tool.
Best regards,
Arne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, it was not my intention to do so!
Like you, I'm working hard on the help-translations, and after some problems I get triggered by the slightest remark ;-)
Boudewijn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
to translate the mising (new) tags to other languages surely is no problem, as you take notice of them immediately.
It took a while that I've noticed there also were changes to existing texts which made me comparing english latest release to english last but one release by file-compare. I must admit, that I didn't try to figure out the changes logged in lang_changelog.txt - maybe that's because the + and * are not to easy to discriminate....
Maybe that it would be a possibility to make the lang-editor "read" the changelog and mark any changed or added or deleted variables ? Would be the most comfortable way for the translators but it would require a properly written changelog (although after a glimpse I think it could meet the requirements).
What do you think Kurt, would that be possible / make sense ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Upppsss...
I thought the editing of help-files was implemented :-(
But it isn't :-(
I will add that :-)
The part with the extra files is also correct. Don''t know if this ever was intendet but it was always the way it is now. Maybe this is not so good for translators but it shows you the messages which are displayed inside PGV. This also means that if you want to translate the original language files you need to renema the extra files or delete the content inside them. But as I write this down I think I will have to think about that again :-)
Let's wait and see...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The first issue is IMO the most important, because it saves lots of time!
The second issue has (at least for me, knowing that the extra files are included) no high priority. So that gives you plenty of time to think it over thoroughly :-)
Boudewijn.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to ask the translators what they would like to add or change in the language editor...
bye, Kurt
Hi Kurt,
I like the language editor as it is. Does exactely what it should do. There are some very annoying bugs however (text without variable-name). I'm still trying to find out what happens (so no bug reported yet). So I would like some reliability added.....
Thnx
Boudewijn.
Hi Boudewijn...
I also wanted to talk about the bugs I really couldn't simulate on my system.
That's why I also need info about those probs.
I was away for about 1 days and couldn't follow the discussions.
I filed a RFE some time ago about some simpler way to get only the messages that is not already tranlslated. Some of the files there are quit a few lines and it is sometimes hard to find the line when it is in the middle. Maybe if you could choose in the Edit utility all or "not translated" lines. Otherwise a like the tool.
I have also have does random bugs talk about before. I haven't succeeded in geting the bugs to repet themeselfes in any predictable way
Best regards
Patrik
Hi Patrick...
I didn't forget that RFE.
But as there were some other problems to be solved I have not found the time to implement this yet :-(
But normally also now it should not be such a problem, because the new messages are highlighted in red and can be found by just scrolling down the window.
bye, Kurt
Showing only the not-translated lines would be nice, but what about changed messages? I sometimes see them appear in the changelog, so I suppose the translators should do something with those messages too?
Boudewijn
I think this is a point the developers should have an eye on.
Every time an adding to the english language files is made or a change on the content of a message of those files this should be added to the changelog.txt.
It should also be added to the changelog.txt if general changes to all language files are made.
For the changes I did to the language files and didn't write into the changelog.txt I want to say:
Mea culpa!
bye, Kurt
Hi Kurt,
I wasn't telling you off for not mentioning changes in the log :-) If they were missing, I hadn't noticed it yet!
What I meant was that it would be great to see changes too in the editor, showing in green or whatever, so we can (if neccesary) adjust the translation.
Bye
Boudewijn
Hi all
Concerning the random bugs in the language editor, I can say that some of the bugs I encountered (perhaps all), was caused by false conditions in the language files.
The last time I encountered bugs, they were caused by the brute-force security handling of the html-entities and other special-chars, and as such I wouldn't blame it on the language-tool.
Best regards,
Arne
Hi Arne,
I'm losing track again... :-(
From Kurt I understand that the editor can handle any string and any character. Can you tell me some more about those "false conditions"?
Thnx
Boudewijn.
Hi Boudewijn
I'm sorry, but now you are asking too much of me.
When the problems was encountered I mentioned some of the problems in this thread:
<http://sourceforge.net/forum/forum.php?thread_id=1003646&forum_id=294245>
and then I turned to manually doing the translations in a text-editor. At that time my main goal was to get the translations done, and therefore I didn't preserve any faulty conditions, and I didn't go into further investigations.
Still, the conditions created by the brute-force replacements probably created different conditions in different language files, and since I was using html-entities I may have encountered different conditions in my language files from what you have encountered in your language file.
At that time you said:
> One way or another the file contained a text with
> no variable name.
I too encountered that problem when trying to translate the new help_text.da.php, but since this happened at the same time when the other "brute force" problems happened, I simply blamed it on the "brute-force" method and did the rest of the translation in a text-editor.
I didn't encounter this problem again, and I don't blame it on the language tool. But then again, I don't expect the language tool to be able handle unforeseen problems in the language files. I do expect the language tool to handle everything correctly, which is feed to the language files using the language-tool.
Best regards,
Arne
Hi Arne,
Sorry, it was not my intention to do so!
Like you, I'm working hard on the help-translations, and after some problems I get triggered by the slightest remark ;-)
Boudewijn
to translate the mising (new) tags to other languages surely is no problem, as you take notice of them immediately.
It took a while that I've noticed there also were changes to existing texts which made me comparing english latest release to english last but one release by file-compare. I must admit, that I didn't try to figure out the changes logged in lang_changelog.txt - maybe that's because the + and * are not to easy to discriminate....
Maybe that it would be a possibility to make the lang-editor "read" the changelog and mark any changed or added or deleted variables ? Would be the most comfortable way for the translators but it would require a properly written changelog (although after a glimpse I think it could meet the requirements).
What do you think Kurt, would that be possible / make sense ?
The Edit tool should also work on the Research Log file.
Hi Kurt,
Translating the ever changing text of the 3.0 files, I noticed that not all files can be compared, it is not implemented yet for the help_xx files.
Also I noticed that in the comparison, the extra-files are included? Am I right? And was that your intention?
Boudewijn.
Upppsss...
I thought the editing of help-files was implemented :-(
But it isn't :-(
I will add that :-)
The part with the extra files is also correct. Don''t know if this ever was intendet but it was always the way it is now. Maybe this is not so good for translators but it shows you the messages which are displayed inside PGV. This also means that if you want to translate the original language files you need to renema the extra files or delete the content inside them. But as I write this down I think I will have to think about that again :-)
Let's wait and see...
OK Kurt, Thnx!
The first issue is IMO the most important, because it saves lots of time!
The second issue has (at least for me, knowing that the extra files are included) no high priority. So that gives you plenty of time to think it over thoroughly :-)
Boudewijn.
Hi Boudewijn...
Thank you very much ;-)
You are soooo generous to me :-)
We'll talk about that later (maybe on chat? but better at weekend...):-)
Hi Meliza...
Didn't understand, what you mean :-(
Meliza,
If the researchlog is installed, the rs_lang file appears automatically in the list of files you can choose for translation.
Boudewijn
Thanks!