-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ideas: Print Customizations #9
Comments
Tom, I began a long-term project regarding print customization of DocBook documents. The will be a several bunch of projects, helping authors to get a typography friendly PDF output. This mostly will related to a technical documentation (manuals, books. etc) and, maybe, marketing brochures. The first project, that is already available, fixes the common problem regarding non-Latin characters (i.e. Cyrillic) in PDF output while using Apache FOP as a formatter. It is available here: https://github.com/eduardtibet/foponts I want to add the appropriate recipe as a:
Where I should add this topic? Yes, I'm aware about fo/ directory. But maybe there are some rules that I need to know before making a patch? Thanks! |
Hi Eduard,
Great to hear that! 👍 Wish you great success for your project.
I should have better documented how to contribute. 😉 Ok, anyway. I would suggest to proceed as follows:
Hope I didn't forget anything. Let me know if you need help here or there. Thanks a lot for your contribution! 👍 |
Thomas, please, edit the following topic to extend one:
The point is, that the topic I'm going to write about, covers only Apache FOP. Other formatters are out of the scope of my article. Thanks! |
@eduardtibet That's perfectly fine! 👍 |
Moved from https://sourceforge.net/p/doccookbook/tickets/22/
These are some of the ideas about print customizations. The list is no guarantee that all will be implemented.
Choosing Open Source Fontshttp://svn.apache.org/viewvc/xmlgraphics/fop/trunk/examples/fo/advanced/bleed-and-crop-marks.fo?view=markup&pathrev=800143
Hyphenating URLsThe text was updated successfully, but these errors were encountered: