On Tue, Nov 29, 2011 at 00:39, Vladimir Macek wrote:
> No, I didn't. How could it help me with my problem and may I ask you for
> examples for my situation?
Any repo would do, but I think that lictionary have a lot of i18n code
from different open projects making it easy to check horizontally.
I
No, I didn't. How could it help me with my problem and may I ask you for
examples for my situation?
V.
On 27.11.2011 00:23, Lachlan Musicman wrote:
> Have you had a look through http://lictionary.in/ to look for prevelance?
>
> cheers
> L.
>
> On Sun, Nov 27, 2011 at 02:23, Sergiy Kuzmenko wrote
Have you had a look through http://lictionary.in/ to look for prevelance?
cheers
L.
On Sun, Nov 27, 2011 at 02:23, Sergiy Kuzmenko wrote:
> I agree. We are getting nested translations here which does not work equally
> well in all languages. Translation strings have to be fully spelled.
>
> On N
I agree. We are getting nested translations here which does not work
equally well in all languages. Translation strings have to be fully spelled.
On Nov 25, 2011 7:25 PM, "Vladimir Macek" wrote:
> Hello translators,
>
> there's a new `naturaltime' template tag coming with the Django dev
> version
Hello translators,
there's a new `naturaltime' template tag coming with the Django dev
version. It construct a phrase specifying how much ago/from-now the given
time is.
https://docs.djangoproject.com/en/dev/ref/contrib/humanize/#naturaltime
When the difference is more than one day, it calls time