Re: Translation templatetag aliases

If you use autocomplete then typing "{% tr" should propose both translate and translateblock which reduces the chances to pick the wrong one because the other choice did not show up -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions

Re: Translation templatetag aliases

On Sat, Jul 27, 2019 at 11:01 AM Florian Apolloner wrote: > Not opposed to changing it, but would make {% translateblock %} more sense > than {% blocktranslate %}? > I'm in favor of the change to using the full word "translate". I don't have a strong opinion on which variant to use for the block

Re: Translation templatetag aliases

Not opposed to changing it, but would make {% translateblock %} more sense than {% blocktranslate %}? On Saturday, July 27, 2019 at 10:51:35 AM UTC+2, Aymeric Augustin wrote: > > Hello, > > I'm in favor of adding support for {% translate %} and {% blocktranslate > %} and switching the Django doc

Re: Translation templatetag aliases

I agree too. Let's change it. Andrew On Sat, Jul 27, 2019 at 4:03 AM Markus Holtermann wrote: > Easy: +1 from me as well for reasons state before. > > /Markus > > On Sat, Jul 27, 2019, at 6:15 PM, Adam Johnson wrote: > > +1 from me too for the reasons that Aymeric states. > > > > Another small

Re: Translation templatetag aliases

Easy: +1 from me as well for reasons state before. /Markus On Sat, Jul 27, 2019, at 6:15 PM, Adam Johnson wrote: > +1 from me too for the reasons that Aymeric states. > > Another small pro: "translate" is a few more characters to type, but it > should make it easier to understand the purpose of

Re: Translation templatetag aliases

+1 from me too for the reasons that Aymeric states. Another small pro: "translate" is a few more characters to type, but it should make it easier to understand the purpose of the tags to newcomers. "trans" is a prefix used for many words - Wiktionary lists 609: https://en.wiktionary.org/wiki/Categ

Re: Translation templatetag aliases

Hello, I'm in favor of adding support for {% translate %} and {% blocktranslate %} and switching the Django documentation to use these for two reasons: - As stated by Mike, the mental associations that "block trans" creates for those who identify as trans are just bad — I can't believe it took

Translation templatetag aliases

Hello all, Recently I had a member of my team bring up that it was uncomfortable for them to work in parts of our codebase where they regularly had to see "blocktrans" in the template files. To make our work environment more inclusive, I wrote a Django package