Support for non-ANSI systems

Why not...

I don't think it's a question of why anymore... but more of a when various people have the time and patience to upload 1(2+ in archives) GB's files and a compatible BGMain.exe patch series... with Miloch being rip apart in various other projects etc.

 

AKA, if you can make the .exe patch so that we can use the normal ANSI letters in the animation letters, you are more than welcome to remake the v5 beta of the install file, and thus fix this issue completely.

Sorry I've been too busy to check up on this until now but yeah, what Jarno said. Erephine in fact already changed the code to enable normal ANSI prefixes that we both agreed on. I just haven't had the time to update the patch, the tp2, the archives etc., and there will be a huge amount of work for EE compatibility, which will be totally different, and which we are in fact working on right now, so I'm waiting until there's a finalized schema for that before getting back to this. Yes, the current mod can pose a problem for non-European systems, but apart from that, it seems fairly stable, so I don't know if we want to introduce variants and more complexity to an already complex scheme if folks can just be patient a bit longer.

, ...if folks can just be patient a bit longer.

Erhm, would you consider allowing pro5 to have access to the "files being worked on", cause I am pretty sure he could... you know... do most of the work for you... without him needing to wait at his end and all. Yeah, I know you are busy guy and all ...

Erhm, would you consider allowing pro5 to have access to the "files being worked on", cause I am pretty sure he could... you know... do most of the work for you... without him needing to wait at his end and all. Yeah, I know you are busy guy and all ...

I'd already offered to pawn it off on him if I can collect everything together. I have no issue shifting work to him given what I had to go through with P5 Tweaks when pro5 disappeared.

1) I wonder if we can use "chcp 65001" or "chcp 437" (en-US) for the part when IA are installed and skip OS codepage changes.

 

2) Can I check this via filenames or maybe I need to load some map with creatures that use one of the new animation with problematic file?

1) Well the chcp is likely to be the 850(Latin I) instead of the 437(en-US), there probably is no difference in InfAnim... but anyways you need to also make the switch back after the InfAnim... and that could be tricky.

2) Well, you should be able to sort the compatibility via the override folders file content. Say for example, you make an install with the codepage 1252 on one install(just the base game, BG2 Fixpack, Infinity Animation and one of the addon archives ), and then another using your trick above, and then use a diff comparison of the two Override -directories. There should be no difference, so add one non game file to one of the directoies to make sure the diffing works.

Edited by The Imp, 11 August 2014 - 09:32 AM.

I have to know how I can check that IA was installed properly using my trick. 
 
Can I check this via filenames or maybe I need to load some map with creatures that use one of the new animation with problematic file?

I once was wondering too whether IA installed correctly, and I've got cool advice on how to quickly check it here. You could either follow it to the letter, or, if you've already installed IA content packs, skip to the step where you're changing PC animation.

P.S. Oh god, could it finally be so that I won't have to struggle with codepage each time I'm reinstalling BWS? Truly blessed times!