Re: Random locale strings translated
Hey Rob, I had "fuzzy" lines in all of the not translated strings. It's actually quite smart, isn't it? I had no idea. Thanks for your help, it's working perfectly now :-) Fred --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Random locale strings translated
On May 11, 3:47 am, phred78wrote: > I've specified translation string, got the translations done and > compiled. > > It's working for the most part, but some of the strings don't show up > correctly translated, where others do. > What could be causing this? Has anyone come across a similar problem? > I'm pretty sure the translations are in the correct .po files. Some things to check: * make sure the latest .po files have been compiled into .mo files. (django/bin/compile-messages.py) * check the .po-file lines that aren't working, and make sure they don't say "#, fuzzy". The fuzzy matches can be a big help to your translators when minor changes to the code and templates are made, but they WON'T be used unless you remove that ", fuzzy" attribute (and recompile the .mo files). --Rob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Random locale strings translated
Hi, I'm building a multilingual website and using django-localeurl so I can get /fr/, /en/, etc in the url. I've specified translation string, got the translations done and compiled. It's working for the most part, but some of the strings don't show up correctly translated, where others do. What could be causing this? Has anyone come across a similar problem? I'm pretty sure the translations are in the correct .po files. Thanks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---