Translation of webgui


  • Banned

    Hi People,

    I am beginning the project translation of webgui using gettext

    I will be working page by page to change the words of gettext variables thus I will be able to create the language archives for gettext.

    I ask for aid to the community to create them archives to me of translation of exactly and thus being able to me to distribute them the pfSense in several languages.

    I will be simultaneously creating the archive of translation for Portuguese of the Brazil (pt_BR)

    Thanks,



  • Just say when you have the export ready, and we will most likely have a bunch of languages fast.
    I'll do the norwegian.



  • german here  ;D


  • Moderator

    Helping hoba with german :)


  • Banned

    COOL !!! the translation already this running!

    ;D ;D ;D ;D ;D ;D ;D ;D



  • Hi, I'll translate the webgui to spanish



  • I'm doing the italian version



  • Norwegian is about 40% translated. This is really timeconsuming !!
    I think we should hold off a little before translating a lot of different languages. I have come across a few issues that might need to be handled before we do something that might turn out to be a lot of unnecessary work. Things like unified wording will cut down translations a lot. Also we have quite a few special cases that needs to be handled in order to handle differences in languages. Specially things like sentences that are cut into pieces because of code bits.
    And example would be somthing like:

    The interface (insert code to get interface name) is part of bridge (code to get bridge name here) and can not be blah blah blah ….

    This would be pieces in the .po file looking like
    "The interface"
    "is part of bridge"
    "and can not be blah blah blah ....."

    But there is no easy way to tell that the three pieces are part of the same sentence.
    They may not even end up after eachother in the export .po file.

    So before we all do a lot of work that needs to be redone, it might be an idea to get one language translated and then see if we should work on handling stuff somewhat different.

    I'd also like for someone to try and unify wording so that we do not have to translate things like:
    "Interface"
    "Interface "
    "Interface:"
    " Interface"

    Translations are not going to be available untill 1.1 anyways.
    I also have a thought about replacing the gettext strings with numbers in order to have a easier way to handle stuff like sentences that are divided by code. And somehow make it possible to tell that 00000001, 00000002 and 00000003 is actually part of the same sentence.
    This might not be the best way to handle it either. But I do see a few issues arise, and untill we have a clear way to handle this, it might be better to only have one language to rewrite while we figure out how it should be handled.

    Just my two cents, feel free to debate this (as long as you have actually seen the exports and know what sort of issues that arises when you try to translate it).



  • I think this is turning into a whining fest, quite frankly.  If it's too much work then leave it be.  If portugese can get 100% translated then I would hope your language could.  Otherwise just leave it be, we're not halting anything.



  • if job will allow - can try translation on russian

    what can i do for translation? where i can join to project?



  • Languagefiles can be found at http://pfsense.com/cgi-bin/cvsweb.cgi/pfSense/usr/local/www/language/
    http://www.poedit.org/ is a useful tool to edit the language files.



  • I am sorry to say so but I don't see any real advantages in translating the webGUI where opposed to "I see a whole bunch of advantages in having proper documentation in English and in 4 or 5 other languages".
    You see, the webGUI is big but at the same time compact and easy to read.
    It has no BS and ~30% of it is technical English words that are not translatable into any other language.
    Can you translate IPSec or PPTP or SNMP?
    Of course you can but if you use your own acronyms then it stops making sense, even in your own country.
    Now the Docs are a whole different story.
    Of course we have got to have proper English Docs that will serve as a standard.
    But reading, let's say, 150 pages in English takes a lot longer than 150 pages in your native language even if 5-10% are still those English based acronyms ;).
    So I'd say we should let the Devs polish this baby for us and the rest of the community should start working on those Docs.
    I speak for myself.
    As soon as the English Docs are out I'll start working on translating them to pt_PT, my native language.
    And I'll keep those 5-10% of English acronyms in the pt_PT docs because at the end of the day they are universal :).
    Just my 0.02€



  • There is many reductions who do not need for translation
    For example Internet-WEB-Site

    For people who understanding in networks  - words LAN WAN IPSec and etc. do not need translate

    PS
    my IMHO - all transliterable wordcombination need replace with constant names and in external lang file make list of this words.
    Now exchange this lang file - and webGUI replace his DisplayLang



  • @rds_correia:

    I am sorry to say so but I don't see any real advantages in translating the webGUI where opposed to "I see a whole bunch of advantages in having proper documentation in English and in 4 or 5 other languages".
    You see, the webGUI is big but at the same time compact and easy to read.
    It has no BS and ~30% of it is technical English words that are not translatable into any other language.
    Can you translate IPSec or PPTP or SNMP?
    Of course you can but if you use your own acronyms then it stops making sense, even in your own country.
    Now the Docs are a whole different story.
    Of course we have got to have proper English Docs that will serve as a standard.
    But reading, let's say, 150 pages in English takes a lot longer than 150 pages in your native language even if 5-10% are still those English based acronyms ;).
    So I'd say we should let the Devs polish this baby for us and the rest of the community should start working on those Docs.
    I speak for myself.
    As soon as the English Docs are out I'll start working on translating them to pt_PT, my native language.
    And I'll keep those 5-10% of English acronyms in the pt_PT docs because at the end of the day they are universal :).
    Just my 0.02€

    What you are failing to understand is that the normal devs are not really participating in this, this is being done by outside of the normal developers that help that expressed an interest in doing the work.  It would be silly for us to turn down anyone wanting to work on pfSense that was not working on it prior.


  • Banned

    Hi people !

    My intention in beginning this work of preparation of the pfSense to the support multi-language and the translation of it for the Portuguese of Brazil is accurately to open more options for the project.

    That I will not be able to see much difference in words techniques IPSEC, DHCP, etc. but it imagines the messages of you alert, help, commentaries, even though imagines the pfSense in japanese or Chinese and in Russian.  When you yourselves it uses the tool, is clearly that not necessary of no translation to understand that the message of alert this informing you that the IP format this incorrect, but when you apply this tool for a person more layperson, the history is another.  I want to be part of this project and to continue to contribute in these works of translation and assist in different others of languages.

    Thanks !



  • freekazoide, we really appreciate your work and will do our best to do good translations. It's not easy (I've started working on german translation already). However, maybe we can find some way to make it a bit easier for the translators but we first need to find the problems with it (though I already found some) and possible solutions.

    Keep up the good work  :D


  • Moderator

    To strengthen hobas comment, I've begun working on german, too (he started from first, me from the last entry so hopefully we will meet in the middle of the file ;) ) and also have some problem parts in mind, but from my end (pun intended), it doesn't look senseless. En contraire. I know many people, who'd like to experiment with that kind of software image, but aren't that good at reading/writing or understanding english good enough. So this will considerably boost their interest :)

    Keep up guys, all of you out there!



  • @sullrich:

    What you are failing to understand is that the normal devs are not really participating in this, this is being done by outside of the normal developers that help that expressed an interest in doing the work.  It would be silly for us to turn down anyone wanting to work on pfSense that was not working on it prior.

    Who said I failed to understand that the core of the DevTeam are not going to participate on the Documentation or on the webGUI translations?
    I'll quote myself.
    @rds_correia:

    So I'd say we should let the Devs polish this baby for us and the rest of the community should start working on those Docs.

    Baby=pfSense 1.0Final
    Rest of the community=non-Dev community
    I don't see any real advantages in translating the webGUI.
    Even because we haven't even reached 1.0 yet.
    And I hope it won't enlarge the size of the downloadable images too much.
    But if someone wants do it and the Devs don't see a problem, I don't see how my humble opinion would matter much.
    I just hope that in 3.0 or 4.0 we don't need to download a DVD instead of 30MB because I hate it when something as sexy as pfS gets bloated ;).
    Again, just my 2 cents…



  • These features will not show up in 1.0.  And it only added about 500K.



  • @sullrich:

    These features will not show up in 1.0.  And it only added about 500K.

    500K here, 500K there…you know what I mean.
    I've seen it happen with too many great projects and I'd hate to see the same happening with pfS.
    And yet, I can't see a much of an advantage of having the webGUI translated.
    I see pfS as a high-end product targeted for routing tech guys or at least some very experienced power users.
    This kind of people can read English 95% of the time  ::).
    But if I can't beat you guys, I'd better join you.
    Right now I'm more interested in Docs but after that I will focus my attention in translating the webGUI to pt_PT :lol:.
    Cheers



  • Hi,

    At the moment I have translated and located to Spanish 60% of the texts. I'm using Poedit.

    But the question is: when I have finished the translation from the file to Spanish, where should I go up it?

    Is there somebody that I can help with the translation to Spanish? There is many excessively complex sentences, and the file to translate  has a lot of work. I take many days being devoted to it.

    The current state of the localization to Spanish is here: http://www.seguridad0.com/ejemplos/messages_spanish.po

    Regards,

    CARLOS MESA



  • Hi all

    I started today the french translation of webgui. It is 20% finished now.

    I'll post again when the work is done, hopefully next week.



  • Keep in mind that translations will be a feature of the next version of pfSense which is not yet even half complete. So even if you have finished everything that is presented now by the end of next week there will be lot of improvement/change until the next version is finished. Just keep that in mind  ;)



  • no problem hoba, this will just be a base. I know that the road to 1.1 is a long one  ;)


Locked