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

FM inserts wrong/strange doctype declaration

Explorer ,
Jul 15, 2013 Jul 15, 2013

When I create and save a new DITA Task in FM11 (using DITA 1.1), FM writes 'Concept' as doctype even though referencing the correct task dtd. FM also auto-inserts a concept element as root element. The XML looks like this:

doctype1.png

The structapps file looks fine to me and also contains the correct doctype statement. Do you have any idea where else I could look to find the error?

doctype2.png

Robert

TOPICS
Structured
879
Translate
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

correct answers 1 Correct answer

Explorer , Jul 15, 2013 Jul 15, 2013

OK, I found it now. Independent from what is configured elsewhere, FM simply inserts the FIRST element from the EDDmarked as 'valid as root element'.

I used a flat EDD with all elements in one file.

So I have to work with separate EDDs for the different topic types to have only a single valid root per file.

Translate
Contributor ,
Jul 15, 2013 Jul 15, 2013
Translate
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
Explorer ,
Jul 15, 2013 Jul 15, 2013

Gorly, thats an interesting topic but it seems that my problem is slightly different. The mapping of the apps is OK and I see no problem in the structapps. My main issue is where does the doctype statement in the saved XML file come from?

As a test, I changed the doctype statement in the structapps (e.g. to "abc") but the doctype in the saved file is unaffected..

Robert

doctype3.png

Translate
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
Explorer ,
Jul 15, 2013 Jul 15, 2013
LATEST

OK, I found it now. Independent from what is configured elsewhere, FM simply inserts the FIRST element from the EDDmarked as 'valid as root element'.

I used a flat EDD with all elements in one file.

So I have to work with separate EDDs for the different topic types to have only a single valid root per file.

Translate
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