Replies: 1 comment 1 reply
-
I can't think of supporting such specific solutions for backwards compatibility with different implementations of different frameworks and libraries in a project like this. I think you could solve the problem by implementing your own translate/plural function :
However this might only work at runtime in any case, so you should put these translations in |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I've recently thought about how to reuse existing JSON translation files. The scenario is my work has 1 legacy project which has some translations and we would like reuse those for the new project with Qwik.
The problem is that, the existing JSON translation uses
|
for pluralization, for examplebanana: 'no bananas | {n} banana | {n} bananas'
andqwik-speak
doesn't know this way.Is it an idea that
qwik-speak
can provide option to define custom plural rules? For example similar like this https://vue-i18n.intlify.dev/guide/essentials/pluralization.html#custom-pluralizationOr any kinds of ways that we can use the same translation files for different projects like this case.
Beta Was this translation helpful? Give feedback.
All reactions