#4841: Same English phrase - different Swedish phrases
--------------------------------+-------------------------------------------
   Reporter:  [EMAIL PROTECTED]  |                Owner:  mtredinnick 
     Status:  closed            |            Component:  Translations
    Version:  SVN               |           Resolution:  wontfix     
   Keywords:                    |                Stage:  Unreviewed  
  Has_patch:  0                 |           Needs_docs:  0           
Needs_tests:  0                 |   Needs_better_patch:  0           
--------------------------------+-------------------------------------------
Changes (by mtredinnick):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 There's nothing we can really do about these. MO file lookup works by byte
 matching, so the same string of bytes/characters cannot be translated in
 two different ways.
 
 All you can do in those cases, unfortunately, is recommend that people
 don't use the Associated Press versions in their non-English text output
 (which kind of makes sense anyway -- AP's style guide is very North
 American-centric).
 
 Particularly the apnumber filter is something we can't solve. Filters
 can't really look ahead and change their behaviour based on the following
 text (which they won't even have access to, in many cases). Again, sites
 requiring localisation into languages with gender-specific word endings
 are going to have to use more specialised filters in those cases.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/4841#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to