translate function replacement - feature request

[dfliess]

Would be nice to allow the use of interpolationPrefix and interpolationSufix options at translate function as you may use i18next at level (ex: view) where you receive messages from different libraries with different formats.

[jamuhl]

have a look at http://i18next.com/pages/doc_features.html#interpolation (hint1) you can set prefix and suffix.

[dfliess]

Hi @jamuhl,
thanks for your reply, I know that, but what I'm saying is that if you need to use different prefixes/sufixes each time you translate a message, maybe because you do not control de source of the message, maybe different libraries you use in one App sends different type of messages, for example:

lib1: Send messages with variable like__myVar__
lib2: Send messages with variable like %myVar
lib3: Send messages with variable like %(myVar)
lib4: Send messages with variable like {{myVar}}

With current state:
one solution would be to call init before you call translate each time ? I do not like that.
another would be to have different instances of i18next. Also I don't like it.

But maybe if the function translate accepts some options, we could modify addReplacement to receive an "optional" parameter "options" instead of using the private "o" and o.interpolationPrefix. Do you get my idea ?

Another thing that you may want to add to that hint 1 at doc_features.html@interpolation is that if you change prefix or suffix at init you may also change resGetPath and/or resPostPath.

[jamuhl]

ok, now i see the point. Shouldn't be do difficult to set this via option in the translate function. Will add this to next release - expected end of january. ok for you?

[dfliess]

Yes, that's perfect!

[jamuhl]

starting from v1.5.11 (should be released this week) you can:

i18n.t('key', {toAdd: 'something', interpolationPrefix: '*', interpolationSuffix: '*'})