Special characters in almanac

[lnpgaceta]

(Whoops, not almanacs—league reports.)

First: very sorry if this has been covered already. I ran through most of the forum last night, but I may have missed a thread.

After OOTP 21 broke the ability to recognize special characters in logo files, this one appears to have some trouble with special characters (accents, tildes, etc.) in player names . . . but only in the reports. (See Screenshot #1.) The accents show up fine in the game.

Everywhere I could find that has a "replace accents" option has it checked—and anyway those are CSV files, not reports. I'm also currently generating an almanac, and they look fine there so far.

Then this morning I noticed that it's even doing that with the "1/2" display for teams that are half a game back, which, frankly, looks pretty silly. (See Screenshot #2.) It is also doing this in the sim. (See Screenshot #3.)

Is there a fix for this that doesn't involve me going and manually removing the accents from each player's names, which I would really rather not have to do, considering the league is set in Puerto Rico?

UPDATE: if this helps, I've been informed that, apparently, adding <meta charset="UTF-8" /> to each HTML file seems to fix the problem, though I have not yet verified it.

[Lukas Berger]

I don't believe there's a fix for this at the moment, that I know of. Fixing things up with accented characters is defiantly on our to do list. We've actually made quite a few improvements here over the last year or so in the code, but there's still some more to do.

[lnpgaceta]

Originally Posted by Lukas Berger

I don't believe there's a fix for this at the moment, that I know of. Fixing things up with accented characters is defiantly on our to do list. We've actually made quite a few improvements here over the last year or so in the code, but there's still some more to do.

Admittedly, I only just migrated to OOTP 22 a couple days ago. Has this been a problem since 22 came out?

I ask for two reasons: one, my league did not have this issue with reports in OOTP 21, and two, I recently got said league hosted, and that’s how I found out that this was becoming a problem for other people, but it seemed to be of pretty recent vintage—I adduced that it was on the more recent side, but on the other hand, sometimes it takes a while for people to notice.

I have no problem telling people to go check out the almanac instead until the issue is fixed, but considering that takes forever to upload, I can only do it once a week or so.

Lastly, I appreciate your attention to this problem; I know there’s a lot of other stuff to worry about.

[Lukas Berger]

Originally Posted by lnpgaceta

Admittedly, I only just migrated to OOTP 22 a couple days ago. Has this been a problem since 22 came out?

I ask for two reasons: one, my league did not have this issue with reports in OOTP 21, and two, I recently got said league hosted, and that’s how I found out that this was becoming a problem for other people, but it seemed to be of pretty recent vintage—I adduced that it was on the more recent side, but on the other hand, sometimes it takes a while for people to notice.

I have no problem telling people to go check out the almanac instead until the issue is fixed, but considering that takes forever to upload, I can only do it once a week or so.

Lastly, I appreciate your attention to this problem; I know there’s a lot of other stuff to worry about.

Well, that's a good question actually. I am not sure how long this specific issue has been around, I just know we still do have some weirdness with accented characters crop up from time to time. It might be that this did work in 21 and something broke at some point. Probably no way to really tell until whenever we get a chance to take a closer look at this.

[lnpgaceta]

Originally Posted by Lukas Berger

Well, that's a good question actually. I am not sure how long this specific issue has been around, I just know we still do have some weirdness with accented characters crop up from time to time. It might be that this did work in 21 and something broke at some point. Probably no way to really tell until whenever we get a chance to take a closer look at this.

It gets better—I just updated the almanac overnight, noticed the characters were off again, and went to check.


The same file displays with the special characters just fine on my computer (should be the screenshot on the left), but not when uploaded to the server where I've been hosting it (screenshot top right), which suggested it was a browser-side issue.


So I tried the fix suggested to me—adding <meta charset="UTF-8"> at the start of the file—and it worked. (That's the screenshot on the bottom, which should look almost identical to the one above it, and which is here.) I'm not a super-experienced HTML editor, but I did notice that there's already something in the head of the file that's supposed to do that. Just doesn't seem to be firing.

[Huckleberry]

Got here from your reply to my post in the cosmetic thread. Thanks for your help, the head_bits.tpl change fixed it for me. But I'm going to start a thread on the "Replace accents" setting for CSV exports not working. As Lukas said, there's quite a bit of work on special characters to be done. I get what's shown in the attached image during report generation.

It's a bit strange that these things used to work and now don't, but I understand unintended consequences with seemingly unrelated coding changes can pop up.

[lnpgaceta]

Originally Posted by Huckleberry

Got here from your reply to my post in the cosmetic thread. Thanks for your help, the head_bits.tpl change fixed it for me. But I'm going to start a thread on the "Replace accents" setting for CSV exports not working. As Lukas said, there's quite a bit of work on special characters to be done. I get what's shown in the attached image during report generation.

It's a bit strange that these things used to work and now don't, but I understand unintended consequences with seemingly unrelated coding changes can pop up.

I noticed that as well, and I'm glad I'm not the only one who did. I know this is very much a minor issue compared to the totality of the game, and maybe it'll turn out to be a much more massive headache than I imagine it is—but at the same time, one of the things I absolutely love about OOTP is the inherent global approach it takes to baseball, so this is very near and dear to my heart.


Glad to hear that helped, though!

[Recte44]

Following, I’m having this issue also


Sent from my iPhone using Tapatalk

[Recte44]

Any chance this will get fixed soon?


Sent from my iPhone using Tapatalk

[Lukas Berger]

Originally Posted by Recte44

Any chance this will get fixed soon?


Sent from my iPhone using Tapatalk

I wouldn't think terribly soon, no. It's relatively low priority and we're super busy at the moment, especially Andreas who would likely be the one to have to fix this.