Interesting approach, but it is a bit of all or nothing, eg there is no choice for a "normal" suffix with localized givennames.
Wouldn't it be in the line of how dbgen works to add sets of localalized givennames, family-names to pick from when generating an ldif ?

Usually pseudolocalization is all or nothing, yes.
Are you talking about some kind of mixed mode? When names will be picked at random from different sets of localized and non-localized strings? It's doable. We can go even further (what ratio of localized names, what attributes to localize, what kind of localization to use - accented, RTL, etc.) but that would make things a bit complex.

And in case of "normal" suffix we can add localized entries separately (for example using user module of lib389).

Recently writing a mr testcase, I had to use 2 UTF-8 ldif files. One containing the entries with localized attributes and one to create the mapping_tree/backend.
Indeed it would have help to create "localized" entries under a regular suffix.

And in case of "normal" suffix we can add localized entries separately (for example using user module of lib389).

ok, with the option of getting a mix by just localizing entries added this is ok for me.
will pseudolocalize() be available to tests to generate their own names ?

pseudolocalize() is in lib389.utils, so yes, it can be used by tests to convert strings.

THe patch looks good to me (and very useful thanks !). You have my ACK

Looks good to me! Thanks!

Why not always do this kind of localisation? It would be good to have dbgen "stress" more cases with complex charsets ...

To ssh://pagure.io/389-ds-base.git
003fa4d0c..b6c1221eb master -> master

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2589

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.