|
|
Well, seems Stefan's conversion from Restructured Text to Markdown broke it. Do we know why it was converted to MD in the first place? |
|
|
Stefan, please clarify why you converted the (at the time working!) Restructured Text to Markdown for the Terms of service and privacy policy. |
|
|
Look at https://bugs.gnunet.org/view.php?id=7882 which ends with Marc's note " The iOS app now successfully receives Markdown ToS." Marc and I wanted to get MarkDown rendered instead of ugly plain text which is displayed very badly on iOS platforms. https://bugs.gnunet.org/view.php?id=8003 solved the issue that the ToS generator generated invalid MarkDown. Now we should ask us whether there is a way to let a MarkDown-tagged text file be displayed properly as plain text. MarkDown is required for iOS. When I git blame the ToS file exchange-tos-v0.rst I see that my last changes were applied on December 14. Was the file not working since then?? Thank you for your contributions to solve this issue. It will be needed for getting translations of the Terms of Service started in Weblate as we are heading for a whole bunch of languages we have to translate to. |
|
|
Oh, and I never touched exchange-pp-v0.rst. |
|
|
I see. Well, in that case the answer is simple: please revert to proper Restructured Text, as the taler-terms-generator had been fixed to generate MD itself from the RST inputs, and so the source should be Restructured Text and NOT markdown! It works nicely for the other RST files. |
|
|
Done: https://git.taler.net/exchange.git/commit/?id=0389821c4b15203aeca55262b865a0b87163d8ab Let's see how it renders. Please make a new build and test it out. Thank you. |
|
|
Florian or Sebastian: I assume you can test this on test.taler.net / with sandcastle? |
|
|
I would expect HEAD to automatically pick this up - that's the main reason for it's existence, isn't it? |
|
|
still testing, but this is what I see... asking the exchange for text/html and server replies text/plain image.png (64,519 bytes) |
|
|
That was similar 3 months ago, when iOS asked for text/markdown and first only got text/plain, and later the server claimed to send text/markdown but the content was still text/plain. Took weeks until there finally was real markdown in the answer... |
|
|
I don't get it. Please do curl -H 'Accept: text/plain' https://exchange.test.taler.net/terms vs. curl -H 'Accept: text/html' https://exchange.test.taler.net/terms vs. curl -H 'Accept: text/markdown' https://exchange.test.taler.net/terms I always get the result in the correct format! |
|
|
this works locally cache may be a separated issue |
- Anonymous
