Marcus Spiegel

https://github.com/DJviolin/lantosistvan/blob/0c0ba696ac186286cbcf08405f98aee40f7e37ba/app.js#L166 should read ``` js app.use('/:lang/contact', contact); ``` to make URLs work like: - /hu/contact - /en/contact you might also consider https://github.com/mashpie/i18n-node#i18n__l to get completly localized urls

@DJviolin please refer to expressjs docs - routing issues are not i18n related - try searching for "Enable strict routing" on http://expressjs.com/en/4x/api.html You should find express.Router([options]) - or check out...

.json is the only supported storage by now. Native, no deps, no eval, no vulnerabilties. Plus: anyone van transpile almost anything to json. No eta but a new 1.x branch...

Alright, I like i18n-next as a framework with it's plugins and adapters while `i18n-node` intended to be a lib not a framework. Do you also plan to try integration with...

...ts I see - well, what I am thinking of is to add a `setCatalog()` as the logikal counterpart to `getCatalog()` https://github.com/mashpie/i18n-node#i18ngetcatalog That would open up loading translations programmatically from...

sry... I don't get your use case or context

Example is about dealing with special chars... i18n supports full unicode so shouldn't be problem to just enter any [space] ` ` or [opt+space] ` ` or let's say "minus"...

so you request a feature like`postTranslation` https://kazupon.github.io/vue-i18n/api/#posttranslation right? as a hint it is easy to "decorate" req in an express based app and wrap existing methods like so (not tested):...

> ...you want to be sure that the strings are well standardized. Just a thought: Shouldn't this be a preProcessor before getting added to translation dictionaries rather than a postProcessor...

hm, not at the moment. I was hoping posessives will make it into messageformat. But didn't as far I see now. Let's keep this open as a reference + that...