3 replies to this topic

[Lollorian]

agb1's post brought to light something up with the CoM mods - they seem to have abandoned the non-EE versions and any new development/fixes are happening to the EE versions of the mods

 

Case in point:

Alora is v1.5 for both non-EE & EE but the EE version has some typo fixes

VampireTales is v1.03 for non-EE but v1.05 for EE with some bugfixes as well as typo bashing

 

Differences in EE & non-EE versions other than fixes?

The TP2 has the ToB check removed - Data/25Dialog.bif - for EE

All TRAs in the EE versions are in UTF-8 format while non-EEs are in Windows-1251 format

 

Why can't I just install the EE versions in non-EE?

Because non-EE can't read the UTF-8 format that the EE TRAs use, non-english installations will see garbage in their game

 

Now my question: How do you want me to handle this in the BWPFixpack?

Edited by Lollorian, 26 December 2015 - 12:28 PM.

[agb1]

Can iconv.exe convert from UTF-8 to Windows-1251 without messing up any symbols?  I don't quite understand how it works, but Item Revisions v4 somehow uses iconv to convert to UTF-8, so maybe the reverse is possible.

[Lollorian]

I've sent a PM to Raven in CoM - it should be simple to handle everything using WeiDU's HANDLE_CHARSETS but everything needs to be in Windows-1251 for it to work.

 

She was last active in October this year though so fingers crossed

[Creepin]

Because non-EE can't read the UTF-8 format that the EE TRAs use, non-english installations will see garbage in their game

Does that mean that if I chose english as a language for my BWS I am free to use EE versions of the mods even on overally non-english Windows? If not, will changing codepage to english as per Infinity Animations routine help?