Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using gettext .po and .mo approach #1642

Open
3 tasks done
jlariza opened this issue Nov 28, 2023 · 0 comments
Open
3 tasks done

Using gettext .po and .mo approach #1642

jlariza opened this issue Nov 28, 2023 · 0 comments
Labels
Status: Proposal Request for comments

Comments

@jlariza
Copy link

jlariza commented Nov 28, 2023

Clear and concise description of the problem

Good day,

Although this library works great; it has some issues when using it:

  • there are no defaults values; if the key does not exist, it renders message.<key>
  • While programming, you don't know what the real message is because it sets only the key (e.g. message.hello vs the actual text Hello world)
  • Handling and managing the JSON file per language is complex in big apps with a lot of text

Suggested solution

Using the .po/.mo approach eases the process

  • you are able to define a default value for a translation (defaulting always to the actual text you wrote in the code)
  • you may actual check the text that is being added to the code
  • updating the .po file and then compiling it is a more natural approach and it may be handled in an easier way

Alternative

There is an external effort for this https://github.com/avast/vuei18n-po

it may be worth it to review that project and integrate it to this one

Additional context

No response

Validations

@jlariza jlariza added the Status: Proposal Request for comments label Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Proposal Request for comments
Projects
None yet
Development

No branches or pull requests

1 participant