-
Notifications
You must be signed in to change notification settings - Fork 23
Improve site-readiness for translations #112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few things I noticed when skimming (not a detailed review yet)
Hi @MichaelCurrin |
Hi @ByteHamster Did you still want to have a look? I'd like to merge it soon so this is out of the way :-) I've received help from an expert and it runs smoothly locally and on Netlify, so I'm comfortable also merging this without your review. If we want a cleaner history, everything but b2574f7 could be squashed. |
Thanks again @ByteHamster for the feedback!
It's a sub-page in the documentation. If for every update we ever make to the documentation requires a redirect, it might get a rather long list. I think such not-prominent pages do not deserve redirects.
The localised file has I just discovered that there's a 'bug' in the menu rendering: the forum URL is prepended by the localised site URL. Once that's fixed as well, I'll commit the changes. |
Ok, changes committed :) |
{% include image.html | ||
alt=" | ||
<!-- mdpo-enable-next-line --> | ||
devices | ||
|
||
" | ||
loc="/assets/images/documentation" | ||
file="gpodder-devices.png" | ||
%} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm this is indeed quite a bit of text. Would it be possible to only include the URL, not the full image? Or does that add whitespaces? Then we do not need the mdpo enable/disable code.
Something like:

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Downside is that there's a bigger chance that translators mess up, as they see the whole code rather than only the translatable text. Not sure whether risk of translators making a mistake is smaller/bigger than site code contributors. So I can change in line with your suggestion :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works but the URLs must be captured first, otherwise the images don't work, indeed due to spaces:
{% capture GP-url %}{% include image-url.liquid folder='badges' file='get-it-on-google-play.png' %}{% endcapture %}
[<img alt="Get it on Google Play" src="{{ GP-url | strip }}" height="80px"/>](https://play.google.com/store/apps/details?id=de.danoeh.antennapod)

full image | url only | |
---|---|---|
capture | only when code otherwise becomes hard to read and in lists | always |
translators | deal only with text to translate | see & have to copy md tag (html tag on download page) |
code complexity | more (particularly in md files) | less |
I'm inclined so use both includes: one for more full html image tags with class & size, one for url-only for md image tags.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, having two different includes could be more confusing than helpful for contributors. I would say let's just keep it the way it is now :)
This pull request has been mentioned on AntennaPod Forum. There might be relevant details there: https://forum.antennapod.org/t/whos-wrong-antenna-or-guardian/1573/16 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the late reply and so much back-and-forth with this PR. Looks good to me now, ready to merge :)
{% include image.html | ||
alt=" | ||
<!-- mdpo-enable-next-line --> | ||
devices | ||
|
||
" | ||
loc="/assets/images/documentation" | ||
file="gpodder-devices.png" | ||
%} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, having two different includes could be more confusing than helpful for contributors. I would say let's just keep it the way it is now :)
Yeey. Thanks a lot for the feedback! |
Ah, actually: do you think we should/could squash into three commits?
With the feedback I made quite a few subsequent changes on the same things - merging stuff would make it easier to understand the changes. But this one commit is just a lot of moving text around which would make reading history harder. No idea how to squash certain commits only, though (only know on web you can squash all). |
93f47f2
to
a9cb33e
Compare
31b8eb9 moves a lot of files, too. I squashed the last few commits that just said "review corrections", "final corrections" etc ;) |
Contributes to #111