Modifying raw data contained in File Info: Is it possible?
Learn / Forums / General InDesign Topics / Modifying raw data contained in File Info: Is it possible?
Tagged: extensis, FONTS, metadata, Scripting, troubleshoot
- This topic has 2 replies, 1 voice, and was last updated 3 years, 8 months ago by Brett Stone.
-
AuthorPosts
-
-
August 7, 2020 at 11:30 am #14328464Brett StoneParticipant
I’m addressing a challenge related to Extensis Suitcase/Universal Type Client fontsense data. This is data saved into each layout that improves auto font activation, even when multiple versions of a typeface may be available to choose from.
The problem: we have thousands of ‘older’ files that contain fontsense data for “yyzFace”, but “yyzFace” is no longer used in the layout. Even when we save as or save as idml the fontsense data is kept in the file, and we receive numerous ‘font not found’ messages for these ghost fonts.
Viewing File Information/Raw Data tab reveals the xml data for each typeface:
<rdf:li rdf:parseType=”Resource”>
<ExtensisFontSense:Family>yyzFace</ExtensisFontSense:Family>
<ExtensisFontSense:Version>1.001</ExtensisFontSense:Version>
<ExtensisFontSense:OutlineFileSize>0</ExtensisFontSense:OutlineFileSize>
<ExtensisFontSense:KerningChecksum>0</ExtensisFontSense:KerningChecksum>
<ExtensisFontSense:Foundry>–</ExtensisFontSense:Foundry>
<ExtensisFontSense:FontKind>OpenType – PS</ExtensisFontSense:FontKind>
<ExtensisFontSense:Checksum>3695082371</ExtensisFontSense:Checksum>
<ExtensisFontSense:PostScriptName>yyzFace</ExtensisFontSense:PostScriptName>
<ExtensisFontSense:FontSense_1.2_Checksum>3695082371</ExtensisFontSense:FontSense_1.2_Checksum>
</rdf:li>
**
Is there a way to manually revise the raw data file associated with an InDesign layout?
Alternatively, is there a way to strip all fontsense data from a document so it can be resaved with the correct and current data?
**
I’ve tried accessing through InDesign (no way to edit), via the metadata panel in Bridge (fontsense data isn’t visible — maybe it’s not really metadata), etc.
And, yes, I’ve been working extensively with Extensis support with zero success.
Any input as to how I might do this — especially if it may be programmatic — is appreciated. -
August 11, 2020 at 1:28 pm #126517David GoodrichParticipant
You might try exporting the file info metadata to a *.xmp file and editing that with a text editor, and then re-importing the modified *.xmp back into ID. Note that importing has options to replace or append. Windows Notepad can serve for editing, but I prefer Notepad++. I have used this to adjust custom metadata categories visible in stock InDesign only as raw data. In fact, I made a modest custom XMP panel for IDCS6 that lets me see (and fill in) custom categories, and have delayed moving to Creative Cloud because I’d have to figure out how to revise it for CC.
Good luck!
David -
September 3, 2020 at 11:25 am #126527David GoodrichParticipant
Some further thoughts. A couple of threads over on Adobe’s InDesign forum offers some tips. “XMP
: Remove a nod from InDesign metadata” includes a useful snippet of Javascript. Also a comment to “Edit
IDML, remove metadata, save, again open in InDesign – can’t open” shows that going through IDML is unnecessary, and includes a longer snippet.
There used to be a complete Javascript for zapping a whole section of XMP metadata: around 2013 Hans-Gerd Claßen posted a complete script for deleting the contents of xmpMM:History, but my link to the forum no longer works (Adobe lists contributions under his username <-hans-> back to 2014).
-
-
AuthorPosts
- You must be logged in to reply to this topic.