Locale selection in Express+Jade broken since 0.3.6 about i18n-node HOT 8 CLOSED

Seems like #48 could be related.

Given that the question about the bindings came up, I started reading the README a bit more closely. In the end, adding the following code to my application took care of the issue:

  app.use( function( req, res, next ) {
    // express helper for natively supported engines
    res.locals.__i = res.__i = function() {
      return i18n.__.apply( req, arguments );
    };
    res.locals.__n = res.__n = function() {
      return i18n.__n.apply( req, arguments );
    };
    next();
  } );

Then I could also remove this obsolete piece of code:

  app.locals( {
                __i: i18n.__,
                __n: i18n.__n
              } );

And now it's working with the latest and greatest :) Feel free to close if I didn't miss anything.

from i18n-node.

ok fine :)

you might even omit that custom setup inside app.use if you start using __() instead of __i(). Please review https://gist.github.com/mashpie/5124626 for details. I'd also like to add a jade example, so don't hesitate sharing any hints.

Thanks!

from i18n-node.

I remember reading that __() doesn't work because jade uses an internal variable named __ which conflicts with this default name. I thought that this is what makes the case with jade special. But I haven't really checked if that still holds true.

from i18n-node.

According this issue: pugjs/pug#403

Jade not use __ anymore. Currently version express + jade + i18n works fine for me

from i18n-node.

correct.. left this ticket open until setup another example...

from i18n-node.

I just created a example here:

[email protected] + [email protected] + [email protected]
https://gist.github.com/hankwang/5994144

from i18n-node.

@HankWang haha! same idea over here, see https://github.com/mashpie/i18n-node/tree/master/examples/express-jade - so I'll link your gist in README, ok?

from i18n-node.

@mashpie sure :)

from i18n-node.