Github messages for voidlinux
 help / color / mirror / Atom feed
From: TeusLollo <TeusLollo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: VLSub not automatically loading subs
Date: Sat, 15 Jul 2023 16:08:25 +0200	[thread overview]
Message-ID: <20230715140825.0-BTZYWv91jIegweCQk7V-5Ewi4lEs__hlvp1ZGx9vY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45045@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/45045#issuecomment-1636778878

Comment:
I'm not a VLSub user, but:

1) Is this the issue you're facing?: https://reddit.com/r/VLC/comments/phwhau/vlsub_0111_not_working/

2) In the same thread, user Radio-Lisboa suggests the following:

_opensubtitles API has changed its request format from XML to JSON only. In adiction it also needs a session token to validate requests. So, in a few words, VLSub needs a re-work to replace the old function, to call the API with a valid token and process JSON data_

_EDIT: But, there's a workarround for this. As the previous version of opensubtitles is still working, you can edit your system hosts file to route VLSub call as XML. The default path of the hosts file in Windows 10 appears to be C:WindowsSystem32driversetc and you have to open your text editor as admin to edit the file. Add a new line and type 104.25.132.104 api.opensubtitles.org Save hosts file and try VLSub again. NOTE: This is valid while XML service is active in the old API address_

Of course, this workaround was meant for windows. Maybe other distros have applied patches on their own, which is why VLSub fails on Void Linux?

3) Where did you get vlsub 0.11.1? https://github.com/exebetche/vlsub is stuck at 0.10.2, and https://addons.videolan.org/p/1154045/ is at 0.10.0. I could find a pull for 0.11.0 at https://github.com/exebetche/vlsub/pull/223/files but it went unmerged. 

  parent reply	other threads:[~2023-07-15 14:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 21:42 [ISSUE] " gorecki3
2023-07-15  3:18 ` gorecki3
2023-07-15 14:08 ` TeusLollo [this message]
2023-07-16 16:09 ` gorecki3
2023-07-16 16:10 ` gorecki3
2023-07-17 20:41 ` TeusLollo
2023-07-18  0:06 ` gorecki3
2023-07-18  1:26 ` TeusLollo
2023-07-18  1:28 ` TeusLollo
2023-07-18 12:40 ` gorecki3
2023-07-18 12:42 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 13:10 ` TeusLollo
2023-07-18 13:10 ` TeusLollo
2023-07-18 21:37 ` gorecki3
2023-07-18 22:06 ` gorecki3
2023-07-18 23:30 ` TeusLollo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230715140825.0-BTZYWv91jIegweCQk7V-5Ewi4lEs__hlvp1ZGx9vY@z \
    --to=teuslollo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).