Quote:
Originally Posted by frabjous
Something perhaps not quite (2), but rather a script that took .tex source and simply made the adjustments for digital readers by adding a line for the geometry package with the appropriate settings (determined at run-time if you like, perhaps even with a GUI), perhaps adding \sloppy if the page size chosen was small enough, and then processed it by calling pdflatex already on the system, wouldn't actually be that difficult. The trickiest thing would be removing any calls to packages (or other formatting) incompatible with geometry.
|
Yes. The main difference here is that it sounds like it would attempt to "domesticate" wild TeX source files. Whereas my conception of #2 would work with files specifically intended to be used by it (and/or other similar programs).
Simplest way is to have there be a simple set of variables defined as basically the first thing in the source, and have everything use those (instead of hard-coded values) thereafter. #2 could alter the values of those variables, and would basically expect the output to change accordingly
because the TeX source is (supposed to be) setup in such a way.
Quote:
Originally Posted by frabjous
With the way PDF renderers on our devices work (or at least on the Sony--I assume others), choosing a page size smaller than the native dimensions of the reader is basically the same thing as choosing a larger font size.
|
True. Although if there is any raster content (that is large enough that it should be downsized/resampled to whatever smaller page size) it would benefit from the correct page size being used.
- Ahi