PDA

View Full Version : Bugs in v5.0.0 (build 3667)


libojun
09-09-2013, 02:47 PM
1. The current version does not support the "Custom Date Format"

I'm trying to custom the Date Format and make it display personality in Windows 7, but when I run the FlashFXP,

Oh! what has happened...? :razz:


PS,

Date Format Setting:
yyyy '年' M '月' d '日' dddd

Time Format Setting:
HH:mm:ss

libojun
09-09-2013, 03:07 PM
2. The problem of Asian "Double Byte Character Set" still not solved

Well, it seems that the default character set and the environment of FlashFXP does not support or compliant with the Asian "Double Byte Character Set", and the FlashFXP Splited the "Full Double Byte Chinese Character" into two "Single Byte Characters", so it made the current version"Cannot show Chinese Correctly"!

And, I think the Japanese and Korean language would got the same problem because they use the "Double Byte Character Set" also!

bigstar
09-09-2013, 03:14 PM
1. The current version does not support the "Custom Date Format"

I'm trying to custom the Date Format and make it display personality in Windows 7, but when I run the FlashFXP,

Oh! what has happened...? :razz:

PS,

Date Format Setting:
yyyy '年' M '月' d '日' dddd

Time Format Setting:
HH:mm:ss

Can you please export the following section from your registry.

HKEY_CURRENT_USER\Control Panel\International

You'll need to zip it up in order to attach it to your reply, .reg files cant be attached directly.

libojun
09-09-2013, 03:21 PM
Can you please export the following section from your registry.

HKEY_CURRENT_USER\Control Panel\International

You'll need to zip it up in order to attach it to your reply, .reg files cant be attached directly.

OK, here is it.

bigstar
09-09-2013, 03:58 PM
2. The problem of Asian "Double Byte Character Set" still not solved

Well, it seems that the default character set and the environment of FlashFXP does not support or compliant with the Asian "Double Byte Character Set", and the FlashFXP Splited the "Full Double Byte Chinese Character" into two "Single Byte Characters", so it made the current version"Cannot show Chinese Correctly"!

And, I think the Japanese and Korean language would got the same problem because they use the "Double Byte Character Set" also!

Are you 100% that the translation is correct?

I am fairly sure that this issue is caused by a bad language translation file.

We have had a problems with the translation sent during submission not being UTF8 encoded and instead they were sent as double byte characters. FlashFXP and the translation manager expects the text as UTF8, while double byte characters may render correctly under some conditions they will not everywhere and that is why we use UTF8. I am still trying to figure out why, when, and how this happened, its possible that when the base of these translations were converted from v4.x that the conversion process was flawed.

Additionally the language files on our website located here (https://oss.azurewebsites.net/languages) should not be used with v5.0, they are v4.x specific.

libojun
09-09-2013, 04:17 PM
3. Grammar problem: Different Language in Different Environments would got Different translation

In the new language file, the String "03EECE5A=Total" has been quoted everywhere in FlashFXP v5. Maybe it meet the specifications of English grammar, but it would not suit for other languages, and made other translators not easy to translate.

So, would you please make it "One by One", not "All in One"?

libojun
09-09-2013, 04:22 PM
Are you 100% that the translation is correct?

I am fairly sure that this issue is caused by a bad language translation file.

We have had a problems with the translation sent during submission not being UTF8 encoded and instead they were sent as double byte characters. FlashFXP and the translation manager expects the text as UTF8, while double byte characters may render correctly under some conditions they will not everywhere and that is why we use UTF8. I am still trying to figure out why, when, and how this happened, its possible that when the base of these translations were converted from v4.x that the conversion process was flawed.

Additionally the language files on our website located here (https://oss.azurewebsites.net/languages) should not be used with v5.0, they are v4.x specific.


Yes!

I'm 100% sure that I got the newest language file because I got it from http://lang.flashfxp.com/5/download/Chinese%20Simplified

And, it is Download / Update automatically by FlashFXP v5 everytime.

bigstar
09-10-2013, 03:40 PM
Okay good news.. I found out what went wrong... There was a mistake on my part. *phew* I thought I was losing my mind..

I am working on all of these bugs together as a single fix and hope to post a new build tonight or tomorrow. I need to finish up some additional testing to make sure nothing was missed.

bigstar
09-10-2013, 03:54 PM
3. Grammar problem: Different Language in Different Environments would got Different translation

In the new language file, the String "03EECE5A=Total" has been quoted everywhere in FlashFXP v5. Maybe it meet the specifications of English grammar, but it would not suit for other languages, and made other translators not easy to translate.

So, would you please make it "One by One", not "All in One"?

As soon as all UTF8/Unicode issues are resolved I plan to do a full review of the translations and I have quite a few changes planned, please remind me of this if you don't see it changed.

We need to come up with a better way of separating nouns and verbs because in many instances the wrong translation is used. X3 had suggested that each translation has a developer/user comment area where additional information regarding the text could be displayed while simple to implement, it would be difficult and very time consuming to comment each individual line.

X3
09-11-2013, 06:14 AM
3. Grammar problem: Different Language in Different Environments would got Different translation

In the new language file, the String "03EECE5A=Total" has been quoted everywhere in FlashFXP v5. Maybe it meet the specifications of English grammar, but it would not suit for other languages, and made other translators not easy to translate.

So, would you please make it "One by One", not "All in One"?

Im not sure if I understand exactly what you mean by this, I cant see anything quoted in the English part, if the translators have quoted the translation string and that's not correct then surely then the translation should be right.

I also dont know what "one by one" and "all in one" means, do you mean that different individual translated words are being mixed together to create a new sentence?? IF yes then it is a problem, currently FFXP uses string combinations to create a message and ideally because other Languages are not as simple as English, the mixing ends up creating a wrong resulting translation.
I have suggested that instead of using string A + String B to create a new sentence/phrase or line that such translations become a whole new stringset and they are translated as a whole.

All and all In Portuguese for e.g. where there can exist Nouns, Verbs, Masculine and Feminine in one sentence can result in very wrong compound translations, I can only imagine what other complex Languages like Chinese handle this.

I would like to see the examples of what you mean by "Different Language in Different Environments would got Different translation"
In v5 The Portuguese Translation got a massive overall and is still under review, The accuracy of the Translation was around 60% at best, it is now over 90% those 10% missing are for the compound strings still in use. It took me weeks to improve the translation and there is much work to do still. The point is that The words in PT Windows OS MUI vs FFXP Translated Words are now the same, for e.g. Copy, Paste, Delete etc.

Yes Translators work is not easy, but hopefully the feedback We provide to bigstar is improving the translator and strings, just because of this feedback I provided bigstar has fixed many issues in the strings and how and where they are used. Much work remains to be done, but it is being done. I have suggested string comments so that we can include information like where the translation is used other useful info so thta translators dont have to find out like I did, that some translations were in wrong context resulting in confusing results.

Thanks for reading this long post and hopefully it will help you in some way.

bigstar
09-11-2013, 07:01 AM
Please try v5.0.0 build 5669 and let me know if the problems are solved.

I tested several different combinations of windows versions with multiple different locales and I think everything should be working however please let me know of any problems.

libojun
09-11-2013, 08:22 AM
In build 3669, most of them are fixed, but some place still not...

such as

bigstar
09-11-2013, 09:13 AM
In build 3669, most of them are fixed, but some place still not...

such as

Thank you, I have fixed these and while fixing them I also noticed "Sites > Key Manager" dialog in the expiration field and the "Valid from" on the "SSL Certificate" dialog.

Have you found any others? I'll post the fix for these in about an hour or two once do another sweep to see if any others were missed.

libojun
09-11-2013, 02:21 PM
Thank you, I have fixed these and while fixing them I also noticed "Sites > Key Manager" dialog in the expiration field and the "Valid from" on the "SSL Certificate" dialog.

Have you found any others? I'll post the fix for these in about an hour or two once do another sweep to see if any others were missed.

I have got the build 3670 just now, and it seems that they are all fixed! :)

libojun
09-11-2013, 03:35 PM
Im not sure if I understand exactly what you mean by this, I cant see anything quoted in the English part, if the translators have quoted the translation string and that's not correct then surely then the translation should be right.

I also dont know what "one by one" and "all in one" means, do you mean that different individual translated words are being mixed together to create a new sentence?? IF yes then it is a problem, currently FFXP uses string combinations to create a message and ideally because other Languages are not as simple as English, the mixing ends up creating a wrong resulting translation.
I have suggested that instead of using string A + String B to create a new sentence/phrase or line that such translations become a whole new stringset and they are translated as a whole.

All and all In Portuguese for e.g. where there can exist Nouns, Verbs, Masculine and Feminine in one sentence can result in very wrong compound translations, I can only imagine what other complex Languages like Chinese handle this.

I would like to see the examples of what you mean by "Different Language in Different Environments would got Different translation"
In v5 The Portuguese Translation got a massive overall and is still under review, The accuracy of the Translation was around 60% at best, it is now over 90% those 10% missing are for the compound strings still in use. It took me weeks to improve the translation and there is much work to do still. The point is that The words in PT Windows OS MUI vs FFXP Translated Words are now the same, for e.g. Copy, Paste, Delete etc.

Yes Translators work is not easy, but hopefully the feedback We provide to bigstar is improving the translator and strings, just because of this feedback I provided bigstar has fixed many issues in the strings and how and where they are used. Much work remains to be done, but it is being done. I have suggested string comments so that we can include information like where the translation is used other useful info so thta translators dont have to find out like I did, that some translations were in wrong context resulting in confusing results.

Thanks for reading this long post and hopefully it will help you in some way.


Well, I have got a easy way to solve this problem, maybe other similar problems can be solved like this!

bigstar
09-12-2013, 11:22 AM
I think this might just be the perfect way to resolve this problem.

Let me see what I can do for the next release.

bigstar
09-14-2013, 03:59 PM
I have released build 3671 with the following changes.

I've added the following new translation strings

%s File
%s Files
%s Folder
%s Folders
%s Total
%s Selected
%s Free

and I added the ? to the string

Are you sure you want to delete the selected task(s)?

I've refactored some code to optimize it for speed and resolve a performance penalty that was introduced over the past few builds.

This build also includes the latest icon set by X3.

This build also addresses some issues where if a "Network Error (10054): Connection reset by peer" error was triggered during certain operations no automatic reconnect was performed.

This includes CHMOD operations, on file download of a remote view/edit (on upload worked correctly), and while changing directories.

libojun
09-15-2013, 02:55 AM
I have released build 3671 with the following changes.

I've added the following new translation strings

%s File
%s Files
%s Folder
%s Folders
%s Total
%s Selected
%s Free

and I added the ? to the string

Are you sure you want to delete the selected task(s)?

I've refactored some code to optimize it for speed and resolve a performance penalty that was introduced over the past few builds.

This build also includes the latest icon set by X3.

This build also addresses some issues where if a "Network Error (10054): Connection reset by peer" error was triggered during certain operations no automatic reconnect was performed.

This includes CHMOD operations, on file download of a remote view/edit (on upload worked correctly), and while changing directories.

I have updated to build 3671, and got the similar problem:

It seems need to add another new translation strings to the language file

X3
09-15-2013, 05:19 AM
@libojun

Language Modified strings within the Translator (where you highlighted) is part of server side text, these strings are not translatable I dont think, you need to find another example since server side string aren't translatable at the moment.

@bigstar

I did find some clipping in site manager where the line height is smaller then others so it clips the g in this line only, see

http://snag.gy/9LdDB.jpg

I've translated those string to PT as well and fixed another half dozen. cheers.

libojun
09-15-2013, 05:37 AM
Language Modified in the Translator is part of server side text, these strings are not translatable I dont think.

Nope!

You can find this strings at "A61D0EFA=Modified" in the language file.

And, this string has quoted to 2 places at least. (as the above (https://oss.azurewebsites.net/forum/attachments/flashfxp/flashfxp-v5-x-public-beta/1359d1379231941t-bugs-v5-0-0-build-bug-3-4.png) and following (https://oss.azurewebsites.net/forum/attachments/flashfxp/flashfxp-v5-x-public-beta/1360d1379241975t-bugs-v5-0-0-build-bug-3-4-2.png) picture)

libojun
09-15-2013, 06:15 AM
4. The string "B19943CE=bytes" in the language file seems Not Work!

I have translated it, but in the GUI, it still show me the English string.

X3
09-15-2013, 07:13 AM
Are you sure that its ok to translate a measurement unit, since these are standard networking terms/names, imo many of these are not ok to be translated. Accurate translations is one thing and like for like translations are not always the best practice.

The server side strings I never noticed them being translatable but idk whats going on.

libojun
09-15-2013, 08:20 AM
Are you sure that its ok to translate a measurement unit, since these are standard networking terms/names, imo many of these are not ok to be translated. Accurate translations is one thing and like for like translations are not always the best practice.

Actually, all of those "measurement unit" has its corresponding translation norms in Chinese languge. (I don't know if other languages also like this?) So it is no need to doubt its accuracy, and, it would be easier to be translated.

X3
09-15-2013, 08:56 AM
If Everywhere in Chinese, like OS and other common programs you find these things also translated then the translation should be equal to that which is commonly found (so its consistent and accurate).

Some things are not meant to be translated because they are universal, like mathematical terms, measurement units. But having said that Im not familiar with Chinese.

Interpreting and translating is not equal. Most of time I find translations are interpretations rather than translations and most of the time they are interpreted inaccurately and incorrectly.

libojun
09-15-2013, 09:39 AM
If Everywhere in Chinese, like OS and other common programs you find these things also translated then the translation should be equal to that which is commonly found (so its consistent and accurate).

Some things are not meant to be translated because they are universal, like mathematical terms, measurement units. But having said that Im not familiar with Chinese.

Interpreting and translating is not equal. Most of time I find translations are interpretations rather than translations and most of the time they are interpreted inaccurately and incorrectly.

Well, maybe you misunderstood what I want to express.

I just means somewhere other programs has been translated (such as a standard multi-language software of Microsoft ), and the previous version of FlashFXP has also Included that strings, but the new version does not works correctly, so it would be a bug in the new version, and it should be fixed. No more means! Maybe you Imagined that as "Everything Should Be Translated, No One Can Be Left!" :confused:

And, I have checked the string "A61D0EFA=Modified", 100% sure that is a "Fixed and full Locally string", not the "server side strings". (You can Confirm it by yourself) :laugh:

bigstar
09-15-2013, 10:23 AM
I am changing the usage of "Modified" to work as followed.

Modified will now only be used in the following 3 places
Text Editor dialog, Active Edits dialog, Language dialog

It will be used exclusively to indicate that the file has been modified.

The "Modified" and "Date" column names are changing to match the English wording "Date Modified"

This was something that should of been done along time ago.

I believe X3 was referring to the use of "bytes" when he replied to you.

In v5 the way translations are done is somewhat different compared to v4, as a result some strings that were previously translated might not be translated, a good example of this is "bytes", please let me know of all situations you encounter like this and I will fix them. this will be corrected for the next build.

X3
09-16-2013, 12:24 AM
Yes I was referring to bytes, but libojun is saying that hes translated it and that the translation doesn't work or show up.

libojun
09-16-2013, 01:26 PM
Yes I was referring to bytes, but libojun is saying that hes translated it and that the translation doesn't work or show up.

Well, actually, some "measurement unit" already has its corresponding translation norms and a good
quality, not only in Chinese but also others language. (such as Japanese, Korean) You can Search them at http://www.microsoft.com/Language/ , it would be help to you!

I also noted that the localize team of Portuguese does not going to translate some of "measurement unit", maybe due to the customs and habits or something else.

My suggestion is, keep all of similar strings in the language file, and give all of translators the rights to choose if they need/want to translate them or not, and respect their choice and customs and habits.

Nowadays, the FlashFXP no longer a "English Only" program, it would be a "International Multilingual software". So I just hope it could keeps an "Open and Tolerant attitude" eyes to the future!

msg7086
09-16-2013, 04:23 PM
Yes I was referring to bytes, but libojun is saying that hes translated it and that the translation doesn't work or show up.
Well since the word is 'byte' not 'B', it should be translated to the native language presentation, if it exists.

The same applies to the 'kilobyte' (which should be translated) and 'KB' (which should not, IMHO).

So that if a file is less than 1KB, it appears as, let's say 500 bytes, it should be 500 å*—节, while if it's 10KB, it would be 10KB.

YMMV.

X3
09-16-2013, 07:02 PM
Yes I understand That Chinese has these "rules" though if you look at it, consistency is throw out the door.

Though the only thing that matter is that it is indeed correct and common place and is consistent with however rules for translations are done.

I have learned something interesting about your Mother tongue today.