briar-manual issueshttps://code.briarproject.org/briar/briar-manual/-/issues2022-11-02T12:31:05Zhttps://code.briarproject.org/briar/briar-manual/-/issues/9Sidebar is hidden on mobile (screen width < 62em)2022-11-02T12:31:05ZakwizgranSidebar is hidden on mobile (screen width < 62em)When the screen width is less than 62em, the sidebar containing the language menu and table of contents is hidden. This means translations of the manual are not accessible on mobile, except via direct links.When the screen width is less than 62em, the sidebar containing the language menu and table of contents is hidden. This means translations of the manual are not accessible on mobile, except via direct links.akwizgranakwizgranhttps://code.briarproject.org/briar/briar-manual/-/issues/10Sidebar is not scrollable2022-11-02T12:30:56ZakwizgranSidebar is not scrollableThe sidebar containing the language menu and table of contents is not scrollable. This makes some translations and/or parts of the table of contents unreachable on certain screens.The sidebar containing the language menu and table of contents is not scrollable. This makes some translations and/or parts of the table of contents unreachable on certain screens.akwizgranakwizgranhttps://code.briarproject.org/briar/briar-manual/-/issues/8Add layout support for RTL languages2021-10-29T12:04:02ZakwizgranAdd layout support for RTL languagesThe manual has been translated into Persian but the layout is still left-to-right.
Adding `dir="rtl"` to the `html` element doesn't fix this, as it causes the ToC sidebar to overlay the content.
Setting `direction: rtl` on the `toc` an...The manual has been translated into Persian but the layout is still left-to-right.
Adding `dir="rtl"` to the `html` element doesn't fix this, as it causes the ToC sidebar to overlay the content.
Setting `direction: rtl` on the `toc` and `wrapper` divs, and then somehow conditionally styling the images to float left rather than right, may work.
Whatever solution we find, we need to be able to trigger it conditionally in the Hugo template based on the `.Site.Language.LanguageDirection` parameter:
https://discourse.gohugo.io/t/direction-rtl/25904/2Sponsor 6 outreach campaignTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-manual/-/issues/7"Use Mobile data": how about paid WiFi Connections?2021-02-05T18:36:22ZJens Korte"Use Mobile data": how about paid WiFi Connections?In the manual there is a paragraph:
> Use Mobile Data
>
>You can control whether Briar uses mobile data. If you turn off mobile data, Briar will only use the internet when you're connected to Wi-Fi.
How about paid WiFi Connections? And...In the manual there is a paragraph:
> Use Mobile Data
>
>You can control whether Briar uses mobile data. If you turn off mobile data, Briar will only use the internet when you're connected to Wi-Fi.
How about paid WiFi Connections? Android or least LineageOS distinguishes between WiFi free of charge and paid ones (translated from the german UI). Imho the Android download manager downloads if the phone is connected to a free of charge WiFi.https://code.briarproject.org/briar/briar-manual/-/issues/2the link to the Briar application on Google Play in the user manual is broken2018-11-09T15:57:43ZRoman Beslikme@beroal.in.uathe link to the Briar application on Google Play in the user manual is brokenIn the chapter "Installation". The error message is "URL not found".In the chapter "Installation". The error message is "URL not found".https://code.briarproject.org/briar/briar-manual/-/issues/1Manual makes users connect to fonts.googleapis.com2018-10-11T08:09:32ZTorsten GroteManual makes users connect to fonts.googleapis.comThe URL it loads is: https://fonts.googleapis.com/css?family=PT+Sans
This should probably be replaced by a local instance of the font.The URL it loads is: https://fonts.googleapis.com/css?family=PT+Sans
This should probably be replaced by a local instance of the font.