Hi alan,
just realised that the output of 2.20 is having some issues.
1) the encoding string in the first line is blank.
2) The info from RT contains unicode accented characters which trip xmltv tv_sort.
The end result is the the file is not readable in SageTV.
Although I haven`t tried 2.19 yet, a user over in the Sagev forums stated that 2.19 works OK.
Ver 2.20 generates some issues in the xml file
-
- Site Admin
- Posts: 495
- Joined: Mon Sep 06, 2004 4:44 pm
1) there is a new option in the ini file for setting the output encoding to be put in the xml, it should default to iso but there seems to be a problem with many people getting blank encodings.
2) this problem has always been present since 2.0, the data is in win-1252 but is written as iso so some characters are invaid, it will be very difficult for me to fix this in the v2 code, it is fixed in v3 though
2) this problem has always been present since 2.0, the data is in win-1252 but is written as iso so some characters are invaid, it will be very difficult for me to fix this in the v2 code, it is fixed in v3 though