Re: Translation application on GSoC



On mié 05 jun 2013 14:25:47 CEST, Gil Forcada Codinachs wrote:



2013/6/5 Marcos Chavarría Teijeiro <chavarria1991 gmail com
<mailto:chavarria1991 gmail com>>

    Hi!

    Thank you for your congratulations and for your ideas!

    Now I have a huge list of interesting features! :D However as Gil
    Forcada says, GSoC is just
    a summer so I cannot implement all this features in this summer.
    On the other hand is important
    to know what is out there so I can make a very extensible design.

    The "previewing" feature would be very very interesting and useful
    but I don't really think I'm going to
    have time for that this summer but is a must for the future ;).

    Project vision has been requested almost for all translators so I
    will include it in my project.



        * Auto-translation, including the feature for auto-translation
        of mass files.


    I don't what you mean by "auto-translation". Does it mean using
    some external (Google
    translate) or local (using the TM) tool to translate some strings?


Just speaking for me... I would say that whenever I open a file (or
choose the option in the project about that) all untranslated strings
are filled with a 100% match (maybe 90% is ok too) and marked as fuzzy
so that they can be reviewed.

As for the source of matching: local TM I would say or on-line if
there's an option for on-line TMs.

    About the user interface my idea is a three column design quite
    similar to the original Gtranslator
    application but where the plugins' windows should be detachable.
    What do you think?


I like the current approach that allows you to move the panels around,
still something like Virtaal that allows you to focus on the
translation (having the translation one next to each other, not below).

Cheers,

    Best regards,
    Marcos Chavarría Teijeiro.


    2013/6/5 Jiro Matsuzawa <jmatsuzawa gnome org
    <mailto:jmatsuzawa gnome org>>
    >
    > Hi Marcos,
    >
    > Congratulations!
    >
    > On Tue, Jun 4, 2013 at 4:59 PM, Nicolas Delvaux
    > <contact nicolas-delvaux org
    <mailto:contact nicolas-delvaux org>> wrote:
    > > The "previewing" part could be useful for Gtranslator too.
    > > You may want to provide integration with an existing
    web-service like
    > > Deckard[1] (which could be extended to suit your needs) or you
    could
    > > implement a similar feature directly in Gtranslator (this
    means downloading
    > > the right assets automatically from git).
    > >
    >
    > I'm not sure if you should work on this during the GSoC, but as
    Nicolas said,
    > a ui preview function like Deckard would be helpful for translators.
    >
    > Good luck,
    >
    >
    >
    >
    > --
    > Jiro Matsuzawa
    > E-mail:
    > jmatsuzawa gnome org <mailto:jmatsuzawa gnome org>
    > matsuzawa jr gmail com <mailto:matsuzawa jr gmail com>
    > GPG Key ID: 0xECC442E9
    > GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B
    ECC4 42E9


    _______________________________________________
    gnome-i18n mailing list
    gnome-i18n gnome org <mailto:gnome-i18n gnome org>
    https://mail.gnome.org/mailman/listinfo/gnome-i18n




_______________________________________________
gnome-i18n mailing list
gnome-i18n gnome org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

I've been using Virtaal for a while and I really like that the input boxes for editing an string it's right inside the list of available strings.

So, I think that the optimal UI design could be a two column design, one wider than the other. The wider column for the list of available strings like Virtaal has, and the other one for plugins.

For me the most important features that this new app has to have are:

- Ability to open gettext files
- Syntax highlighting for code
- Easy system for copying chunks of code and variables. And please, in the same way as Virtaal does, not how Gtr behaves now.
- Project manager: manager multiple po files in one project.
- Allow to use multiple TM, import/export them by using TMX files, activatable by project - Allow to use multiple glossaries, import/export them by using TBX files, activatable by project
- Statistics: strings/words per file or project
- Plugin system

Less important, or for implement in the future:
- Pology integration
- Languagetools integration
- Pofilter integration
- Ability to edit and save different file types: xliff, tmx, ...

As someone said, GSoC is a very limited time project so, I think you should create a really good base that after GSoC you or others could extend easily. Documenting all the API to make more easier create plugins for Gtr.

Regards


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]