Hi Robert,
While the Xerces-C++ codebase notionally supports translation, I’m unaware of any translations ever having been publicly submitted or used in the lifetime of the project to date. So for the conventions indicated in the XML file, which were likely written many years ago, I wouldn’t treat them as hard and fast rules for a translation—there simply hasn’t been the need to revisit it or any experience with translations which influenced it. It’s not likely that the translation will work without some additional support work being done on the build system side, both for the CMake build and the Autoconf/Automake build. It’s currently set up to build the en_US translation, and anything new will need adding in. It might possibly need logic writing to support selection of the language; it’s quite likely untested and possibly incomplete. To complicate matters we currently support several alternative translation systems. I did suggest last year we should drop some of them to make this more maintainable. Kind regards, Roger > On 2 Jan 2021, at 16:48, Robert Hairgrove <evorgri...@hispeed.ch> wrote: > > I have built the latest version of Xerces-C++ 3.2.3 on Linux Ubuntu 18.04 LTS > and would like to translate the loadable message file "XMLErrList_EN_US.Xml" > located under "src/xercesc/NLS/EN_US/" into German. > > At the top of the XML file are some instructions which don't play well with > German: > > "(...) - All messages start with a lower-case letter (except where > a name is used as the first word) and do not have a period > at the end." > > Leaving a period (AKA "full stop") off of the string's end is OK. But German > language uses upper-case initial letters for all nouns, not just words at the > beginning of a sentence. Also, since many of the terms should be left in > English which refer to XML names, these should be enclosed in single or > double quotes since they are not German. > > Is this a problem? I don't want to go to the trouble of creating translations > for hundreds of strings only to discover that they cannot be used due to the > way they are processed after being loaded. > > (Or perhaps someone has already done this chore?) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org > For additional commands, e-mail: c-dev-h...@xerces.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
