Opened 9 years ago

Closed 7 years ago

#1127 closed task (fixed)

new nViz tcl messages are not indicated for gettext

Reported by: naokiueda Owned by: marisn
Priority: major Milestone: 6.4.1
Component: Tcl/Tk NVIZ Version: 6.4.0 RCs
Keywords: Cc:
CPU: Unspecified Platform: All


We are GRASS Japanese translation team in Osaka city university. In latest version, nViz module can not be translated into Japanese.

We have translated nViz in old version with message file, 'ja.msg', but I couldn't see corresponding message file in latest code here.

Currently we have no way to translate nViz module.

Change History (9)

comment:1 Changed 9 years ago by neteler

I see that in GRASS 6.1 NVIZ was translated to Japanese:

I wonder why the current grasstcl_*.po files do not contain (any more?) NVIZ strings, say, could this be fixed?

comment:2 Changed 8 years ago by naokiueda

Priority: normalmajor

In new NVIZ nodule, text is hard-coded and no way to translating to environment language.

text should not be hard coded.

Since we need to translate GRASS into Japanese, if have no choice but creating a branch version by replacing with translated Japanese text. However, this is not a good way.

I think for other language version has the same problem.

So I would like to increase this priority.


comment:3 Changed 8 years ago by marisn

Platform: MSWindows 7All

I have started to mark messages for translation in NVIZ. Compile recent develbranch (6.5 r44588); cd locale; make pot; (only at first time) cp templates/grassnviz.pot po/grassnviz_ja.po; translate that file; make mo; test in NVIZ. In future replace "cp" step with "make update-po".

Not all strings are extracted for translation, as it takes some time to go over code to find strings. Report any issues at this bug.

comment:4 Changed 8 years ago by neteler

Maris, what are your backport plans for 6.4?

comment:5 Changed 8 years ago by marisn

Work is not yet finished. It will need serious testing to see if I haven't broken anything. In some places it's tricky to extract messages as english texts are used also to keep application state and not only to display it to user. For this reason I had such large delay till I figured out how to hack around BWidget ComboBox? without breaking backwards compatability.

comment:6 Changed 8 years ago by marisn

Owner: changed from grass-dev@… to marisn

Most of NVIZ now should be extracted for translation. Do some translation and play around with NVIZ to see how it works.

There still are some strings untranslable as BWidgets are not (yet) prepeared for string extraction.

If there are any problems or strings not extracted for translation, add comments here.

comment:7 Changed 8 years ago by neteler

The backported message extraction is now available in 6.4.SVN for DE and JA languages:

-> grassnviz_de.po

-> grassnviz_ja.po

While nviz translations may start, these message catalogues may be better added to grasstcl_XX.po?

comment:8 Changed 7 years ago by hamish

does this relate to #1551?

comment:9 in reply to:  8 Changed 7 years ago by marisn

Resolution: fixed
Status: newclosed

Replying to hamish:

does this relate to #1551?

No. #1551 was a missed case while fixing this issue. This issue is solved by 99% and only BWidgets part is missing. As translated messages seem to work in NVIZ, I'm closing it. If somebody is really interested in some left untranslated messages, he should open a new bug report.

Note: See TracTickets for help on using tickets.