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

Re: [tor-bugs] #1613 [BridgeDB]: i18n bridgedb



#1613: i18n bridgedb
----------------------+-----------------------------------------------------
 Reporter:  phobos    |       Owner:  kaner                    
     Type:  task      |      Status:  needs_review             
 Priority:  normal    |   Milestone:  BridgeDB Upgrades Phase 1
Component:  BridgeDB  |     Version:                           
 Keywords:            |      Parent:                           
----------------------+-----------------------------------------------------

Comment(by kaner):

 Thanks for reviewing.

 1.) As an alternative to configuring available languages, we could also
 iterate through the i18n directory, see what's there and add that to the
 pool of available languages. But a) as far as i understood our Pootle
 process, we pull in all possible languages into that directory and wait
 for poeple to translate things. That means we'd have a large percentage of
 unusable languages for a good while and a small percentage of unusable
 languages for a long while. Also, b) if we learn available languages in an
 automated way from the i18n directory, we can't disable a certain language
 for a certain time (for whatever reason, we've had that case in GetTor).
 It's obviously much easier to do that via config. Also, c) is it really so
 awkward?

 2.) Yes. I agree that it is ugly. The idea is here that we can re-use
 certain chunks in other parts (Compare HTML_3 and EMAIL_4, for instance.
 Yes, I know this needs to be changed in the current code) and make it
 easier for Pootle users and Pootle itself. I've learned that both like
 smaller chunks better. I'm all ears (eyes?) for a more elegant way to do
 this.

 3.) I agree on the global state itchyness. I'll look into it.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1613#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs