RDF file info?

Hi,
Can anyone tell me which table in oracle apps database stores .RDF file information like name, location etc?
Thanks

Titas wrote:
Hi,
Can anyone tell me which table in oracle apps database stores .RDF file information like name, location etc?
ThanksHi Titas,
If you are talking about EBS, then your are in wrong form. Post at {forum:id=475} and close this thread marking as answered.
If someone's response is helpful or correct, please mark it accordingly.*

Similar Messages

.RDF file: Need info

Hi,
I have a .rdf file but I don't have report builder installed in machine. Is theere any way to view the underline sql in the data model?
I heard that there are some options where rdf can be converted to rtf file and then in microsoft word the underline query can be visible. Is it tru?
Thanks

Actually for that also you need Report Builder / the related executables.
Check the following links.
http://docs.oracle.com/cd/E10415_01/doc/bi.1013/e10416/convertrpts.htm
Convert Oracle Reports to BI Publisher
http://oracle-ebspro.blogspot.com/2012/01/rdf-to-bi-publisher-conversion-utility.html
By
Vamsi

How to make my old file info panel from photoshop work in xmp

Help. Not a photoshop guy but rather a genealogist. Many years ago downloaded a custom file info panel for photoshop which I used to enter meta text about the family photos I scanned. Currently using adobe creative cloud but cant figure out how to use panel or see most of my metatext last few version. Below is information about the panel. All I really want to do is install my panel and get back to genealogy. I apologize but not sure I need to understand the basics of photoshop..
john weis
[email protected]
This is the authors description of the panel:
Genealogy Photo (Private Collection) Custom File Info Panel 1.0 for Photoshop. 11 FEB 2007
Developed by Ron Reiger [email protected]
Please contact me to suggest improvements.
1. BASIS FOR THIS CUSTOM FILE INFO PANEL
2. DESCRIPTION OF EACH PROPERTY NAME
3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
1. BASIS FOR THIS CUSTOM FILE INFO PANEL
The Custom File Info Panel is used to capture metadata about a genealogy/family history photo that is privately held (that is, the photo is not in the possession of a library). The metadata property names on the File Info Panel are based on my interpretation of the recommended primary citation for a photograph (private possession) (annotated, with provenance) as described on page 95 of Elizabeth Shown Mill's "Evidence! Citation & Analysis for the Family Historian" and on my interpretation of recommended primary citation for an Electronic File (Image from Private Files - Annotated), Mills, "Citation!", page 81. I added a few more property names for location and date the photo was taken and keywords (to ID people by number rather than by name), the name of the person who provided the description, a surety for their description, and an informal description. Each field is discussed below.
2. DESCRIPTION OF EACH PROPERTY NAME
Date Scanned: This is the date the photo was scanned. Date is populated by Photoshop and is not editable.
Provider: The owner of the photo as of the date it was scanned. A researcher in a future generations will know who had the photo at a particular point in time.
Provenance: Describe as best you can how the photo got from the person in the photo to the Provider.
Description Provided By: List the person who identified the people and location in the image.
Description Surety: (This is an open text field. You can use any surety rating system you want.) Describe or rate the quality of the Description of the image's people and location. Note any uncertainties regarding any particular people in the photo.
Complete Subject Description: List the full name of each individual in the image, in order. You may want to list the location and date of the image even though there are separate property names for that data.
Informal Subject Description: An optional non-genealogical description of the image, perhaps for using the photo outside of genealogy. Example Informal Subject Description: "Grandpa as a young man."
Media Description: Describe the paper photo you scanned. Dimensions, border, frame, damage, etc. Your ancestors will have an easier time finding the paper photo later if you describe it well!
Annotations: Copy any annotations on the front or back of the photo and frame. Transcribe any photographer embossing/imprint; this is a clue for dating/locating photos.
Special Editing/Alterations: Describe any restoration you performed on the digital image. Did you correct for the lateral reverse of a tintype or daguerreotype?
City/County: List the City/County where the image was taken.
State: List the State where the image was taken.
Country: List the County where the image was taken.
Photo Date: List the date the image was taken.
Keywords: This is the standard keyword entry. Commas or semicolons can be used to separate keywords. I type the TMG ID number of each person in the photo here so I can search for all photos of the person without typing their name.
3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
I have not created a working namespace URI or rdf ala http://purl.org/dc/elements/1.1/ for this panel. I have not created localization dictionary files for this panel. Data entered into the panel will appear in Adobe Bridge. As you can see below I re-used lots of pre-existing property names and dumped all my new property names into the photoshop namespace. I don't know if this approach has drawbacks.
Date Scanned: xmp_path: 'CreateDate' Pre-existing property name
Provider: xmp_namespace: photoshop, xmp_path: 'Credit' Pre-existing property name
Provenance: xmp_namespace: photoshop, xmp_path: 'Provenance'
Description Provided By: xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy' Pre-existing property name
Description Surety: xmp_namespace: photoshop, xmp_path: 'DescriptionSurety'
Complete Subject Description: xmp_namespace: photoshop, xmp_path: 'Description' Pre-existing property name
Informal Subject Description: xmp_namespace: photoshop, xmp_path: 'Caption' Pre-existing property name
Media Description: xmp_namespace: photoshop, xmp_path: 'MediaDescription'
Annotations: xmp_namespace: photoshop, xmp_path: 'Annotations'
Special Editing/Alterations: xmp_namespace: photoshop, xmp_path: 'SpecialEditing'
City/County: xmp_namespace: photoshop, xmp_path: 'City' Pre-existing property name
State: xmp_namespace: photoshop, xmp_path: 'State' Pre-existing property name
Country: xmp_namespace: photoshop, xmp_path: 'Country' Pre-existing property name
Photo Date: xmp_namespace: photoshop, xmp_path: 'DateCreated' Pre-existing property name
Keywords: xmp_path: 'Keywords' Pre-existing property name
4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
I have tested this panel with Photoshop CS2 and Adobe Bridge CS2 only. It may not work on earlier versions. FWIW a malformed Custom File Info Panel will fail to load in File Info; it won't crash Photoshop.
The following was taken from "XMP Custom Panels," Adobe, Oct 2003.
Each time an Adobe application opens the File Info dialog, it scans all the files in these directories and appends them to the file list. If more than one of the description files has
the same panel name, the one found in the last file to be loaded is added, and others are ignored.
Changes to the contents of the directories do not require you to reload an application; changes are automatically reflected in the dialog the next time it is opened.
The panel description and localization dictionary files must reside in the following locations for use with Adobe Creative Suite applications:
Mac OS X
{Root Volume}/Library/Application Support/Adobe/XMP/Custom File Info Panels
{Home Directory}/Library/Application/Adobe/XMP/Custom File Info Panels
Windows
\Program Files\Common Files\Adobe\XMP\Custom File Info Panels
\Documents and Settings\<user>\Application Data\Adobe\XMP\Custom File Info Panels
The panel description and localization dictionary files must reside in the following locations for use with Adobe Acrobat 7.0 or 6.0:
Mac OS X
{Root Volume}/Library/Application Support/Adobe/Custom File Info Panels
{Home Directory}/Library/Preferences/Adobe/Custom File Info Panels
Windows
\Program Files\Common Files\Adobe\\Custom File Info Panels
\Documents and Settings\<user>\Application Data\Adobe\Custom File Info Panels
I actually do not understand how to write a panel but here is the actual panel:
<?xml version="1.0">
<!DOCTYPE panel SYSTEM "http://ns.adobe.com/custompanels/1.0">
<panel title="$$$/CustomPanels/Acro/PanelName=Gen Photo (Private Collection)" version="1" type="custom_panel">
group(placement: place_column, spacing: gLargeSpace, horizontal: align_fill, vertical: align_top)
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned:', font: font_small_bold_right, vertical: align_top);
date_static_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned', name: '$$$/AWS/FileInfoLib/Panels/DateCreated=Created', xmp_path: 'CreateDate', horizontal: align_fill, vertical: align_top, truncate: true, locked: true);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Provider=Provider:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Provider=Provider', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Credit', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Credit', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Provenance=Provenance:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Provenance=Provenance', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Caption', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Caption', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'MediaDescription', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'MediaDescription', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Annotations=Annotations:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Annotations=Annotations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Annotations', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Annotations', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'SpecialEditing', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'SpecialEditing', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/City=City/County:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/City=City/County', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'City', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'City', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/State=State:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/State=State', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'State', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'State', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Country=Country:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Country=Country', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Country', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Country', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DateCreated', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DateCreated', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords:',font: font_small_bold_right, vertical: align_top);
cat_container_edit_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords',horizontal: align_fill, height: gTextViewHeight, xmp_path: 'Keywords', container_type: bag_struct, v_scroller: true);
mru_popup(xmp_path: 'Keywords', container_type: alt_struct, no_check: true, vertical: align_top);
</panel>

You are not going to be able to run your old system from the backup on this old computer as the hardware is incompatible.
You need to get a new computer or a refurbished one.

XMP data not showing up in the custom file info panels when upgraded to CC

For several versions of Photoshop, I have been able to use a modified custom file info panel to input, update, and track psd files. With each version of photoshop there are always some changes in the way the object data is handled. The lastest challenge is:
1. XMP data not showing up in the custom file info panels when upgraded CC from CS6.
2. Raw data is not visible in CC in the File info panel.
3. This occurs in new documents where we create the xmp wrapper while the file template is built.
4. When metadata is manually entered into the file, the data is not added to the XMP wrapper when it is recreated on the save.
5. When a file that was created in CS6 is opened that contains the Metadata in the file info template. It is visible. the Raw data is also visible. Once the XMP wrapper is recreated - write and then close. The data is no longer available. the Raw data will not pull up in the file info panel.
Any feedback or a direction will be appreciated.

I have a script that the user runs to input xmp data into a Customized version of the generic file info panel. it is data that is gathered from the user when the psd file is created. once the file is open in photoshop. the information is visible in the File info panel , the raw data, and as a schema addition in the advanced tab.
in CC the nodes and the children of the XMP packet have changed positions. so that the XML -this.XMP.child(0).appendChild(this.createNode())
is no longer the node that can be appended.
Where XML.child(0).elements().length(); would enable the xmlns to be added in CS6
<rdf:Description xmlns:phsa="' + this.namespace + '" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:x="adobe:ns:meta/" rdf:about="" />'
it is visible in CC as namespace in a different arrangement. XML.child(0).child(0).namespaceDeclarations().toString()) and the children are XML.child(0).child(0).elements().length().toString()); There are now 7 child nodes where before there were 1.
with all shifted, the initialize of the values and the delete XMP packet wrapper and create new or the amend to the XMP packet wrapper is undefined.

CreatorContactInfo struct in Generic File Info Panels

Hi all,
I developed a custom panel with custom metadata in Adobe Bridge CS4, using the Generic File Info Panels.
In this panel, I have to include custom metadata and the IPTC Contact metadata.
No problem with custom metadata, I have a problem with IPTC Contact:
If I insert value in the IPTC Panel provided by Adobe, I see that metadata is written in this way:
<Iptc4xmpCore:CreatorContactInfo
 Iptc4xmpCore:CiAdrExtadr="value"
 Iptc4xmpCore:CiAdrCity="value"
 Iptc4xmpCore:CiAdrRegion="value"
 Iptc4xmpCore:CiAdrPcode="value"
 Iptc4xmpCore:CiAdrCtry="value"
 Iptc4xmpCore:CiTelWork="value"
 Iptc4xmpCore:CiEmailWork="value"
 Iptc4xmpCore:CiUrlWork="value"/>
If I insert values in my custom metadata I haven't CreatorContactInfo structure:
<rdf:Description rdf:about=""xmlns:Iptc4xmpCore="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/"
Iptc4xmpCore:CiAdrExtadr="value" Iptc4xmpCore:CiAdrCity="value" Iptc4xmpCore:CiAdrRegion="value"
Iptc4xmpCore:CiAdrPcode="value" Iptc4xmpCore:CiAdrCtry="value" Iptc4xmpCore:CiTelWork="value"
Iptc4xmpCore:CiEmailWork="value" Iptc4xmpCore:CiUrlWork="value"
xap:MetadataDate="2010-04-20T09:07:47+02:00">
<tiff:BitsPerSample> <rdf:Seq> <rdf:li>8</rdf:li> <rdf:li>8</rdf:li> <rdf:li>8</rdf:li> </rdf:Seq>
</tiff:BitsPerSample> </rdf:Description>
Is there a way to reproduce the orginal (and standard) structure??
There is my custom properties.xml (only the IPTC rows):
<xmp_schema prefix="Iptc4xmpCore" namespace="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/" label="$$$/Custom/IPTC Contact=IPTC Contact" >
 <xmp_property name="CreatorContactInfo:CiAdrExtadr" category="external" label="$$$/Custom/Property/Address=Address:" type="text"/>
 <xmp_property name="CreatorContactInfo:CiAdrCity" category="external" label="$$$/Custom/Property/City=City:" type="text"/>
 <xmp_property name="CiAdrRegion" category="external" label="$$$/Custom/Property/State/Province=State/Province:" type="text"/>
 <xmp_property name="CiAdrPcode" category="external" label="$$$/Custom/Property/Postal Code=Postal Code:" type="text"/>
 <xmp_property name="CiAdrCtry" category="external" label="$$$/Custom/Property/Country=Country:" type="text"/>
 <xmp_property name="CiTelWork" category="external" label="$$$/Custom/Property/Phone=Phone:" type="text"/>
 <xmp_property name="CiEmailWork" category="external" label="$$$/Custom/Property/Email=Email:" type="text"/>
 <xmp_property name="CiUrlWork" category="external" label="$$$/Custom/Property/Website=Website:" type="text"/>
 <ui:separator/>
 </xmp_schema>

Edited reply:
Try:
name="CreatorContactInfo/Iptc4xmpCore:CiAdrExtadr"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrCity"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrRegion"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrPcode"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrCtry"
name="CreatorContactInfo/Iptc4xmpCore:CiTelWork"
name="CreatorContactInfo/Iptc4xmpCore:CiEmailWork"
name="CreatorContactInfo/Iptc4xmpCore:CiUrlWork"
Carl

Need help on How to edit RDF file to see fields

Hi all ,
Thank you all for being helping
could please someone explain where and how to edit the RDF file to view the code and fields, sometimes we need extra fields to add in the RTF templates.
And if I get XML file from EBS, on top of the page of xml file tags says <RAXINV>
how can i able to see this RAXINV short name in EBS on particular application to view fields and other info reg report,that way I can see columns and tablenames by using Help- ->record history, and Diagonise that particular report.
any help please
vasu

Hi Srinuk, I'm not sure what you mean?
An EBS report (RDF) "root" tag will always start with the "module" name in the property pallete of the report itself. Your XML tags and nestings are a direct result of your data model groupings combined with whatever your layout is defined as?
Looking at a record history within EBS only tells you what table the form is looking at and I can't see what this has to do with an EBS report definition unless I'm missing something in your question.
You need to open the RDF to getting the data model to understand the XML tags.
Rob.
http://www.scnet.com.au

File Info XAP XMP XML

I'm not having any luck trying to figure out how to store some XML data into an AI file using the SDK. I was wondering if anyone had any suggestions on how to accomplish what I am trying to do: My plugin is notified when the file is being saved. At this point, I extract some information, and want it to be stored with the file when it's saved, so it can be extracted later. If you open the AI file in a text editor, you will see that there is a readable XML packet (<x:xmpmeta>) near the top of the file. Using AIXMLDocumentSuite and AIXMLNodeSuite I'm able to save some nodes to the file, however, that information does -not- get stored in the human readable <x:xmpmeta> text packet at the top of the file. This is not good enough for my purposes. I tried using: AIDocumentSuite::GetDocumentXAP Which seems to return exactly the information I'm referring to in the file.. Make modifications, then: AIDocumentSuite::SetDocumentXAP My changes are not saved into the file. I suspect that maybe I write the data with Set, and then immediately afterward, as Illustrator finishes the saving process, it's overwritten. I need to insert my data into the AI structure somehow, so that it is written when the file is saved... This information is available through illustrator if you choose the menu options "File -> File Info" then click on "Advanced" in the list on the left. Does anyone know how I can properly manipulate this "File Info" data? and store custom information? There are no XML related examples in the Illustrator SDK, and very little documentation on how it is supposed to be used. Thanks in advance.

Ok, I've made some progress on this issue, that being I finally forced my way to getting my data saved into the file. I talked about this a bit in another thread, but I'll reiterate here, hoping that someone else searching for solutions to this problem can know where to start. I did exactly as I suggested above: AIDocumentSuite::GetDocumentXAP Make modifications, then: AIDocumentSuite::SetDocumentXAP It was not easy to avoid the phenomenon I described above however. The modifications you make must comply with some undocumented rules; because if you pass some text in that does not pass the rule, all of your changes are discarded; replaced by whatever was there originally. There is no error reported. There should be an error when calling SetDocumentXAP if you pass in 'invalid' data, or at the very least, the valid data structure (schema) should be defined in the documentation (it's not). What I did was put all of my additions inside a <rdf:Description> tag and put it right after the other ones already in there. Sample: <rdf:Description rdf:about="" xmlns:my_tagname="http://www.mycompany.com/1.0/"> <my_tagname:my_metadata rdf:parseType="Resource"> <my_tagname:my_parameter>value</my_tagname:my_parameter> <my_tagname:my_data_1> <rdf:Bag> <rdf:lirdf:parseType="Resource"> <my_tagname:my_parameter_2>Value</my_tagname:my_parameter_2> <my_tagname:my_parameter_3>Value</my_tagname:my_parameter_3> <my_tagname:my_parameter_4> <rdf:Seq> <rdf:li>some data</rdf:li> <rdf:li>some data</rdf:li> </rdf:Seq> </my_tagname:my_parameter_4> </rdf:li> </rdf:Bag> </my_tagname:my_data_1> </my_tagname:my_metadata> </rdf:Description> I hope this helps someone else. (Excuse the bad formatting in this forum post)

CS5 Custom File Info Panels showing up in Bridge

If I create a custom XMP panel using the GENERIC model, how do I make it appear in Bridge, also?

I have a script that the user runs to input xmp data into a Customized version of the generic file info panel. it is data that is gathered from the user when the psd file is created. once the file is open in photoshop. the information is visible in the File info panel , the raw data, and as a schema addition in the advanced tab.
in CC the nodes and the children of the XMP packet have changed positions. so that the XML -this.XMP.child(0).appendChild(this.createNode())
is no longer the node that can be appended.
Where XML.child(0).elements().length(); would enable the xmlns to be added in CS6
<rdf:Description xmlns:phsa="' + this.namespace + '" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:x="adobe:ns:meta/" rdf:about="" />'
it is visible in CC as namespace in a different arrangement. XML.child(0).child(0).namespaceDeclarations().toString()) and the children are XML.child(0).child(0).elements().length().toString()); There are now 7 child nodes where before there were 1.
with all shifted, the initialize of the values and the delete XMP packet wrapper and create new or the amend to the XMP packet wrapper is undefined.

File info or metadata

I cannot seem to find a way to enter the job name into the "file info" or metadata in Photoshop CS. If the job name was entered in a previous version of photoshop such as PS7 it will appear in the file info under the advanced tab underthe XMP Basic job ticket properties but cannot be edited. As a work around I am using PS 7 to enter my job name and then using CS for everything else. There must be a better way. Am I missing something?

Ahem, well this is interesting. I haven't found a way to write a custom panel to display the JobName in CS and make it editable - perhaps a limitation to the panel language. One option is to create a template to apply to multiple files - either through the flyout menu in File Info, Replace in the Advanced panel or via the File Browser > Edit > Replace Metadata. Below is a template that I created. Best way to create your own is to save a template with the JobName property present, then go in an edit the file to remove the other template data and retain the jobName section as I did below. Edit the jobName value between the tags and rename the template - then use the Replace command to apply it to files in CS. Not a pretty work around. Otherwise I would suggest using another field going forward. Gunar <?xpacket begin='Ôªø' id='W5M0MpCehiHzreSzNTczkc9d'?><x:xmpmeta xmlns:x='adobe:ns:meta/' x:xmptk='XMP toolkit 3.0-29, framework 1.6'> <rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#' xmlns:iX='http://ns.adobe.com/iX/1.0/'> <rdf:Description rdf:about='' xmlns:stJob='http://ns.adobe.com/xap/1.0/sType/Job#' xmlns:xapBJ='http://ns.adobe.com/xap/1.0/bj/'> <xapBJ:JobRef> <rdf:Bag> <rdf:li rdf:parseType='Resource'> <stJob:name>new info goes into here</stJob:name> </rdf:li> </rdf:Bag> </xapBJ:JobRef> </rdf:Description> </rdf:RDF> </x:xmpmeta> <?xpacket end='r'?>

How can i fix blank "File Info...." in Photoshop CS5?

I wanted to add metadata to some of my photos. However, when I attempted to open "File Info" there was nothing in the dialogue box. It was just empty. Is there a method for fixing this apart from reinstalling Photoshop?

This might also have something to do with your graphics card.
I don't have cS5 loaded, but it might be close to what CS6 has There are some differences in the acutal panels between the two, but that might be in relation to the swf files. The main file structure looks something like this:
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\3.0 with these folders under 3.0: AMT, bin, custom, panels. There are no files under this folder.
Under the "panels" folder there are all the folders of the tabs: Advanced, audioData, camera, categories, description, dicom, gpsData, history, IPTC, IPTCExt, mobile, origin, rawpacket, and videoData.
Under each of these are folders: bin and location. And the one file manifest.xml.
Advanced:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "advanced"
 label = "$$$/AWS/FileInfoLib/Panels/Advanced/PanelName=Advanced"
 order = "200"
 description = "$$$/AWS/FileInfoLib/Panels/Advanced/PanelDescription=Displays the XMP data in a tree view."
 type = "built-in"
 version = "1.0"
 panelLibrary = "advanced"
 panelClass = "com.adobe.xmp.panels.Advanced"
 localizationFile = "Advanced"
 visible = "true"
 modifyDate = "2008-03-04Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
audioData:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "audio"
 label = "$$$/AWS/FileInfoLib/Panels/DynamicMedia/AudioData/PanelName=Audio Data"
 order = "50"
 description = "$$$/AWS/FileInfoLib/Panels/DynamicMedia/AudioData/PanelDescription=Contains the most important audio properties."
 type = "built-in"
 version = "1.0"
 panelLibrary = "audioData"
 panelClass = "com.adobe.xmp.panels.AudioData"
 localizationFile = "AudioData"
 visible = "true"
 modifyDate = "2008-01-28Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
camera:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "camera"
 label = "$$$/AWS/FileInfoLib/Panels/Camera/PanelName=Camera Data"
 order = "30"
 description = "$$$/AWS/FileInfoLib/Panels/Camera/PanelDescription=Contains the most important TIFF and Exif properties."
 type = "built-in"
 version = "1.0"
 panelLibrary = "camera"
 panelClass = "com.adobe.xmp.panels.CameraData"
 localizationFile = "Camera"
 visible = "true"
 modifyDate = "2008-01-21Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
categories:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "categories"
 label = "$$$/AWS/FileInfoLib/Panels/Categories/PanelName=Categories"
 order = "70"
 description = "$$$/AWS/FileInfoLib/Panels/Categories/PanelDescription=Image Categories"
 type = "built-in"
 version = "1.0"
 panelLibrary = "categories"
 panelClass = "com.adobe.xmp.panels.Categories"
 localizationFile = "Categories"
 visible = "true"
 modifyDate = "2008-01-29Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
description:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "description"
 label = "$$$/AWS/FileInfoLib/Panels/Description/PanelName=Description"
 order = "10"
 description = "$$$/AWS/FileInfoLib/Panels/Description/PanelDescription=Contains the core properties of the asset."
 type = "built-in"
 version = "1.0"
 panelLibrary = "description"
 panelClass = "com.adobe.xmp.panels.Description"
 localizationFile = "description"
 visible = "true"
 modifyDate = "2007-09-13Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
dicom:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "dicom"
 label = "$$$/DICM/FileInfoLib/Panels/DICOM/PanelNameAllLang=DICOM"
 order = "90"
 description = "$$$/DICM/FileInfoLib/Panels/DICOM/PanelDescription=Digital Imaging and Communications in Medicine."
 type = "built-in"
 version = "1.0"
 panelLibrary = "dicom"
 panelClass = "com.adobe.xmp.panels.Dicom"
 localizationFile = "DICOM"
 visible = "true"
 modifyDate = "2007-12-10Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
gpsData:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "gpsData"
 label = "$$$/AWS/FileInfoLib/Panels/GPSData/PanelName=GPS Data"
 order = "35"
 description = "$$$/AWS/FileInfoLib/Panels/GPSData/PanelDescription=Contains the EXIF GPS tag properties."
 type = "built-in"
 version = "1.0"
 panelLibrary = "gpsData"
 panelClass = "com.adobe.xmp.panels.GPSData"
 localizationFile = "GPSData"
 visible = "true"
 modifyDate = "2011-08-15Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
history:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "history"
 label = "$$$/AWS/FileInfoLib/Panels/History/PanelName=History"
 order = "100"
 description = "$$$/xmp/photoshop/History_description=The Photoshop History displays an accumulated log of edit history that has been done to the document. The logging capability can be turned on via the PS preference dialog under General>History Log."
 type = "built-in"
 version = "1.0"
 panelLibrary = "history"
 panelClass = "com.adobe.xmp.panels.History"
 localizationFile = "History"
 visible = "true"
 modifyDate = "2008-01-29Z">
 
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
IPTC:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "IPTC"
 label = "$$$/AWS/FileInfoLib/Panels/IPTC/PanelName=IPTC"
 order = "20"
 description = "$$$/AWS/FileInfoLib/Panels/IPTC/PanelDescription=International Press Telecommunications Council Core schema properties."
 paneltype = "built-in"
 version = "1.0"
 panelLibrary = "iptc"
 panelClass = "com.adobe.xmp.panels.IPTC"
 localizationFile = "IPTC"
 visible = "true"
 modifyDate = "2008-04-01Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
IPTCExt:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "IPTCExt"
 label = "$$$/AWS/FileInfoLib/Panels/IPTCExt/PanelName=IPTC Extension"
 order = "25"
 description = "$$$/AWS/FileInfoLib/Panels/IPTCExt/PanelDescription=International Press Telecommunications Council Extension schema properties."
 paneltype = "built-in"
 version = "1.0"
 panelLibrary = "iptcExt"
 panelClass = "com.adobe.xmp.panels.IPTCExt"
 localizationFile = "IPTCExt"
 visible = "true"
 modifyDate = "2009-06-12Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
mobile:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "mobile"
 label = "$$$/AWS/FileInfoLib/Panels/Mobile/PanelName=Mobile SWF"
 order = "60"
 description = "$$$/AWS/FileInfoLib/Panels/Mobile/PanelDescription=Lets you define metadata of a mobile SWF document."
 type = "built-in"
 version = "1.0"
 panelLibrary = "mobile"
 panelClass = "com.adobe.xmp.panels.Mobile"
 localizationFile = "Mobile"
 visible = "true"
 modifyDate = "2008-02-21Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
origin:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "origin"
 label = "$$$/AWS/FileInfoLib/Panels/Origin/PanelName=Origin"
 order = "80"
 description = "$$$/AWS/FileInfoLib/Panels/Origin/PanelDescription=Displays information about the origin of the asset."
 type = "built-in"
 version = "1.0"
 panelLibrary = "origin"
 panelClass = "com.adobe.xmp.panels.Origin"
 localizationFile = "origin"
 visible = "true"
 modifyDate = "2007-09-13Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
rawpacket:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "rawpacket"
 label = "$$$/AWS/FileInfoLib/Panels/RawData/PanelName=Raw Data"
 order = "210"
 description = "$$$/AWS/FileInfoLib/Panels/RawData/PanelDescription=Displays the XMP packet in raw RDF/XML form."
 type = "built-in"
 version = "1.0"
 panelLibrary = "rawpacket"
 panelClass = "com.adobe.xmp.panels.RawPacket"
 localizationFile = "Rawpacket"
 visible = "true"
 modifyDate = "2008-02-22Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>
videoData:
<xfi:fileinfo xmlns:xfi="http://ns.adobe.com/xmp/fileinfo/">
 <xfi:panels>
 <xfi:panel
 name = "video"
 label = "$$$/AWS/FileInfoLib/Panels/DynamicMedia/VideoData/PanelName=Video Data"
 order = "40"
 description = "$$$/AWS/FileInfoLib/Panels/DynamicMedia/VideoData/PanelDescription=Contains the most important video properties."
 type = "built-in"
 version = "1.0"
 panelLibrary = "videoData"
 panelClass = "com.adobe.xmp.panels.VideoData"
 localizationFile = "VideoData"
 visible = "true"
 modifyDate = "2008-01-28Z">
 </xfi:panel>
 </xfi:panels>
</xfi:fileinfo>

Photoshop changes file info xmp metadata - unknown to public domain?

Curious if anyone has feedback or solution for the following:
My PSD file's metadata enters photoshop with "unknown" as the copyright status, and then after I save it in a new format or with a new name
, I notice that in Bridge the copyright status shows up incorrectly as "public domain." This is incorrent and should not change on
its own. I've been using Photoshop with Bridge for many years, and have never seen this...

I have a script that the user runs to input xmp data into a Customized version of the generic file info panel. it is data that is gathered from the user when the psd file is created. once the file is open in photoshop. the information is visible in the File info panel , the raw data, and as a schema addition in the advanced tab.
in CC the nodes and the children of the XMP packet have changed positions. so that the XML -this.XMP.child(0).appendChild(this.createNode())
is no longer the node that can be appended.
Where XML.child(0).elements().length(); would enable the xmlns to be added in CS6
<rdf:Description xmlns:phsa="' + this.namespace + '" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:x="adobe:ns:meta/" rdf:about="" />'
it is visible in CC as namespace in a different arrangement. XML.child(0).child(0).namespaceDeclarations().toString()) and the children are XML.child(0).child(0).elements().length().toString()); There are now 7 child nodes where before there were 1.
with all shifted, the initialize of the values and the delete XMP packet wrapper and create new or the amend to the XMP packet wrapper is undefined.

JS scripted needed to add custom text plus filename to file info in document title

Would greatly appreciate any help with this one...
JS script to add custom text plus filename to file info in document title
many thanks

Super :O)
I have a folder of say 50 images and I want to run a JS script batch
example in the document title : image Nr 81205
custom text is "image Nr" + file name "81205"
activeDocument.info.title =" image Nr" + decodeURI(activeDocument.name);
would this be correct without seening the file ext
many thanks

How to create a custom panel in the right way (without having an empty panel in the file info) ?

Hi Everyone
My name is Daté.
I'm working in the fashion industry as a designer and Design consultant to help fashion brands improving the design workflow by using Adobe softwares and especially Illustrator.
I'm not a developper, but i'm very interested about the possibility to introduce xmp technology to provide more DAM workflows in the fashion industry.
Fashion designers produce a lot of graphical objects in illustrator or Photoshop. Unfortunately they are faced to a big challenge which is about how to manage, search, classify and get this files faster. Of course PDM system or PLM system are used in the Fashion industry to manage data, but for many companies, implemanting this kind of database is very complex.
When i look at what you can do with xmp, it seems to be an interesting way of managing design files, then i started to follow Adobe instruction to try to build a custom panel.
The main idea is to (Theory) :
create custom panels used by fashion designers to classify their design files.
Use Adobe Bridge to search files, create smart collection to make basic reports in pdf and slideshows
Find someone to make a script able to export metadata in xml files
Use indesign and the xml file to generate automatically catalogues or technical sheets based on xmp values
I have created a custom panel by using the generic panel provided by Adobe and i have modified the fields to feet with the terms used in the fashion industry and it works well.
But unfortunately, when i try to create my own custom panel from scratch with Flashbuilder (4.6) and the Adobe CSExtensionBuilder_2 (Trial version), it doesn't work!
Here is the process :
I have installed flashbuilder 4.6
I have download the XMP Fileinfo SDK 5.1 and placed the com.adobe.xmp.sdk.fileinfo_fb4_1.1.0.jar in C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\eclipse\plugins
In Flashbuilder, i have created a new project and select xmp Custom panel
The new project is created in flashbuilder with a field with A BASIC Description Field
To generate the panel, right click the project folder and select xmp / Publish Custom Panel
The panel is automatically generated in the following folder : C:\Users\AppData\Roaming\Adobe\XMP\custom file info panels\3.0\panels
Go to illustrator, Open the file Info
The panel appears empty
The others panel are also empty
The panel is created and automatically placed in the right folder, but when you open it in Illustrator by selecting the File Info option in the File Menu, this custom panel appears empty!!! (only the title of the tab is displayed). This panel also prevent the other panels to be displayed.
When you delete this custom panels from the folder C:\Users\AppData\Roaming\Adobe\XMP\custom file info panels\3.0\panels and go back to the File Info, the other panels display their content properly.
I also try to use the plugin XMP Namespace designer to create my own namespace. this plugin is also able to generate a custom panel, but this one also appears empty in AI or Photoshop.
I try to follow the process described in Adobe xmp documentation many times, but it didn't works.
It seems that many peaople have this issue, but i dodn't find a solution in the forum.
I try to create a trust file (cfg), but it didn't work.
It would be so kind if you can help me to understand why i can't create a custom panel normally and how to do it in the right way.
Thanks a lot for your help,
Best regards,
Daté

Hi Sunil,
After many trial, i realize the problem was not coming from the trust file, but from the way i have created the custom panel.
There is 2 different ways, the first described below is not working whereas the second is fine :
METHOD 1 :
I have downloaded the XMP-Fileinfo-SDK-CS6
In the XMP-Fileinfo-SDK-CS6 folder, i copied the com.adobe.xmp.sdk.fileinfo_fb4x_1.2.0.jar plugin from the Tools folder and i pasted it in the plugind folder of Flashbuilder 4.6
The plugin install an XMP project
In Flashbuilder 4.6 i have created a new project (File / New /Project /XMP/XMP Custom Panel)
A new xmp project is created in flashbuilder.
You can publish this project by right clicking the root folder and selecting XMP / Publish Custom Panel
The custom file info panel is automatically published in the right location which is on Mac : /Users/UserName/Library/Application Support/Adobe/XMP/Custom File Info Panels/3.0 or /Users/UserName/Library/Application Support/Adobe/XMP/Custom File Info Panels/4.0
Despite the publication of the custom file info panel and the creation of a trust file in the following location : "/Library/Application Support/Macromedia/FlashPlayerTrust", the panel is blank in Illustrator.
I try this way several times, with no good results.
METHOD 2 :
I have installed Adobe CSExtensionBuilder 2.1 in Flash Builder
In FlashBuilder i have created a new project (File / New /Project /Adobe Creative Suite Extension Builder/XMP Fileinfo Panel Project)
As the system display a warning about the version of the sdk to use to create correctly a custom file info, I changed the sdk to sdk3.5A
The warning message is : "XMP FileInfo Panel Projects must be built with Flex 3.3, 3.4 or 3.5 SDK. Building with Flex 4.6.0 SDK may result in runtime errors"
When i publish this File info panel project (right click the root folder and select Run as / Adobe illustrator), the panel is published correctly.
The last step is to create the trust file to display the fields in the panel and everything is working fine in Illustrator.
The second method seems to be the right way.
For sure something is missing in the first method, and i don't understand the difference between the XMP Custom Panel Project and the XMP Fileinfo Panel Project. Maybe you can explain it to me.
So what is the best solution ? the right sdk to use acording to the creative suite (the system asks to use 3.3 or 3.5 sdk for custom panels, so why ?)
I'm agree with Pedro, a step by step tutorial about this will help a lot of peaople, because it's not so easy to understand!!!
Sunil, as you belong to the staff team, can you tell me if there is :
A plugin or a software capable to extract the XMP from llustrator files to generate XML workflows in Indesign to create catalogues
A plugin to allow indesign to get custom XMP in live caption
A plugin to allow Bridge to get custom XMP in the Outputmode to make pdf or web galeries from a smart collection
How can you print the XMP data with the thumbnail of the file ?
Thanks a lot for your reply.
Best Regards
Daté

How to give a profile a default mimetypes.rdf file?

Hello,
I'm deploying Mozilla Firefox 31ESR on thousands of computers. I'm looking for a way to pre-configure how firefox handle the mimetypes. For instance, to open pdf with Adobe Acrobat Reader.
To achieve this, I put a mimetypes.rdf file in "C:\Program Files (x86)\Mozilla Firefox\browser\defaults\profile".
When the profile is created, this file is copied, then modified.
The lines:
<RDF:Description RDF:about="urn:mimetype:handler:application/pdf"
NC:useSystemDefault="true"
NC:alwaysAsk="false" />
Becomes:
<RDF:Description RDF:about="urn:mimetype:handler:application/pdf"
NC:handleInternal="true"
NC:alwaysAsk="false" />
-If I replace manually the file "mimeTypes.rdf" in the newly created profile, it works perfectly.
It seems to be the same problem as: https://support.mozilla.org/fr/questions/1015378
Why is the mimetypes.rdf file modified? How can I set a mimetype policy?
Thanks a lot!

It works for me with both the user.js file and your mimeTypes.rdf file.
<pre><nowiki>user_pref("pdfjs.disabled", true);
user_pref("plugin.state.nppdf", 2);
</nowiki></pre>
<pre><nowiki><?xml version="1.0"?>
<RDF:RDF xmlns:NC="http://home.netscape.com/NC-rdf#"
xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<RDF:Description RDF:about="urn:mimetype:handler:application/pdf"
NC:alwaysAsk="true"
NC:saveToDisk="true">
<NC:externalApplication RDF:resource="urn:mimetype:externalApplication:application/pdf"/>
</RDF:Description>
</RDF:RDF>
</nowiki></pre>

File Info Dialog problem

Hi,
Not sure if this is a bug or if I'm just missing a setting someplace.
Problem: I write a lengthy caption in the "Description" window of the File Info dialog. Later on I want to use that same caption on a different image.
Using CS3 on Windows I can click on the flyout arrow next to the "Description" window and input the entire caption.
Using CS3 on Mac, the flyout will only input sections of the caption. It seems like the Mac version breaks the caption apart based on any punctuation that is in the caption.
Ex. If my caption is "01 July 2008, Los Angeles, California, USA - Paul has issues with Photoshop, causing a problem when captioning files."
Windows puts the entire caption in the field. Mac breaks it down like this:
01 July 2008
Los Angeles
California
USA
Paul has issues with Photoshop
causing a problem when captioning files
I don't recall this being an issue with PS7 or CS1. Am I missing something or is this just the way CS3 works?
Thanks in advance for any help!
-Paul

I narrowed down the issue even more. Non-English languages have their strings, tags, and texts stored in a file named strings.txt in a language-specific subdirectory in the Resources directory in the Adobe Bridge CS6 program folder. The strings.txt file includes, among many other things, a language-specific decimal separator character—which in English is a dot but in many non-English languages is a comma.
When I replace the comma as the decimal separator in the German-language strings.txt file by a dot then all of sudden the f-stops are displayed correctly in the thumbnail pane ... well, except that e. g. "f/2,8" now gets displayed as "f/2.8" which in German is wrong but acceptable—and definitely much better than "f/2,0" which is unacceptably wrong when the actual value is 2.8.
The idea to try this dawned on me when I noticed that in some places in the metadata pane, decimal numbers are displayed with a comma (respecting the decimal separator character given in strings.txt); in other places, they're displayed with a decimal point (ignoring strings.txt). Those using a dot are correct; those using a comma are wrong. So there's two bugs in Bridge rather than just one. First bug: In some places, the language-specific decimal separator character is ignored. Second bug: When it is not ignored then the number displayed will be wrong.
So my workaround now is to use a dot as the decimal separator character rather than a comma.

RDF file info?

Similar Messages

Maybe you are looking for