Support for structured json about i18n-node HOT 13 CLOSED

keeping on roadmap

from i18n-node.

Just FYI, I implemented something similar for experimental purposes: https://github.com/oliversalzburg/i18n-node/tree/complex-backend

It uses dot notation (home.title) for structured lookups. To avoid issues with existing translation terms (which might include . in a phrase), this has to be enabled with objectNotation:true in the i18n.configure call.

There's only an implementation for single terms (no plural support). As I said, it was an experiment ;)

from i18n-node.

+1

from i18n-node.

+1!

from i18n-node.

+1

@oliversalzburg your modification works like a charm and as I can see the mustache support is at the package.json, too. please keep this fork updated as long as possible. may be it should be discussed to use you configuration modification for later versions (the naming is very obvious). at least it could be very helpful to add the changes to the documentation of your fork to make the usage easier for people who don't know this thread ;-).
for me the usage of structured language files is very important to keep the clarity. the support at webtranslateit is very useful.

from i18n-node.

@ronny332 Cool to see that someone has use for it :) We use i18n-node very extensively ourselves and I'd be happy to maintain the fork if anyone is actually using it ;)

from i18n-node.

please also keep reading notification - this will definitely get merged. I am again stuck in some paid jobs with critical deadlines but will catch up in july... promised :)

from i18n-node.

Cool. I'll try to complete the feature then and give it a little more thought. Cheers! :)

from i18n-node.

I've made a couple of changes in my fork. I made sure that pluralization works and made it possible to declare a default string to use for each object literal.

I also added some documentation: https://github.com/oliversalzburg/i18n-node/tree/complex-backend#object-notation

from i18n-node.

@oliversalzburg could you make a pull request and merge your fork?

from i18n-node.

@juancroca I created a PR at #114 But it's not up to me to merge :)

I'd appreciate it if you could test the branch regardless of it being merged. Cheers

from i18n-node.

@oliversalzburg I did and it works wonderfully thanks hope they merge it.

from i18n-node.

so this is merged, please kindly retest - thanks again to @oliversalzburg

from i18n-node.