On Sun, May 10, 2009 at 2:20 PM, Steve Borho <[email protected]> wrote:
> 2009/5/10 Yuki KODAMA <[email protected]>:
>> Thanks for comment, steve.
>> Yes, changing translation domain is good thought.
>>
>> Well, will you start to resolve this in a few days?
>> I suppose you work on thg-shellext branch now.
>> So if that's ok, I want to try this on my own branch in bitbucket.
>> (at this time, I don't know I can make out it perfectly ...)
>
> I have indeed begun hacking on a personal branch.  If anyone is
> interested in the carnage, you can find it here:
>
> https://[email protected]/sborho/thg-shellext/
>
> This will eventually get merged back into crew, once it's stable and I
> can build installers on it.  I've done a massive re-org of the
> repository:
>
> 1) remove the Python shell extensions, including tortoisehg.py
> 2) remove the tortoise/ package entirely
> 3) introduced a new thgutils/ package for menuthg, cachethg, and
> utility files previously in hggtk
> 4) C++ extensions and accompanying .py files are now under win32/
> 5) remove old installer directory
> 6) moved icons/tortoise/* into icons/, removed all obsolete files
> 7) renamed hggtk/vis to hggtk/logview
> 8) cleaned up imports across hggtk, removed a lot of environment variable 
> hacks
>
> thgutils now has a paths.py for wrangling file locations, and an
> i18n.py for managing gettext.  The C++ shell extensions were a nice
> excuse to do all this, but it needed to be done for i18n, unix
> packaging, and the potential migration to Qt.
>
> --
> Steve Borho
>

Great, I didn't know that THG i18n was done mostly.
And new directory structure looks like so smart.
I'll try thg-shellext repository to test my translation file without
ShellExt registration.

ShellExt is C++, so it just uses gettext, outputs PO file and merges
with PO file from python sourcecode.
About the rest of i18n (of ShellExt), I'll wait for completion of your
hacking on thg-shellext branch.

Yuki

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Tortoisehg-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop

Reply via email to