Age | Commit message (Collapse) | Author |
|
(#31170)
* back-port from yt-dlp 8f53dc44a0cc1c2d98c35740b9293462c080f5d0, thanks pukkandan
* also support void, improve <</>> precedence, improve expressions in comma-list
* add more tests
|
|
|
|
|
|
|
|
The current logic in `js_to_json` tries to rewrite octal/hex numbers to
decimal. However, when the logic actually happens the `"` or `'` have
already been trimmed off. This causes what were originally strings, that
happen to look like octal/hex numbers, to get rewritten to decimal and
returned as a number rather than a string.
In practive something like:
```js
{
"0x40": "foo",
"040": "bar",
}
```
would get rewritten as:
```json
{
64: "foo",
32: "bar
}
```
This is problematic since this isn't valid JSON as you cannot have
non-string keys.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Despite visual similarity "þ" is unrelated to "p".
It is normally transliterated as "th":
$ echo þ-Þ | iconv -t ASCII//TRANSLIT
th-TH
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This fixes handling of non-UTF8 TTML subtitles
Closes #14191
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Used in Youku Show pages
|
|
|
|
Seen at http://zaq1.pl/video/xev0e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Used in daisuki.net (#4738)
|
|
|
|
|