Accessing a property defined in languages (internationalization) from client-side JS

[PitaJ]

Right, and I'm asking why you are translating these strings yourself in the first place.

[cool]

Simply because of internationalization. Right now, I am targeting en-GB only. Later on, may be, we need to support 'n' different number of languages. So my map.js (client side) will remain untouched.

[PitaJ]

That's not what I'm asking. I'm asking why you want to do the parsing of the translations manually instead of using the automatic translation that NodeBB does.

[cool]

I am not aware of this automatic translation. Could you pl. write an example about how this can be achieved, in my case, global:my_location.

[PitaJ]

Please provide the code where you use these translations. It depends on what you're doing.

[cool]

require(['translator'], function (translator) {
  translator.translate('[[map:my_location]]', function (translated) {
    my_location = translated;
  });
});

....

marker = L.marker(initialLocation, {
  draggable: true,
  title: my_location,
  alt: my_location,
  riseOnHover: true
}).addTo(map)
.bindPopup(initialLocation.toString()).openPopup();

[PitaJ]

Ok so this is one of the rare cases where manually translating is your only option.

If you want to get a bunch of translations, I'd suggest using a filename besides global.json, maybe use map.json instead. Then, you can do this:

require(['translator'], function (translator) {
  translator.getTranslations(translator.getLanguage(), 'map', function (translations) {
    translations.my_location === 'My Location';
  });
});

Also, please use code blocks from now on. It works like this:

```
// code goes here
```

[cool]

Great! I understand

btw where to use the code blocks?

[PitaJ]

Use code block when you make a post with code in it

[cool]

oh.. Right