[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Maposmatic-dev] [Maposmatic] Generalising paper sizes, possibly sim

From: David MENTRE
Subject: Re: [Maposmatic-dev] [Maposmatic] Generalising paper sizes, possibly simplifying its configuration
Date: Wed, 4 Apr 2012 12:34:52 +0200

Hello Jeroen,

2012/4/3 Jeroen van Rijn <address@hidden>:
> libpaper seems to agree:
> $ paperconf -c -s -p a4 # show size of a4 in centimetres
> 21 cm 29.7 cm
> $ paperconf -m -s -p a4 # show size of a4 in millimetres
> 210 mm 297 mm
> $ paperconf -s # show size of default paper (a4 in my case) in
> Postscript units (1/72th of an inch)
> 595.276 841.89
> $ paperconf -a # list all paper sizes by name, quite a few
> I imagine it wouldn't be hard to write a python class to encapsulate
> this knowledge. A dict keyed on paper name holding a tuple of
> dimenions, at its base. The configuration could then be simplified to
> listing minimum and maximum dimensions you want ocitysmap to tackle,
> on the basis of design/layout and runtime.
> Indeed, if libpaper is installed on the system, this python class
> might even be built on the fly during a 'make install' pass and defer
> to a supplied version if libpaper is missing.
> Yes/No/Cancel?

I don't know. Currently the top priority is to put current dev into production.

Could you add a task on Savannah with all above information so that we
can take a decision at a latter point?

Best regards,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]