Henning von Bargen

I don't know if the problem I described actually exists. Certainly not on our machines which are configured as German or English. But who knows which Collator configuration `getInstance()` returns...

I still believe a clean solution would be to perform comparions in the same way the Table item does. And I still believe it is risky to change such a...

BT-149 is mapped to two elements (ram:BasisQuantity). BT-150 is mapped to the unitCode attribute only for ram:GrossPriceProductTradePrice/BasisQuantity. The EN says on p.50 that BT-150 should be mapped to /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem/ram:SpecifiedLineTradeAgreement/ram:GrossPriceProductTradePrice/ram:BasisQuantity/@unitCode and...

> To use these, simply provide a sample dataset containing names that start with accented characters (e.g., Ágatha or Ágnes), bind it to the report, and ensure the columns match...

I see. I tested this with Germany instead of Portugal and can confirm this issue. Looks like a bug to me. In particular, the locale settings seem to be completely...

Just want to say that I know this kind of problem from other software as well (e.g. from Oracle, at least with older releases). I don't know how to fix...

Well, this is a change in behavior. In theory, this might be a breaking change, because the output sorting sequence has changed. But for me, I would consider this a...

This is somewhat concerning, but obviously no one really complained about it in 15 years. Using the default Collator is still much better than using no Collator at all. So...

Did you try e.g. adding a blank to the SQL statement, to force BIRT to parse it again? I mean it is strange that the error message mentions a column...

Shouldn't we discuss if we allow AI PRs, and if so, how to deal with them? I'm not against AI usage in general, but I fear that sooner or later...