Re: Current translation status in gtkpod 2

On 31/12/10 10:49, Daniele Forsi wrote:
> There are still two issues concerning translations.
>
> The plugin list isn't translated. It seems that intltools use the file
> extension to get file type and defaults to C sources with unknown
> extensions like .plugin and you can't force the type in POTFILES.in
> eg. with
> [type:ini] path/to/file.plugin
> because the types known internally are stripped. Every solution seems
> an hack to me.
> Also list heading and other texts aren't translated but this seems due
> to anjuta.
>
>    
Anjuta plugins seem to do it using .in files. The gdb plugin is an example:

gdb.plugin.in
[Anjuta Plugin]
_Name=Gdb
_Description=GNU Debugger Plugin

gdb.plugin
[Anjuta Plugin]
Name=Gdb
Name[ar]=Gdb
Name[be@latin]=Gdb
Name[bg]=GDB
Name[ca]=Gdb
Name[ca@valencia]=Gdb
Name[cs]=Gdb
Name[da]=Gdb
...
...

Makefile.am
plugin_in_files = anjuta-gdb.plugin.in
%.plugin: %.plugin.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*po) 
; $(INTLTOOL_MERGE) $(top_srcdir)/po $< $@ -d -u -c 
$(top_builddir)/po/.intltool-merge-cache

Being more of a translation expert than me, do you think we should 
change all the .plugin files to be generated accordingly?

phantomjinx

------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl