Ootte ihania! (*^‿^*)

Summary

Release v1.47.2 was mentioned in another issue’s comments, and Play Store version has indeed been updated, but that release is missing from Github releases.

Steps to reproduce

Open Github releases page for the project.

Expected behavior

Find release v.1.47.2 (or later).

Observed behavior (that appears unintentional)

The current latest release on Github is 1.47.0.

Possible fixes

I don’t know if it’s related, but v.1.47.0 has been tagged ”changeme” instead of the usual vX.Y.Z pattern.

Emme ole rengasvastaisia, vaan *rengaskriittisiä*.

Okay, I can appreciate avoiding extra trouble for others, and it’s certainly easier for me to add the workaround translation for just this one case. I’ve now done that (with your suggestion, which was probably as good as this can be).

%{month_name} %{year} would work better for Finnish, as that would allow the month name to be inflected apart from the year (which is how the current accepted translation of this string was intended to work). OTOH, the Finnish way a ”month name + year number” combination in inflected in most, if not all (relevant) cases is like that: add a suffix to the month name, leave the year number as-is. Without workarounds, %{month_year} generally only works for the nominative case.

”Monthly Supporter since December 2018” would be ”Kuukausittainen tukija joulukuusta 2018 lähtien”, where ”joulukuu” is the month name (and the current translation for that string doesn’t correctly account for the inflection either). Finnish has 6 different locational cases alone, so yeah, Finnish inflection can be a pain :)

I’ve only come across this title string (%{taxon} from %{place} in %{month} by %{user}) on an observation page where the date is obscured to month, whereas the (more usual case of) title for non-obscured observations has already been translated to work around the inflection. Although the latter makes for varyingly clunky Finnish, at least it’s technically not incorrect, and hence that’s how the problem is usually worked around in Finnish software translations. I can figure out a similar workaround translation for this string too (that is, take your option b).

I’m still confused by the source string here using %{month}, which then gets turned into %{month_year}, requiring translators to pay attention to the explainer text in the reference, instead of just using %{month_year} in the source directly.

All right, I got curious enough try again, and found that this is apparently caused by the static build of ffmpeg that I’m using: I used yle-dl --verbose again, then interrupted the download immediately, ran the ffmpeg command (as reported by yle-dl) directly, and this resulted in a segmentation fault.

I then tried the same command in a VM with ffmpeg from Ubuntu repositories, and there the download finished successfully.

So the only remaining issue with yle-dl in this is the terminal being broken: that did not occur with directly-run ffmpeg despite the segfault.

I’m closing this issue though, so that it remains as documentation for the problem (and cause) as originally reported.

For some reason, instead of the %{month} here, a %{month_year} is shown instead, at least when it comes to <title> elements. So for instance, an observation from July 2020 currently has the <title> rendered as ”heinäkuu 2020ssa”, when it should be ”heinäkuussa”.

Trying to download this 7-hour long program only downloads (about) the first 6 hours and 40 minutes (~ 11 GB), after which the process just stops, and leaves Gnome terminal screwed up (typed characters are invisible until I run reset). In the web player the video seems to play past that point just fine.

This is on Ubuntu 20.04 with ffmpeg version N-58594-g715f63232f-static (static build from git master on 20210908).

jani@saegusa:Työpöytä$ /usr/local/bin/yle-dl 'https://areena.yle.fi/1-50934704'
yle-dl 20210808: Download media files from Yle Areena and Elävä Arkisto
Copyright (C) 2009-2021 Antti Ajanki <antti.ajanki@iki.fi>, license: GPLv3

Unsupported codec with id 98313 for input stream 2
Unsupported codec with id 98313 for input stream 5
Unsupported codec with id 98313 for input stream 8
Unsupported codec with id 98313 for input stream 11
Unsupported codec with id 98313 for input stream 14
Unsupported codec with id 98313 for input stream 17
Unsupported codec with id 98313 for input stream 20
Unsupported codec with id 98313 for input stream 23
Unsupported codec with id 98313 for input stream 26
Unsupported codec with id 98313 for input stream 29
Output file: YleX Esittää: Yle 95 - synttäribileet Linkkitornista: 2021-09-18T00:00.mkv
jani@saegusa:Työpöytä$  size=10814976kB time=06:39:40.68 bitrate=3694.5kbits/s speed=  44x

Note the prompt appearing on top of ffmpeg output on the last line. Typing echo $? reveals that the process exited with code 1.

Here’s the output when run with --verbose.

I’ve only tested this over the past couple of days so I don’t know if it’s a temporary error. Since the portion of the stream that I actually care about is all prior to the 6-hour mark, and the partial download is playable, I’m not too bothered to have the rest download. Reporting this just in case it’s a useful test of a corner case.

Also, I tested the 94.0a1 nightly now, and the issue is still present.