Translations using gettext instead of csv? about gozen HOT 2 CLOSED

I have been experimenting with the pot file system today. It is great that I can generate them very easily by just selecting the scene. But it gets quite confusing from that point onwards. There won't be too many translations needed for this project so I'll stick with my YAML to csv approach for now whilst I learn more about gettext which will probably take some time. I don't want to switch the systems I use from one day to another.

At this moment we use YAML to get over the limitations when using csv with git. This approach may change in the future, to gettext or to a solution which would be easier for people to contribute to. However, YAML is quite easy and user friendly which makes it also very useful for people to contribute, this will change however as soon as we start having many more and more languages and keys.

So far there is also nobody in the team of contributors with gettext knowledge, which makes transitioning to that system a lot more troublesome/difficult. Updating pot files in Crowdin also removes the previously made adjustments to the context part (this is probably by design?). Right now I use clear keys which define what's a title, a popup, ... and that is within the key name. For pop files it takes the original string in English, which I think makes it more complicated for translators to know what a correct translation could be.

But I see your point, the moment that this project would grow, using something standardized such at gettext could be beneficial so I will think about it and test it out every now and then. I have a busy schedule so testing this could take time. Thank you for bringing this to my attention and taking your time to write this.

from gozen.

Thank you for submitting your first issue to GoZen! We appreciate the time you take to do this!

from gozen.