Translators requested for Hugin 2012.0 release

[Harry van der Wolf]

All,

Yesterday I sent out the mail (1,2) for the beta1 release of the hugin 2012.0 version.
In this version quite a few new strings have been added that need to be translated.
I did forget to ask translators to have a look at the translation files to make them up to date again.
So to make it as clear as possible: Translators please update the translation files for your language.

The beta 1 release mail can be found via:
1: https://groups.google.com/forum/?fromgroups#!topic/hugin-ptx/VxuiVN1uRgk
2: http://old.nabble.com/Hugin-2012.0beta1-released-td34198515.html


best,
Harry

[Jorge González]

Hello Harry,

How long do we have until you release the official version?

Thanks and best regards.

> --
> You received this message because you are subscribed to the Google Groups
> "Hugin and other free panoramic software" group.
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> To post to this group, send email to hugi...@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx



--
Jorge González González <alo...@gmail.com>
Weblog: http://aloriel.turismogoogle.net
Weblog: http://turismogoogle.net
Fotolog: http://www.flickr.com/photos/aloriel

[Harry van der Wolf]

Hi Jorge,

2012/7/24 Jorge González <alo...@gmail.com>

Hello Harry,

How long do we have until you release the official version?

Thanks and best regards.

At least some weeks. We are now in the middle of the holiday season (at least on the northern hemisphere). Test binary builds need to be built and tested before we can proceed further.

Harry

[Luís Henrique Camargo Quiroz]

--
You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

    Hi!

    Its already for a while that I stopped with the Portuguese translations, it´s a pitty...
    Now I´m applying for a new job - tomorrow will be start of a selection process! - and I hope that very soon I could translate the new strings. With a fews weeks deadline it seens OK for me to do :)

    regards,

    Luís Henrique

Luís Henrique Camargo Quiroz - http://luishcq.tripod.com
my chant page - http://www.christusrex.org/www2/cantgreg

[T. Modes]

Hi all,

there is a first bug report about typos in the strings which should be
translated.
https://bugs.launchpad.net/hugin/+bug/1028387
Are there more typos? If you found one please report back. We will
collect some typos and fix them in one rush to keep the annoyance for
the translators as low as possible.
Maybe also a native speaker could help us with some better words/
sentences for the proposals in the bug report.

Thanks
Thomas

[T. Modes]

Hi translators,

just to remember.

==The current status of the translations==

Only 4 languages are fully translated:
cs_CZ.po
1333 translated messages.
da.po
1333 translated messages.
it.po
1333 translated messages.
nl.po
1333 translated messages.

All other language contains still untranslated or fuzzy strings:
bg.po
576 translated messages, 429 fuzzy translations, 328 untranslated
messages.
ca_ES.po
344 translated messages, 516 fuzzy translations, 473 untranslated
messages.
de.po
1276 translated messages, 38 fuzzy translations, 19 untranslated
messages.
en_GB.po
52 translated messages, 4 fuzzy translations, 1277 untranslated
messages.
es.po
1136 translated messages, 97 fuzzy translations, 100 untranslated
messages.
fi.po
915 translated messages, 195 fuzzy translations, 223 untranslated
messages.
fr.po
1275 translated messages, 37 fuzzy translations, 21 untranslated
messages.
hu.po
1276 translated messages, 38 fuzzy translations, 19 untranslated
messages.
ja.po
1269 translated messages, 38 fuzzy translations, 26 untranslated
messages.
ko.po
577 translated messages, 413 fuzzy translations, 343 untranslated
messages.
pl.po
941 translated messages, 222 fuzzy translations, 170 untranslated
messages.
pt_BR.po
1276 translated messages, 37 fuzzy translations, 20 untranslated
messages.
ro.po
747 translated messages, 316 fuzzy translations, 270 untranslated
messages.
ru.po
1074 translated messages, 137 fuzzy translations, 122 untranslated
messages.
sk.po
1144 translated messages, 108 fuzzy translations, 81 untranslated
messages.
sl.po
547 translated messages, 401 fuzzy translations, 385 untranslated
messages.
sv.po
1230 translated messages, 64 fuzzy translations, 39 untranslated
messages.
uk.po
427 translated messages, 506 fuzzy translations, 400 untranslated
messages.
zh_CN.po
1276 translated messages, 38 fuzzy translations, 19 untranslated
messages.
zh_TW.po
1081 translated messages, 206 fuzzy translations, 46 untranslated
messages.

So in same language there are only some ten strings missing. Maybe you
could contribute for the missing languages.

Thanks
Thomas

[Jorge González]

Hello,

On Wed, Aug 1, 2012 at 6:44 PM, T. Modes <Thomas...@gmx.de> wrote:
> Hi translators,
>
> just to remember.
>
> ==The current status of the translations==
>

> es.po
> 1136 translated messages, 97 fuzzy translations, 100 untranslated
> messages.

This is actually interesting; I might have downloaded the wrong
version and that's the revision I sent; could you specify where to get
the pos, please?

Thanks.

[T. Modes]

Hi Jorge,

> This is actually interesting; I might have downloaded the wrong
> version and that's the revision I sent; could you specify where to get
> the pos, please?
>

You could use the version from the source code beta release:
http://sourceforge.net/projects/hugin/files/hugin/hugin-2012.0/hugin-2012.0.0_beta1.tar.bz2/download

or you can download from the repository:
http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/file/b21c646215be/src/translations/es.po
(use the link "raw" at the top of the page)

Thomas

[Carl von Einem]

Hi Thomas,

T. Modes schrieb am 01.08.12 18:44:
> Hi translators,

>
> All other language contains still untranslated or fuzzy strings:

> de.po
> 1276 translated messages, 38 fuzzy translations, 19 untranslated
> messages.

Harry's build seemed to be fully functional at first glance so thanks
for the heads-up! I'll grab the DE version...

Carl

[Carl von Einem]

Hi,

I just see a string which contains "...If you experience malfunction,
please go to the menu File -> Preference..."

Since menus differ between platforms, can we have a more neutral
description of the Preferences' whereabouts?

On Mac the Prefs are in menu <application name> -> Preferences...

So maybe something like "...please select Preferences from the menu and..."

Cheers,
Carl

T. Modes schrieb am 01.08.12 19:00:

[Carl von Einem]

Hi all,

sorry, I have a bunch of questions and observations regarding
translation of the current beta:

In line 4149 (according to Poedit) there's a string "Mount:", does that
relate to the mount between lens and camera (e.g. something about the
lensfun database)? "Bajonett:" in German?
I couldn't find the original string in the latest 2012.0.0 beta 1.
Ah, here it is: in "camera and lens" tab -> "Save lens" button -> "Save
camera parameters to lensfun database" (so I was right about that)

In the lensfun "load lens from database" dialog I see a value "subject
distance". Is this in m, cm, mm or ft?

And trying to save a test "camera" via "Save camera to database" I get
an error (translated by me as follows)
"directory '/Users/carl/.local/share/lensfun' could not be created.
(error 2: no such file or directory)"
Mac OS X (10.6.8 here at the moment) has a /usr/local/share/ directory,
so this seems to be a wrong path on Mac, right?

Cheers,
Carl

[Bruno Postle]

On 2 Aug 2012 00:13, "Carl von Einem" <ca...@einem.net> wrote:
>
> And trying to save a test "camera" via "Save camera to database" I get an error (translated by me as follows)
>  "directory '/Users/carl/.local/share/lensfun' could not be created.
>   (error 2: no such file or directory)"
> Mac OS X (10.6.8 here at the moment) has a /usr/local/share/ directory, so this seems to be a wrong path on Mac, right?

/usr/local/share or /usr/share would be where the database installed with lensfun would go. Your 'personal' database would be in this .local/share folder.

Hugin ought to create the folder if it doesn't already exist.

--
Bruno

[Carl von Einem]

Bruno Postle schrieb am 02.08.12 14:14:

> On 2 Aug 2012 00:13, "Carl von Einem" <ca...@einem.net

Thanks, Bruno, than that seems to be a bug... I'll look into it this
evening and file a bug report with some more details.

Carl

[T. Modes]

Hi Carl,

> In line 4149 (according to Poedit) there's a string "Mount:", does that
> relate to the mount between lens and camera (e.g. something about the
> lensfun database)? "Bajonett:" in German?
> I couldn't find the original string in the latest 2012.0.0 beta 1.
> Ah, here it is: in "camera and lens" tab -> "Save lens" button -> "Save
> camera parameters to lensfun database" (so I was right about that)

That's correct. In the lensfun library "mount" is the main tag. So the
same lens can be used on different cameras. So I used the word also in
Hugin for consistency.

> In the lensfun "load lens from database" dialog I see a value "subject
> distance". Is this in m, cm, mm or ft?

It's in m. I added the unit to the dialogs. Thanks for spotting.

> And trying to save a test "camera" via "Save camera to database" I get
> an error (translated by me as follows)
>   "directory '/Users/carl/.local/share/lensfun' could not be created.
>    (error 2: no such file or directory)"
> Mac OS X (10.6.8 here at the moment) has a /usr/local/share/ directory,
> so this seems to be a wrong path on Mac, right?

Bruno answered already on part. The private part of the lensfun lib
needs to be in a directory which is writable for the user. So /usr/
local/share can't be used. So the private part is saved in the home
directory of the user.
But it seems that the directory is not correctly created if some of
the parent directories does not exists (in your case I assume also /
users/carl/.local and all subdirectories are missing). I committed
already a patch, which - I hope - will correctly create this directory
(changeset 1f1600006c50).

> I just see a string which contains "...If you experience malfunction,
> please go to the menu File -> Preference..."

> Since menus differ between platforms, can we have a more neutral
> description of the Preferences' whereabouts?

> On Mac the Prefs are in menu <application name> -> Preferences...

> So maybe something like "...please select Preferences from the menu and..."

I can change it. There are already some more typos and errors on my
list (see one of my last mails in this thread and bug report
https://bugs.launchpad.net/hugin/+bug/1028387 ).
But I want to collect some more (hopefully not too much) and fix all
with one go, so the translators will not disturbed to much. If you
found more of such strings, please report back. In some days I will
push then all fixed strings.

Thomas

[Gareth Jones]

> en_GB.po
> 52 translated messages, 4 fuzzy translations, 1277 untranslated
> messages.

I'll get to work on this over the next couple of days. Not that en_GB
is ever a particularly major job... I expect I'll report a few typos
or inconsistencies too as usual.

Gareth

[Harry van der Wolf]

2012/8/2 Carl von Einem <ca...@einem.net>

We might have an issue here which I completely overlooked.

/usr/local is a linux like folder structure normally not on Mac OS X. If you build programs that are ported from linux, the latest step is always the "sudo make install" and the install defaults to /usr/local. As I have done this many times to check & build software,  I have a complete /usr/local folder structure on my Apple created under the sudo command.

When hugin tries to create the /usr/local/<etcetera> folder structure it does need sudo rights. Normally you never execute Hugin with sudo rights of course and that's where I think the error comes from.
I can rework the official installer to make sure this folder structure is created but that will not work for the current beta1 which is not an installer. Of course I can make an installer based on the beta1 and that one should do it as the installer uses "Administrator" rights, like it is called on OSX.
I'll try to do that in the coming two days. I'm not much at home these days.

Harry

[Carl von Einem]

Hi Harry,

Harry van der Wolf schrieb am 03.08.12 10:25:
>
> 2012/8/2 Carl von Einem <ca...@einem.net <mailto:ca...@einem.net>>

>
> Bruno Postle schrieb am 02.08.12 14:14:
>
> On 2 Aug 2012 00:13, "Carl von Einem" <ca...@einem.net
> <mailto:ca...@einem.net>

> <mailto:ca...@einem.net <mailto:ca...@einem.net>>> wrote:
> >
> > And trying to save a test "camera" via "Save camera to
> database" I
> get an error (translated by me as follows)

> > "directory '/Users/carl/.local/share/__lensfun' could not be

> created.
> > (error 2: no such file or directory)"
> > Mac OS X (10.6.8 here at the moment) has a /usr/local/share/
> directory, so this seems to be a wrong path on Mac, right?
>
> /usr/local/share or /usr/share would be where the database installed
> with lensfun would go. Your 'personal' database would be in this
> .local/share folder.
>
> Hugin ought to create the folder if it doesn't already exist.
>
> Thanks, Bruno, than that seems to be a bug... I'll look into it this
> evening and file a bug report with some more details.
>

> We might have an issue here which I completely overlooked.
>
> /usr/local is a linux like folder structure normally not on Mac OS X. If
> you build programs that are ported from linux, the latest step is always
> the "sudo make install" and the install defaults to /usr/local. As I
> have done this many times to check & build software, I have a complete
> /usr/local folder structure on my Apple created under the sudo command.
>
> When hugin tries to create the /usr/local/<etcetera> folder structure it
> does need sudo rights. Normally you never execute Hugin with sudo rights
> of course and that's where I think the error comes from.
> I can rework the official installer to make sure this folder structure
> is created but that will not work for the current beta1 which is not an
> installer. Of course I can make an installer based on the beta1 and that
> one should do it as the installer uses "Administrator" rights, like it
> is called on OSX.
> I'll try to do that in the coming two days. I'm not much at home these days.

Not sure if this is part of the problem: I'm one of those rare Mac users
who sport the habit to log in as a standard user, i.e. without admin
rights.

Btw do you know about the Panotools meeting in Den Haag in September?
Are you in the area?

Carl

[Bruno Postle]

On 3 Aug 2012 09:25, "Harry van der Wolf" <hvd...@gmail.com> wrote:

> /usr/local is a linux like folder structure normally not on Mac OS X. If you build programs that are ported from linux, the latest step is always the "sudo make install" and the install defaults to /usr/local.

Not a problem here, this folder structure is in each users home directory, I.e.

  $(HOME)/.local/share/

(sent from Olympic handball arena, 15 mins to go!)

--
Bruno

[Harry van der Wolf]

2012/8/3 Bruno Postle <bruno...@googlemail.com>

The $(HOME)/.local/share is not a problem, the /usr/local/share might be a problem.

Harry
 

[Harry van der Wolf]

Hi Carl,

2012/8/3 Carl von Einem <ca...@einem.net>

Hi Harry,

Btw do you know about the Panotools meeting in Den Haag in September? Are you in the area?

Carl

Yes, I know about it but I will not attend the meeting. The meeting is mostly about 360 immerse panoramas: That's not my cup of tea. I'm more into the high-res "wide screen" panoramas like you find on Max Lyons pages (although I do like your "ceremonial room of Ratibor castle"). In these kind of panormas I do like the 360 degrees panos, not the outside ones of big crowds and so on.

and w.r.t. "in the area". I live in Zwolle and that's about a 1 hours 45  minutes drive to Den Haag.

best,
Harry

[T. Modes]

Hi Harry,

> The $(HOME)/.local/share is not a problem, the /usr/local/share might be a
> problem.

Only $(HOME)/.local/share is used for storing the private lensfun
lib. /usr/local/share is not used.
You can check the paths in the about dialog. There should be

Path to public lensfun database: a path readable by the user, not
writable, on MacOS I assume it should show the path to the lensfun
files inside your bundle.
Path to user lensfun database: a path, user readable and writable,
from the thread $(HOME)/.local/share/lensfun on MacOS

Thomas

[RizThon]

I tried updating the fr.po file.

I'm wondering how to translate "Hugin&stitch&project"
("Hugin&assemblage&projet" ?). I'm not sure whether that string is
even displayed to the user.

I'm not sure how to translate "HDR". Currently, sometimes "HDR" is
directly used, sometimes it's the translation of "High Dynamic Range",
sometimes it's both "High Dynamic Range (HDR)". FWIW, the french
wikipedia article uses the acronym HDR.

Also the word "stack" is usually translated as "ensemble" instead of
"pile", which is closer to "set" than "stack".

[Frederic Da Vitoria]

Suggestions:

Hugin stitch project: Projet d'assemblage Hugin.

I think sticking to HDR is OK, at least until someone finds a translation.

I am not sure, but I believe that stack/pile is closer to the true meaning as IIUC the photos in a stack have to be almost identical. I would maybe even use "superposition".

2012/8/4 RizThon <riz...@gmail.com>

--
Frederic Da Vitoria
(davitof)

Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org

[Thomas Pryds]

Den 04/08/2012 05.10 skrev "RizThon" <riz...@gmail.com>:
> I'm not sure how to translate "HDR". Currently, sometimes "HDR" is
> directly used, sometimes it's the translation of "High Dynamic Range",
> sometimes it's both "High Dynamic Range (HDR)". FWIW, the french
> wikipedia article uses the acronym HDR.

In the Danish translation I sticked to using "HDR" in lack of a good translation. This means that, to avoid confusion, I also kept the English term when it's spelled out as "High Dynamic Range". I decided to only change it when I have both a good Danish translation AND its Danish acronym. Which may not happen anytime in the near future, as the English term (spelled out or as acronym) seems to be used in Danish on e.g. wikipedia and elsewhere.

Thomas

[T. Modes]

Thanks for the translations.

> I'm wondering how to translate "Hugin&stitch&project"
> ("Hugin&assemblage&projet" ?). I'm not sure whether that string is
> even displayed to the user.

I assume you refer to Hugin_stitch_project (with underscores between
the words). In this case this is a program name and does not need to
translated.

Thomas

[T. Modes]

On 4 Aug., 05:10, RizThon <rizt...@gmail.com> wrote:
> I tried updating the fr.po file.
>

All fine (from syntax, did not check the French ;-). Committed the
translation to repository. Thanks.

Thomas

[Gareth Jones]

> I'll get to work on this over the next couple of days.

Okay, en_GB translations are at
https://bugs.launchpad.net/hugin/+bug/1032993, and my suggested typos
etc. are at https://bugs.launchpad.net/hugin/+bug/1032991.

Gareth

[T. Modes]

> I can change it. There are already some more typos and errors on my
> list (see one of my last mails in this thread and bug report https://bugs.launchpad.net/hugin/+bug/1028387).
> But I want to collect some more (hopefully not too much) and fix all
> with one go, so the translators will not disturbed to much. If you
> found more of such strings, please report back. In some days I will
> push then all fixed strings.

There are now some more typos spotted (see bug report
https://bugs.launchpad.net/hugin/+bug/1032991 ).
Most of them are already in previous versions.

Most of them can fixed without the need for another round of
translations.
But there 2 strings, which will generate new strings for your
translators.
The first one is: "Removes all control points, which are in one mask" -
> "Removes all control points that are in masks" (tooltip text in
menu).
The second one is the warning: "...If you experience malfunction,
please go to the menu File -> Preference..." -> "...please select
Preferences from the menu and..." (at the first start of the new
version)

So my questions is: do we add these 2 strings for 2012.0 and you
translate them too. Or do we postpone these 2 strings to the next
release.

Thomas

[Harry van der Wolf]

2012/8/5 T. Modes <Thomas...@gmx.de>

There are now some more typos spotted (see bug report
https://bugs.launchpad.net/hugin/+bug/1032991 ).
Most of them are already in previous versions.

Most of them can fixed without the need for another round of
translations.
But there 2 strings, which will generate new strings for your
translators.
The first one is: "Removes all control points, which are in one mask" -
> "Removes all control points that are in masks" (tooltip text in
menu).
The second one is the warning: "...If you experience malfunction,
please go to the menu File -> Preference..." -> "...please select
Preferences from the menu and..." (at the first start of the new
version)

So my questions is: do we add these 2 strings for 2012.0 and you
translate them too. Or do we postpone these 2 strings to the next
release.

Thomas

As we are currently in the translation phase anyway and as we also have a few incorrect strings, my preference is to include both the 2 new strings and correct the faulty ones.
The translators who already did their work only need to do a few more modifications: That's not a big issue (and nothing compared to what you have done so far for hugin).
For the translators who are currently way behind with their translation it doesn't make a difference whether they have to translate 110 strings or 112 strings.

We can correct it and release a beta2 afterwards.
I hope to be able to dive into the current reported issues with the osx build which seems to do some things twice.

Harry

[T. Modes]

Okay, there were no objections. So I committed the fixes.

Translators, please use from now on the files from this changeset. You
can download from
http://hugin.hg.sourceforge.net/hgweb/hugin/hugin/file/f0987326279b/src/translations
(select your language, click on it; on the next page select raw on the
top to download the file)
Otherwise it becomes difficult to merge with the modified files in the
repository.

If you started the work already, so please note it that you used the
"old" templates/version.

Thomas

[Gareth Jones]

> Okay, there were no objections. So I committed the fixes.

I'm afraid I missed a few minor ones:
https://bugs.launchpad.net/hugin/+bug/1034122.

I've also tweaked en_GB with a few I missed:
https://bugs.launchpad.net/hugin/+bug/1034120.

Gareth

[zarl]

I'm just working on the last few strings (using the new changeset) and
stumbled over "Removes all control points, which are in masks". Do we
need a comma here, and (technically) I hope this doesn't remove points
from include masks... (does it?)

[T. Modes]

Hi Carl,

On 7 Aug., 22:36, zarl <c...@einem.net> wrote:
> I'm just working on the last few strings (using the new changeset) and
> stumbled over "Removes all control points, which are in masks". Do we
> need a comma here,

Don't know exactly. Maybe a native speaker can help.

> and (technically) I hope this doesn't remove points
> from include masks... (does it?)

It does.
If you use only the part from one image, it does not need to be
aligned with part of other images, which does not show up in the final
pano.
Also include mask are used to fix moving object, parallax errors or
the like. In this case you don't need control points in this areas.
Further, it is an optional command, it not called automatically.
Or have you an other use case, I did not consider?

Thomas

[arclance]

But if there are no control points in the include mask would that not
make that area more likely to produce stitching and alignment errors
since you are forcing that area to be used but are removing the points
that are used to calculate how to warp and blend that area of the image
with other images?

If you use both include and exclude masks on the same image to force
only the included area to be used you may not want control points in the
exclude masks but you do need them in the include mask.

You could do all your control points manually but if the image with
masks overlaps with a lot of other images that could take a long time.

[Gareth Jones]

>> I'm just working on the last few strings (using the new changeset) and
>> stumbled over "Removes all control points, which are in masks". Do we
>> need a comma here,
>
> Don't know exactly. Maybe a native speaker can help.

Ah, I thought I suggested that in my first round of typos. Yes, the
comma should go away. I'm torn whether it should be "which" or "that"
though, but leaning toward "that".

Gareth

[Carl von Einem]

What about "Removes all control points inside/from masked areas."?

Carl

Gareth Jones schrieb am 08.08.12 20:51: