Getting Clipping Path name with Japanese characters

[coffeesmell]

Is there a way of getting the clipping path name with japanese characters of an image?
I use the command `exiftool -clippingPath name image.eps`
But it returns garbled letters.

Any help will be appreciated.

[StarGeek]

I'm assuming you're on Windows, as Mac/Linux usually don't have a problem like this.

You can try the solutions in FAQ #18, but overall, Windows command line has problems with unusual characters.  Personally, I was never able to get any of the solutions in FAQ #18 to work. 

What worked for me was this StackOverflow answer, but it has the side effect of creating some font/spacing issues with some older Windows programs.

[coffeesmell]

Hi StarGeek,

Thank you for your suggestions.

Yes, you are correct, Im using windows OS.

I also tried by redirecting the output to a text file but still no luck.

Below are commands that I tried:

`exiftool -charset UTF8 -clippingPathName C:\src_img\test_jp.eps > C:\output\log\out_UTF8.txt`
`exiftool -charset Photoshop=UTF8 -clippingPathName C:\src_img\test_jp.eps > C:\output\log\out_photo_UTF8.txt`
`exiftool -charset exif=UTF8 -clippingPathName C:\src_img\test_jp.eps > C:\output\log\out_photo_exif_UTF8.txt`
`exiftool -charset filename=UTF8 -clippingPathName C:\src_img\test_jp.eps > C:\output\log\out_filename_UTF8.txt`

The `clipping path name` is 省がない
But the exiftool command output on the txt file is È,ª,È,¢

I also tried using exifToolGUI, but still the same result, garbled characters.

Still no luck.

I wonder if `Shift-JIS` is supported as charset?

[StarGeek]

Did you change the console to UTF-8 as per steps 1-3?

[coffeesmell]

Yes, I changed console to UTF-8 by following steps1-3 in changing system locale settings.

The clipping path name characters have changed to �Ȃ��Ȃ�

Still garbled.

[coffeesmell]

below attached file is the eps file i am checking on right now.

[StarGeek]

Yeah, I get nothing but garbage as well.  Hopefully someone with Mac/Linux can check the file.  If they see garbage as well, then the source is the problem.

[Phil Harvey]

Looks like garbage here.

Code Select Expand

Clipping Path Name              : È,ª,È,¢

Here is the binary from the -v3 output:

Code Select Expand

  | | ClippingPathName = ..........
  | | - Tag 0x0bb7 (15 bytes):
  | |     1e24: 08 8f c8 82 aa 82 c8 82 a2 00 00 00 00 00 01    [...............]


- Phil

[StarGeek]

Code Select Expand

  | | ClippingPathName = ..........
  | | - Tag 0x0bb7 (15 bytes):
  | |     1e24: 08 8f c8 82 aa 82 c8 82 a2 00 00 00 00 00 01    [...............]


And copy/pasting 省がない into a UTF8 to hex converter shows it should be
0xe7 0x9c 0x81 0xe3 0x81 0x8c 0xe3 0x81 0xaa 0xe3 0x81 0x84

coffeesmell, are you seeing 省がない in a program?  If so, what program?  Or if you wrote the data yourself, what program was used?

[coffeesmell]

Hi,

Im using Photoshop.

Attached below is screenshot file.

[coffeesmell]

can exiftool return the id number of the main clipping path?

Im just thinking that if the clipping path name has limits in charset, perhaps exiftool can return the id or order number of main clipping path?

[StarGeek]

can exiftool return the id number of the main clipping path?

Phil will have to answer that.

Unfortunately, I've got nothing on this.  I looked over the hex values of the name, trying to find some way to figure out why the output is different and came up empty.  The closest thing on the web I could find was this question which seems slightly similar but it's on a Mac.  And if the path name is showing up correctly if you close Photoshop down and then reopen the file, that link wouldn't really apply.

[Phil Harvey]

This one will take me a while to answer.

- Phil

[Phil Harvey]

I've generated a test file and analyzed the information.  The index of the clipping path is not stored, so what you are asking would have to be done with a Composite tag.  But this would be complex because you would have to start with the photoshop_paths.config file to first get the path names, and I don't have any time to help with this right now.

- Phil