xdvipsk sync with dvips needed

[kberry]

In 2024, the Japanese developers added some code for a new encoding for their upTeX engine. I think it would be highly desirable to merge that code into xdvipsk, so that we don't have two versions of the program going in different directions. I don't think it will be too difficult, since hopefully there are no clashes with your extensions.

In theory, I could imagine merging all your changes into base dvips, but I'm not sure how Tom (Rokicki) would feel about that. I could ask if you're interested in going that route.

Meanwhile, there are few enough changes that I can undertake to duplicate any changes in dvips into xdvipsk.

[sigto]

We' re trying to keep xdvipsk up-to-date with latest dvips updates. I need to review the latest code more accurately, but it might have been updated already. Are there any test data are available to check it?

I’m a bit unsure about merging the code in one direction or another. My concern is that xdvipsk isn't stable enough, still some development is active. Extension code review and cleaning would be a good idea. But after a year at least of using in TeXLive, it might be time to return to this question.

[kberry]

Indeed, may already be merged -- I see the current ``` #define MAX_VF_CODE 0x1000000 ``` in dvips.h. I didn't check beyond that, though. Yes, the JP devs did create tests for the latest changes, as noted in the ChangeLog. If you copy all the testdata/ and *.test files and add to Makefile.am, hopefully they will (eventually) run ok under xdvipsk too. Agreed that we don't need to worry about merging the whole directories for now. But can we start copying the ChangeLog entries when changes are copied over? I find that a lot easier to understand and match up than trawling through the endless vc logs. Thanks, Karl