XML Parsing Error - not well-formed (invalid token) at line 1

Imperialism32 · 07-04-2016, 07:39 PM

Hey guys,

I'm re-writing my 16-team schedule so I started from a working file, but I've tried this twice and I'm getting that same error both times. I've attached the file, it would be great if someone could take a look and see what's wrong.

Thanks!

joefromchicago · 07-04-2016, 10:09 PM

Here's your first problem:

type="ILY_BGN_G150_SL1_D1_T4_D2_T4_SL2_D1_T4_D2_T4 _C_neu3"

The manual doesn't spell it out, but you can't have anything after the C_ in the schedule type line. You can have that in the file name, but not in the file itself (yeah, weird right?). That problem, however, prevented you from seeing all of the "smart quotes" in your file that would have also prevented the schedule from loading.

The easiest way to track down errors is to open the schedule file in Notepad++ or some other application that gives you line numbers, so you can match them up to the error message in OOTP. For your convenience, I've attached a corrected file. It works.

neu3.lsdl

Ruwisc · 07-04-2016, 11:34 PM

I've found that the thing I screw up in a schedule every time, without fail, at least once is that formatting.

Instead, what I do now is to have the game generate its own schedule, and then export it to a new file. I can then just copy the format from that schedule onto my new one and it'll always work how it's supposed to.

Imperialism32 · 07-05-2016, 06:25 AM

Quote:

Originally Posted by joefromchicago

Here's your first problem:

type="ILY_BGN_G150_SL1_D1_T4_D2_T4_SL2_D1_T4_D2_T4 _C_neu3"

The manual doesn't spell it out, but you can't have anything after the C_ in the schedule type line. You can have that in the file name, but not in the file itself (yeah, weird right?). That problem, however, prevented you from seeing all of the "smart quotes" in your file that would have also prevented the schedule from loading.

The easiest way to track down errors is to open the schedule file in Notepad++ or some other application that gives you line numbers, so you can match them up to the error message in OOTP. For your convenience, I've attached a corrected file. It works.

Attachment 461006

Thanks a lot!

07-04-2016, 10:09 PM	#2
joefromchicago Hall Of Famer Join Date: Jun 2011 Posts: 3,630	Here's your first problem: type="ILY_BGN_G150_SL1_D1_T4_D2_T4_SL2_D1_T4_D2_T4 _C_neu3" The manual doesn't spell it out, but you can't have anything after the C_ in the schedule type line. You can have that in the file name, but not in the file itself (yeah, weird right?). That problem, however, prevented you from seeing all of the "smart quotes" in your file that would have also prevented the schedule from loading. The easiest way to track down errors is to open the schedule file in Notepad++ or some other application that gives you line numbers, so you can match them up to the error message in OOTP. For your convenience, I've attached a corrected file. It works. neu3.lsdl __________________ American-Ethnic (and Canadian) Namesets Historical Minor League Schedules 1870s City/Team Nickname Randomizers "It's Usually Sunny in Philadelphia" weather mod

07-04-2016, 11:34 PM	#3
Ruwisc All Star Reserve Join Date: Jul 2013 Location: Southwestern Illinois Posts: 610	I've found that the thing I screw up in a schedule every time, without fail, at least once is that formatting. Instead, what I do now is to have the game generate its own schedule, and then export it to a new file. I can then just copy the format from that schedule onto my new one and it'll always work how it's supposed to.