Re: [PATCH v2 0/2] MR2700: msxml3: Rename msxml3 to winexml and point msxml* to it.

[Loïc Rebmeister]

I think this commit is great as it will reduce the maintenance cost of the different `msxml*` dlls by unifying work.

If a version of a different `msxml*` act differently than the other version we can always do something like in `.spec` files:
```
@ stdcall -private DllGetClassObject(ptr ptr ptr) winexml.MSXML*_DllGetClassObject
```

But by checking: https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/msvcr120/Makefile.in

Moving all code to `msxml` and using `PARENTSRC` would seems to be more in line with what wine is already doing.

Either way is fine, the only thing that is sure is that splitting xml source work for each dll is not healthy, and code need to be cross merged in some way.

Using a `winexml` is more memory efficient, but using `msxml` + `PARENTSRC` seems more application compatible, either way is fine for me.

Also making `wine*` modules seems to become a recent common trend, see: https://gitlab.winehq.org/wine/wine/-/merge_requests/2298

@julliard I think you should make clearer guidelines about making `wine*.dll` modules, and proposing alternative to these modules in the guidelines.

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/2700#note_31956