Jump to content
Sign in to follow this  
tim copperfield

Non-ASCII channel names in "Channel List Editor" turn into ???'s after editing

Recommended Posts

tim copperfield

Basically the title, and probably related to the other post about timers.xml saving as ASCII.


How to reproduce:


1) Open channel editor

2) Select channel by keyboard or mouse

3) Press F2 to edit channel name

4) Copy/type in ช่องทำอาหาร or anything else not ASCII


What happens:

Text is replaced with ? or .


What should happen:


Entered text should remain


Share this post

Link to post

Fixed in DVBViewer Pro 6.0.4 (just released). :)


However, that won't help permanently because the ??? will reappear after closing and re-opening DVBViewer. You already know why.

Share this post

Link to post
tim copperfield
27 minutes ago, Griga said:

Fixed in DVBViewer Pro 6.0.4 (just released).


Hopefully these fixes will eventually turn permanent, including saving.


It shouldn't even be that hard, have a pref to save as CP_ACP (whatever the current non-unicode locale is) or as UTF-8 w/correct XML header. Those who rely on broken add-ons that expect ASCII could leave this off.

Edited by tim copperfield

Share this post

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • tim copperfield
      By tim copperfield
      When recordings are scheduled, timers.xml (%programdata%\CMUV\DVBViewer) state is saved as encoding="iso-8859-1".
      This prevents any international (Arabic, CJK, Thai, etc) filenames from being recorded if DVBViewer is shutdown and re-opened.
      Any non-iso8859 characters are replaced with "?". and turn into " " (space) in recording filename as a result.
      If DVBViewer is continuously running (not shutdown between recordings) then the filenames are correctly written as they appear on EPG.
      Solution: change timers.XML encoding to utf-8