Hi Bob! On 2016-01-16 06:13, Bob Bib <bobbib ukr net> wrote:
1) thanks for a fix!
BTW, have you noticed a little typo visible in the diff ("coversion"
instead of "conversion")?
"/* Prepare str for writing according to easytag charset coversion
settings */"
I have now! I pushed a typo fix: https://git.gnome.org/browse/easytag/commit/?id=238b1e3da15de8acd4ebad4749feb6751371b11c
2) can you please explain what effect do startup codepage guesses have? E. g. (from my previous message): === 01:21:20 System locale is ‘en_GB.UTF-8’, using ‘ISO-8859-1’ === 02:34:56 System locale is ‘uk_UA.UTF-8’, using ‘KOI8-U’ ===
Those are used as fallback encodings for converting to and from UTF-8 (the encoding used for display in the UI), if conversion fails, such as when old filenames exist on a system which predominantly uses UTF-8 filenames.
There has been a large amount of refactoring around encoding handling in EasyTAG recently, so the detection of fallback locales should now work more consistently. Also, filename on handling on Windows should work more reliably. The changes will be in an upcoming 2.4.1 release.
-- http://amigadave.com/
Attachment:
signature.asc
Description: Digital signature