re-encode tags/comments which are not UTF8

[GoogleCodeExporter]

What steps will reproduce the problem?
1. import/refresh a picture with non-UTF8 encoding.

What is the expected output? What do you see instead?
jBrout currently displays correctly the data (which is fine), but it does
not alter the encoding.
I suggest that jBrout could offer to re-encode such data in UTF8. Of
course, I do not suggest that jBrout asks the question each time! This
should be a global setting, just like the renaming of files.

What version of the product are you using? On what operating system?
Windows XP SP3, jBrout 0.3.145 patched to revision 155.

Please provide any additional information below.
If it is accepted, this is low-priority IMO.

Original issue reported on code.google.com by davito...@gmail.com on 11 Jan 2009 at 1:41

[GoogleCodeExporter]

very very low priority ...

if you add/del a tag : it will rewrite all tags in utf8
if you add/mod a comment : it will rewrite jpeg-comment in utf8

this kind of thing should be done at import time ... but will slow down a lot a
refresh/import process (IO write)

Original comment by manat...@gmail.com on 11 Jan 2009 at 2:09

[GoogleCodeExporter]

Hmm, maybe it shouldn't even be an import option but a separate tool, so that 
users
could run it when they have the time.

Original comment by davito...@gmail.com on 11 Jan 2009 at 2:29

[GoogleCodeExporter]

Sounds like this would be ideal to write this as a plugin.

Original comment by r...@wallace.gen.nz on 11 Jan 2009 at 5:22

• Added labels: Priority-Low, Type-Enhancement

[GoogleCodeExporter]

Probably. Maybe it'll end up on my to-do list :-)

Original comment by davito...@gmail.com on 11 Jan 2009 at 6:04

[GoogleCodeExporter]

This is particularly uneasy as there is no way to know which encoding is used 
here.
It's even impossible to automatically detect that it's not utf-8 unless if it
crashes. The only reliable possibility would be to ask the user which encoding 
is
used and make the conversion. 

Original comment by tbenita on 11 Jul 2009 at 12:43

[GoogleCodeExporter]

Difficult to ask the user, since he may very well not know the answer. Even if I
remember which software put that string there, I would probably have 
difficulties
finding out what encoding this software uses. 

Ok. I'll try this: if there is a crash because of a non-utf8 string, handle it 
by
asking the user. I may show the original string as it would be transcoded using 
the
different character systems and let him choose the correct one. There is no 
hurry, I
seem to be the only one who has this problem, so please let me handle this, 
even if
it takes a few months :-)

(before someone makes a remark, yes, I am a big fan of asking the user :-) )

Original comment by davito...@gmail.com on 11 Jul 2009 at 6:24

[GoogleCodeExporter]

I think that generally people know what encoding is used, or at least which 
type. If you say "Western Europe" instead of ISO-8859-1, or "Eastern Europe" 
for ISO-8859-2, most people will have a clue, I guess.

Moreover, some versions of Exif/XMP data have explicite encoding provided.

Original comment by matej.c...@gmail.com on 7 Jul 2011 at 8:48

[GoogleCodeExporter]

Original comment by matej.c...@gmail.com on 12 Aug 2013 at 10:05

• Added labels: Component-plugins

[GoogleCodeExporter]

Original comment by matej.c...@gmail.com on 12 Aug 2013 at 10:06

• Changed state: Accepted