rss and atom feed of l10n news show po file source
Move release notes back to the corresponding release announce page.
- copy them into monthly reports (that are rarely translated anyway,
so this won't waste translators' time; and it's useful to include
this information there, as reported about on
- salvage existing translations (only relevant for 1.7)
Release process: remove now obsolete bits about release notes as inlined snippets.
#2 Updated by intrigeri over 4 years ago
I just spent quite some time trying to fix that locally. I tried many combinations of:
inlinedirectives we've recently added on
- "translating" every such
inlinedirective into German:
- pointing it to the English page name (e.g.
[[!inline pages="inc/release_notes/1.4" raw="yes"]])
- pointing it to the German page name (e.g.
[[!inline pages="inc/release_notes/1.4.de" raw="yes"]])
- pointing it to the English page name (e.g.
None of those worked.
However, removing these three
inline directives fixed the problem for me. So, it looks like this chain of
inline (the one on
news.mdwn that generates the feeds, that pulls the ones from these 3 pages in
news/, that themselves pull content from
wiki/src/inc/release_notes/) is buggy with current ikiwiki. I can't say I'm very surprised: inline + po plugin have been fragile historically, and here we're pushing the limits a bit too far, maybe.
So, either someone fixes the bug in ikiwiki, or someone finds a workaround, or we'll have to remove these new inline directives, and deal with the duplication of content between release notes and monthly reports in another way.
#5 Updated by anonym over 4 years ago
So, either someone fixes the bug in ikiwiki
perl sucks too much for even considering trying...
or someone finds a workaround
... and my knowledge of ikiwiki is pretty shallow. I couldn't even had come up with the fixes you tried.
or we'll have to remove these new inline directives, and deal with the duplication of content between release notes and monthly reports in another way.
So this is the only thing what I could do, without much of a solution for how to deal with the translations in a sweet way. How much of a problem would that be? It doesn't look like our reports get translated much, and frankly the reports seems mostly targeted at people interested in Tails development, which require knowing English any way. Isn't copy-pasting the release notes an acceptable "solution"? Or just skipping that part, and just linking to any actual release's page.
Unfortunately, I feel like a poor match for actually solving the problem. :/
#7 Updated by intrigeri over 4 years ago
Isn't copy-pasting the release notes an acceptable "solution"? Or just skipping that part, and just linking to any actual release's page.
I think we need to remove all inlines introduced by e.g. https://mailman.boum.org/pipermail/tails-project/2015-June/000227.html, and same in all following monthly reports. There was an argument in this thread in favour of not merely linking, and at DebConf I've talked with at least one person who's reading our monthly reports and is happy to have the release notes in them, so my preferred "solution" currently is simply copy'n'pasting release notes into reports, and too bad if they won't be translated in the monthly reports.
#14 Updated by intrigeri about 4 years ago
- Assignee changed from intrigeri to sajolida
- % Done changed from 0 to 50
- QA Check set to Ready for QA
- Feature Branch set to bugfix/9671-no-inline-for-release-notes
sajolida, can you please review this and merge into master if you like it?
(You'll want to temporarily enable feed generation in
ikiwiki.setup in order to test it; anonym doesn't know these things much, which I bet explains why he didn't work on it in the past few months, so better have someone better skilled at ikiwiki craziness review my branch :)
I'm told that some people would like to resume work on monthly reports, and since we had inlines no such report was completed, which might not be a mere coincidence... hence my motivation today to fix this situation! Sorry I didn't revert this mess earlier..
#16 Updated by intrigeri about 4 years ago
Now that 1.8 and 1.8.1 have been released, more work is needed since these two release processes have followed the unpatched release doc. Do you want to do the forward-porting yourself? I can do it once now, if I'm confident the result will be merged before the 2.0 release process and thus I don't have to do it again in the future.
#17 Updated by intrigeri about 4 years ago
Now that 1.8 and 1.8.1 have been released, more work is needed since these two release processes have followed the unpatched release doc.
Add 1.8.2 to this list.
Do you want to do the forward-porting yourself? I can do it once now, if I'm confident the result will be merged before the 2.0 release process and thus I don't have to do it again in the future.
Ping? The more we wait, the more boring, useless forward-porting work will be needed.
You can also tell me that I should not block on you for this one any longer, and then I'll do the forward-porting and merge myself, and then you'll give it a look when you have more time :)
#20 Updated by sajolida almost 4 years ago
- Assignee changed from sajolida to intrigeri
Sorry for taking so long on this one. It's the kind of TODO that I've seen for ages in my agenda view but in the end even forget what it was about. I checked you're work, it's fine and I'm excited we get rid of this. I updated your branch for 1.8.1 and later. Please review again.