Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

"tabstyle" attribute of table element not supporting multiple values

Guest
Jun 03, 2008 Jun 03, 2008

Copy link to clipboard

Copied

After many trials and errors, I have structured my many legacy documents (using CALS for the table structure), but I did them several months ago. I now have a "leftover" document that I followed my procedure step-by-step to convert it to a structured FM doc as well; however, when I test saving the structured FM doc as an XML file, I get the following error messages for the many tables in the doc:
"Error at line nnn, char 45, Message: Attribute 'tabstyle' does not support multiple values"

I can use the same EDD, DTD, and r/w rules to correctly save my previously structured docs to XML with no such errors, but not this one. Any idea what I've done... or not done... to cause this error?

Thanks in advance...

Cheryl Dwyer
TOPICS
Structured

Views

871
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jun 03, 2008 Jun 03, 2008

Copy link to clipboard

Copied

Cheryl,
My guess is that in this case the table format name includes one or more spaces. This is interpreted as multiple values in XML.

So if you have a table format named "CALS table" in FrameMaker try renaming it without a space, perhaps "CALS_table", or "CALStable".

I hope this helps

Ian

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Jun 03, 2008 Jun 03, 2008

Copy link to clipboard

Copied

Cheryl,

You can also check the DTD, the attribute definition might of type "token" that does not allow spaces as Ian said. Changing that to CDATA type probably helps.

BR, Martti

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jun 04, 2008 Jun 04, 2008

Copy link to clipboard

Copied

Yes changing the DTD as Martti said would also fix the problem. However the CALS table definition is an industry standard, so it may cause problems with data interchange if you make any alterations. If the DTD is fully under your control, then making such a change would mean that you don't have to alter your FrameMaker templates.

Regards
Ian

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Jun 04, 2008 Jun 04, 2008

Copy link to clipboard

Copied

Ian is right. The OASIS Exchange model defines tabstyle attribute as NMTOKEN (name token), so the value cannot include spaces.

Martti

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Jun 04, 2008 Jun 04, 2008

Copy link to clipboard

Copied

LATEST
Yesss!!! Thanks to you all; the culprit was a space in the table name "Format A" instead of "FormatA" that was present in the doc... once changed and configured correctly, it is error-free.

Thank you, thank you!
Cheryl

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines