Loading Profile...
CHAMP
Strange rendering of non-ascii chars.
It looks like Expono displays non-ascii chars in a strange way. Look at this image http://www.expono.com/jemostrom/photo... notice how "Åsele" in the title is displayed. Here is how it looks like on my computer
I’m happy
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
-
Inappropriate?Hmm.. it looks fine for me in Safari 4.0.3 and Firefox 3.0.14
Which browser are you using?
Did you enter the title manually or was it extracted from IPTC/EXIF ?
Everything in Expono is UTF-8 based. Data is stored UTF-8 encoded, displayed as UTF-8, handled in the web server as UTF-8.
Data imported from external sources are UTF-8 encoded (maybe we missed something?)
I’m encoded
2 Comments
Add a comment
This solves the problem
-
Hmmm, that's bad I can't find the original picture ... I seem to have deleted it. Don't know how that happened. Anyway, it was probably embedded in the image (all other photos from that set have that title in Aperture). I don't remember how it was uploaded but I'm 99.9% sure that it was using the flash uploader.
I'm using OS X 10.6.1, Safari 4.0.3 (6531.9). If I use FF v3.5.4 then it looks OK. So apparently there is some interaction with Safari. -
The original is kept untouched on expono, so you can just download it :-)
-
Inappropriate?Yep
-
Inappropriate?I guess this wasn't an issue?2 Comments Add a comment
This solves the problem
-
Well, the problem is the same but I seem to remember that I've seen a similar problem at another place. UTF-8 in IPTC seem to be a problem.
-
Ok, if this problem persists we have to fix it. Let me know if you encounter more weird stuff. Please, provide an example photo if you do. Thanks for highlighting the issue!
-
Inappropriate?
Hmmm, I just did a test upload of this photo http://www.expono.com/jemostrom/photo... and here it happens on the 'ä' (see screendump). I've used Aperture to enter the text and generate the jpg. I'm using Snow Leopard (did a clean install since my first message on this subject) with the latest updates
3 Comments Add a comment
This solves the problem
-
Which screendump? I checked the photos and it looks right to me (displaying lägret correct) in Safari on Leopard. Did you fix it manually?
-
I see .. lol .. missed your embedded screenshot :)
-
Ok.. I got Aperture myself, so I can see if I can reproduce the problem. It may double UTF8-encoded strings or something like that... character encodings is a ***** :)
-
Inappropriate?To give you an update on this topic.
After some research this week we have come to the conclusion that we will make some major changes to the code which extracts IPTC and EXIF information. The reasons for this is that we have seen a few (not many, but still countable) compatibility problems between software and camera makers.
The source of the problem is the EXIF parser we use, which is not reliable. It sometimes tries to be too smart and validate EXIF data by itself, which can result in missing data. In order words, exif data returned to us has been stripped (this usually affects GPS information which doesn't have a clear standard).
We have found a great replacement which I think will solve most if not all problems we've had. It also have support for XMP, which is has been high up on the feature request list.
This means we won't spend time to find your issue, in the old code. I hope these changes will be available within a couple of weeks. It has to be rolled into another upcoming update. -
Inappropriate?Sorry about the trouble --- but I hope that it wasn't just me causing this extra work :)
I’m happy
1 Comment Add a comment
This solves the problem
-
Oh no :) I was following up on another user's missing GPS info, when I found out that our EXIF parser was behaving unreliable. Anyway, I'm very excited about this change, because I believe we will have less meta data compatiblity issues. Let's not forget about XMP support :)
But it requires a great deal of testing. We don't want to introduce new bugs :)
EMPLOYEE
