Language Translation Policy



  • Some words happen to match English words, but actually they are defined keywords that are in various status files.
    e.g. Status->OpenVPN can have status values like:

    reconnecting; ping-restart
    up
    down
    
    

    Status->DHCP Leases uses words like:

    online offline expired active static
    

    Some of these things are not really English any more - they are "International Computer Speak" - and translating them on the GUI could actually obfuscate things for people who are trying to match a value they know from the FreeBSD documentation to what is on the GUI status display.

    Is there a policy on what words in what contexts are deemed to be "International Computer Speak" and thus not to be translated?


  • Rebel Alliance Developer Netgate

    We don't have a defined policy for that as far as I'm aware.

    It may be something that needs to be handled on a case-by-case basis since such keywords vary from daemon to daemon and other various areas.



  • Surely pfSense is not the first project to ask that?  Can we learn from someone else (RedHat, FreeBSD, KDE, mozilla, maybe even Cisco…)?

    The Fedora project had (and probably still does) volunteer translators, with one lead person per language.  I think there was some infrastructure or guidance set up for them, maybe something is there?


Log in to reply