klama: Section 1.17, Section 2.4
rather than:
klama: 4, 8
Either an html->pdf converter that handles this, or something that
converts the cross references in the resulting pdf, would be
fantastic.
-Robin
--
http://singinst.org/ : Our last, best hope for a fantastic future.
Lojban (http://www.lojban.org/): The language in which "this parrot
is dead" is "ti poi spitaki cu morsi", but "this sentence is false"
is "na nei". My personal page: http://www.digitalkingdom.org/rlp/
No, we can't; the whole point here is to automatically generate a
number of different outputs from a single source format, which
happens to be docbook.
> Anyway, have you tried Word?
I don't consider that an acceptable source format for a wide variety
of reasons.
--
You received this message because you are subscribed to the Google Groups "lojban" group.
To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban?hl=en.
I believe so, yes.
> The only thing I can think of that might fix it is to first
> determine what page each of these sections is on, and do a
> find/replace on them in the references. The problem with that is,
> the initial work of creating the section x = pg(s) y database is
> quite likely a lot of effort, even if the actual find/replace can
> be fully automated, and the database would need to be recreated
> anytime there's a change to the page structure (I mostly refer to
> addition or deletion of content, but even font changes apply).
If you know enough about PDF format to do the replace, wouldn't you
also know enough about it to count pages in it and figure out which
page something is on?
On Fri, Nov 18, 2011 at 01:27:15AM -0700, Jonathan Jones wrote:I believe so, yes.
> Obviously this doesn't matter with printouts, but are the
> references linked? That is, in the generated pdf, if you click on
> the "Section 1.17" bit, will it take you to that section?
If you know enough about PDF format to do the replace, wouldn't you
> The only thing I can think of that might fix it is to first
> determine what page each of these sections is on, and do a
> find/replace on them in the references. The problem with that is,
> the initial work of creating the section x = pg(s) y database is
> quite likely a lot of effort, even if the actual find/replace can
> be fully automated, and the database would need to be recreated
> anytime there's a change to the page structure (I mostly refer to
> addition or deletion of content, but even font changes apply).
also know enough about it to count pages in it and figure out which
page something is on?
-Robin
--
http://singinst.org/ : Our last, best hope for a fantastic future.
Lojban (http://www.lojban.org/): The language in which "this parrot
is dead" is "ti poi spitaki cu morsi", but "this sentence is false"
is "na nei". My personal page: http://www.digitalkingdom.org/rlp/
--
You received this message because you are subscribed to the Google Groups "lojban" group.
To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban?hl=en.
If I understand correctly, everything there is all vanilla CSS2/3, and
the company they mention just charges an exorbitant amount of money to
mash ^P for you.
mu'omi'e.djeims.
I was unable to get this to work.
mu'omi'e.djeims.
Loading it in LibreOffice and saving as PDF would get you *page
numbered internal references*? *Really*?
If so, I'm thoroughly impressed.
The full (in progress) html file is at
http://vrici.lojban.org/~rlpowell/media/public/tmp/pdf-test-input.html
, but you can use
http://vrici.lojban.org/~rlpowell/media/public/tmp/pdf-test-input-short.html
as an easier test case.
-Robin
> --
> You received this message because you are subscribed to the Google Groups "lojban" group.
> To post to this group, send email to loj...@googlegroups.com.
> To unsubscribe from this group, send email to lojban+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/lojban?hl=en.
>
--
You don't seem to understand the goal here at all. Any solution
that involves by-hand work to convert the source format to all of
the destination formats is completely out ofthe question. The goal
is a completely automated system.
If you want to help with the former, I think I outlined the problem
decently below; let me know if not and I'll try to explain further.
Where I think *you* could best help, though, is the problem
described at
http://groups.google.com/group/lojban/browse_frm/thread/2bc7fb6f3c8830fc
, which is a TeX problem (specifically, with redering IPA
characters).
-Robin
Just tried and the HTML is indeed to complex. Will you share the
docbook files too? I never tried importing docbook files into
Libreoffice, not sure what comes out.
remod
Even the short one?
> Will you share the docbook files too? I never tried importing
> docbook files into Libreoffice, not sure what comes out.
http://vrici.lojban.org/~rlpowell/media/public/tmp/cll_pdf_test.xml
is a slightly pared down version, but should do fon this test.
I would be very surprised if it did anything useful.
-Robin
I was hoping to be able to load it into libreoffice and do the changes
with a script or by definining the proper style in a template.
Turned out it was not so simple to do it, as you already had guessed.
You want to fix only the indices, right? Not to augment any
crossreference with the page number.
If you have the PDF "almost right", what about generating a .ps file,
write a script to replace the "Section x.y" with the proper number and
then transform the .ps into a .pdf file?
Do you have something that will generate .ps from HTML?
This is all somewhat moot anyways, as the docbook -> latex -> pdf
process is actually going reasonably well; I just figured that maybe
someone out there knew a really good way to do html -> pdf that I
wasn't aware of, so I didn't have to solve a bunch of presentation
problems twice (once in XSLT and CSS, and once in XSLT and LaTex).
Confirmed; the LaTeX route is working well now.
If someone has a beatiful, magical way to make the HTML route work,
I'll take it, but it's not worth sinking real time into anymore.