gmane.editors.serna.user

Sonu Mangla | 18 Jul 13:18

[Serna] How to configure Serna to use XEP instead of FOP?

Hi,

I have syntext serna 3.8 installed on my system. I am trying to use XEP to
publish PDF but unable to do so. Can anyone help me?

Steps that I have performed so far are:

1)       Installed Serna 3.8

2)       Installed the Idiom fo plug-in into the C:\Program
Files\Syntext\Serna-3.8\plugins\dita\DITA-OT1.4\demo\fo folder.

3)       Installed the XEP into C:\Program Files\Syntext\Serna-3.8
\plugins\dita\DITA-OT1.4\demo\fo\lib\xep folder

4)       Installed the saxon.jar in C:\Program Files\Syntext\Serna-3.8
\plugins\dita\DITA-OT1.4\demo\fo\lib\xep\lib folder.

5)       Installed the ICU4j.jar in C:\Program Files\Syntext\Serna-3.8
\plugins\dita\DITA-OT1.4\demo\fo\lib\ folder.

6)       Added saxon.jar to the classpath in the startcmd.bat file

7) Made a copy of the dita2pdf.bat and did modifications as per FO
readme instructions.

8) Run the "ant -f integrator.xml" from the C:\Program
Files\Syntext\Serna-3.8\plugins\dita\DITA-OT1.4\ folder. Result: Build
successful.

I checked the generated PDF, it is using FOP not XEP.

headers

Sonu Mangla | 18 Jul 13:09

[Serna] Configure Serna to use XEP processor

Hi,

I have syntext serna 3.8 installed on my system. I am trying to use XEP to 
publish PDF but unable to do so. Can anyone help me?

Steps that I have performed so far are:

1)       Installed Serna 3.8

2)       Installed the Idiom fo plug-in into the C:\Program 
Files\Syntext\Serna-3.8\plugins\dita\DITA-OT1.4\demo\fo folder.

3)       Installed the XEP into C:\Program Files\Syntext\Serna-3.8
\plugins\dita\DITA-OT1.4\demo\fo\lib\xep folder

4)       Installed the saxon.jar in C:\Program Files\Syntext\Serna-3.8
\plugins\dita\DITA-OT1.4\demo\fo\lib\xep\lib folder.

5)       Installed the ICU4j.jar in C:\Program Files\Syntext\Serna-3.8
\plugins\dita\DITA-OT1.4\demo\fo\lib\ folder.

6)       Added saxon.jar to the classpath in the startcmd.bat file (also 
attached)

7)       Made a copy of the dita2pdf.bat and did modifications as per FO 
readme instructions. (Attaching the modified dita2pdf_xep.bat)

8)       Run the "ant -f integrator.xml"  from the C:\Program 
Files\Syntext\Serna-3.8\plugins\dita\DITA-OT1.4\ folder. Result: Build 
successful.

 
I checked the generated PDF, it is using XSL-FO not XEP.

headers

Nadezhda Sidorova | 3 Jul 11:23

Re: [Serna] Serna 4.0b comment 1

Hello,

> That's no problem. I've observed one crash in version 4.0b. I had two 
> documents opened and I was editing one of them all the time. After a 
> few hours I wanted to save the document and exit the application, but 
> at the moment of saving the crash happened. I sent a crash report but 
> it probably went to Microsoft. Is there any way I could obtain such 
> crash and send it to you, and is it a useful source of information for 
> you?

This information is useful for us but we need some more details about 
the issue.
Please, describe the problem step by step:
 - which templates do you use?
 - do you create or open document?
 - which commands do you use while editing the document?

Please give us as much information as possible.

Thank you.
Regards,
Nadia Sidorova.

> Nadezhda Sidorova wrote:
>> Hello,
>>
>>> Thank you for your help. That almost works fine, besides that the 
>>> "Insert Element" and "Attributes of <>" windows each are being saved 
>>> with the default size. When I resize the docking panel and save 
>>> again, and then reopen the document, the docking panel restores with 
>>> a default width, which additionally depends on what windows are 
>>> docked (i.e. the panel is wider with Insert Element and Attributes 
>>> of <> windows one on top of another, than with only Insert Element). 
>>> I am testing with 4.0b version. It is not a big issue, however would 
>>> be nice to be able to save the size of docking panel too.
>>
>> Thank you for your bug-report. I've managed to reproduce the issue. 
>> It is submitted to the engineers.
>>
>> Thank you.
>> Regards,
>> Nadia Sidorova.
>>
>>
>>> Nadezhda Sidorova wrote:
>>>> Hello,
>>>>
>>>>> One more suggestion regarding the "Insert element" dialog. It can 
>>>>> be docked as the left panel in the application. But it is actually 
>>>>> docked only for the document, which was opened when the dialog was 
>>>>> docked. When more than one document are open and user switches to 
>>>>> another document, then the docked dialog disappears. It is not 
>>>>> only not very usable, but also looks weird because the tabs panel 
>>>>> with the list of documents is actually to the right from that 
>>>>> docked dialog, suggesting that the dialog is docked for all 
>>>>> documents, not just for one. If it should be docked only for the 
>>>>> current document, then these tabs should be below both windows: 
>>>>> Insert Element, and the current document view.
>>>>>
>>>>> I think it might be useful to be able to switch the Insert Element 
>>>>> dialog as permanently docked somewhere in the application (i.e. 
>>>>> Option in View menu to show the window regardless of documents 
>>>>> open, and then remember where it has been docked and leave it 
>>>>> there for all documents - similarly to how Toolbox and many other 
>>>>> windows in MS VisualStudio).
>>>>
>>>> This is not a bug really.
>>>> It's possible to customize Serna view for each document separately. 
>>>> See documentation:
>>>>
>>>> "Syntext Serna 3.8 User's Guide" -> "Customizing Serna" -> "Making 
>>>> Customizations" -> "Serna View Customization" -> "Changing Serna 
>>>> View" -> "Serna GUI Layout Customization"
>>>>
>>>>
>>>> In your case we suggest you save view of the documents where docked 
>>>> "Insert Element" dialog is necessary. You should do the following:
>>>>  - open document
>>>>  - dock "Insert Element" dialog
>>>>  - click "Main menu" -> "View" -> "Save view..." menu item
>>>>  - click "Save" button in "Serna: Save view" dialog -> then "Insert 
>>>> Element" dialog will be docked for all documents opened with a 
>>>> particular template.
>>>>
>>>> For more information see Serna documentation:
>>>>
>>>> "Syntext Serna 3.8 User's Guide" -> "Customizing Serna" -> "Making 
>>>> Customizations" -> "Serna View Customization" -> "Saving Customized 
>>>> Serna View"
>>>>
>>>>
>>>>
>>>> Thank you.
>>>> Regards,
>>>> Nadia Sidorova.
>>>>
>>>>>
>>>>> cherdn@... wrote:
>>>>>>  Hello,
>>>>>>
>>>>>>  It's not an expected behavior, of course.
>>>>>>  The question is too complicated to be answered at once. Your 
>>>>>> inquiry has
>>>>>>  been
>>>>>>  forwarded to our engineers for working it out.
>>>>>>
>>>>>>  Thank you.
>>>>>>  Regards,
>>>>>>  Daria Chernova
>>>>>>
>>>>>>
>>>>>>  On Sun, 22 Jun 2008, Grzegorz Junka wrote:
>>>>>>
>>>>>> >  Hi,
>>>>>> >  I am using two monitors and Serna 4.0b version. Whenever I 
>>>>>> select any >  option
>>>>>> >  from Element menu (i.e. Insert Element, or Element Attributes) 
>>>>>> the window >  is
>>>>>> >  being opened on the other monitor than the Serna program 
>>>>>> itself (i.e. if >  Serna
>>>>>> >  is on monitor 1 these windows are being opened on monitor 2). 
>>>>>> It is not >  very
>>>>>> >  useful and rather annoying. I hope that feature is not an 
>>>>>> expected >  behavior?
>>>>>> >  Regards
>>>>>> >  Grzegorz Junka
>>>>>> > > > >  To unsubscribe send empty e-mail to: 
>>>>>> serna-users-unsubscribe@...
>>>>>> >
>>>>>
>>>>
>>>>
>>>
>>
>>
>

headers

Nadezhda Sidorova | 2 Jul 12:05

Re: [Serna] Serna 4.0b comment 1

Hello,

> Thank you for your help. That almost works fine, besides that the 
> "Insert Element" and "Attributes of <>" windows each are being saved 
> with the default size. When I resize the docking panel and save again, 
> and then reopen the document, the docking panel restores with a 
> default width, which additionally depends on what windows are docked 
> (i.e. the panel is wider with Insert Element and Attributes of <> 
> windows one on top of another, than with only Insert Element). I am 
> testing with 4.0b version. It is not a big issue, however would be 
> nice to be able to save the size of docking panel too.

Thank you for your bug-report. I've managed to reproduce the issue. It 
is submitted to the engineers.

Thank you.
Regards,
Nadia Sidorova.

> Nadezhda Sidorova wrote:
>> Hello,
>>
>>> One more suggestion regarding the "Insert element" dialog. It can be 
>>> docked as the left panel in the application. But it is actually 
>>> docked only for the document, which was opened when the dialog was 
>>> docked. When more than one document are open and user switches to 
>>> another document, then the docked dialog disappears. It is not only 
>>> not very usable, but also looks weird because the tabs panel with 
>>> the list of documents is actually to the right from that docked 
>>> dialog, suggesting that the dialog is docked for all documents, not 
>>> just for one. If it should be docked only for the current document, 
>>> then these tabs should be below both windows: Insert Element, and 
>>> the current document view.
>>>
>>> I think it might be useful to be able to switch the Insert Element 
>>> dialog as permanently docked somewhere in the application (i.e. 
>>> Option in View menu to show the window regardless of documents open, 
>>> and then remember where it has been docked and leave it there for 
>>> all documents - similarly to how Toolbox and many other windows in 
>>> MS VisualStudio).
>>
>> This is not a bug really.
>> It's possible to customize Serna view for each document separately. 
>> See documentation:
>>
>> "Syntext Serna 3.8 User's Guide" -> "Customizing Serna" -> "Making 
>> Customizations" -> "Serna View Customization" -> "Changing Serna 
>> View" -> "Serna GUI Layout Customization"
>>
>>
>> In your case we suggest you save view of the documents where docked 
>> "Insert Element" dialog is necessary. You should do the following:
>>  - open document
>>  - dock "Insert Element" dialog
>>  - click "Main menu" -> "View" -> "Save view..." menu item
>>  - click "Save" button in "Serna: Save view" dialog -> then "Insert 
>> Element" dialog will be docked for all documents opened with a 
>> particular template.
>>
>> For more information see Serna documentation:
>>
>> "Syntext Serna 3.8 User's Guide" -> "Customizing Serna" -> "Making 
>> Customizations" -> "Serna View Customization" -> "Saving Customized 
>> Serna View"
>>
>>
>>
>> Thank you.
>> Regards,
>> Nadia Sidorova.
>>
>>>
>>> cherdn@... wrote:
>>>>  Hello,
>>>>
>>>>  It's not an expected behavior, of course.
>>>>  The question is too complicated to be answered at once. Your 
>>>> inquiry has
>>>>  been
>>>>  forwarded to our engineers for working it out.
>>>>
>>>>  Thank you.
>>>>  Regards,
>>>>  Daria Chernova
>>>>
>>>>
>>>>  On Sun, 22 Jun 2008, Grzegorz Junka wrote:
>>>>
>>>> >  Hi,
>>>> >  I am using two monitors and Serna 4.0b version. Whenever I 
>>>> select any >  option
>>>> >  from Element menu (i.e. Insert Element, or Element Attributes) 
>>>> the window >  is
>>>> >  being opened on the other monitor than the Serna program itself 
>>>> (i.e. if >  Serna
>>>> >  is on monitor 1 these windows are being opened on monitor 2). It 
>>>> is not >  very
>>>> >  useful and rather annoying. I hope that feature is not an 
>>>> expected >  behavior?
>>>> >  Regards
>>>> >  Grzegorz Junka
>>>> > > > >  To unsubscribe send empty e-mail to: 
>>>> serna-users-unsubscribe@...
>>>> >
>>>
>>
>>
>

headers

Nadezhda Sidorova | 1 Jul 14:59

Re: [Serna] Serna 4.0b comment 1 (fwd)

Hello,

> One more suggestion regarding the "Insert element" dialog. It can be 
> docked as the left panel in the application. But it is actually docked 
> only for the document, which was opened when the dialog was docked. 
> When more than one document are open and user switches to another 
> document, then the docked dialog disappears. It is not only not very 
> usable, but also looks weird because the tabs panel with the list of 
> documents is actually to the right from that docked dialog, suggesting 
> that the dialog is docked for all documents, not just for one. If it 
> should be docked only for the current document, then these tabs should 
> be below both windows: Insert Element, and the current document view.
>
> I think it might be useful to be able to switch the Insert Element 
> dialog as permanently docked somewhere in the application (i.e. Option 
> in View menu to show the window regardless of documents open, and then 
> remember where it has been docked and leave it there for all documents 
> - similarly to how Toolbox and many other windows in MS VisualStudio).

This is not a bug really.
It's possible to customize Serna view for each document separately. See 
documentation:

"Syntext Serna 3.8 User's Guide" -> "Customizing Serna" -> "Making 
Customizations" -> "Serna View Customization" -> "Changing Serna View" 
-> "Serna GUI Layout Customization"

In your case we suggest you save view of the documents where docked 
"Insert Element" dialog is necessary. You should do the following:
  - open document
  - dock "Insert Element" dialog
  - click "Main menu" -> "View" -> "Save view..." menu item
  - click "Save" button in "Serna: Save view" dialog -> then "Insert 
Element" dialog will be docked for all documents opened with a 
particular template.

For more information see Serna documentation:

"Syntext Serna 3.8 User's Guide" -> "Customizing Serna" -> "Making 
Customizations" -> "Serna View Customization" -> "Saving Customized 
Serna View"

Thank you.
Regards,
Nadia Sidorova.

>
> cherdn@... wrote:
>>  Hello,
>>
>>  It's not an expected behavior, of course.
>>  The question is too complicated to be answered at once. Your inquiry 
>> has
>>  been
>>  forwarded to our engineers for working it out.
>>
>>  Thank you.
>>  Regards,
>>  Daria Chernova
>>
>>
>>  On Sun, 22 Jun 2008, Grzegorz Junka wrote:
>>
>> >  Hi,
>> >  I am using two monitors and Serna 4.0b version. Whenever I select 
>> any >  option
>> >  from Element menu (i.e. Insert Element, or Element Attributes) the 
>> window >  is
>> >  being opened on the other monitor than the Serna program itself 
>> (i.e. if >  Serna
>> >  is on monitor 1 these windows are being opened on monitor 2). It 
>> is not >  very
>> >  useful and rather annoying. I hope that feature is not an expected 
>> >  behavior?
>> >  Regards
>> >  Grzegorz Junka
>> > > > >  To unsubscribe send empty e-mail to: 
>> serna-users-unsubscribe@...
>> >
>

headers

Grzegorz Junka | 22 Jun 21:41

[Serna] Serna 4.0b comment 1

Hi,
I am using two monitors and Serna 4.0b version. Whenever I select any option
from Element menu (i.e. Insert Element, or Element Attributes) the window is
being opened on the other monitor than the Serna program itself (i.e. if Serna
is on monitor 1 these windows are being opened on monitor 2). It is not very
useful and rather annoying. I hope that feature is not an expected behavior?
Regards
Grzegorz Junka

headers

Eric Sirois | 2 Jun 16:28

Re: [Serna] Compiling non-standard attributes with DITA open toolkit

Hello Grzegorz,

Yes, XSD does provide that capability to enforce content via datatypes. For instance, making sure that dates follow ISO 8601 standard. I just uploaded some fixes to OASIS a couple of weeks ago. Both are equivalent, but if there is a discrepancy between the two, the DTDs will be normative.

If you are planning to use the out-of-the box topic types, either one will be fine. If you have a requirement for entities, then you have to use the DTDs (remove XSD). If you are planning on creating new specializations then DTDs are easier. The XSD 1.0 spec does not make specialization an easy process. I hoping that we will be able to simplify things when XSD 1.1 comes out.

You will need to change multiple files, because each topic will need to add the xmlns and xsi attributes. To get a sense of what file would need to be changed for the DTDs look for %arch-atts; in the *.mod files.

If you don't remove the doctype in you will get both. I think that the best suggestion, at the moment, is the one that Paul provided. - adjust the templates to remove the XML Schema attributes.

Hope that helps.

Kind rgards,
Eric
Eric A. Sirois
Staff Software Developer
DB2 Universal Database - Information Development
DITA Migration and Tools Development
IBM Canada Ltd. - Toronto Software Lab
Email: esirois-G1DYhSM1WHTQT0dZR+AlfA@public.gmane.org
Phone:(905) 413-2841
Blue Pages (Internal)

"Transparency and accessibility requirements dictate that public information and government
transactions avoid depending on technologies that imply or impose a specific product or
platform on businesses or citizens" - EU on XML-based office document formats.

Grzegorz Junka <xgjx-wo4oW1Pw1HF3vZ0LZ0W7Rg@public.gmane.org>

05/31/2008 08:46 AM

To	Eric Sirois/Toronto/IBM <at> IBMCA
cc	news <news-dbVV3NMTNubNLxjTenLetw@public.gmane.org>, serna-users-YYLLxrGCLz9BDgjK7y7TUQ@public.gmane.org
Subject	Re: [Serna] Compiling non-standard attributes with DITA open toolkit

Hi Eric,
Thanks for your response. I did some reading and it looks like it is better if documents get XSD validation instead of DTD validation, but it probably depends on the type of documents and the purpose of validation? I wouldn't know which option to choose as I don't know what are the differences in choosing these options.

Regarding c), if I don't remove DOCTYPE won't I get both XSD and DTD validation?

Also, to include bot xmlxs:xsi and xsi:noNamespaceSchemaLocation in DTDs I should be able to change only one file, as all the other topic types derive from the main topic? Is that right, and which file I would need to change? I tried to find out but there are a few DTD files related to the main topic definition.

Many thanks for your help
Regards
Grzegorz Junka

Eric Sirois wrote:

Hello Grzegorz,

It's not a bug per se. That final decision rests with the folks at Syntext. Serna has the capability to support entities (which XML Schema does not have). In order to do get that capability, Serna uses in-line DOCTYPE.

That said, to process those documents in the Toolkit one needs to do one of the following:
a) remove the DOCTYPE from the XML docs; you get XSD validation
b) remove xmlxs:xsi namespace and xsi:noNamespaceSchemaLocation attribute from the XML docs; you get DTD validation
c) modify the DTDs in the Toolkit to include xmlxs:xsi namespace and xsi:noNamespaceSchemaLocation attribute; you get DTD validation

Changing the XML parser parameters will not do anything useful since it is dependent on what appears in the XML docs. The easiest one to do ay this point would be to modify the DTDs in the Toolkit. That would allow you to process the documents without having to modify each one them.

Kind regards,
Eric
Eric A. Sirois
Staff Software Developer
DB2 Universal Database - Information Development
DITA Migration and Tools Development
IBM Canada Ltd. - Toronto Software Lab
Email: esirois-G1DYhSM1WHTQT0dZR+AlfA@public.gmane.org
Phone:(905) 413-2841
Blue Pages (Internal)

"Transparency and accessibility requirements dictate that public information and government
transactions avoid depending on technologies that imply or impose a specific product or
platform on businesses or citizens" - EU on XML-based office document formats.

Grzegorz Junka <xgjx-wo4oW1Pw1HF3vZ0LZ0W7Rg@public.gmane.org>

05/26/2008 02:52 PM

To	Eric Sirois/Toronto/IBM <at> IBMCA
cc	news <news-dbVV3NMTNubNLxjTenLetw@public.gmane.org>, serna-users-YYLLxrGCLz9BDgjK7y7TUQ@public.gmane.org
Subject	Re: [Serna] Compiling non-standard attributes with DITA open toolkit

Hi Eric,
I may understand what causes the parser to validate the document using the Map DTD but what I don't understand is why this the default template of a document created with Serna Syntext. If I need to manually amend each created document then this is clearly a bug. Do you agree?

BTW Could you please advise what would be the best solution here? Changing the beginning of the file to comply with both XML and DTD definitions or changing parameters of the XML parser?

Thanks for your help & Regards
Grzegorz Junka

Eric Sirois wrote:

Hi Grzegorz,

Ahh. That's not an issue with the XML Schema. You are getting that error because the xml document contains a DOCTYPE.

<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd" []>
<map xsi:noNamespaceSchemaLocation="urn:oasis:names:tc:dita:xsd:concept.xsd:1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

The XML parser is attempting to validate the XML document using the Map DTD. The xsi namespace and attribute are not defined in the DTDs.

Here is the FAQ that explains the validation algorithm.
http://xerces.apache.org/xerces2-j/faq-pcfp.html#faq-3

Eric
Eric A. Sirois
Staff Software Developer
DB2 Universal Database - Information Development
DITA Migration and Tools Development
IBM Canada Ltd. - Toronto Software Lab
Email: esirois-G1DYhSM1WHTQT0dZR+AlfA@public.gmane.org
Phone:(905) 413-2841
Blue Pages (Internal)

"Transparency and accessibility requirements dictate that public information and government
transactions avoid depending on technologies that imply or impose a specific product or
platform on businesses or citizens" - EU on XML-based office document formats.

Grzegorz Junka <xgjx-wo4oW1Pw1HF3vZ0LZ0W7Rg@public.gmane.org>
Sent by: news <news-dbVV3NMTNubNLxjTenLetw@public.gmane.org>

05/26/2008 12:03 PM

To	serna-users-YYLLxrGCLz9BDgjK7y7TUQ@public.gmane.org
cc
Subject	Re: [Serna] Compiling non-standard attributes with DITA open toolkit

Grzegorz Junka <xgjx <at> ...> writes:

>
> Hi,
> I have a simple structure with some ditamaps and some topics, which I try to
> compile with 1.4.1 DITA open toolkit. The compilation fails because original
> schemas don't define attributes xmlns:xsi and xsi:noNamespaceSchemaLocation,
> which Serna adds to each created DITA file. Also the Publish command from Serna
> produces warnings for each such file.
>
> How can I configure Serna to not add not standard attributes to these files, or
> change relevant schemas in the toolkit directory so these attributes are
> recognized and don't produce any errors or warnings?
>
> Many thanks for your help in advance.
> Kind Regards
> Grzegorz Junka
>

Hi Eric,
Here is the error from DITA open toolkit:

----->
Unable to locate tools.jar. Expected to find it in C:\Program Files
(x86)\Java\jre1.6.0_03\lib\tools.jar
Buildfile: build_test.xml

(...)

check-arg:
[echo] *****************************************************************
[echo] * basedir = C:\DITA-OT1.4.1
[echo] * dita.dir = C:\DITA-OT1.4.1
[echo] * input = DITA\Root.ditamap
[echo] * transtype = xhtml
[echo] * tempdir = temp
[echo] * outputdir = DITA\_output
[echo] * extname = .xml
[echo] * clean.temp = true
[echo] * xslt.parser = XALAN
[echo] *****************************************************************

(...)

gen-list-without-flagging:
[pipeline] Using XERCES.

BUILD FAILED
C:\DITA-OT1.4.1\build_test.xml:117: The following error occurred while executing
this line:
C:\DITA-OT1.4.1\build_preprocess.xml:32: [DOTJ012F][FATAL] Failed to parse the
input file 'Root.ditamap' due to below ex
ception. Please correct the input base on the exception message.:Root.ditamap
Line 3:Attribute "xsi:noNamespaceSchemaLoc
ation" must be declared for element type "map".

Total time: 1 second
c:\DITA-OT1.4.1>
----->

Here are errors from Serna:

----->
(...)

check-arg:
[echo] *****************************************************************
[echo] * basedir = D:\Program Files
(x86)\Syntext\Serna-3.7\plugins\dita\DITA-OT1.4
[echo] * dita.dir = D:\Program Files
(x86)\Syntext\Serna-3.7\plugins\dita\DITA-OT1.4
[echo] * input = I:/DITA/publishTemp.520.ditamap
[echo] * transtype = xhtml
[echo] * tempdir = z:/_publishTemp.520.ditamap_
[echo] * outputdir = I:/DITA/_output
[echo] * extname = .xml
[echo] * clean.temp = ${clean.temp}
[echo] * xslt.parser = XALAN
[echo] *****************************************************************

(...)

gen-list-without-flagging:
[pipeline] Using XERCES.
[pipeline] [Error] :3:152: Attribute "xmlns:xsi" must be declared for element
type "map".
[pipeline] [Error] :3:152: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "map".
[pipeline] [Error] :3:132: Attribute "xmlns:xsi" must be declared for element
type "map".
[pipeline] [Error] :3:132: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "map".
[pipeline] [Error] :3:155: Attribute "xmlns:xsi" must be declared for element
type "concept".
[pipeline] [Error] :3:155: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "concept".
[pipeline] [Error] :3:155: Attribute "xmlns:xsi" must be declared for element
type "concept".
[pipeline] [Error] :3:155: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "concept".
[pipeline] [Error] :3:155: Attribute "xmlns:xsi" must be declared for element
type "concept".
[pipeline] [Error] :3:155: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "concept".
[pipeline] [Error] :3:155: Attribute "xmlns:xsi" must be declared for element
type "concept".
[pipeline] [Error] :3:155: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "concept".

gen-list-with-flagging:

gen-list:

debug:
[pipeline] [Error] Portals.ditamap:3:152: Attribute "xmlns:xsi" must be
declared for element type "map".
[pipeline] [Error] Portals.ditamap:3:152: Attribute
"xsi:noNamespaceSchemaLocation" must be declared for element type "map".
[pipeline] [Error] shopping.xml:3:155: Attribute "xmlns:xsi" must be declared
for element type "concept".
[pipeline] [Error] shopping.xml:3:155: Attribute
"xsi:noNamespaceSchemaLocation" must be declared for element type "concept".
[pipeline] [Error] Profiles.ditamap:3:132: Attribute "xmlns:xsi" must be
declared for element type "map".
[pipeline] [Error] Profiles.ditamap:3:132: Attribute
"xsi:noNamespaceSchemaLocation" must be declared for element type "map".
[pipeline] [Error] event.xml:3:155: Attribute "xmlns:xsi" must be declared for
element type "concept".
[pipeline] [Error] event.xml:3:155: Attribute "xsi:noNamespaceSchemaLocation"
must be declared for element type "concept".
[pipeline] [Error] product.xml:3:155: Attribute "xmlns:xsi" must be declared
for element type "concept".
[pipeline] [Error] product.xml:3:155: Attribute "xsi:noNamespaceSchemaLocation"
must be declared for element type "concept".
[pipeline] [Error] definition.xml:3:155: Attribute "xmlns:xsi" must be declared
for element type "concept".
[pipeline] [Error] definition.xml:3:155: Attribute
"xsi:noNamespaceSchemaLocation" must be declared for element type "concept".
----->

And here is the beginning of Root.ditamap:

----->
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd" []>
<map xsi:noNamespaceSchemaLocation="urn:oasis:names:tc:dita:xsd:concept.xsd:1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<title>The main root of all documents</title>
----->

When I remove both attributes:
xsi:noNamespaceSchemaLocation="urn:oasis:names:tc:dita:xsd:concept.xsd:1.1"
and
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

everything compiles without any problems

Thanks
GregJ

headers

Eric Sirois | 27 May 18:54

Re: [Serna] Compiling non-standard attributes with DITA open toolkit

Hello Grzegorz,

It's not a bug per se. That final decision rests with the folks at Syntext. Serna has the capability to support entities (which XML Schema does not have). In order to do get that capability, Serna uses in-line DOCTYPE.

That said, to process those documents in the Toolkit one needs to do one of the following:
a) remove the DOCTYPE from the XML docs; you get XSD validation
b) remove xmlxs:xsi namespace and xsi:noNamespaceSchemaLocation attribute from the XML docs; you get DTD validation
c) modify the DTDs in the Toolkit to include xmlxs:xsi namespace and xsi:noNamespaceSchemaLocation attribute; you get DTD validation

Changing the XML parser parameters will not do anything useful since it is dependent on what appears in the XML docs. The easiest one to do ay this point would be to modify the DTDs in the Toolkit. That would allow you to process the documents without having to modify each one them.

Kind regards,
Eric
Eric A. Sirois
Staff Software Developer
DB2 Universal Database - Information Development
DITA Migration and Tools Development
IBM Canada Ltd. - Toronto Software Lab
Email: esirois-G1DYhSM1WHTQT0dZR+AlfA@public.gmane.org
Phone:(905) 413-2841
Blue Pages (Internal)

"Transparency and accessibility requirements dictate that public information and government
transactions avoid depending on technologies that imply or impose a specific product or
platform on businesses or citizens" - EU on XML-based office document formats.

Grzegorz Junka <xgjx-wo4oW1Pw1HF3vZ0LZ0W7Rg@public.gmane.org>

05/26/2008 02:52 PM

To	Eric Sirois/Toronto/IBM <at> IBMCA
cc	news <news-dbVV3NMTNubNLxjTenLetw@public.gmane.org>, serna-users-YYLLxrGCLz9BDgjK7y7TUQ@public.gmane.org
Subject	Re: [Serna] Compiling non-standard attributes with DITA open toolkit

Hi Eric,
I may understand what causes the parser to validate the document using the Map DTD but what I don't understand is why this the default template of a document created with Serna Syntext. If I need to manually amend each created document then this is clearly a bug. Do you agree?

BTW Could you please advise what would be the best solution here? Changing the beginning of the file to comply with both XML and DTD definitions or changing parameters of the XML parser?

Thanks for your help & Regards
Grzegorz Junka

Eric Sirois wrote:

Hi Grzegorz,

Ahh. That's not an issue with the XML Schema. You are getting that error because the xml document contains a DOCTYPE.

<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd" []>
<map xsi:noNamespaceSchemaLocation="urn:oasis:names:tc:dita:xsd:concept.xsd:1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

The XML parser is attempting to validate the XML document using the Map DTD. The xsi namespace and attribute are not defined in the DTDs.

Here is the FAQ that explains the validation algorithm.
http://xerces.apache.org/xerces2-j/faq-pcfp.html#faq-3

Eric
Eric A. Sirois
Staff Software Developer
DB2 Universal Database - Information Development
DITA Migration and Tools Development
IBM Canada Ltd. - Toronto Software Lab
Email: esirois-G1DYhSM1WHTQT0dZR+AlfA@public.gmane.org
Phone:(905) 413-2841
Blue Pages (Internal)

"Transparency and accessibility requirements dictate that public information and government
transactions avoid depending on technologies that imply or impose a specific product or
platform on businesses or citizens" - EU on XML-based office document formats.

Grzegorz Junka <xgjx-wo4oW1Pw1HF3vZ0LZ0W7Rg@public.gmane.org>
Sent by: news <news-dbVV3NMTNubNLxjTenLetw@public.gmane.org>

05/26/2008 12:03 PM

To	serna-users-YYLLxrGCLz9BDgjK7y7TUQ@public.gmane.org
cc
Subject	Re: [Serna] Compiling non-standard attributes with DITA open toolkit

Grzegorz Junka <xgjx <at> ...> writes:

>
> Hi,
> I have a simple structure with some ditamaps and some topics, which I try to
> compile with 1.4.1 DITA open toolkit. The compilation fails because original
> schemas don't define attributes xmlns:xsi and xsi:noNamespaceSchemaLocation,
> which Serna adds to each created DITA file. Also the Publish command from Serna
> produces warnings for each such file.
>
> How can I configure Serna to not add not standard attributes to these files, or
> change relevant schemas in the toolkit directory so these attributes are
> recognized and don't produce any errors or warnings?
>
> Many thanks for your help in advance.
> Kind Regards
> Grzegorz Junka
>

Hi Eric,
Here is the error from DITA open toolkit:

----->
Unable to locate tools.jar. Expected to find it in C:\Program Files
(x86)\Java\jre1.6.0_03\lib\tools.jar
Buildfile: build_test.xml

(...)

check-arg:
[echo] *****************************************************************
[echo] * basedir = C:\DITA-OT1.4.1
[echo] * dita.dir = C:\DITA-OT1.4.1
[echo] * input = DITA\Root.ditamap
[echo] * transtype = xhtml
[echo] * tempdir = temp
[echo] * outputdir = DITA\_output
[echo] * extname = .xml
[echo] * clean.temp = true
[echo] * xslt.parser = XALAN
[echo] *****************************************************************

(...)

gen-list-without-flagging:
[pipeline] Using XERCES.

BUILD FAILED
C:\DITA-OT1.4.1\build_test.xml:117: The following error occurred while executing
this line:
C:\DITA-OT1.4.1\build_preprocess.xml:32: [DOTJ012F][FATAL] Failed to parse the
input file 'Root.ditamap' due to below ex
ception. Please correct the input base on the exception message.:Root.ditamap
Line 3:Attribute "xsi:noNamespaceSchemaLoc
ation" must be declared for element type "map".

Total time: 1 second
c:\DITA-OT1.4.1>
----->

Here are errors from Serna:

----->
(...)

check-arg:
[echo] *****************************************************************
[echo] * basedir = D:\Program Files
(x86)\Syntext\Serna-3.7\plugins\dita\DITA-OT1.4
[echo] * dita.dir = D:\Program Files
(x86)\Syntext\Serna-3.7\plugins\dita\DITA-OT1.4
[echo] * input = I:/DITA/publishTemp.520.ditamap
[echo] * transtype = xhtml
[echo] * tempdir = z:/_publishTemp.520.ditamap_
[echo] * outputdir = I:/DITA/_output
[echo] * extname = .xml
[echo] * clean.temp = ${clean.temp}
[echo] * xslt.parser = XALAN
[echo] *****************************************************************

(...)

gen-list-without-flagging:
[pipeline] Using XERCES.
[pipeline] [Error] :3:152: Attribute "xmlns:xsi" must be declared for element
type "map".
[pipeline] [Error] :3:152: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "map".
[pipeline] [Error] :3:132: Attribute "xmlns:xsi" must be declared for element
type "map".
[pipeline] [Error] :3:132: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "map".
[pipeline] [Error] :3:155: Attribute "xmlns:xsi" must be declared for element
type "concept".
[pipeline] [Error] :3:155: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "concept".
[pipeline] [Error] :3:155: Attribute "xmlns:xsi" must be declared for element
type "concept".
[pipeline] [Error] :3:155: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "concept".
[pipeline] [Error] :3:155: Attribute "xmlns:xsi" must be declared for element
type "concept".
[pipeline] [Error] :3:155: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "concept".
[pipeline] [Error] :3:155: Attribute "xmlns:xsi" must be declared for element
type "concept".
[pipeline] [Error] :3:155: Attribute "xsi:noNamespaceSchemaLocation" must be
declared for element type "concept".

gen-list-with-flagging:

gen-list:

debug:
[pipeline] [Error] Portals.ditamap:3:152: Attribute "xmlns:xsi" must be
declared for element type "map".
[pipeline] [Error] Portals.ditamap:3:152: Attribute
"xsi:noNamespaceSchemaLocation" must be declared for element type "map".
[pipeline] [Error] shopping.xml:3:155: Attribute "xmlns:xsi" must be declared
for element type "concept".
[pipeline] [Error] shopping.xml:3:155: Attribute
"xsi:noNamespaceSchemaLocation" must be declared for element type "concept".
[pipeline] [Error] Profiles.ditamap:3:132: Attribute "xmlns:xsi" must be
declared for element type "map".
[pipeline] [Error] Profiles.ditamap:3:132: Attribute
"xsi:noNamespaceSchemaLocation" must be declared for element type "map".
[pipeline] [Error] event.xml:3:155: Attribute "xmlns:xsi" must be declared for
element type "concept".
[pipeline] [Error] event.xml:3:155: Attribute "xsi:noNamespaceSchemaLocation"
must be declared for element type "concept".
[pipeline] [Error] product.xml:3:155: Attribute "xmlns:xsi" must be declared
for element type "concept".
[pipeline] [Error] product.xml:3:155: Attribute "xsi:noNamespaceSchemaLocation"
must be declared for element type "concept".
[pipeline] [Error] definition.xml:3:155: Attribute "xmlns:xsi" must be declared
for element type "concept".
[pipeline] [Error] definition.xml:3:155: Attribute
"xsi:noNamespaceSchemaLocation" must be declared for element type "concept".
----->

And here is the beginning of Root.ditamap:

----->
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd" []>
<map xsi:noNamespaceSchemaLocation="urn:oasis:names:tc:dita:xsd:concept.xsd:1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<title>The main root of all documents</title>
----->

When I remove both attributes:
xsi:noNamespaceSchemaLocation="urn:oasis:names:tc:dita:xsd:concept.xsd:1.1"
and
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

everything compiles without any problems

Thanks
GregJ

headers

Grzegorz Junka | 25 May 17:42

[Serna] Compiling non-standard attributes with DITA open toolkit

Hi,
I have a simple structure with some ditamaps and some topics, which I try to
compile with 1.4.1 DITA open toolkit. The compilation fails because original
schemas don't define attributes xmlns:xsi and xsi:noNamespaceSchemaLocation,
which Serna adds to each created DITA file. Also the Publish command from Serna
produces warnings for each such file.

How can I configure Serna to not add not standard attributes to these files, or
change relevant schemas in the toolkit directory so these attributes are
recognized and don't produce any errors or warnings?

Many thanks for your help in advance.
Kind Regards
Grzegorz Junka

headers

Jakob Fix | 4 May 16:29

[Serna] formatting gets lost when switching to markup view

Hello,  I am a new user of Syntext Serna.  I have created a xsl fo
 stylesheet to customise the look for my documents.  Among other
 things, I have added background colours to a number of elements.  When
 switching to markup view where all element tags are displayed, the
 background colours disappear.

 How can I avoid this?  It is really helpful to see the background
 colours.  Thanks in advance.

 --
 cheers,
 Jakob.

--

-- 
cheers,
Jakob.

headers

cherdn | 4 May 16:11

[Serna] test1

test1

Mon	Tue	Wed	Thu	Fri	Sat	Sun

	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31