Ook thank you
On Mon, May 10, 2021, 11:48 PM Paolo Melchiorre
wrote:
> Hi Zain,
>
> I think you can ask on the specific mailing list for this subject
> https://groups.google.com/g/django-i18n
>
> Paolo
>
> On Mon, May 10, 2021, 22:36 Zain Al-abdeen wrote:
>
>> hi ,
>> i want to translate the dj
Hi Zain,
I think you can ask on the specific mailing list for this subject
https://groups.google.com/g/django-i18n
Paolo
On Mon, May 10, 2021, 22:36 Zain Al-abdeen wrote:
> hi ,
> i want to translate the django website and documentation ,
>
> can anyone show me the way to do this?
>
--
You r
hi ,
i want to translate the django website and documentation ,
can anyone show me the way to do this?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving em
Thank you for your response Claude. I just wrote to that group and I am
waiting for their response,
Soyuzbek
On Tue, Oct 15, 2019 at 9:09 PM Claude Paroz wrote:
> Hi,
>
> There is a specific group dedicated to translation issues:
> django-i...@googlegroups.com
> Please write to that group.
>
> C
Hi,
There is a specific group dedicated to translation issues:
django-i...@googlegroups.com
Please write to that group.
Claude
Le mardi 15 octobre 2019 13:40:38 UTC+2, Soyuzbek orozbek uulu a écrit :
>
> Hi all,
> I want to translate Django to Kyrghyz language using transifex. I already
> sent
Hi all,
I want to translate Django to Kyrghyz language using transifex. I already
sent a request but I didn't get any response. Can you help me with it?
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To u
Hi Claude,
Very good point. I am not familiar with the translation process. I think we
would benefit from the linter. It’s not so much a linter in the traditional
sense, since it’s not linting any code. It rather finds small errors in
translations files. Inconsistencies in punctuation, line
Thanks Joe for this proposal. Unfortunately, I fear it does not play well
with our current workflow, where we download files produced by Transifex.
Could you give us an example where an error revealed by this linter could
improve the quality of the resulting translations?
Claude
--
You
x27;, '--no-fuzzy-matching']
>
> As for your second question, your should use a dedicated tool to translate
> messages (poedit, gtranslator, virtaal, lokalize, etc.), so you won't have
> to search for untranslated messages yourself. Even text editors like vim or
> emacs provi
Regarding the "default keyword TODO": there are tools that can be used
for working with translations, in the gettext suite.
For instance, for a given django.po file, the following command prints
all untranslated strings:
msgattrib --untranslated path/to/django.po
W
y-matching']
As for your second question, your should use a dedicated tool to translate
messages (poedit, gtranslator, virtaal, lokalize, etc.), so you won't have
to search for untranslated messages yourself. Even text editors like vim or
emacs provide po mode translations.
HTH,
Cla
nning makemessages I have to search for the "fuzzy" keywords,
delete them and also delete translations which are incorrect. I would like
all the translations to be blank if not exactly translated.
I didn't understand what you mean by "msgmerge with the "-N" option swiches
ugh. Docs say that if `de-at` is not available,
Django will use `de` and that's the case. What does not work is the case
where `de-at` exists but is a sparse catalog of only translation
differences specific to `de-at`. In that situation translations missing
from `de-at` should be filled
On Fri, May 19, 2017 at 9:31 PM, Matt Westcott wrote:
> Hi all,
>
> I've noticed that the django.utils.translation module apparently doesn't
> recognise gettext's handling of fallback translations when both a
> territory-specific translation catalog (e.g. Spa
Hi all,
I've noticed that the django.utils.translation module apparently doesn't
recognise gettext's handling of fallback translations when both a
territory-specific translation catalog (e.g. Spanish (Spain), 'es_ES') and
a generic one (e.g. Spanish, 'es&#x
e using country-specific translations as well as a fallback
translation, for instance "de-de" (Germany) and "de-ch" (Switzerland) as
well as the global "de" (German) translation. In case the country-specific
translation doesn't exist or does not contain a certain
ntation in main repository or should it be managed by local DUG ?
>>
>
> Yes :-)
>
> In a perfect world, you'd be able to get documentation in other languages
> on docs.djangoproject.com. If you look at the URL space, you'll see that
> we've already prepare
et documentation in other languages
on docs.djangoproject.com. If you look at the URL space, you'll see that
we've already prepared for translations -- you hit /en/dev to get the
development docs; in theory, we could serve /fr/dev for french
documentation.
However, what we're m
Héllo,
Everything is in the title. Does Django core dev's want to have localized
documentation in main repository or should it be managed by local DUG ?
Thanks to Pilot Systems, I improved a bit the french documentation
[1] basically what I've done is converted it to use the Sphinx support of
today Transifex can be used by the translators to update the
translations. We will pull the updates from there before we release 1.3.
Jannis
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to d
On Fri, Jan 21, 2011 at 9:27 PM, Jannis Leidel wrote:
> If there are any questions, please don't hesitate to ask :)
how will 1.3 release be handled?
should translators use transifex for 1.3 release?
Aljosa
--
You received this message because you are subscribed to the Google Groups
"Django de
Hi all,
I'm very happy to announce today the move of Django's own translation efforts
to a hosted platform based on the Open Source project Transifex:
http://www.transifex.net/projects/p/django/
It will make it easier to submit updates for the 63 translations Django
currently has,
/5 Russell Keith-Magee
> On Wed, May 5, 2010 at 9:03 PM, Felipe Prenholato
> wrote:
> > Hello people.
> > Last night I opened ticket 13473 that aims easy use of model fields for
> > Braziliam CPF and CNPJ fields (as showed in ticket).
> > After initial work, I need to
run tests
in 'submodules' at regressiontests directory.
Cheers, Felipe
2010/5/5 Russell Keith-Magee
> On Wed, May 5, 2010 at 9:03 PM, Felipe Prenholato
> wrote:
> > Hello people.
> > Last night I opened ticket 13473 that aims easy use of model fields for
> > Bra
On Wed, May 5, 2010 at 9:03 PM, Felipe Prenholato wrote:
> Hello people.
> Last night I opened ticket 13473 that aims easy use of model fields for
> Braziliam CPF and CNPJ fields (as showed in ticket).
> After initial work, I need to construct tests and make translations.
> My
Hello people.
Last night I opened ticket
13473<http://code.djangoproject.com/ticket/13473> that
aims easy use of model fields for Braziliam CPF and CNPJ fields (as showed
in ticket).
After initial work, I need to construct tests and make translations.
My first point is: what is right pl
When using related table based approach for the translations, django
could use pivoting to fetch all the translations with just one normal
join.
Some pseudo sql, skipping constrains and indexes...
create table a (
id integer pkey
);
create table b (
id integer pkey,
a_id integer references
Hi Gonzalo,
> [...] sorry for the late answer.
Sorry for my late answer, too.
> I like your proposal! You simplified some over designed or complex
> stuff about my original proposal and added some very neat ideas, good
> work.
Thanks!
>> 4. Special case: Create an own mode
2009/7/11 David Danier :
> Hi Marc, hi Gonzalo, hi django-dev,
[...]
> So I thought about how model translations in django could work, and how
> this should be used by the developer. I send this email directly to
> Marc, because he is currently working on some i18n-stuff (GSoC). Gon
Hi Veena,
first sorry for my late answer, I missed your email somehow.
The SomeObjTranslation-model is what should be dynamically created by
some registry. This registry is a little more difficult than your
suggestion, but should keep things simple enough:
---
\
> default=settings.LANGUAGE_CODE)
> object = models.ForeignKey(SomeObj,
> related_name='translations')
> foo = models.CharField(...)
> class Meta:
> # only one translation per language and object
> uniq
gth=5, \
choices=settings.LANGUAGES, \
default=settings.LANGUAGE_CODE)
object = models.ForeignKey(SomeObj,
related_name='translations')
foo = models.CharField(...)
class Meta:
# only one translation per lang
t for the job anyway), keep usage as
simple as using model inheritance (keep working with translations as
simple as possible) while using a register approach to keep this
application independent (thats some kind of killer feature).
Hope this helps to see the differences here. Perhaps the file I attac
I need some kind of future proof model
> translation in django in the near future. I tried many solutions and
> came up with two of my own (not released anywhere), but nothing seems to
> fit all needs translations might impose.
>
> So I thought about how model translations in django co
> I have looked into the code and think implementing this should be
> possible, but needs some changes in the django-ORM itself.
I read some of the code around Queryset, Model Inheritance and the
Query-object itself. I _think_ the parts where django needs some
adjustments can be limited to two p
Hi David,
I'm working on some other i18n parts right now, but I'll review your
email before working on model translations.
Thanks for sharing your idea, and I'll be back with comments soon.
Cheers,
Marc
David Danier wrote:
> Hi Marc, hi Gonzalo, hi django-dev,
>
>
Hi Marc, hi Gonzalo, hi django-dev,
I'm writing this email, because I need some kind of future proof model
translation in django in the near future. I tried many solutions and
came up with two of my own (not released anywhere), but nothing seems to
fit all needs translations might impose.
yes, lets close this thread: and use this one:
http://groups-beta.google.com/group/django-users/browse_thread/thread/6a96426735ffd7f1
On Jan 23, 1:55 pm, nesh <[EMAIL PROTECTED]> wrote:
> * [EMAIL PROTECTED] wrote, On 23.01.2007 13:04:
>
> >> p.s. Let's go to django-i18n, *the* place for I18N dis
* [EMAIL PROTECTED] wrote, On 23.01.2007 13:04:
>> p.s. Let's go to django-i18n, *the* place for I18N discussions :)
> I thought about it but did not want to create fourth thread for the
> same discussion within two days. How about staying on django-users?
> It is a use of Django after all ;)
O
On 23 Sty, 12:45, nesh <[EMAIL PROTECTED]> wrote:
> Storing ML content is the completely different beast.
Unfortunately, this is what I need right now :)
> I tried this approach first (although before MR branch) and I hated explosion
> of the new tables which it creates. Until
> full model inhe
the display.
> I disagree. To me translations (of content) are not just another
> version of the
> data, they *are* the data. In many cases I need to have data ordered
> and filtered
> with regards to different language versions. This is something
> different than what
> "i18n
* stuff4ash wrote, On 23.01.2007 10:24:
> the problem with translations is the many different use "cases". and in
> many cases, avoiding a change to the model is not posible. for example,
> when u have a site with several languanges, but one object is not
> directly tran
nesh napisał(a):
> I'm -1 on this, translation must be done *without* any changes to the model.
I'm -1 on that -1 :)
> IMHO, best place to translate content is in the template -- at the point of
> the display.
I disagree. To me translations (of content) are not just ano
thx for the links :)
> > passI'm -1 on this, translation must be done *without* any
> > changes to the model.
the problem with translations is the many different use "cases". and in
many cases, avoiding a change to the model is not posible. for examp
* stuff4ash wrote, On 22.01.2007 10:57:
> after searching and reading all the posts related to internalization
> and multilanguange, my first question is if there is any active
> development to integrate or make easy translations in the django core,
> and if not, if there are any peop
after searching and reading all the posts related to internalization
and multilanguange, my first question is if there is any active
development to integrate or make easy translations in the django core,
and if not, if there are any people who would be interested in a joint
effort.
in my
Jeroen Ruigrok van der Werven wrote:
> On 5/19/06, ymasuda <[EMAIL PROTECTED]> wrote:
> > Although there are no explicit rules for translated doc, I think there
> > should be some guidelines: for example, reStructuredText, with ".txt"
> > extension, UTF-8 for non-ASCII charsets, etc. If there are
On 5/19/06, ymasuda <[EMAIL PROTECTED]> wrote:
> Although there are no explicit rules for translated doc, I think there
> should be some guidelines: for example, reStructuredText, with ".txt"
> extension, UTF-8 for non-ASCII charsets, etc. If there are any
> additional requirements, please point th
On Thu, 2006-05-18 at 18:41 -0700, ymasuda wrote:
> I have finished Japanese (ja-jp) translations for revision 2933, and
> I wish to contribute them (after proofread patches for tutorials).
>
> Although there are no explicit rules for translated doc, I think there
> should be
I have finished Japanese (ja-jp) translations for revision 2933, and
I wish to contribute them (after proofread patches for tutorials).
Although there are no explicit rules for translated doc, I think there
should be some guidelines: for example, reStructuredText, with ".txt"
extens
On 5/18/06, Marcelo R. Minholi <[EMAIL PROTECTED]> wrote:
> I'll start the translation for documents '/docs' from svn trunk but
> there is some things that I want to know:
>
> - It's possible to host this translations at the djangoproject website?
> - It&#
I'll start the translation for documents '/docs' from svn trunk but
there is some things that I want to know:
- It's possible to host this translations at the djangoproject website?
- It's possible to get a '/docs/pt-br' area for my translated docs at
the svn
>The fact is that the "old" admin is not ready for full translation and
>I am not sure if translators should wait for the new one, or someone
>should look on the "old" admin strings and make them available in the .po
>files.
Actually I already started with adding translation hooks to new_admin,
Hi,
because you are discussing what will be included in 1.0 I wonder how
it will be with the new admin.
The fact is that the "old" admin is not ready for full translation and
I am not sure if translators should wait for the new one, or someone
should look on the "old" admin strings and make them
54 matches
Mail list logo
