[
https://issues.apache.org/jira/browse/XERCESC-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132685#comment-17132685
]
Roger Leigh commented on XERCESC-2204:
--------------------------------------
In practice, most distributions providing Xerces-C++ are using "inmemory" since
it's the simplest and has no additional external dependencies, and it's
platform-independent.
In the first instance, we could drop the "icu" and "iconv" message loaders
without any loss of functionality, and retain "inmemory". We could do this in
two steps: (1) change the CI to inmemory across the board to check it's not
breaking anything and then (2) remove the "icu" and "iconv" configuration
options and supporting code.
If we wanted to, we could later drop the translation machinery entirely, but
the above would be noninvasive and simple.
> Remove message loader
> ---------------------
>
> Key: XERCESC-2204
> URL: https://issues.apache.org/jira/browse/XERCESC-2204
> Project: Xerces-C++
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 3.3.0
> Reporter: Roger Leigh
> Assignee: Roger Leigh
> Priority: Major
> Fix For: 3.3.0
>
>
> We support several different message loaders (inmemory, icu, iconv).
> However... we don't have any translations to actually warrant all this
> complexity, and likely never will. We have the basic en_US and that's it.
> So this code is essentially unused, and I don't see much prospect of it being
> used in the future given that there have been zero translations written in
> the last two decades.
> In order to reduce the size of the test matrix and reduce the maintenance
> burden, I'd like to ask if this is something we could safely drop?
> See also XALANC-808 which is the same issue for Xalan-C.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
