Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#12999 closed Bugs (Fixed)

(Nightly) XML character codes visible in UI and scrapers

Reported by: Voyager-xbmc Owned by:
Priority: 4 - Normal Milestone: 12.0 "Frodo"
Component: Other (un-categorized if does not fit anywhere else) Version: GIT
Severity: Normal Keywords:
Cc: jmarshall, amejia, Blocked By:
Blocking: Platform: All
Revision:

Description

Since the TinyXML update (4226619109d0) xml escaped character codes are visible everywhere, at least for accentuated characters, quotes, etc. No logs are supplied, but I used the May 6th nightly to makes some screenshots. See attached.

Attachments (3)

screenshot000.png (412.0 KB) - added by Voyager-xbmc 3 years ago.
screenshot001.png (468.3 KB) - added by Voyager-xbmc 3 years ago.
screenshot002.png (437.5 KB) - added by Voyager-xbmc 3 years ago.
here it should say "Geïnstalleerde"

Download all attachments as: .zip

Change History (11)

Changed 3 years ago by Voyager-xbmc

Changed 3 years ago by Voyager-xbmc

Changed 3 years ago by Voyager-xbmc

here it should say "Geïnstalleerde"

comment:1 Changed 3 years ago by Voyager-xbmc

sorry to bump, any chance this will be looked at during the may merge timeframe?

comment:2 Changed 3 years ago by jmarshall

Apology not accepted :p

Merge windows have nothing to do with bugfixing.

comment:3 Changed 3 years ago by Github Janitor

  • Resolution set to Fixed
  • Status changed from new to closed

Fix issue where parsing XML character entries are ignored. Fixes issue #12999.

Changeset: da85867e59d0ebbc02360a0711ac3c362a6d0156 By: Andres Mejia

comment:4 Changed 3 years ago by jmarshall

  • Milestone changed from Future / Pending to 12.0

comment:5 Changed 3 years ago by Github Janitor

Fix issue where parsing XML character entries are ignored. Fixes issue #12999.

Changeset: 565c88f1e7126e1819d9caac55a346c5e6b3dbe0 By: Andres Mejia

comment:6 Changed 3 years ago by Voyager-xbmc

seems to be only fixed for hexadecimal notation. Decimal xml character codes are still not parsed correctly.

comment:7 Changed 3 years ago by sho

Same issue as #13059?

comment:8 Changed 3 years ago by Voyager-xbmc

@sho - yes that's the reason for putting the comment here, so that the cc'd people would notice that this is to be reopened for add'l fixes.

Note: See TracTickets for help on using tickets.