Namespaces in conversion table

We're encountering an issue with the use of namespaces with elements in a conversion table. The Adobe documentation seems to suggest that namespaces are supported in Frame, and, in documents that are already structured, we encounter no problems.
However, when we attempt to convert an unstructured doc using namespaced elements in the second column of the conversion table, the process won't work. We get errors for every element that includes a namespace prefix.
We've tried to get around the issue by assigning qualifiers in the third column and then using those in the first column, but with no luck.
Any thoughts or suggestions would be much appreciated.

Quoted from the Structure Developer Reference:
The following characters are not allowed in an element tag, but
can appear in a format or qualifier tag if you precede them with a backslash (\) in the table:
( ) & | , * + ? % [ ] : \
end quote.
The structure conversion tables have been around far longer than namespaces in XML, so we just have to hope that they get updated soon.
You will also find that some of FrameMaker's building blocks and EDD context rules have trouble with the colon character where it has long been used by FrameMaker for other purposes.
I tend to rename elements that have an XML namespace using XSLT, eg:
xml:lang in XML is transformed into xml.lang in FrameMaker which makes it possible to write EDD rules that refer to the value of the xml.lang attribute.
Ian

Similar Messages

Font sizes between Photoshop and Edge - Any Accurate conversion table?

I have been trying to make sense of the font sizes between Photoshop and Edge. It seems that the conversion tables I have found do not actually give the right numbers and I am wondering if there is a table from Adobe that would make it easy to have the right size rather than an approximation.
I prefer to use text in Edge rather than Photoshop for many different reasons one being dynamic text.
For example a font in Photoshop in a 780 x 475 image is 8pt - In Edge, according to conversion tables it should be 11 px but it is totally wrong. It needs to be closer to 30 px to be about the same.
So, Adobe Team, any documentation on that?

By the way, I have to correct the numbers but they still do not make too much sense. The artist gave me a 300 dpi file so of course the px size what wrong. After converting the file to 72 dpi, the font size happens to be 33.33 pt or 40 px which is now way too big in Edge. It looks like the size my just be the same 33.33 pt would be 33.33 px. Is this correct?

How to add an entry in the currency conversion table

Hi all,
I am loading data to ODS from 2LIS_11_VAITM. i am getting an error as below in a record.How do we enter a missing entry in the currency conversion table? Please help.
Kind Regards,
Shanbagavalli.S
Enter rate EUR / EUR rate type 00000000 for 2200016564 in the system settings
Message no. SG105
Diagnosis
For the conversion of an amount into another currency, an entry is missing in the currency conversion table.
Procedure
Add the missing entry in the currency conversion table.
Execute function
You can then continue to process the commercial transaction.

Hi,
Goto RSA1 -> source system -> R/3 source system -> transfer exchange rates.
Bye
Dinesh

" No entry in the conversion table for the syntax group" error

Hi,
Iu2019m getting an error in the port setup when I try to run an Access Test on the logical directory.
Definition of path
TFTS02\INTF\RD1\OUTB\MM\RFC WINDOWS NT missing
Message no. SG024
Diagnosis
There is no entry in the conversion table for the syntax group WINDOWS NT and the logical path
TFTS02\INTF\RD1\OUTB\MM\RFC.
System Response
The system cannot generate a platform-specific path.
Procedure
Make an entry for the syntax group WINDOWS NT and the logical Pfad
TFTS02\INTF\RD1\OUTB\MM\RFC in the conversion table using the FILE transaction.
Regards,
Rajiv

Hi
the error is simple. The path
TFTS02\INTF\RD1\OUTB\MM\RFC you are trying to access is not there so create the path in the FILE transaction.
In file tcode goto NEW ENTRIES and give the path and also make sure that in AL11 the path and the filename you are trying to open exists.
Thanks & Regards
Jyo

Crash while launching in "building color conversion tables"

Photoshop CS6 crashes while "building color conversion tables" I reinstalled the program but it still hangs up at this point. please help!

I've only seen 3 things that can cause a crash at that point: corrupt profiles (mostly display profiles), corrupt information coming from the OS about the system profiles, and bad floating point units in CPUs.
First thing to check is the display profiles. If setting them to sRGB doesn't solve the crash, it might be a bug in the OS profile cache. And let's hope it isn't the CPU, because those problems are a @$%^@#%# to track down in modern processors.

Conversion tables and table entries

I'm working on a conversion table to move our legacy products from unstructured FM to DITA. I understand the basic concepts but I'm having a problem with the table cells.
In my conversion table I have P:CellBody in the first row, mapped to entry with a qualifier of cellbody.
I also have TC mapped to entry.
The same holds true for P:CellHeading and TH.
Consequently, my text is wrapped in two entry elements. The Show Element Context tab shows:
entry
entry
row
tbody
tgroup
table
body
NoName
NoName
I'm pretty sure it should be the same as above with only one entry element (and of course with the NoNames fixed which I think I know how to do; I just haven't gotten there yet).
How do I avoid having my cells wrapped in two entry elements?
Thanks in advance,
Marsha

Marsha,
    I don't quite understand either what you are trying to do or what exactly is in your conversion table. Be aware, however, that FrameMaker will always create elements for the basic components that occur in your tables. The conversion table gives you limited control of how those elements will be tagged, but not whether the elements will exist.
   If your conversion table contains rows such as:
P:CellBody
entry
cellbody
TC:
entry
You will indeed get nested entry elements. The outer one is the table cell itself and the inner one is the paragraph. FrameMaker does not permit a valid document to use the same element tag for both a cell and a container, so aside from the results not being what you wanted, they are not correct within FrameMaker.
If your table cells contain single paragraphs and you don't want elements for both the cells and the paragraphs, your conversion table doesn't even need to mention the CellBody and CellHeading paragraph tags. In fact, if your table formats use CellBody as the paragraph format for cells in the body of a table and CellHeading as the paragraph format for cells in the table heading, your EDD doesn't even have to apply the paragraph formats.
Another variation is to include a paragraph tag in a conversion table row for a table cell by combining TC: and P: to match table cells containing particular paragraphs. For example:
TC:P:CellBody
entry
creates cell elements named entry from table cells containing paragraphs tagged CellBody. The paragraph within such a cell is not wrapped in an additional element.
One final comment is that TH: in a conversion table refers to the entire table heading; its children are heading rows. The table body analog of TH: is TB:, not TC:.
       --Lynne

Capturing a nested "Section" hierarchy with a Conversion Table?

(Frame 9) - I'm using a Conversion Table to convert a client's unstructured documents to structured. Much of the structure is importing with a certain amount of success, but I can't figure out how to capture the nested hierarchy. The client's template uses the same "Section" element with a "Title" child element for each level of the document.
I can capture the document headings from the H1, H2, H3 paragraph tags form the old document and wrap them in "Title" elements with H1, H2, H3 qualifiers but I can't figure out how to then wrap the Title elements in the corresponding Section elements that reflect the hierarchy levels. Frame must have an internal qualifier for the Section elements but I can't figure out how to look it up?
Thanks, Chris

Chris,
It should work fine if you have the qualifiers properly specified in the rules for wrapping the sections. Here is a link to a working sample that shows how it is done, which coincidentally also uses Section elements (but Heading elements in place of Title elements):
http://www.weststreetconsulting.com/WSC_ResourceDownloads.htm
Get the FrameSLT sample.
Russ

Conversion Table: Image with Title

I'm using conversation tables to move from Unstructured FM8 to Structured (DITA) FM10.
I am trying to move the existing tables and graphics with titles into the DITA structure. My understanding is that in DITA, it should look like this:
So I've developed my conversion table to look like this:
But when I run Structure Current Document, it doesn't wrap the (title[fig], image) in the figure element:
The one part that seems odd to me is that when I generate the conversion table, I don't see any row that represents the image element itself. Is that the problem? Is there something else that I should be doing?
Thanks!

You need a row that has "G:" in column 1 and "image" in column 2 to indicate that anchored frames should map to the image element.
--Lynne

FDK - apply Conversion Table to document

Hello,
I want to be able to apply a conversion table to an open document, through FDK.
Is there a way of calling the "Structure Current document..." command from the client and pass it a filepath, so that it opens the Conversion table document and applies that to the current document?
I want to be able to pass the filepath to the command automatically without displaying the dialog box.
I appreciate any help!,
Thanks in advance,
pnk

Hi pnk,
Yes. It is in the chapter of the FDK ref called "Calling Clients Shipped with FrameMaker." The conversion table process is actually handled by another API client called the Structure Generator, and you'll need to make calls to it. However, in the latest FDK ref I have, I believe that the syntax in the documentation is wrong. I'll copy/paste the operative parts below, substituting the syntax that I know works. Note that you need to have all documents open with their IDs captured... you can't simply send a file path.
To execute most operations with FrameMaker clients, you must make a sequence of several
F_ApiCallClient() calls.
To structure a document, use the following sequence of F_ApiCallClient() calls:
F_ApiCallClient("Structure Generator", "INPUTDOCID objectID");
...where objectID is the ID of the input document.
F_ApiCallClient("Structure Generator", "RULEDOCID objectID");
...where objectID is the ID of the rule (conversion) table document.
F_ApiCallClient("Structure Generator", "OUTPUTDOCNAME pathname");
...where pathname is the full pathname of the output document. This command is optional. If you do
not specify a pathname, the structure generator leaves the document unsaved and open.
F_ApiCallClient("Structure Generator", "StructureDoc");
...This call instructs the structure generator to generate structure, using the parameters provided by the
calls listed above.
pnk, this is Russ again. So, for example, to make the call where you send the ID of the document you want to structure, you would do something like:
UCharT msg[1024];
F_ObjHandleT docId;
. . . code to get docId, etc . . .
F_Sprintf(msg, "INPUTDOCID %d", docId);
F_ApiCallClient("Structure Generator", (StringT)msg);
. . . rest of calls, etc . . .
Hope this helps.
Russ

Conversion table: How does it know whether a topic is a task, concept, or reference?

FM 11
DITA 1.2
I'm just starting to work on my conversion table for our non-structured files. I've only gone as far as my first couple of iterative tests to create FM binary files; i.e., I haven't imported my EDD or templates yet. I'm just trying to apply logic to the process.
Marsha

Hi Marsha...
The only way for it to know is based on the heading tag names. You'll need to assign different tags for each heading that starts a new "topic type". You'll also need to assign different tags within topics (like "task") to differentiate between the different sections within a topic.
I have a tool that helps with this "retagging" process (as well as many other conversion-related issues). it lets you define a retagging scheme based on previous tags or tags that follow a certain tag. It also lets you assign new tags based on text in the heading. You may want to download the trial of this tool just to get an idea of what it can do. The sample files and documentation may be helpful for your learning process, even if you don't buy it.
http://leximation.com/tools/info/fm2dita.php
Also .. you might want to look at the webinar I gave for Adobe on this subject ..
http://leximation.com/downloads/adobe-fm2xml-2013
Cheers,
...scott

Conversion Table Questions: problems converting tables to structured

I'm in the process of converting unstructed FM8 docs to structured docs using FM10 and DITA structure. Right now I'm trying to build a conversion table to structure the docs, but I'm having a lot of trouble with the tables. The main problem seems to be with the tgroup element since I can't figure out how to get the thead and tbody to wrap in the tgroup element.
Here is an example of one of the tables I'm trying to structure:
This is the Table section of the conversion table I've had the most success with:
And this is the result:
As you can see, the thead and tbody elements are not wrapped in tgroup and the structure is invalid. I've been playing around with the conversion table for several days now and can't seem to figure out how to fix this. If anyone has any suggestions, they would be greatly appreciated!
Thanks,
D'Arcy

D'Arcy,
Here are a few observations that might help:
1) The structure you use within FM (which is what the conversion table helps create) need not be exactly the same as the structure you use in XML.
2) Do not confuse the element named table with a FrameMaker table.
3) As Michael has pointed out, the CALS table model used by DITA is a five-level structure:
table
tgroup
    tbody
       row
         entry
while the FrameMaker table model has 4 levels:
table
tbody
    row
      cell
4) FrameMaker can map between the 5-level structure and the 4-level structure in one of two ways, controlled by the element definitions (usually specified in an EDD), the read/write rules, and the DTD:
a) The element named table can be a container while the element named tgroup is the actual table. This model has a closer correspondence between the FrameMaker and the DITA table structure. Michael has pointed out one of its biggest weaknesses. If a FrameMaker table (regardless of its element name) has a title, then FrameMaker repeats the title on each page of a multipage table. However, if the element named table is a container and the actual table is an element named tgroup, the title is a container preceding the table and this automatic repetition does not happen.
b) If you are sure that your tables will always consist of a single tgroup, you don't have to use the tgroup element within FrameMaker. Make the element named table a FrameMaker table and include the read/write rule:
element "tgroup" unwrap;
FrameMaker will recreate the tgroup element whenever you save a document as XML. This model allows you to make the table title a FrameMaker table. However, you cannot use the element named title as both a FrameMaker table title and a container. Typically, therefore, people use the element named title as a container that is the title of things like chapters and sections and use an element named something like tabletitle for the title of tables.
Read/write rules like:
element "title" is fm element:
element "title" is fm table title element "tabletitle"'
let you save your documents as XML with both title and tabletitle represented as <title> in XML. You'll need to use a custom client or XSLT to map the XML element named title to either title or tabletitle depending on whether the XML element occurs within a table or not.
5) Your conversion table had one row with T: in column 1 and another with T:Format A in column 1; one mapped to table and the other to tgroup. The row with T:Format A would apply to all tables with the specified format, the other row would apply to all tables with other formats. These conversion table rows do not define a relationship between table and tgroup. Map T: to table if you want the model in 4b) above and to tgroup if you want the model in 4a). In the latter case, use an additional row with:
title?, tgroup
in column 1 and table in column 2.
     --Lynne

Conversion table for oil products

Hi Experts
I want to download conversion table for oil products in SAP please help me regarding this

Hi Pravin,
If you need a convertion factors then, youcan find in this link for Petroleum Products.
ttp://www.quantityware.com/_data/BCP_10A_customizing_SP09.pdf
http://www.mycalculations.com/jmm/uni01.html
http://www.chemlink.com.au/conversions.htm.
http://www.quantityware.com/support/index.php?rubric=20.
Best Regards
Satish

How to fill conversion table TAUUM in BW for conversion of Sales Order Type

When importing sales order data from SAP ECC to SAP BI, conversion routine AUART can be used to convert Sales order Type from its internal representation to an external representation. (For example, the standard sales order has an internal Sales Document Type code TA, and an external code OR).
The standards SAP conversion routine AUART uses table TAUUM as a lookup table. This table has lots of data in SAP ECC, but it is empty in SAP BW.
How can we copy data from table TAUUM in ECC to table TAUUM in BW?
Do we have to create a maintenance view on the table, and type in the entries? Or is there a more automated way?

Hi Jay,
Make sure the extract structure is active. You can check the same from LBWE > 11: SD Sales BW> MC11VA0STI is active.
If the extract structure is active. Inorder to fill the setup table. First delete the setup table for the application area 11 from SBIW transaction. Then fill the set-up table for the application area 11 as you did for deliveries.
Then check whether data source is pulling data.
Let me know if there is an issue even after following the above steps.
Thanks & Regards,
Namrata

Urgent: Unicode conversion - table splitting

Hi all,
I am having a problem when trying to perform the export step of the unicode conversion on ERP2005, MSSQL server 2005. Due to previously very long runtime, I am trying to use the table splitting option. I have performed the "Table Splitting Preparation" step with what seems to be a success.
The problem is when I run the actual database instance export.
First of all:
Which filepath should I provide SAPinst when it is asking for "Table input file"?
Second:
How can I actually determine the Package Unload Order? I tried selecting this option, but I was not given the opportunity to change this order in the subsequent screen. (The F1 help in SAPinst sais that I would be able to...)
Have anyone of you experience with this?
Best Regards,
Thomas

Hi Thomas,
As I can imagine from the date of your last posting, you probably have your answers. But just so other people, who are searching on this topic, can find the answer here, I will fill in the blanks.
First, when using table splitting, you must export using the migration monitor (MIGMON). That means, when you run SAPINST, on the ABAP System -> Database Export screen, select the Export Method: Export using Migration Monitor.
At this point, as you said, you have already run the Table Splitting option from SAPINST, so the WHR files are in the export DATA directory. This whr.txt file is also there.
The file input screen you are mentioning does not appear when you select the Export method mentioned above. But you can create such a file for MIGMON. You have to create this on your own and can only do it after the SAPINST has split the STR files.
When finished with SAPINST, create the .txt file (I usually call it table_order.txt) and add the names of the STR files which you want to make sure are exported first. After MIGMON completes that list, all other STR files are exported in alphabetical order.
Create your table_order.txt file inserting the filenames of the packages that were created, without the STR/WHR extensions (using some large tables which STR splitter broke out into their own STR files during my last export). You have to look in DB02 and sort descending based on used space to determine the order in which these tables should be exported and listed in the .txt file:
<SPLIT Table>-1
<SPLIT Table>-2
<SPLIT Table>-n
BSIS
RFBLG
CE1VVOC
CE1WWOC
DBTABLOG
CE3VVOC
COEP
ARFCSDATA
GLPCA
KONV
SWW_CONT
SOC3
CDCLS
CE3WWOC
BSE_CLR
STXL
EDIDS
COSP
BSAD
EDI40
ACCTIT
BSIM
VBFS
BSAS
ACCTCR
CDHDR
CE4VVOC_ACCT
SGOHIST
MSEG
In the export_monitor_cmd.properties file, you specify this file name for the 'orderBy=' parameter. Create and keep the table_order.txt file in the same directory as the export_monitor.sh/.bat files.
For importing, again you will need to use the Migration Monitor. SAPINST will automatically stop and prompt you to start the import using MIGMON. Here, you can specify the same table_order.txt file. You might want to amend it to control when the rest of the packages are imported, if you found one or more tables holding up the completion of the export.
I hope this helps someone.
Best Regards,
Warren Chirhart

Converting Tables Using FM Conversion Tables

Hi All,
I need to convert a table from unstructured FM to the HTML-like format:
<table>
<tr>
<td><para>Cell 1</para></td>
<td><para>Cell 2</para></td>
</tr>
<tr>
<td><para>Cell 3</para></td>
<td><para>Cell 3</para></td>
</tr>
</table>
However, it seems I'm missing something because I cannot make FM to wrap <para> in <td>. If I setup the conversion this way:
TC: P:CellBody ---------------- td
TR:td+ ---------------- tr
...it works like a charm, but the content is inserted directly to <td>. If I try to define:
TC: P:CellBody ---------------- para
TE: E:para ---------------- td
TR:td+ ---------------- tr
... it doesn't work. What am I missing?
Thanks in advance,
Alex

Alex,
When you have something like:
TC: P:CellBody
The "TC:" part defines the table component that will be tagged. The "P:" part is only a qualifier. So when you have:
TC: P:CellBody ---------------- para
This says literally, "tag all tables cells with the para element IF it has a child paragraph with the CellBody format." I think you are expecting it to wrap the child paragraph itself, which isn't the case. It is still affecting the table cell only, just with a qualifier.
Russ

Namespaces in conversion table

Similar Messages

Maybe you are looking for