Forum OpenACS Development: OpenACS 5.10: Portuguese translation
Unfortunately Portuguese idiom isn't much popular (at least, that I'm aware of it) in OpenACS community. Even though, I can contribute with pt_BR translation if, when and where (i.e. packages) is necessary.
Let me know how and in what pace I could submit those catalog xml files.
... of course, it is also possible, to add this later.
all the best -g
You may start working with Russian translation, while I'm working with the pt_BR
With these packages installed, I just checked the status of the pt_BR localization and it is not in a bad shape. Only roughly 33% of message keys are missing (1930 messages).
Russian is also not so bad, with around 42% missing translations (2438 messages).
A nice contribution would already be to complete all acs-* packages. You could also just localize any upstream packages you use in your projects. Other good candidates for localization are the xo* packages.
We will gladly massage any patch into the codebase!
In fact, I saw this list in your post regarding Italian translation. I grabbed everything from there, and got started already.
Don't worry. 5.10 shall be release with no delays. As per Gustaf's post, we can upload pt_BR translation anytime in the future.
Gradually, I'm going to share DIFFs (i.e. new catalog files) with you three.
Most of the i18n messages, I have created in customized pkgs. So, it will take a little while to move them to core pkgs.
One tool I have found very useful during my translations was https://www.deepl.com/translator. It normally gets you very close to the correct result and one only has to refine it (e.g. making sure that certain recurring terms in a package catalog are translated consistently, fixing gendering...).
Hope it helps
In the translation process, I use to work with Linguee, Google
Then, to learn meanings, and/or understand context and semantics, I visit https://www.dictionary.com/
Currently, I'm focused on writing a e-tool to speed up the translation from a custom package to a core package.
Some sort of a "two columns page", having all i18n messages listed in the left column (i.e. custom pkg), and core pkg in the right. Not sure yet, I'm still design it, even proving if that's achievable.
Concerning priority: i would say, first the openacs-core packages , then the packages from the 5-10 branch, and then others...