Gold Sponsors
\n\n\n \n ![](\"https://raw.githubusercontent.com/i18next/i18next/master/assets/locize_sponsor_240.gif\")
\n \n
\n all inside will be used as on segment, even if having other\n elements inside\n
\n\n// key = all inside will be used as on segment, even if having other\nelements inside\n```\n\nSame could be done using options:\n\n```js\nmergeTags: [], // tags to merge innerHtml to one key\ninlineTags: [], // tags to inline (eg. a, span, abbr, ...)\nignoreInlineOn: [], // tags to ignore inlining tags under inlineTags\n```\n\n## Fragment replacement for links and images\n\n```html\n![\"big](\"/images/{{a.png}}\")
\n```\n\nYou will find `a.png` to be a key in your translation files - it's value can be replaced to eg. `a-de.png` for German (all other languages will fallback to `a.png`)\n\n```html\nOpen my statistics\n```\n\n`statistic` will be a regular key that can be translated. But be aware you will need to provide that routes - eg. using [localized routes on the server](https://github.com/i18next/i18next-express-middleware#add-localized-routes)\n\n## Avoid translating\n\n#### an element\n\nJust set translated attribute:\n\n```html\nfoo {{foo}}; foo2 {{foo2}}
\ndifferent namespace: i18next-options='{\"ns\": \"common\"}'
\n\n set it on i18next options and assert to add it to\n i18next.options.ns array on init\n
\n\n \n \n \n