On Fri, Feb 13, 2009 at 2:41 PM, 3lancer.eu wrote:
>
> Thanks for all the help with 'fuzzies'. Any clues on translating
> foreign key fields in admin interface?
>
> Regards,
> Piotr
> >
>
A foreignkey can be marked for translation the same as any field, by
providing a verbose_name argument.
Alex
Thanks for all the help with 'fuzzies'. Any clues on translating
foreign key fields in admin interface?
Regards,
Piotr
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send
On Thu, 2009-02-12 at 16:58 -0500, Alex Gaynor wrote:
[...]
> I don't think strings marked as fuzzy are actually used for
> translations, they are just kept around as references for the
> translators benefit.
That's correct. xgettext has identified that those translations aren't
exact matches for
On Thu, Feb 12, 2009 at 4:56 PM, rskm1 wrote:
>
> > Also, what does 'fuzzy' mean in my .po file?
>
> I'm not an authority on the subject but have dealt with translations
> and .po files quite a bit.
>
> The term "fuzzy" in this context means it's not an EXACT match, but
> it's very similar; i.e.
> Also, what does 'fuzzy' mean in my .po file?
I'm not an authority on the subject but have dealt with translations
and .po files quite a bit.
The term "fuzzy" in this context means it's not an EXACT match, but
it's very similar; i.e. a "fuzzy match".
The "fuzzy" usually shows up when the origi
5 matches
Mail list logo
