Difference between revisions of "Hugin translation guide"

From PanoTools.org Wiki
Jump to: navigation, search
(Gives more explanations on the steps needed to help with translation)
(Puts the explanations on how to contribute with translating at the top)
Line 2: Line 2:
  
 
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.
 
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.
 +
 +
== Getting Started on translations ==
 +
 +
Each language has a *.po file containing all the translated strings. Those *.po files use the [http://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1] naming convention (like "fr.po" for French, "ja.po" for Japanese, ...). If no translation for your language exist, you'll have to create one using that naming convention or ask the [http://groups.google.com/group/hugin-ptx developers list] for assistance.
 +
 +
In general, you need the latest *.po files (or at least the one for the language you want to modify). You can download the current translation file for you language in the [http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/src/translations/ SVN repository]. If there is no *.po file for your language, you can download the hugin.pot file.
 +
 +
To edit the *.po or *.pot files, use [http://sourceforge.net/projects/poedit/ poedit] (it is a cross-platform PO files editor which runs on Mac OS X, Unix and Windows) or [http://kbabel.kde.org/ kbabel] (it runs on any KDE platform). Note that you don't have to translate everything if you don't have time or knowledge to do it all. Also check below for things that shouldn't be translated (like software names) or for some explanations on specific words.
 +
 +
NB: When using poedit, editing comments directly in the right pane doesn't work, the text isn't saved into the .po file. To edit comments, use the "edit comment" dialogue from the menu.
 +
 +
Submit your edited translation via hugin's [http://sourceforge.net/tracker/?func=add&group_id=77506&atid=550443 patches tracker] on sourceforge.
 +
 +
== Use your new translation file ==
 +
 +
poedit updates your PO file and creates a MO file for your language. You can rename your MO file into hugin.mo and replace the hugin.mo file from your current installation (don't forget to make a backup of the original MO file, just in case).
 +
 +
- If you use Windows, the MO file is under your hugin directory, in <tt>share\locale\XX\LC_MESSAGES\hugin.mo</tt>, where XX is your language.
 +
 +
- If you use Linux, the MO file is under <tt>/usr/local/share/locale/XX/LC_MESSAGES/hugin.mo</tt>
 +
 +
If you want to can also rebuild hugin (doesn't have to be a heavy job when you only changed the .po file, the process only updates that part).
  
 
== Translation guide for specific terms ==
 
== Translation guide for specific terms ==
Line 152: Line 174:
  
 
This will start hugin in dutch. Other languages have different names of course, try looking in <tt>/usr/share/i18n/locales/</tt>.
 
This will start hugin in dutch. Other languages have different names of course, try looking in <tt>/usr/share/i18n/locales/</tt>.
 
== Getting Started on translations ==
 
 
Each language has a *.po file containing all the translated strings. Those *.po files use the [http://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-1] naming convention (like "fr.po" for French, "ja.po" for Japanese, ...). If no translation for your language exist, you'll have to create one using that naming convention or ask the [http://groups.google.com/group/hugin-ptx developers list] for assistance.
 
 
In general, you need the latest *.po files (or at least the one for the language you want to modify). You can download the current translation file for you language in the [http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/trunk/src/translations/ SVN repository]. If there is no *.po file for your language, you can download the hugin.pot file.
 
 
To edit the *.po or *.pot files, use [http://sourceforge.net/projects/poedit/ poedit] (it is a cross-platform PO files editor which runs on Mac OS X, Unix and Windows) or [http://kbabel.kde.org/ kbabel] (it runs on any KDE platform). Note that you don't have to translate everything if you don't have time or knowledge to do it all.
 
 
NB: When using poedit, editing comments directly in the right pane doesn't work, the text isn't saved into the .po file. To edit comments, use the "edit comment" dialogue from the menu.
 
 
Submit your edited translation via hugin's [http://sourceforge.net/tracker/?func=add&group_id=77506&atid=550443 patches tracker] on sourceforge.
 
 
=== Use your new translation file ===
 
 
poedit updates your PO file and creates a MO file for your language. You can rename your MO file into hugin.mo and replace the hugin.mo file from your current installation (don't forget to make a backup of the original MO file, just in case).
 
 
- If you use Windows, the MO file is under your hugin directory, in <tt>share\locale\XX\LC_MESSAGES\hugin.mo</tt>, where XX is your language.
 
 
- If you use Linux, the MO file is under <tt>/usr/local/share/locale/XX/LC_MESSAGES/hugin.mo</tt>
 
 
If you want to can also rebuild hugin (doesn't have to be a heavy job when you only changed the .po file, the process only updates that part).
 
  
 
----
 
----
  
 
[[category:Software:Hugin]]
 
[[category:Software:Hugin]]

Revision as of 12:38, 15 March 2009

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.

Getting Started on translations

Each language has a *.po file containing all the translated strings. Those *.po files use the ISO 639-1 naming convention (like "fr.po" for French, "ja.po" for Japanese, ...). If no translation for your language exist, you'll have to create one using that naming convention or ask the developers list for assistance.

In general, you need the latest *.po files (or at least the one for the language you want to modify). You can download the current translation file for you language in the SVN repository. If there is no *.po file for your language, you can download the hugin.pot file.

To edit the *.po or *.pot files, use poedit (it is a cross-platform PO files editor which runs on Mac OS X, Unix and Windows) or kbabel (it runs on any KDE platform). Note that you don't have to translate everything if you don't have time or knowledge to do it all. Also check below for things that shouldn't be translated (like software names) or for some explanations on specific words.

NB: When using poedit, editing comments directly in the right pane doesn't work, the text isn't saved into the .po file. To edit comments, use the "edit comment" dialogue from the menu.

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

Use your new translation file

poedit updates your PO file and creates a MO file for your language. You can rename your MO file into hugin.mo and replace the hugin.mo file from your current installation (don't forget to make a backup of the original MO file, just in case).

- If you use Windows, the MO file is under your hugin directory, in share\locale\XX\LC_MESSAGES\hugin.mo, where XX is your language.

- If you use Linux, the MO file is under /usr/local/share/locale/XX/LC_MESSAGES/hugin.mo

If you want to can also rebuild hugin (doesn't have to be a heavy job when you only changed the .po file, the process only updates that part).

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=parameters other than standard (+context???)
NL=aangepaste parameters
bundle
Meaning=Seems to be used only on Mac OSX
NL=bundle (bundel?)
bundled version
Meaning=? version distributed with hugin MacOSX bundle?
NL=ingebouwde versie (gebundelde versie?)
image
Meaning= photo, scan, ....
ET=pilt
NL=afbeelding
Stitcher (the tab)
Meaning= Where the actual combining of the images is done
ET=Ühendaja
NL=Samenvoegen (alt: Combineren, Naaien?)
grayscale
Meaning=monochrome colourspace. Typically grayscale images can have many shades of gray as well as black and white.
ET=halltoonid
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, vervorming, projectie?
control points
Meaning=corresponding areas in two images (or the same image for horizontal and vertical control points)
ET=juhtpunktid
NL=ijkpunten (was controle punten), IJkpunten bij hoofdletters
Druid
Meaning=wizard for ease of use, alternative names: Assistant, workflow guide, etc.
NL=Druide (kan beter?)
Cropped (images)
Meaning=image cut smaller than the original size
Discussion=Should this be translated? Like Blend, this is jargon, may be clearer when untranslated?
ET=kärbitud (pildid)
NL=uitgesneden (afbeeldingen)
Exposure blending
Meaning=Taking a bracketed photo stack and picking the best bits to create a new image.
NL=Blend van belichtingen?
Photometric Optimisation
Meaning=Optimisation of non-mapping image parameters?
ET=fotomeetriline optimeerimine
NL=fotometrische optimalisatie
Photometric Alignment
Meaning=Determining relative exposure and vignetting
ET=fotomeetriline joondamine
NL=fotometrische uitlijning (beter?: fotometrische afstemming)
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
ET=vaateväli
NL=beeldhoek
flatfield
Meaning=An astronomical technique, using a photo taken with the lens covered or of an even white surface to calibrate normal photos
NL=flatfield (astrofoto jargon, ook in NL gebruikt)
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)?
Estimate (position, FoV, etc.)
Meaning=? in my book, estimate means an educated guess. I get the impression that a more exact term is intended for hugin. Where can this term be replaced with "calculate" or "determine"?
ET=määratlema
NL=bepalen (eng:determine), bereken (eng:calculate) alternative suggestion: Schatten (eng:estimate)
Camera response (C. r. curve)
Meaning=it corresponds with photo-electrical transfer function, and I am not sure can I translate it to "opto-electic curve of camera" in my language, because stright tranlation of "camera response" statement sounds trivial and not clear.
PL=krzywa optoelektryczna aparatu?


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]

List of source string problems

  • approximation of values beetwen source pixels
between
  • calculate highest sensible width. (uses every image pixel)
I can translate this literally, but is this even helpful in English? (this is a tooltip for the size calc button in the Stitcher tab)

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/.