Hi there,
I have a Django site with multi-language support through i18n.
The default user's language is set based on the browser headers but users
can change it via the regular set_language view.
Recently I noticed that the UI is shown in a different language than the
one my user is sup
zation" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For mor
this message because you are subscribed to the Google Groups
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n
s from it, send an email
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.
ject! Nice to realize it's build on Django. The design is
> really sleek. Imagining the big amount of work invested.
>
> I guess my user scenario is the most common one and I personally find some
> obstructions however. Sometimes I even wonder whether there were a black
> box huma
he Google Groups
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at
's build on Django. The design is
really sleek. Imagining the big amount of work invested.
I guess my user scenario is the most common one and I personally find some
obstructions however. Sometimes I even wonder whether there were a black
box human testers employed.
My scenario:
Ordinary tr
/www.transifex.com/
--
You received this message because you are subscribed to the Google Groups
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-i18n+unsubscr...@googlegroups.com.
To post
ore usable.
--
: Vladimir Macek : http://macek.sandbox.cz : +420 608 978 164
: UNIX && Dev || Training : Python, Django : GPG key 1F059424
--
You received this message because you are subscribed to the Google Groups
"Django internationalization and localization" group.
To un
>
> Problem is that the replacement for `Meta.verbose_name` and
> `Meta.verbose_name_plural` we finally come up with also needs to:
>
> * Maintain backward compatibility
>
> * Not change verbose names behavior when i18n isn't being used. IMHO
> disrupting the workf
lural` we finally come up with also needs to:
* Maintain backward compatibility
* Not change verbose names behavior when i18n isn't being used. IMHO
disrupting the workflow native English developers (especially
English-speaking Django core developers) use (and the results
they get) the least
e because you are subscribed to the Google Groups
> "Django internationalization and localization" group.
> To post to this group, send email to django-i18n@googlegroups.com.
> To unsubscribe from this group, send email to
> django-i18n+unsubscr...@googlegroups.com.
> For
F059424
--
You received this message because you are subscribed to the Google Groups
"Django internationalization and localization" group.
To post to this group, send email to django-i18n@googlegroups.com.
To unsubscribe from this group, send email to
django-i18n+unsubscr...@googlegr
Hi fellow translators,
I've been working that new-feature ticket starting with an idea Jannis
Leidel had posted in a GitHb [0]Gist some months ago and would like to
get some feedback from developers with real i18n experience about this
first iteration of a [1]patch for it.
Solving this
2, 2011 at 01:23, Sergiy Kuzmenko wrote:
>
>> I believe you should file a bug report.
>> Cheers
>>
>>
>> On Sat, Oct 1, 2011 at 7:09 PM, Erik Wognsen wrote:
>>
>>> Ok. Does the i18n group have the possibility of deciding and committing
>>>
3
[2] https://code.djangoproject.com/ticket/16350
On Sun, Oct 2, 2011 at 01:23, Sergiy Kuzmenko wrote:
> I believe you should file a bug report.
> Cheers
>
>
> On Sat, Oct 1, 2011 at 7:09 PM, Erik Wognsen wrote:
>
>> Ok. Does the i18n group have the possibility of decidi
I believe you should file a bug report.
Cheers
On Sat, Oct 1, 2011 at 7:09 PM, Erik Wognsen wrote:
> Ok. Does the i18n group have the possibility of deciding and committing
> this or should it go through a regular bug report?
>
> On Sun, Oct 2, 2011 at 01:00, Sergiy Ku
Ok. Does the i18n group have the possibility of deciding and committing this
or should it go through a regular bug report?
On Sun, Oct 2, 2011 at 01:00, Sergiy Kuzmenko wrote:
> > According to gettext manual[1] one can use \u to uppercase the next char.
>
>> > But I have n
nd localization" group.
To post to this group, send email to django-i18n@googlegroups.com.
To unsubscribe from this group, send email to
django-i18n+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-i18n?hl=en.
//www.gnu.org/software/gettext/manual/gettext.html#Interpolation-I
That section of the documentation is Perl-specific AFAICT.
--
Ramiro Morales
--
You received this message because you are subscribed to the Google Groups
"Django internationalization and localization" group.
To post to this
t;>> and some others.
>>> >
>>> > This works well in languages that only use an article for definiteness.
>>> But what about other languages?
>>> >
>>> > For example, in Danish "employee" is "ansat" but "the em
". The current translation for many languages including Danish simply
>> uses a form of "%(name)s \"%(obj)s\" was changed successfully.". For
>> example: 'ansat "Foo Bar" blev ' or, in other words, '[lower case,
>> indefinite form
indefinite form of model name] "Foo Bar" was changed successfully'.
> >
> > Is it possible to handle 'The %(name)s' such that the translator may
> specify an upper case and definite version of the model name?
> >
> > Regards,
> > Erik Wog
ords, '[lower case,
indefinite form of model name] "Foo Bar" was changed successfully'.
>
> Is it possible to handle 'The %(name)s' such that the translator may
specify an upper case and definite version of the model name?
>
> Regards,
> Erik Wognsen
he model name?
Regards,
Erik Wognsen
--
You received this message because you are subscribed to the Google Groups
"Django internationalization and localization" group.
To post to this group, send email to django-i18n@googlegroups.com.
To unsubscribe from this group, send email to
django-i18n+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-i18n?hl=en.
(Re-sending unsent email to django-i18n)
On Wed, Mar 9, 2011 at 12:11 PM, Vladimir Macek wrote:
> Hi, does anyone use an easy way to review translation changes for his/her
> language?
>
> Consider the situation that you developed some i18n rules for your language
> and want to ch
On 9.3.2011 12:20, Dimitris Glezos wrote:
> On Wed, Mar 9, 2011 at 12:11 PM, Vladimir Macek wrote:
>> Hi, does anyone use an easy way to review translation changes for his/her
>> language?
>>
>> Consider the situation that you developed some i18n rules for your la
Vladimir Macek wrote:
> Hi, does anyone use an easy way to review translation changes for
> his/her language?
As a coordinator I too feel the need for this, in order to check team
contributions.
> Consider the situation that you developed some i18n rules for your
> language and w
Hi, does anyone use an easy way to review translation changes for his/her
language?
Consider the situation that you developed some i18n rules for your language
and want to check whether the changes done by team members or anyone else
still abide those. You certainly don't want to rea
mplate and
print out all the non-i18n bits of text that you have left to do.
Link to page: http://www.technomancy.org/python/django-template-i18n-lint/
It's a bit rigid at the moment, and works for our code base. It uses
regular expressions to 'parse' the HTML & Django templates
are subscribed to the Google Groups
"Django internationalization and localization" group.
To post to this group, send email to django-i18n@googlegroups.com.
To unsubscribe from this group, send email to
django-i18n+unsubscr...@googlegroups.com.
For more options, visit this g
Hebrew translator here. Tx handle: yishaibeeri
Thanks,
Yishai
On Thu, 24 Feb 2011 17:51:59 +0200, Django internationalization and
localization wrote:
Hello yis...@platonix.com,
You are now a member of the django-i18n group.
If you have questions related to this or any other Google Group
On 09/19/2010 11:54 PM, madewulf wrote:
Hello everybody,
I just finished a blog post about i18n with Django. Comments/patches
are welcome !
http://www.multitasked.net/2010/sep/19/django-i18n-tricks/
Martin De Wulf
While at it, I gave a talk few months ago regarding RTL, l10n and i18n
excellent, thanks!
L.
On Mon, Sep 20, 2010 at 07:54, madewulf wrote:
> Hello everybody,
>
> I just finished a blog post about i18n with Django. Comments/patches
> are welcome !
>
> http://www.multitasked.net/2010/sep/19/django-i18n-tricks/
>
> Martin De Wulf
>
>
Hello everybody,
I just finished a blog post about i18n with Django. Comments/patches
are welcome !
http://www.multitasked.net/2010/sep/19/django-i18n-tricks/
Martin De Wulf
--
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To po
>> Recently we submitted somewhat larger i18n update for our language. Now
>> that we have a RC out, I guess the source changes will be minimal, but
>> will still happen.
>
> With the release of the release candidate we are in "string freeze" mode,
&g
Am 06.05.2010 um 13:39 schrieb Vlada Macek:
> Recently we submitted somewhat larger i18n update for our language. Now
> that we have a RC out, I guess the source changes will be minimal, but
> will still happen.
With the release of the release candidate we are in "string freez
Hi.
Recently we submitted somewhat larger i18n update for our language. Now
that we have a RC out, I guess the source changes will be minimal, but
will still happen.
I'd like to sync the translation with the final release code. Therefore,
when will be the best time to create and submit the
Doesn't Django I18N google group have an manager who can delete all
the junk mail that comes to the list and ban the offending users?
It look more like porn tube currently and less like serious mailing
list. :(
Davor
--~--~-~--~~~---~--~~
You received
Hi folks,
for those who don't know it, I've been working on a branch, where I
fixed some bugs, and where I tried to improve Django's i18n in
general. Basically what's done, is making Django consider current
locale when working with dates, numbers and calendars. For example,
a
Hi folks,
just wanted to let you know, that I started coding for the i18n
refactorization, and that you can already check the changes at [1].
See details of what this changeset does at [2].
For now, checking that code is only worth for developers interested on
Django itself, so actually nothing
getting the translation
near 100% complete and open a ticket with the attachment sometime
between 1.1 RC and 1.1 final.
Regards,
--
Ramiro Morales
http://rmorales.net
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&quo
://www.easis.cz
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to this group, send email to Django-I18N@googlegroups.com
To unsubscribe from this group, send email to
django-i18
Hi fellow i18n workers,
I wanted to ask for testing, feedback and (in case it is deemed
correct) hopefully
help with getting a core committer to include it in 1.1, for the latest patch
for [1]ticket #10436.
What's needed to get the application names translated is to include
(and transla
Hi!
I just wanted to point you out, that I started a thread on django-
developers [1] about some improvements that could be done for a better
i18n of Django.
I'll try to include those changes on 1.0.
[1]
http://groups.google.com/group/django-developers/browse_thread/thread/db149543262
Desperate for a little help troubleshooting - I've read the docs, and
have the correct file layout for i18n, with conf/locale/LANG/
LC_MESSAGES/django.po files (and their compiled brethren) - and in my
code I've got:
from django.utils.translation import gettext
followed by uses of gett
anguage. You just don't know
who the end-user is going to be and erring on the side of politeness is
almost always the better approach.
Regards,
Malcolm
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Dja
his way. Dunno about
> 'es-AR'. Any other languages you're aware that have this treatments?
Yes, the es_AR maintains/sues the polite form.
Regards,
--
Ramiro Morales
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
http://www.advogato.org/person/mgonzalez/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to this group, send email to Django-I18N@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PRO
>
> --
> http://www.advogato.org/person/mgonzalez/
>
> >
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to this group, send email to Django-I18N@googlegroups.c
h to take!
>
ok, so the problem is:
Spanish | English
==
Tu | You (informal)
Usted | You (Formal, poite)
>
--
http://www.advogato.org/person/mgonzalez/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
o tutear ;-)
>
>Well, I'm agree that all translations must stay in a formal tone.
>
> >
>
> --
> http://www.advogato.org/person/mgonzalez/
>
> >
>
--~--~-----~--~~~---~--~~
You received this message because you are subscribed to the Google
--~--~~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to this group, send email to Django-I18N@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Django-I18N?hl=en
-~--~~~~--~~--~--~---
messages are used only in the admin, and I
think that 90% of the cases where you give admin access to someone
they expect to see a 'polite' interface, it is a working tool for
these people after all.
I would also like to know what other people thing about this.
Regards,
Jorge
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to this group, send email to Django-I18N@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Django-I18N?hl=en
-~--~~~~--~~--~--~---
Some time ago I sent this message to django-developers and django-i18n, it
never appear on django-i18n hence I forwarded to django-developers. As there
seems to be some activity here those days about the Spanish language I
wanted to recall in this issue but Google Groups seems to have
jango tests against that.
Anyone have any thoughts on an action plan to get more tests to
excercise the i18n code?
vic
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to t
I found a page with links about Guidelines, Checklists, and Resources
of Internationalization (I18n), Localization (L10n), Globalization
(G11n)
http://www.i18nguy.com/guidelines.html
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
to do much on the tickets, but I think I will be able to
have a go on them the coming week at latest. Sorry for the
inconvenience.
bye, Georg
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django I18N" gr
58 matches
Mail list logo
