Question
ExtendScript fails to read UTF-8 but can write it?
I've found what looks like a massive bug in the ExtendScript SDK/API for Bridge but I cannot find anyone else complaining about it and I find it hard to believe I could possibly be the only person to have noticed.
Bridge CS3 v2.1.1.9, ExtendScript Toolkit v2.0.2.77
In Bridge right-click on a JPEG image, do file-info and enter in a title and description for the image ensuring you use accented or extended characters (French, German, Japanese, whatever). Now this should work because XMP uses unicode/UTF-8. Save your changes. Re-opening the file-info window shows the correct data, as does the right-hand metadata palette etc.
Now from the ExtendScript Toolkit, execute the sample code SnpInspectMetadata.jsx which comes as part of the Adobe Bridge CS3 SDK.
Observe the characters displayed in the JavaScript console within the ExtendScript toolkit are garbled.
For example, enter title: ロンドン
Displayed in console: ãã³ãã³
I have done further tests and as far as I can tell XMPMeta.setProperty() works fine, but XMPMeta.getProperty() doesn't read properties as UTF-8/unicode.
Can anyone else reproduce this and confirm my findings? Has anyone else experienced this problem... and does anyone have a solution?
Thanks
James.
Bridge CS3 v2.1.1.9, ExtendScript Toolkit v2.0.2.77
In Bridge right-click on a JPEG image, do file-info and enter in a title and description for the image ensuring you use accented or extended characters (French, German, Japanese, whatever). Now this should work because XMP uses unicode/UTF-8. Save your changes. Re-opening the file-info window shows the correct data, as does the right-hand metadata palette etc.
Now from the ExtendScript Toolkit, execute the sample code SnpInspectMetadata.jsx which comes as part of the Adobe Bridge CS3 SDK.
Observe the characters displayed in the JavaScript console within the ExtendScript toolkit are garbled.
For example, enter title: ロンドン
Displayed in console: ãã³ãã³
I have done further tests and as far as I can tell XMPMeta.setProperty() works fine, but XMPMeta.getProperty() doesn't read properties as UTF-8/unicode.
Can anyone else reproduce this and confirm my findings? Has anyone else experienced this problem... and does anyone have a solution?
Thanks
James.
