On Tue, Aug 10, 2021 at 04:08:04PM +0200, Thomas Corthals wrote: > Machine translation often does a better job with paragraphs because the > words are in context. Single word labels such as "Logging" are what gets it > confused because it can't always figure out if that's about log files or > felling trees. > > Op di 10 aug. 2021 om 15:27 schreef Dave <hastings.recurs...@gmail.com>: > > > Gotcha, I don’t know Russian so I didn’t know that. the admin ui has very > > limited English to translate there aren’t paragraphs, unless you want the > > results translated, otherwise it’s pretty straight forward I would have > > thought
That makes sense, but the first issue is going to be: was the code written to be localizable? It sounds to me, from a previous post, as if the answer is "no", though the UI kit seems to support it. To make code localizable, you first have to internationalize it. That means moving every scrap of user-visible text to a message catalog. Every button label; every error message; many link bodies; every bit of explanation. Otherwise, every translator will have to hunt down all of these places, and that takes a skill set rather different from those involved in translation -- people who are good at both are not common. Once you have all the text in a catalog, translation mostly involves reading one catalog and writing another. Upgrading starts with listing the changes in one catalog and making corresponding changes in another. That is much easier than trawling through code looking for things that might have changed. Machine translation *may* help. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu
signature.asc
Description: PGP signature
