gelst enforces icu on xercs-c. Since xercs ofers icu OR iconv as i18n, ist there any particular reason, icu is enforced? Is xerces-c's i18n api interface not stable against the choice of i18n backend? Reproducible: Always Expected Results: If glest needs i18n in xercs-c, it should be up to the user to decide which i18n he wants to use.
No, it forces either icu *or* -iconv -icu. Your choice, but it doesn't work correctly otherwise.
So, is this a broken in xercs-c then? Why would something work with icu fopr i18n, but not iconv? But then again without any i18n? Something sems to be broken.