If you are trying to determine if your files are portable, I'd run your content through the standard OT plugins for pdf and html to test your results.I'd also suggest that rather than trying to use the framemaker converted files I'd start building some test content that you build directly with oxygen. It doesn't have to be big and complicated, just enough to verify your questions and concerns. You might want to use your content for examples but build a 2 col 3 row table and see what happens when you apply the different attributes at different levels. Start simple and where you would like to mange the rules, process and see what you get. Once you get the sample table the way you want compare it with the framemaker version and strip out or add markup as needed.Collect all of these samples together in an organized manner and now you have a minimal test document that you can test with rather than trying to find examples in the larger content body. This format sample will help you as you add tools or switch vendors an approaches. You will now have a small sample you can quickly run or import into these tools to understand how well they work or changes you will have to make.Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: Frank Dissinger <frank.dissinger@cgs-oris.com> Date: 4/12/23 8:18 AM (GMT-08:00) To: Oxygen User Mailing List <oxygen-user@oxygenxml.com> Subject: [oXygen-user] Understanding @colsep and @rowsep Thank you! Hm... These attributes were set on <table> and <tgroup> in my DITA files, but not on <entry>, and the attribute value was sometimes = "0", sometimes = "1". Nevertheless the tables rendered correctly, but perhaps only because I have set up the CSS and MiramoPDF styles to create frames for all table cells for all <table> elements. I'll have to investigate this... So perhaps, to keep my DITA data portable and to ensure they are rendered correctly with other transformations, it would be safer to also set @colsep and @rowsep to "1". But really for each <entry>? Wouldn't it be enough for <table>? Frank Am 12.04.2023 um 16:36 schrieb Michael Boudreau: @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4;}@font-face {font-family:"Times New Roman \(Body CS\)"; panose-1:2 11 6 4 2 2 2 2 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;}span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext; font-weight:normal; font-style:normal;}.MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;}div.WordSection1 {page:WordSection1;} For a CALS table, @frame="all" draws a border around all four outside edges of the table; it does not affect the interior lines. See https://dtd.nlm.nih.gov/options/OASIS/tag-library/19990315/index.html To indicate a table with all the grid lines visible, CALS requires @frame="all" as well as @colsep="1" and @rowsep="1" on all <entry> elements (you can omit colsep on the rightmost cells and rowsep on the finalrow). -- Michael R. Boudreau Electronic Publishing Technology Manager The University of Chicago Press 1427 E. 60th Street Chicago, IL 60637 www.journals.uchicago.edu From: oXygen-user <oxygen-user-bounces@oxygenxml.com> on behalf of Frank Dissinger <frank.dissinger@cgs-oris.com> Date: Wednesday, April 12, 2023 at 9:26 AM To: Oxygen User Mailing List <oxygen-user@oxygenxml.com> Subject: [oXygen-user] Understanding @colsep and @rowsep Hi all, Can someone shed some light on how the @colsep and @rowsep attributes are used for CALS tables? The information I found is not clear and detailed enough for me. I understand that these attributes create separator lines for colums and rows. Do I only need these attributes when I do not set @frame="all" to create lines for particular rows or columns only? For a normal CALS table with lines for all rows and columns (i.e. like a grid), is enough to set @frame="all" or do I additionally need these attributes? The code that Oxygen creates (see below) with these settings (i.e. without these attributes) ... does not have these @colsep and @rowsep attributes, only @frame="all", and is rendered as desired with my CHM and PDF transformations. I have several tables with @colsep/@rowsep="0" or ="1". These attributes may have been added by FrameMaker when I converted unstructured content to DITA. Can I safely remove all of these attributes when I just want a CALS table with row and line separators every (like a grid)? Regards, Frank -- div.signature {font-family: Verdana, sans-serif; font-size: 10pt; color: #7F8C8D; padding-top: 0.4em;} div.name {padding-bottom: 0.8em; padding-top: 0.8em} div.contact {padding-bottom: 0.8em;} p {margin: 0;} span.separator {border-top-style: dotted; border-top-width: 2px; padding-top: 0.6em;} a {color: inherit} Frank Dissinger Documentation Manager .................................................................... CGS Publishing Technologies International GmbH Email frank.dissinger@cgs-oris.com | Web www.cgs-oris.com Address Kettelerstr. 24 | D-63512 Hainburg | Germany Phone +49 6182 9626-27 | Fax +49 6182 9626-99 Commercial register Offenbach, HRB no. 21495 Managing directors Bernd Rückert, Christoph Thommessen
