Hugin translation guide

Introduction

This page intends to provide guidance to translators of the Hugin project. Some terminology is very specific or used in a specific way in hugin, making it hard to find a close translation that fits the context of hugin in another language than English.

Translation guide for specific terms

Note to translators, please add your language variant to the term on a new line in the same format as NL=
Also add your own difficult terms that are not mentioned here.

Note to developers, please check and enhance the meanings of these terms if they are unclear or incorrect.

Custom parameters

Meaning=paramters other than standard (+context???)

NL=aangepaste paramters

bundle

Meaning=? software package, install kit? Could this be a MacOSX-ism? Can this be made version specific?

NL=?

bundled version

Meaning=? version distributed with hugin package?

NL=ingebouwde versie

image

Meaning= photo, scan, ....

NL=afbeelding

grayscale

Meaning=monochrome colourspace. Typically grayscale images can have many shades of gray as well as black and white.

NL=grijsschaal (kan beter!)

pyramid image

Meaning=This is the practice of creating a stack of successively smaller versions of an image, useful for many image manipulation tasks.

NL=piramidale afbeelding

mapping

Meaning=render to a different projection?

NL=translatie, afbeelding?

control points

Meaning=corresponding areas in two images (or the same image for horizontal and vertical control points)

NL=ijkpunten (was controle punten)

Druid

Meaning=wizard for ease of use

NL=Druide (kan beter?)

Cropped (images)

Meaning=image cut smaller than the original size

NL=gesneden afbeeldingen (zou moeten worden: uitgesneden)

Exposure blending

Meaning=Taking a bracketed photo stack and picking the best bits to create a new image.

NL=belichtings vermenging? (of moeten we blend invoeren in de nederlandse taal?)

Photometric Optimisation

Meaning=Optimisation of non-mapping image parameters?

NL=fotometrische optimalisatie

Low Dynamic Range (LDR)

Meaning=Luminance values are within a small numeric range (typically 8-bit or 16bit integer)

NL=Laag Dynamisch Bereik (LDR)

High Dynamic Range (HDR)

Meaning=Luminance values are within a large numeric range (typically floating point)

NL=Hoog Dynamisch Bereik (HDR)

Anchor

Meaning=Reference

NL=referentie (was anker)

Num. Transf.

Meaning=Numerical Transform?

NL=Num. Transf.

Field of View

Meaning=Horizontal Angle of view

NL=beeldhoek

flatfield

Meaning=?

NL=platbeeld (?)

flatfile

Meaning=?

NL=?

Aligning versus Finding control points

Problem= they appear to be similar or the same, can they be interchanged?

Vertical or Horizontal guide

Meaning=Horizontal or Vertical "control points"

NL=h/v hulp (suggestie: ijklijnen)?

Do not translate:

• Nona (program name)
• Enblend (program name)
• Autopano (program name)
• Autopano-SIFT (program name)
• PTStitcher (program name)
• Deflate (zip method)
• JPEG (file type)
• EXR (HDR file type)

Technical translation issues

Some strings don't appear to be translated, they are apparently generated by the GUI toolkit or the operating system. Most likely they will be in the same language as hugin, because very few people, other than translators, start a program with a specific language other than that of the environment.

If you find a source term that isn't correct, spelling or meaning, probably best to bring it up with Pablo d'Angelo or on the hugin mailinglist: [1]

Tips and Tricks

Running hugin in a specific language

If you want to run hugin in another language than the default, use the following command (Linux with UTF8):

$ LANG=nl_NL.utf8 hugin

This will start hugin in dutch. Other languages have different names of course, try looking in /usr/share/i18n/locales/.

Getting Started on translations

In general, you need the latest *.po files (or at least the one for the language you want to modify), these are either in the SVN repository or here.

To edit the *.po files, use poedit, a cross-platform PO files editor which runs on Mac OS X, Unix and Windows. PO files use the ISO 639-1 naming convention. Use that list to name new language versions or ask the developers list for assistance.

Submit your edited translation via hugin's patches tracker on sourceforge.

Here are some basic instructions for different platforms to get started:

Linux

First of all, you need to get the sources, best to get the latest SVN version. See [link to getting hugin from svn]

The translation source is in hugin/src/translations and they are files with extension .po. These files can be opened and edited using poedit. If poedit is not installed, try installing poedit using your favourite/available package manager or get poedit from sourceforge.

After making changes, the new translation must be activated. Either you can copy the *.mo file that poedit created when you saved the file to /usr/local/share/locale/nl/LC_MESSAGES/hugin.mo (substitute your language abbreviation for nl) or hugin source must be rebuilt and installed to see the effect. Rebuilding hugin doesn't have to be a heavy job when you only changed the .po file, the process only updates that part.

See above on how to start hugin in a specific language.

---