|
|
Post by kimtisott on Jan 21, 2019 22:44:00 GMT -5
So I'd like to change the Simoleon symbol (§) to something else.
Thanks in advance.
|
|
|
|
Post by minimonster on Jan 22, 2019 9:41:06 GMT -5
Hi kimtisott. I have one bit of data and one idea of what may be needed to be accomplished - hopefully one or both will let you know the probable complexity of what you want to do. I looked through the 92,179 extracted files of .xml from the latest tuning of Get Famous. The .xml files ate formatted seemingly to be Unicode, so I used my favorite needle-in-a-haystack open-source search program - Astrogrep, and found the Simoleon symbol (§) in only 48 of those 92k files, and only in 54 instances. None of the files were of the more 'Global' kind that one would want to see to indicate that it would be an 'easy' task.What I suspect the case is that the § for global game-wide usage would be somewhere within the Python files, which is an area that I have so far avoided learning (but mean to someday...). I suspect that possibly the .py files may by Unicode as well, so that is some small comfort... I do not know if it is possible, but I think that this situation would require some sort of run-time injector to replace any instances of § as the game would call for the symbol. Urf... Cheers! |
|
|
|
Post by kimtisott on Jan 22, 2019 12:25:13 GMT -5
Hi minimonster. I managed to retrieve and decompile the EA python scripts. I couldn't find any '§' but I found a 167 (unicode number for §) in EA\base\lib\html\entities.py. There is some code definition for some words and their respectively unicode numbers so I guess you were right about that. § is called Section Sign and EA called it 'sect' in the file. Here's a snippet of the second line of the entities.py file. name2codepoint = { [...], 'sdot': 8901, 'sect': 167, 'shy': 173, [...] }There is no definition for '$' (36 in unicode), so I could create one. However it must be really time consuming to change all the script calls that use 'sect'. So my idea is to change the 'sect' number to 36, as in name2codepoint = { [...], 'sdot': 8901, 'sect': 36, 'shy': 173, [...] }Practically this would work, however I don't know how to compile this piece of code and make it work in the game. I might create another thread for this. |
|
|
|
Post by minimonster on Jan 22, 2019 15:21:02 GMT -5
Hi kimtisott. I am genuinely surprised that you went ahead and decompiled the Python scripts. That's dedication! Good on you for taking that initiative, which I am not even brave enough to try! So, since you seem to already know all of the right angles to try to crack this thing, the only other thing that I want to add, which is something that I had suspected but was unsure of, is that it appears that for the Python files, instead of parsing the Unicode character itself of the sect symbol in their code, what the above lines look like most to me is common CSS-based substitution of code to outputted character. I do not know if that is also apparent to you, but I wanted to mention it just in case... Thank You for sharing your discovery with us/me! It is a rare glimpse into the Python that I almost never get! |
|
|
|
Post by kimtisott on Jan 22, 2019 18:00:43 GMT -5
|
|
