@ByteHamster I must admit that I donât really know/remember what the motivation is behind the Manage downloads section (I noticed it was not in my initial mock-ups). So I just invented a reason, but if you have any better text for it, please let me know (same for any other text).
I have not explicitly requested permission, if thatâs what youâre after. But given that the majority is open source and public broadcasters, combined with the fact that this is a one-off explainer and not standard promotional material (like the play store), I say itâs fine to use.
Will do a french translation before tomorrow evening if no else does it before. Didnât have much time before.
Is there a deadline?
I also think it doesnât matter too much if press release is not converted for all languages. Itâs often in news to have quoted info in English and the reviewer usually take excerpt and translate it. (Besides giving a link to the original source)
For the Google Play screenshots, a German public broadcaster denied my request to use their logo. Even a small science podcast told me that we can only show some of their episode covers because they already had problems with licensing. So for âofficialâ screenshots (and I think a blog post is quite official), Iâm a bit careful.
Not for now. We can only send it when v 3.0 is available on Google Play & F-Droid, and much depends on a) Googleâs approval process (which seems to take quite a bit longer for now) and b) the number of new types of crashes weâre getting back from the slowed roll-out. Weâll mention it when we have a deadline in sight
Journalists (like anyone of us I guess) prefer to be âlazyâ if they can be, so taking out one step in their process by providing a translation increases our chance of being picked up. But indeed, no need to get it in all languages. Based on this list of outlets that weâre trying to reach we identified FR, DE & IT as target languages for now.
Thatâs what I was saying: having your work (as a âneutralâ broadcaster) used in permanent promotion of a product (even if open source) is something else than being featured one time in a blog post or on social media in a product explainer. The exposure is much less (with it the chance of license issues) and the purpose/aim (with it the âdegree of associationâ) is (slightly) different. Therefore I think weâre safe here.
(Happy to include my personal name, in case anyone ever complaints or makes a claim about this graphic they can point to me.)
Has been a little challenging to keep it under approximately the same length and keeping it all.
I think itâs ok but feel free to comment of course ! I will myselft have a look back in 2/3 days to see if I am still satisfied ! AntennaPod releases home screen in new version - Fr.pdf (179.4 KB)
Hmmm I modified the extension to the docx files so I could upload it. And weirdly it seems to have stripped my added .pdf⌠Well it doesnât matter but maybe sharing that will be usefull to others (?) AntennaPod releases home screen in new version - Fr.docx.pdf (173.8 KB)
I mainly corrected some typos, and the part about the brand refresh which was not good enough. Didnât notice at first since as it uses a lot of words close in meaning refresh / update / evolution while keeping it short so it all still fit on one page. Miles better now.
Thanks a lot @Matth78!
I donât want to be annoying, but it seems you translated the version without the tracked changes. Following @loucasalâs feedback I cut it down a bit.
Can I ask you to check if you can see the tracked changes from this version? Maybe the tracked changes didnât come through with the software changes (I used LibreOffice but saved in docx format).
As usual, I tried to avoid translating too closely in favour of what sounded more natural in the target language.
@keunes When translating, I noticed a couple of other things (sorry for spotting them only now):
The term âpodcastingâ (both in IT and in EN) seems to refer to podcast creation more than podcast listening, so I wouldnât call AntennaPod a âpodcasting appâ in the title.
âPodcasting 2.0â is usually capitalised as far as I can see.
On the date at the start: I guess the press release would be binned as yesterdayâs news if it is dated too far in the past. I assume you will replace it in all languages when sending it out? Based on the discussion, it is an arbitrary date anyway.
I prefer to refer to apps used to listen to podcasts as podcatchers but I am not sure that is in popular use since the explosion of the platform amongst the public at large.
I stumbled over the word âStart-Bildschirmâ. Wouldnât âStartbildschirmâ be more common?
âEine weitere Ănderung, ist das aktualisierte App-Symbolâ Should there really be a comma?
âeine bessere Verteilung der Episoden wenn in der Warteschlange die intelligente Zufallswiedergabe verwendet wirdâ I think there should be a comma before âwennâ
I didnât have the same font, so libreoffice rendered it with the default one. It wouldnât be a problem for me to send the odt file, but Iâm not allowed to upload it.
Awesome, thanks! Sorry for not replying earlier. It seems weâre ready for the real release now - would you mind sending me the odf indeed? [username]@mailbox.org