National characters in tags not correctly displayed.
See enclosed screeshot. The "Ø" character is not correctly displayed (in "Lars-Erik Østerud").
Seems like the tags are only displayed for standard ASCII (up to 127).
National characters in tags not correctly displayed
Moderators: xnview, Dreamer
-
LarsErikOsterud
- Posts: 4
- Joined: Fri Aug 24, 2018 6:20 pm
National characters in tags not correctly displayed
You do not have the required permissions to view the files attached to this post.
-
xnview
- Author of XnView
- Posts: 48405
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
Re: National characters in tags not correctly displayed
sorry but there is no metadata in this file
-
LarsErikOsterud
- Posts: 4
- Joined: Fri Aug 24, 2018 6:20 pm
Re: National characters in tags not correctly displayed
This was only a screenshot of how the wrong chacters look...
I'll attach the image itself to this post so you can examine the tags...
I'll attach the image itself to this post so you can examine the tags...
You do not have the required permissions to view the files attached to this post.
-
xnview
- Author of XnView
- Posts: 48405
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
Re: National characters in tags not correctly displayed
you can change Settings>Metadata>Encoding - EXIF
-
user0
- XnThusiast
- Posts: 3080
- Joined: Sat May 09, 2015 9:37 am
Re: National characters in tags not correctly displayed
Your file lists 'AttributeMagic Pro' in the EXIF Software tag, which has known issues handling non-ASCII characters.
Test
I wrote 'ØÅ 국민 Λδ 旅ロ पढा 側経 йё եմ'
Under EXIF 2.x specifications, standard text tags (Artist, Copyright, Make, Model, Software, etc.) officially supported only 7-bit ASCII (Type 2). Because there is no standard character encoding header for these tags, apps that store non-ASCII characters must rely on custom logic, heuristics, or user settings to encode and interpret the raw data, often leading to display issues across different tools.
Worth noting that EXIF 3.0 introduced Type 129 specifically for UTF-8, providing an unambiguous way to identify UTF-8 text. However, Type 129 remains rarely used in practice, largely because software developers prioritize backward compatibility with legacy EXIF decoders that might ignore or fail on unrecognized tag types. Related suggestion
Test
I wrote 'ØÅ 국민 Λδ 旅ロ पढा 側経 йё եմ'
Under EXIF 2.x specifications, standard text tags (Artist, Copyright, Make, Model, Software, etc.) officially supported only 7-bit ASCII (Type 2). Because there is no standard character encoding header for these tags, apps that store non-ASCII characters must rely on custom logic, heuristics, or user settings to encode and interpret the raw data, often leading to display issues across different tools.
Worth noting that EXIF 3.0 introduced Type 129 specifically for UTF-8, providing an unambiguous way to identify UTF-8 text. However, Type 129 remains rarely used in practice, largely because software developers prioritize backward compatibility with legacy EXIF decoders that might ignore or fail on unrecognized tag types. Related suggestion
You do not have the required permissions to view the files attached to this post.