On 22 Dez., 04:40, Tom Sharpless tksharpl...@gmail.com wrote:
I keep suggesting that our primary stitching targets should include
the cube, since so many of our panos end up that way. It would be only
a little extra work to make an engine for that do the TOAST and Pierce
Quincuncial
I just downloaded the current es_la.po
(http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/raw-file/6a5ac6a405c7/src/translations/es_la.po)
and opened it in Poedit:
- 47 untranslated strings
- 161 fuzzy strings
This version is from Dec. 6 so are you sure you uploaded your
translations already
On 22 Dez., 04:16, Tom Sharpless tksharpl...@gmail.com wrote:
Kay is right. There is no way software, just looking at an image, can
tell which way is up. That requires outside information, either from
a person, who can judge such things, or even better, from a sensor in
the camera.
Maybe
I re-added a straightening function the the calibrate_lens tool. Call it
with a -w 1 flag.
It assumes that all lines that are taller than they are wide are vertical.
Then it rotates these about the image centre such that the difference in
their max/min x-coordinates is minimised, and returns the
On 22 Dez., 10:55, Tim Nugent timnug...@gmail.com wrote:
I re-added a straightening function the the calibrate_lens tool. Call it
with a -w 1 flag.
It assumes that all lines that are taller than they are wide are vertical.
Then it rotates these about the image centre such that the
i didnt upload the file yuval did it..
On Wed, Dec 22, 2010 at 4:59 AM, Carl von Einem c...@einem.net wrote:
I just downloaded the current es_la.po (
http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/raw-file/6a5ac6a405c7/src/translations/es_la.po)
and opened it in Poedit:
- 47 untranslated
The current release cycle has highlighted some weaknesses in how we deal with
translations. Below are my findings. Comments, verifications, sanity checks
welcome.
Most translations arrive as incremental additions/improvements/corrections to
existing po files.
The right way to update
