How to change EPG "code page"

[sub]

FYI, your broadcaster is incorrectly encoding these strings though. The default for DVB unless otherwise specified is supposed to be ISO-6937. Instead your broadcaster is encoding the strings as ISO-8859-1. They can use ISO-8859-1, but they're supposed to explicitly mark the string as being ISO-8859-1, which they're not doing.

[hugo84]

Busy day today.
I made from scratch 2 ini files based on the ones that NextPVR provides itself.
I went to the path mentioned... c:\users\public\npvr-data\tuning but no such folder.
Then I used the dir command to search for folders named tuning and there are 2 matches.
One from c:\users\public\tscapture\tuning and C:\program files\nextpvr\data\tuning\dvb-t.
I choosed the 2nd path and I inspected the spanish ini files like the galicia. Simply enough. I checked that the ini file encoding is utf-8 but is weird that some filenames also have bad encoding like the í showing as an inverted !.
I started creating the "MEO Canais RF" or in English.. "MEO RF Channels".
I had to open the lastscan.xml created by tscapture, parsed the frequency tag, got the uniques, and it gave me 14 frequencies.
Then I created the "MEO - TDT"... TDT meaning Terrestrial Digital Television or something similar.
I had to check the channels and got the frequencies and I got from channel 30 to 48. They moved broadcasting channels to free the 700 Mhz band for the 5G tech.
Then I placed both files to c:\program files\nextpvr\data\tuning\dvb-t\ and for good measure, I stop/start the nextpvr service.
Then I went to the web gui, logged in, clicked settings, devices, dvb-t device (AF9015), cleared the channels, clicked scanning, I clicked the dropdown box and the entries from the 2 new files are there.
I selected "Portugal / Canais RF", clicked Scan, and it was fast. I didn't need to wait. It started searching from the 474MHz frequency and the next 13 frequencies. And I got the 126 channels.
Obviously some channel names still appear wrong agian.

[mvallevand]

These files won't help with the language decoding but the they should reduce the time it takes to scan as you noted,

The path I mentioned was for the language file I uploaded, the tuning files on Windows are with the program.

Martin

[hugo84]

Yes, I know but it will help when scanning.
I'm trying to delete the first zip file but I can't.

[hugo84]

Trying to following the posts now. I had a busy day.
Offtopic
Regarding, I discourage.. devs... from using Google Translate when translate things.
Because... It doesn't do a great job. When you tell Google Translate to translate from English to Portuguese, it outputs everything to Brazillian Portuguese, which is gibberish of the worst kind.
I've no idea why Google and other companies prefer a derived language instead of a native language.
We in Portugal do not like to eat such thing.
Bing Translate does a lil better job because it has Portuguese Portugal and Portuguese Brasil separated.
Brazil and other portuguese speaking countries tried to revise the grammar (again...for the 9999th time) and everything got worse.
The idea was to try to unify Portuguese of all countries but they did a big s...t...
Portuguese from Portugal and Portuguese from Brazil have too many differences.
I read the languages file and many things would need to be changed.
For example... The English word Delete... In Portugal is Eliminar. In Brazil is Exluir. "Excluir".."Exclude".. It doesn't put the idea of deletion but putting things to a side.
Or the English word File. In Portugal is Ficheiro (from french workd Fichier). In Brazil, is Arquivo. "Arquivo"..."Archive"... way or place to put files.
Brazil just took ideas from other languages and they made a bad mixture.
I can translate the language file you appended and reupload. It will take a couple of hours or less. It will depend of many changes I have to make.

[hugo84]

I loaded the language file to the path, edited config.xml. I had to reboot because of a update.
The App Ui is in fact translated to gibberish. Needs some retouches here and there... to fix context.
But I don't see no changes regarding channel names/descriptions.

[sub]

But I don't see no changes regarding channel names/descriptions.

Channel names, and show names/descriptions are fixed for the next release. There is no work around you can do (other than hoping your broadcaster starts doing the correct text encoding).

[mvallevand]

I loaded the language file to the path, edited config.xml. I had to reboot because of a update.
The App Ui is in fact translated to gibberish. Needs some retouches here and there... to fix context.
But I don't see no changes regarding channel names/descriptions.

It came from Google, it is meant as a start then a final solution, it takes me just a few minutes to get to this stage. The main point was to show that NextPVR.exe is rendering valid characters correctly.

For the channel name you can edit that yourself in NextPVR channel settings with the wrench.

The fact that the Linux version is working in 6.1.5 shows one reason why sub has been making big OTA EPG changes for the next version, there were too many combinations for him to manage issues like this easily.

Martin

[hugo84]

Yes, I know. I'm just pointing out that Google Translate isn't very good for translations.
Translation made by people is perhaps the best way to get the context right.

Meanwhile, I thought of trying to check if I have the same problem on Linux.
I created a VirtualBox virtual machine and installed Debian with Mate desktop.
Then I installed NextPVR.
I had some problems during installation like not having curl not being installed by default and _apt user having access denied (I had to sort that out by chmod 777 the deb file).
Then I launched the Firefox browser, entered the url and user/password. Settings, devices and.... the tuner wasn't there.
I clicked the usb icon of VM window to make sure the tuner was ticked.
lsusb sees it tuner but when I run sudo dmesg | tail, I see some errors. Hmm.. I forgot to check if the VM is using usb 1.1 or 2.0.
I know the tuner uses AF9015 but dmesg lists says its trying to use AF9035 and then I see mentions of i2c and checksum error.

[mvallevand]

The curl requirement is well documented on the forum an the wiki and fortunately the _apt_user error can be ignored.

VMs and USB devices can be tricky. Did you install sudo apt install firmware-linux-nonfree You can confirm if the tuner is working with ls /dev/dvb I wouldn't trust the BDA driver name in Windows though it could be a AF9035

I might just be easier to use this xmltv guide source http://www.xmltvepg.nl/rytecPT.xz until the next version of NextPVR comes out.

Martin