Wireshark · Wireshark-dev: Re: [Wireshark-dev] About translations of Wireshark

[Alexis La Goutte <alexis.lagoutte@xxxxxxxxx>]

Hi Richard,

On Sun, May 5, 2013 at 6:26 PM, Turner <turner@xxxxxxxxx> wrote:

Hi,

In http://wiki.wireshark.org/Development/Translations we reached a conclusion that "Translating all the dissector output is practically impossible. But without this, it might not make real sense to translate other parts."

This page need (a big) update.

It is now possible to translate the Gui with Qtshark (wireshark-qt),

Look README.qt doc (chapiter 3) if you need more information

There is a chinese translation ( https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8597) in dev (not yet include i still have some modification before commit)

By means of a RegExp search I figured out that there are roughly about 10000 string literals hard-coded in the dissector source files, but the majority of them aren't really user-visible strings that need to be translated.

What RegExp have you used ? because there is more of 10000 String in dissectors

In my humble opinion if we're not going to do i18n work all at once, maybe it is possible that we can put a tag on all the translatable strings, so that we can use automatic tools like GNU's gettext to extract these strings for translation later on.
(Perhaps the amount of translation work is not that much if we use automated tools to extract strings to be translated, and if given a helping hand from our vast user community)

Is there any tips/tricks that help with the work of manually going through all these hard-coded string literals in source code and pick out the translatable ones?

Thanks,
-Richard Turner

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe