Author Topic: Automatic conversion of Metadata (IPTC) into 7-bit ASCII when transmitting photo  (Read 553 times)

Offline Claude Diderich

  • Newcomer
  • *
  • Posts: 39
  • Claude Diderich
    • View Profile
    • Claude Diderich Sports Pictures
Some clients to which I send photos via ftp only allow ASCII characters, while others support accented characters, for example, in player names like "Alizé Cornet" versus "Alize Cornet". It would be great if PM could offer a functionality (checkbox) in the File Uploader (for example, below "Apply Metadata (IPTC) Template") that states "Replace IPTC Encoding with ASCII" and would replace any non-7bit-ASCII character by its closes approximation in the ASCII set when transmitting the photo. I want retain fully accented metadata in my written captions locally, while also adhering to 7-bit ASCII requirements that multiple clients of mine have without having to manually tweak the caption data.
Claude Diderich, sports photographer, member of AIPS and sportpress.ch
Mülibachstrasse 49, CH-8805 Richterswil, Switzerland, phone: +41 (44) 450 81 66, fax: +41 (44) 450 81 19, mobile: +41 (79) 450 81 66, e-mail: cdiderich@cdsp.photo, internet: http://www.cdsp.photo/

Offline ulrik

  • Member
  • **
  • Posts: 52
    • View Profile
Would be nice but you can also do it through code replacement (I do that with some).

Offline Claude Diderich

  • Newcomer
  • *
  • Posts: 39
  • Claude Diderich
    • View Profile
    • Claude Diderich Sports Pictures
The challenge with using code replacements seems to me that they are final (once the replacement has been made), or is there a functionality that does CRs only when transmitting, but not when viewing the metadata. I really want to be able to send a photo to A with accents and to B without accent and then store the photo in my database with accents. How would you do this with CRs?
Claude Diderich, sports photographer, member of AIPS and sportpress.ch
Mülibachstrasse 49, CH-8805 Richterswil, Switzerland, phone: +41 (44) 450 81 66, fax: +41 (44) 450 81 19, mobile: +41 (79) 450 81 66, e-mail: cdiderich@cdsp.photo, internet: http://www.cdsp.photo/

Offline ulrik

  • Member
  • **
  • Posts: 52
    • View Profile
I think you would do the following (but that might not work with you. We all have different needs):

on your Code replacement file:

a10 (shirt number etc)        Alizé Cornet       Alize Cornet

The above means that if you write /a10#2/ you get Alize Cornet.

But back to a possible solution (I use similar to make it all as quick as possible)

Type a10 (in the above example) into one field (lets say Identity)

Then for client A you have an IPTC template where the following is written where you need the above

/{identity}#2/ gives you Alize Cornet

And then client B:

/{identity}/ gives you Alizé Cornet

And you either send the accented one or run the IPTC template with accented  one in the end.

The problem is if you have to add many players etc. So not perfect at all....