Custom nugget not being taken into account for localization of requests about i18n HOT 6 CLOSED

"Same thing for black and white list"

Would you elaborate? Expected vs. observed behavior?

from i18n.

If the webconfig has a configuration for

• i18n.BlackList
• i18n.WhiteList
• i18n.NuggetBeginToken
• i18n.NuggetEndToken

Botht the parser and the module that localizes the text should taken them into account
Observed: With the following configuration:

<add key="i18n.BlackList" value="\bin;" />
<add key="i18n.WhiteList" value="*.cs;*.cshtml" />
<add key="i18n.AvailableLanguages" value="en" />
<add key="i18n.NuggetBeginToken" value="[||[" />
<add key="i18n.NuggetEndToken" value="]||]" />

The parser will use the new nuggets and respect the black and white list configuration but when the application runs the module will ignore these configurations and localize all pages with the original '[[[' and ']]]' nuggets

Expected: With the same configuration, the parser will observe the new nuggets and white and black list configurations and so will the application not translating the blacklisted folders when part of the request and only looking for the nuggets defined here

from i18n.

Just tested your exact config with a token [||[Home]||] and it works. Are you using the latest build? If not, did you not get notification of the the commit above?

from i18n.

I'm using the version from yesterday morning, I'll update and check this again

from i18n.

BTW, we should change the default token, I'm getting tons of conflicts with JSON structures

from i18n.

Works fine in the latest version, thanks
I'm going to open a new issue to track changing the nugget, and we can talk suggestions

from i18n.