#6755 NORM Never A: 'etoys' textdomain should be divided as smaller pieces

[Zarro Boogs per Child]

#6755: 'etoys' textdomain should be divided as smaller pieces
----------------------------+-----------------------------------------------
 Reporter:  korakurider     |       Owner:  etoys                            
     Type:  defect          |      Status:  new                              
 Priority:  normal          |   Milestone:  Never Assigned                   
Component:  etoys-activity  |     Version:  Development build as of this date
 Keywords:                  |    Verified:  0                                
 Blocking:                  |   Blockedby:                                   
----------------------------+-----------------------------------------------
 We have all of translations of etoys in single textdomain 'etoys'
 with over 3000 phrases.
 That is too many for translators who think of starting translation of
 etoys.  And that seems to cause problem for Pootle transaction.

 So dividing the textdomain would make life easier for translators.

 Points to consider:
 1) There are many way how to divide.  how do we decide?
 my thoughts:
 + At beginning of our gettextize work, we divided translations by class
 categories, but that made too many POs that people didn't want to work on.
 So proper size is very important.
 + By splitting advanced features as different domain, starting translation
 would be easier (at least in people's mind)

 2) Because of OO nature of Squeak/Etoys, there is possibility that some
 string is defined with #translatedNoop in some domain, and is translated
 in another domain.  We need to handle this properly, but original gettext
 seems not to have good semantics for the situation.
 (note that there is similar risk with msgctxt)

-- 
Ticket URL: <http://dev.laptop.org/ticket/6755>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system