Custom pdf plugin - static text language issue
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 34
- Joined: Mon Oct 08, 2018 12:16 pm
Custom pdf plugin - static text language issue
Hello,
I am trying to print my content to PDF with my own customized plugin. So I changed in DITAmap root:
<bookmap xml:lang="fi">
After that it seems that the dita-ot is using some other settings to produce the pdf than the ones in my plugin: it is using different images for note/caution/warning than I specified in my own plugin. I also don't want the "Chapter 1" phrase in there.
I attach screenshot example:
Can you help?
I am trying to print my content to PDF with my own customized plugin. So I changed in DITAmap root:
<bookmap xml:lang="fi">
After that it seems that the dita-ot is using some other settings to produce the pdf than the ones in my plugin: it is using different images for note/caution/warning than I specified in my own plugin. I also don't want the "Chapter 1" phrase in there.
I attach screenshot example:
example_en.png
example_fi.png
I don't understand why when in my plugin word "chapter" does not show, it shows after changing the language.Can you help?
You do not have the required permissions to view the files attached to this post.
-
- Posts: 34
- Joined: Mon Oct 08, 2018 12:16 pm
Re: Custom pdf plugin - static text language issue
Also the font of the header is a bit different.. Why do only some settings stay from my own plugin and some from original base pdf?
example_en2.png
example_fi2.png
You do not have the required permissions to view the files attached to this post.
-
- Posts: 9451
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Custom pdf plugin - static text language issue
Hi,
Most DITA OT PDF customization plugins use common stylesheets from the base PDF plugin. It's hard to tell what the problem is without seeing how your plugin is constructed.
For example if for the note caution icon you have modified the path in the "vars/en.xml" you probably need to also create an "fi.xml" next to it and modify the value also there.
Regards,
Radu
Most DITA OT PDF customization plugins use common stylesheets from the base PDF plugin. It's hard to tell what the problem is without seeing how your plugin is constructed.
For example if for the note caution icon you have modified the path in the "vars/en.xml" you probably need to also create an "fi.xml" next to it and modify the value also there.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
-
- Posts: 34
- Joined: Mon Oct 08, 2018 12:16 pm
Re: Custom pdf plugin - static text language issue
The plugin was created by a subcontractor and it has a lot of unnecessary files, parameters and settings in double places (it was created by a plugin generator and later heavily modified) - I would prefer it done from scratch but we did not know how they would build it. The plugin generator automatically creates some customized plugin with altered parameters but also adds a lot content and files.
It is very difficult to modify anything in there.
Do you have any idea how to get rid of the "chapter 1" from the pdf?
It is very difficult to modify anything in there.
Do you have any idea how to get rid of the "chapter 1" from the pdf?
-
- Posts: 9451
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Custom pdf plugin - static text language issue
If you look in this XML configuration file OXYGEN_INSTALL_DIR/frameworks/dita/DITA-OT3.x/plugins/org.dita.pdf2/cfg/common/vars/en.xml it contains a variable like:
The entire en.xml (or in your case the fi.xml) could be overwritten from the plugin customization and the variable contents could be set to empty.
Or instead of publishing a DITA bookmap you would convert it to a regular DITA Map for which by default the publishing engine does not show "Chapter" labels in the PDF output.
Regards,
Radu
Code: Select all
<variable id="Chapter with number">Chapter <param ref-name="number"/></variable>
Or instead of publishing a DITA bookmap you would convert it to a regular DITA Map for which by default the publishing engine does not show "Chapter" labels in the PDF output.
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service