gmane.editors.serna.user

Re: [Serna] Default font in Serna 4 (RC 2)

Don Day — 2008-11-20T20:46:40

Yours is an interesting question, Bob. The Serna styles are based on the original FO transforms created for the DITA Open Toolkit. At the time I created those OT transforms, to avoid having to support font embedding for PDF outputs, I decided to constrain font usage to those available in the PDF Standard font set. Those fonts, as describe in this FAQ (http://www.pdf-tools.com/asp/faq.asp?s=&q=58) are: Times?Roman, Times?Bold, Times?Italic, Times?BoldItalic, Helvetica, Helvetica?Bold, Helvetica?Oblique, Helvetica?BoldOblique, Courier, Courier ?Bold, Courier?Oblique, Courier?BoldOblique, Symbol, ZapfDingbats Good old Arial is outside the fold, but could be accommodated through an override that redefines the setup parms. Since the Serna display stylesheets are not used for publication, this seems like it could be made into a configuration option, in fact, without causing the kind of problems that led to the original decision about what fonts to include by default. Regards, -- Don Day Chair, OASIS DITA Technical Committee Architect, Lightweight DITA Publishing Solutions Email: dond-r/Jw6+rmf7HQT0dZR+AlfA< at >public.gmane.org 11501 Burnet Rd. MS9033E015, Austin TX 78758 Phone: +1 512-244-2868 (home office) "Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" --T.S. Eliot news public.gmane.org> wrote on 11/20/2008 10:39:27 AM: the carried Helvetica aren't Symbol... Serna

[Serna] Default font in Serna 4 (RC 2)

Bob Beims — 2008-11-20T16:39:27

Folks; We've run across an interesting problem at my company. For Windows installations, Serna style sheets for the WYSIWYG window use Helvetica as the default font. Of course, Helvetica is not a standard font on Windows systems, so somewhere in the system (haven't figured out where) a substitution is carried out (probably to Arial). That's all fine and good if a user doesn't have a Helvetica font package installed. But in our case, many users have an old, non-unicode, Helvetica package installed. Because of this, characters such as Greek symbols aren't displayed properly, nor do all of the glyphs show up in the Insert Symbol... dialog box. Would anyone have a huge problem if Syntext were to update the default Serna style sheets to specify Arial as the default font (at least for Windows installs)? On all recent versions of Windows, an OpenType (unicode) Arial package is included in the base installation. Regards, Bob

[Serna] Want to upgrade from serna2 to serna4

Johan Groth — 2008-11-10T22:06:44

But the site wants me to input serial number and password. Well, I assume the serial number is the serial number in serna.lic but password? I bought serna2 two and a half years ago so I have forgotten the password. How do I retrieve/recover it? Regards, Johan

Re: [Serna] Bug - Serna 4.1b on Mac OS X

2008-09-04T14:21:32

Thank you Bob for your bug report. I've added it in our bug-tracking system. Regards, Daria Chernova On Wed, 3 Sep 2008, Bob Beims wrote:

[Serna] Bug - Serna 4.1b on Mac OS X

Bob Beims — 2008-09-03T13:32:37

I just installed 4.1b under Mac OS X 10.5.4 on an Intel-based MacBook, and encountered one serious problem: I can't resize the main window by click-dragging the lower left corner. There's no "grab handle" (although the window can be maximized with the green button in the upper right). Bob

Re: [Serna] Configure Serna to use XEP processor

Nadezhda Sidorova — 2008-08-14T11:07:08

Hello, Which stand-alone tool do you use to generate PDF2 output? It seems to be a problem with your modified 'dita2pdf_xep.bat' script. Please send it to us. We'll try to sort out the problem. Thank you. Regards, Nadia Sidorova.

Re: [Serna] Serna 4.0b comment 1

Nadezhda Sidorova — 2008-08-14T11:06:48

Hello, You may work with Serna-4 using your purchased license (serial is 874803805). It hasn't been expired yet. Unfortunately I didn't manage to reproduce the issue again. We are working Serna-4 out hard now and we are planing to issue Serna-4.1b soon. As soon as it releases, can you please retest this crash. We use such mechanism for Serna-3.X. But this functionality hasn't existed for Serna-4 yet. We are working it out. That's way I asked you about step-by-step description of reproducing the crash. Thank you. Regards, Nadia Sidorova.

[Serna] Re: Thank You for Evaluating Syntext Serna, Do You Need Any Guidance?

2008-08-12T16:09:26

Hello Michel, Your use-case is connected not with Serna but with DITA OT, which Serna uses for publishing to PDF or HTML. You may find all the documentation about it here: http://dita-ot.sourceforge.net/ If you want to change header and footer of the generated pdf file, you have to change DITA OT's xsl files. I've prepared a small sample for you - how to work with xsl files: New header content I've attached sample xsl file. How to apply it: 1. download attached 'topic2foImpl.xsl' 2. replace existing file here: "c:\Program Files\Syntext\Serna-3.8\plugins\dita\DITA-OT1.4\xsl\xslfo\" 3. run Serna 4. create DITA 1.1 Topic file 5. publish it to PDF -> see result In the generated pdf file there must be text "New header content" in the header. Hope it helps you to solve the issue. But it's better to ask DITA OT developers about this use-case in DITA OT mailing list. Thank you. Regards, Daria Chernova

[Serna] PDF Generation Help

Michel — 2008-08-06T07:35:25

Hi, I'm new to DITA and serna. I've downloaded a trial version and created a small dita test document from which I wanted to generate a pdf. All of this worked wonderfully, however I want to add my own header and footer to the generated pdf and cannot find out how to achieve this. I've looked in many forums, faqs and tutorials, but without avail. Maybe someone on this list can give me hint, how I can achieve this. Thanks!

[Serna] Recall: [Serna] Configure Serna to use XEP processor

Beims Bob — 2008-07-23T17:09:47

Beims Bob would like to recall the message, "[Serna] Configure Serna to use XEP processor".

RE: [Serna] Configure Serna to use XEP processor

Beims Bob — 2008-07-23T16:39:06

Sonu; I'd suggest posting the question to dita-users-hHKSG33TihhbjbujkaE4pw< at >public.gmane.org, as there's a lot more activity there than on the OT mail list. You'll need to join the group first: http://tech.groups.yahoo.com/group/dita-users/ (or dita-users-subscribe-hHKSG33TihhbjbujkaE4pw< at >public.gmane.org). Regards, Bob -----Original Message----- From: Nadezhda Sidorova [mailto:sidnv-YYLLxrGCLz9BDgjK7y7TUQ< at >public.gmane.org] Sent: Wednesday, July 23, 2008 10:58 AM To: Sonu Mangla Cc: serna-users-YYLLxrGCLz9BDgjK7y7TUQ< at >public.gmane.org Subject: Re: [Serna] Configure Serna to use XEP processor Hello, (also FO Your question is related to DITA-OT, not Serna. I suggest you to consult a DITA-OT community at http://sourceforge.net/projects/dita-ot/ Thank you. Regards, Nadia Sidorova. To unsubscribe send empty e-mail to: serna-users-unsubscribe-YYLLxrGCLz9BDgjK7y7TUQ< at >public.gmane.org

Re: [Serna] Configure Serna to use XEP processor

Nadezhda Sidorova — 2008-07-23T15:57:34

Hello, Your question is related to DITA-OT, not Serna. I suggest you to consult a DITA-OT community at http://sourceforge.net/projects/dita-ot/ Thank you. Regards, Nadia Sidorova.

Re: [Serna] Serna 4.0b comment 1

Nadezhda Sidorova — 2008-07-23T09:04:15

Hello, Sorry for the delay in answering your letter. I tried to reproduce the problem with crash but I was failed. I did the following: -create two DITA 1.1 Concept documents -drap and drop some documents from external file browser to Serna -edit some document (type text, insert elements including ) -save documents. Can you please provide me with some more details about this crash? Thank you. Regards, Nadia Sidorova.

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

Sonu Mangla — 2008-07-18T11:19:38

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.

[Serna] Configure Serna to use XEP processor

Sonu Mangla — 2008-07-18T11:10:28

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.

Re: [Serna] Serna 4.0b comment 1

Nadezhda Sidorova — 2008-07-03T09:23:11

Hello, 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.

Re: [Serna] Serna 4.0b comment 1

Nadezhda Sidorova — 2008-07-02T10:05:18

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

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

Nadezhda Sidorova — 2008-07-01T12:59:13

Hello, 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.

Re: [Serna] Serna 4.0b comment 1

2008-06-25T10:05:45

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:

[Serna] Serna 4.0b comment 1

Grzegorz Junka — 2008-06-22T19:43:38

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

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

Eric Sirois — 2008-06-02T14:28:16

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< at >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 public.gmane.org> 05/31/2008 08:46 AM To Eric Sirois/Toronto/IBM< at >IBMCA cc news public.gmane.org>, serna-users-YYLLxrGCLz9BDgjK7y7TUQ< at >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< at >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 public.gmane.org> 05/26/2008 02:52 PM To Eric Sirois/Toronto/IBM< at >IBMCA cc news public.gmane.org>, serna-users-YYLLxrGCLz9BDgjK7y7TUQ< at >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. 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< at >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 public.gmane.org> Sent by: news public.gmane.org> 05/26/2008 12:03 PM To serna-users-YYLLxrGCLz9BDgjK7y7TUQ< at >public.gmane.org cc Subject Re: [Serna] Compiling non-standard attributes with DITA open toolkit Grzegorz Junka ...> writes: try to original xsi:noNamespaceSchemaLocation, from Serna files, or 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: -----> The main root of all documents -----> 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 To unsubscribe send empty e-mail to: serna-users-unsubscribe-YYLLxrGCLz9BDgjK7y7TUQ< at >public.gmane.org