Hi Ben,
Thanks very much for the information!
I moved the blueprint to:
https://blueprints.launchpad.net/oslo.i18n/+spec/more-gettext-support
Best Regards,
Peng Wu
On Tue, 2014-08-26 at 10:05 -0500, Ben Nemec wrote:
> Hi Peng,
>
> We're using the spec process described in
> https://wiki.o
Hi Peng,
We're using the spec process described in
https://wiki.openstack.org/wiki/Oslo#Design_Proposals to manage
blueprints now. You'll need to create a spec review as described in the
wiki for this. Unfortunately, I don't think we've opened up Kilo specs
yet, so you might want to either wait
Hi Doug,
I created a i18n blueprint for oslo.i18n.
URL:
https://blueprints.launchpad.net/openstack-i18n/+spec/more-gettext-supports
Could you review it?
I am reading django gettext code, I think I will use a similar approach
for the "contextual markers" gettext function.
Thanks,
Peng Wu
On M
Yes, that would be a good next step.
Doug
On Aug 17, 2014, at 10:03 PM, Peng Wu wrote:
> Yes, I am interested in adding these missing gettext functions to
> oslo.i18n library.
>
> Guess the next step is to create a blueprint for Kilo?
>
> Thanks,
> Peng Wu
>
>
> On Fri, 2014-08-15 at 16:
Yes, I am interested in adding these missing gettext functions to
oslo.i18n library.
Guess the next step is to create a blueprint for Kilo?
Thanks,
Peng Wu
On Fri, 2014-08-15 at 16:02 -0400, Doug Hellmann wrote:
> On Aug 15, 2014, at 3:18 AM, Peng Wu wrote:
>
> > Hi,
> >
> > Recently
On Aug 15, 2014, at 3:18 AM, Peng Wu wrote:
> Hi,
>
> Recently I just read the code of oslo.i18n library,
> The lazy translation idea is great!
>
> But I found a question about gettext "contextual markers"
> and "plural form", such as pgettext and ungettext functions,
> see [3].
>
> It s
Hi,
Recently I just read the code of oslo.i18n library,
The lazy translation idea is great!
But I found a question about gettext "contextual markers"
and "plural form", such as pgettext and ungettext functions,
see [3].
It seems the two gettext functions are missing in the oslo.i18n
