[
https://issues.apache.org/jira/browse/SOLR-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703660#comment-13703660
]
Cassandra Targett commented on SOLR-4886:
-----------------------------------------
A couple things to note about customizing the PDF export:
# The default CSS is attached to this page of Atlassian documentation:
https://confluence.atlassian.com/display/CONF35/Editing+the+PDF+Stylesheet.
# Confluence first exports the requested pages to HTML, then converts the HTML
to PDF. The divs you need to modify are found in the HTML, which can only be
grabbed off the server. That's probably not an option here. However, the PDF
does have good coverage of the various divs that are used, it's just you won't
really know if you're changing what you hope you're changing without a lot of
trial & error. (Since I have the same version of Confluence, I could probably
get you a copy of pre-PDF HTML output if you wanted.)
# Good news, though, is that this doesn't look much changed between 3.x and
5.x, so whatever changes you do should survive the rest of the Confluence
upgrade process.
At LucidWorks we stopped using the default PDF export tool in 2011 because of a
few limitations I decided were too much of a pain in my ass (we license a
commercial tool instead):
* Changing the font was difficult. Unless you want Times New Roman, Helvetica
or Courier, you have to upload the font file to the server and reference it's
location in an @font-face call in the CSS. (It does seem that Confluence 5 has
made this uploading fonts business easier:
https://confluence.atlassian.com/display/DOC/Creating+PDF+in+Another+Language
discusses a way to upload fonts.)
* I could never figure out how to get the Table of Contents page to have a
header that said "Table of Contents", or any other text (others who are better
with CSS might know this, but I didn't).
* Bookmarks are created during PDF creation, but they link to the end of the
previous section, not the start of the new section that should be bookmarked.
This might not be a bad thing, depending on if you want to make page breaks at
the start of specific header levels (I did).
There were other reasons for using a commercial tool, but they don't really
impact this issue.
> configure and test PDF export of SOLR CWIKI after existing ref guide content
> is loaded
> --------------------------------------------------------------------------------------
>
> Key: SOLR-4886
> URL: https://issues.apache.org/jira/browse/SOLR-4886
> Project: Solr
> Issue Type: Sub-task
> Components: documentation
> Reporter: Hoss Man
> Assignee: Hoss Man
>
> * add the ASL as a page in the wiki such that it appears early in the
> exported PDF
> * test that exporting the PDF works ok with the large space
> * review the exported PDF for problems
> * confirm/tweak-configs so that PDF exporting can done really easily, ideally
> automatically
> * document/script steps to create PDF on each solr release.
> Lots of tips here:
> https://confluence.atlassian.com/display/DOC/Providing+PDF+Versions+of+your+Technical+Documentation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
