plk

@pripple - any time to look at these suggestions? We would like to get this resolved.

The multiscript code was never in a released version and was in a separate git branch but it is currently in limbo and hasn't been updated in a long time...

It's not so much anything to do with the data source format (biblatexml has had a lot of work for version 3.4 which will be released soon) but the internals...

It's exactly point three you mention that made me think that the last PoC I did of this was not the right way - it got extremely complicated and ugly...

I would need to experiment a bit but essentially, any name parts defined by `\DeclareDatamodelConstant[type=list]{nameparts}{ ... }` are available to names. This doesn't really address the multi-script requirement though. The...

You need to use `--input-format=biblatexml` on the second run. I suppose I could auto-detect this from the filename extension.

@u-fischer - I have added an extended name format for bibtex data sources when using biber. It allows you to specify the name parts explicitly and you can mix and...

Actually, you are right about the bibbiblatexml round-trip. There is currently no support for biblatexml->bib, only bib->bib. EDIT: See below, this is now possible - tool mode can now convert...

This could be helpful when I get time to look more into it. The new name format you mention is already in bibaltex 3.5/biber 2.6 development versions (on sourceforge) and...

@moewew - yes, that's important. It should work now for per-namelist and per-name scope in bibtex datasources - see the biblatex doc on `\DeclareSortingNamekeyScheme`. I agree about biblatexml - until...