Merge pull request #1800 from openaps/l10n_master

New Crowdin updates

docs/CROWDIN/cs/Hardware/DexcomG7.md

@@ -7,7 +7,7 @@ In spring 2022, the Dexcom G7 received its CE certificate and was sold at the en
 
 Noteworthy is the fact that the G7 system, compared to the G6, does not smooth the values, neither in the app, nor in the reader. More details about this [here](https://www.dexcom.com/en-us/faqs/why-does-past-cgm-data-look-different-from-past-data-on-receiver-and-follow-app). Consequently, the values have to be smoothed to be able to use them sensibly in AAPS.
 
-![G7 english](https://github.com/blaqone/AndroidAPSdocs/assets/37814299/6fe30b84-227a-4bae-a9a5-527cee341dbf)
+![G7 english](../images/6fe30b84-227a-4bae-a9a5-527cee341dbf.png)
 
 ## 1.  Patched Dexcom G7 App (DiAKEM)
 

docs/CROWDIN/cs/Hardware/Libre3.md

@@ -2,7 +2,7 @@
 
 Freestyle Libre 3 (FSL3) requires a unique setup to receive BG values in to AAPS. There are two possible ways of getting Freestyle Libre 3 (FSL3) values to AAPS.
 
-![FL3](https://github.com/blaqone/AndroidAPSdocs/assets/37814299/d912c1d3-06d2-4b58-ad7c-025ca1980fae)
+![FL3](../images/d912c1d3-06d2-4b58-ad7c-025ca1980fae.jpeg)
 
 !!! Version 3.2.0.1 of AndroidAPS does not support 1-minute values. Acceleration and Smoothing does not work with 1-minute values. !!!
 

docs/CROWDIN/cs/Installing-AndroidAPS/Releasenotes.md

@@ -57,7 +57,7 @@ Release date: 23-10-2023
 
 - NS 15 is required
 - While using websockets in NS v3 plugin treatments entered through NS UI (plus button) and other applications using v1 API are not sent to AAPS. This will be fixed in future release of NS. Always use the same client (v1 or v3) in AAPS and AAPSClient until NS fully switch to v3 internaly. The same is valid for AAPS and AAPSClient itself.
-- Websockets in v3 plugin works similiar way to v1 plugin. Without websockets enabled AAPS schedules regularly downloads from NS which should lead to lower power consumption because NS is not permanently connected. On the oposite side it means delays in exchanging data.
+- Websockets in v3 plugin works similiar way to v1 plugin. Without websockets enabled AAPS schedules regularly downloads from NS which should lead to lower power consumption because NS is not permanently connected. On the oposite side it means delays in exchanging data. Please read [here](Important-comments-on-using-v3-versus-v1-API-for-Nightscout-with-AAPS) the important comments from the dev team before you use it!
 - If you are using xdrip as cgm source you must select it again after update due to internal changes
 - Tidepool can be used as a replacement of NS to pass first objective
 - If you send to xDrip+ you must configure xDrip synchronization plugin. In order to receive BGs from AAPS in xDrip it must be selected source "xDrip+ Sync Follower"
@@ -96,6 +96,34 @@ Release date: 23-10-2023
 - tests cleaup @ryanhaining @MilosKozak
 - new 110k+ lines of code, changed 240k lines, 6884 changed files
 
+(Important-comments-on-using-v3-versus-v1-API-for-Nightscout-with-AAPS)=
+### Important comments on using v3 versus v1 API for Nightscout with AAPS
+
+v1 is the old protocol used for exchanging data between NS web site and NS server. It has many limitations
+- v1 sends only 2 days of data
+- v1 send all 2 days data on every reconnection
+- using websockets is mandatory = permanent connection, more battery compsumption
+- during frequent disconnects to NS connection is paused for 15 minutes to prevent high data usage
+
+v3 is new protocol. More safe and efficient
+- while using tokens you can better define access rights
+- protocol is more efficient on both sides (AAPS & NS)
+- It can read up to 3 months of data from NS
+- you can choose to use or to not use websockets on every device (using means faster updates, not using means lower power compsumption, but slower updates ie. minutes)
+- NSClient is not paused on disconnections
+
+LIMITATIONS
+- NS 15 must be used with AAPS 3.2
+- v3 doesn't see updates done by v1 protocol (probably it will be resolved in some future version of NS)
+- in opposite because of old uneffective method of tracking changes v1 see changes done by v3
+- remember NS still uses v1 internaly so far thus is not possible to enter data through NS web UI if you are using v3. You must use AAPSClient on SMS if you want enter data remotely
+
+RECOMMENDED SETTING
+- because of all above you should choose only one method and use it on all devices (remember all other uploaders at time of writing this are using v1). If you decide to go to v3, select v3 in AAPS and all AAPSClients
+- v3 is preffered because of efficiency
+- using websockets or not using with v3 depends on your preference
+- it HIGHLY recommended to let AAPS gather all data and then upload it to NS as a single uploader. All other devices/applications should only read from NS. By doing it you'll prevent conflicts and sync errors. This is valid for getting BG data to NS using Dexcom Share connector etc. too
+
 ## Version 3.1.0
 
 Release date: 19-07-2022

docs/CROWDIN/cs/Installing-AndroidAPS/Update-to-new-version.md

@@ -2,19 +2,23 @@
 
 ## Vyrobte si místo stažení
 
-**AAPS is not available as download due to regulation for medial devices. Je legální vytvořit aplikaci pro své vlastní použití, ale nesmíte dát kopii ostatním! Další informace naleznete v části [Časté dotazy](../Getting-Started/FAQ.md).**
+**AAPS** is not available to download, due to regulations concerning medical devices. It is legal to build the app for your own use, but you must not give a copy to others! Další informace naleznete v části [Časté dotazy](../Getting-Started/FAQ.md).
 
 ## Důležité poznámky
 
-* Aktualizujte co nejdříve, jakmile bude k dispozici nová verze. You will receive an [information on the AAPS home screen](Releasenotes-release-notes) about the new version.
-* As of version 2.7 repository location changed to <https://github.com/nightscout/AndroidAPS>. If you are not familiar with git the easiest way for update is remove directory with AAPS and do a [new clone](../Installing-AndroidAPS/Building-APK.md).
-* Please use **[Android Studio Version 2020.3.1 (Arctic Fox)](https://developer.android.com/studio/)** or newer to build the apk.
-* [Windows 10 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio 2020.3.1.
-* Make sure you read the [Release Notes](../Installing-AndroidAPS/Releasenotes.md) for the current version
+* Please update to the new version of **AAPS** as soon as possible after a new release is available.
+* When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version.
+* The new version will also be announced on Facebook at the time of release.
+* Following the release, please read the [Release Notes](../Installing-AndroidAPS/Releasenotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update.
+* For **AAPS** versions 2.7 and newer, the location for the new files is at <https://github.com/nightscout/AndroidAPS>.
+* The easiest way to update **AAPS** is to remove the directory with **AAPS** and do a [new clone](../Installing-AndroidAPS/Building-APK.md).
+* If you are unsure about how to do this, you can also completely uninstall and reinstall Android Studio to make sure the build is a success. 
+* Ideally, use the latest version of Android Studio, **[Giraffe, 2022.3.1](https://developer.android.com/studio/)**, but at least **Arctic Fox (2020.3.1)** or newer, to build the updated **AAPS** apk.
+* If building the **AAPS** app using a Windows platform, you will need to use a Windows 64-bit system since 32-bit systems are not supported.
 
-## Overview for updating your AAPS version
+## Overview for updating to a new version of AAPS
 
-1. [Export your settings](../Usage/ExportImportSettings-export-settings) from the existing AAPS version on your phone. You might not need it, but better be save than sorry.
+1. [Export your settings](../Usage/ExportImportSettings-export-settings) from the existing **AAPS** version on your phone. You might not need it, but better be safe than sorry.
 2. [Update local copy](Update-to-new-version-update-your-local-copy) of the AAPS sourcecode (Git->Fetch and Git -> Pull)
 3. [Build signed APK](Update-to-new-version-build-the-signed-apk)
 4. [Transfer the built apk](Building-APK-transfer-apk-to-smartphone) to your phone and install it

docs/CROWDIN/cs/Sandbox/crowdintest.md

@@ -0,0 +1,9 @@
+# Small Crowdin Test
+
+This is a small set for testing the translation with Crowdin.
+
+We want to see how changes to a sentence affect the existing translation of the entire page.
+
+Normally, only one sentence should need to be retranslated and not everything.
+
+We will see soon.

docs/CROWDIN/cs/following-only.md

@@ -4,7 +4,7 @@ In addition to the range of possibilities available for remotely controlling _an
 
 A good overview of the extensive options available for following **AAPS** is at [Nightscout follower](https://nightscout.github.io/nightscout/downloaders/#) webpage; if you expand the menu on the left-hand side:
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/dfa981c1-5a15-4498-88d2-0fd1462d8242)
+![image](./images/dfa981c1-5a15-4498-88d2-0fd1462d8242.png)
 
 The most common strategies used in combination with **AAPS** are explained in more detail below.
 
@@ -17,7 +17,7 @@ A)  Dexcom Follow (Android/iOs) B)  Nightguard (iOs) C)  Nightwatch (Android) D)
 
 #### A) Dexcom Follow (compatible with both Android and iOs devices)
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/ded350b0-6012-4104-b21c-5d5bfd91aa65)
+![image](./images/ded350b0-6012-4104-b21c-5d5bfd91aa65.png)
 
 ●   Dexcom Follow is compatible with a wide range of handsets (both Android and iPhone). Dexcom Follow can be used even if you are not using the official Dexcom app to receive sensor data.
 
@@ -46,7 +46,7 @@ For Dexcom Follow, the sensor data is then exported from the AAPS phone either d
 
 #### B) Nightguard (iOs only)
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/f2c7d330-9889-4526-9a5c-bbb012d804ab)
+![image](./images/f2c7d330-9889-4526-9a5c-bbb012d804ab.png)
 
 Pros (as reported by users):
 
@@ -72,7 +72,7 @@ Cons (as reported by users)
 
 #### C) Nightwatch (Android only)
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/855c3a74-e612-4a6f-8b63-18d286ea0a3f)
+![image](./images/855c3a74-e612-4a6f-8b63-18d286ea0a3f.png)
 
 
 ●   Nightwatch markets itself as a Nightscout client and monitors the user’s Nightscout glucose levels on either Android phone or tablet.
@@ -121,9 +121,9 @@ An easier solution is therefore to download the **Shuggah** app.
 
 App:
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/03fc0c6a-067a-40ea-8be3-c66d4ce8b5d9)
+![image](./images/03fc0c6a-067a-40ea-8be3-c66d4ce8b5d9.png)
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/fae3ec63-2c2c-4152-ab42-97f9744a8f36)
+![image](./images/fae3ec63-2c2c-4152-ab42-97f9744a8f36.png)
 
 
 "What is Shuggah?" A group of Ukrainian developers took the project code for xDrip4iOS (which is shared publicly on Github) and released it on the App Store under a business account (the app is free, and their intentions are good). The app had to be slightly modified to add a privacy statement and disclaimer to get past the review, but the rest of the app should be the same as xDrip4iOS. The Shuggah release is not officially managed by the xDrip4iOS developers so it cannot be guaranteed that it will function in the same way as xDrip4iOS, or that Apple won't remove it from the App Store at some point.
@@ -133,9 +133,9 @@ The [XdripiOs Facebook group](https://www.facebook.com/groups/853994615056838/an
 
 #### F) Sugarmate (iOs)
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/340cd555-a9e0-4a20-a131-36c078f5b8ea)
+![image](./images/340cd555-a9e0-4a20-a131-36c078f5b8ea.png)
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/21b83c41-85c6-4619-a702-a65450768855)
+![image](./images/21b83c41-85c6-4619-a702-a65450768855.png)
 
 
 [Sugarmate](https://sugarmate.io/) is available to download onto iPhones from the App store. Sugarmate is compatible with: ●   Apple iPhone (Requires software version 13.0 or later) ●   Apple iPad (Requires software version 13.0 or later) ●   Google Android (Save web app to your homescreen)
@@ -145,7 +145,7 @@ It has been reported by users of Sugarmate that it can be used with Apple CarPla
 
 #### G)  [Spike](https://spike-app.com/) on iOS
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/1129ba00-8159-4940-936e-76fd4ae45a2d)
+![image](./images/1129ba00-8159-4940-936e-76fd4ae45a2d.png)
 
 Spike can be used as a primary receiver or as a follower app, providing BG, alarms and IOB and more. Whilst the website is no longer biDetails are [here](https://spike-app.com/#features2). Details and support can be found on [Facebook](https://www.facebook.com/groups/1973791946274873) and Gitter](https://gitter.im/SpikeiOS/Lobby).
 
@@ -163,24 +163,24 @@ Here we summarise some of the follow-only watch options popular with **AAPS** us
 
 A developer called Artem has created xDrip integration for various smartwatch models, mostly for Xiaomi (_e.g._ Mi band) and Amazfit brands:
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4dba454b-f808-4e9e-bfc6-aba698e006f8)
+![image](./images/4dba454b-f808-4e9e-bfc6-aba698e006f8.png)
 
 
 You can read more about them, including how to set-up at his website [here](https://bigdigital.home.blog/). The advantage of these watches is that they are small and relatively affordable (the Xiaomi Mi Band 5 has a RRP of £39.99 GBP). They are a popular option especially for kids and those with smaller wrists to wear.
 
 #### b) Pebble watch
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/52032f3b-c871-4342-b8e7-659c285a39c8)
+![image](./images/52032f3b-c871-4342-b8e7-659c285a39c8.png)
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/935d28bb-a909-4ca8-850d-6a765bd4fcde)
+![image](./images/935d28bb-a909-4ca8-850d-6a765bd4fcde.png)
 
 
 Pebble watches [now discontinued](https://en.wikipedia.org/wiki/Pebble_(watch))) were on general sale from 2013 - 2016, and may still be available second-hand. Fitbit took over Pebble’s assets. Pebble users can use the Urchin watchface to view Nightscout data. Displayed data options include IOB, currently active temp basal rate and predictions. If open looping you can use IFTTT to create an applet that says if a Notification has been received from **AAPS**  then send either an SMS or pushover notification.
 
 #### c) [Bluejay GTS watch](https://bluejay.website/shop/product/bluejay-gts-26)
 
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/4d034157-b3d0-4dcb-98c8-fde0c2e7ad74)
+![image](./images/4d034157-b3d0-4dcb-98c8-fde0c2e7ad74.png)
 
 
 This is a unique piece of technology which can receive glucose data **directly** from the Dexcom G6 transmitter. It is not widely known that a Dexcom G6 transmitter actually broadcasts the current glucose data on _two_ separate channels, a phone channel and a pump channel. The Bluejay GTS watch runs a modified version of Xdrip+ software, and can be set to receive glucose data on either channel, so if **AAPS **  is using the phone channel, then the Bluejay GTS watch can use the pump channel.
@@ -203,7 +203,7 @@ Devices include: A)  M5 stack/M5 stickC B)  Sugarpixel C) PC (Teamviewer)
 #### A) M5 stack
 
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/061edb52-56d2-45f4-b3da-82b2036d7bc6)
+![image](./images/061edb52-56d2-45f4-b3da-82b2036d7bc6.png)
 
 
 
@@ -214,9 +214,9 @@ The [M5Stack](https://github.com/mlukasek/M5_NightscoutMon) is a small box which
 
 SugarPixel is a device for secondary glucose display alert system for continuous glucose monitoring that connects with Dexcom app or Nightscout app on the user’s smartphone. The device displays real time blood sugar readings. This CGM hardware monitor benefits from random tone generation audio alerts (which are incredibly loud), vibration alerts for hearing impaired, customisable display options and native multi-user following.
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/39137beb-17cc-4c87-98b7-cf1831d484cb)
+![image](./images/94044064/39137beb-17cc-4c87-98b7-cf1831d484cb.png)
 
-![image](https://github.com/openaps/AndroidAPSdocs/assets/94044064/87883ebb-9683-4aa8-8014-49c2ca902c93)
+![image](./images/87883ebb-9683-4aa8-8014-49c2ca902c93.png)
 
 ●   SugarPixel has multiple display options in mg/dL and mmol/L to suit the user’s needs with colour-coded glucose values. ●   The standard face displays BG, Trend Arrow, and Delta. Delta is the change + or - from the last reading. ●   SugarPixel can be customised for use in low brightness with the BG and Time face to see the user’s BG reading and current time on the user’s nightstand. ●   SugarPixel’s xolour face utilises the entire display to show a single colour representing the BG value. This enables the user to see BG readings at a distance through the window while outside playing in the backyard, patio, or pool. ●   The Big BG face is useful for nightstand users who wear glasses or contact lenses.
 

docs/CROWDIN/cs/index.md

@@ -276,6 +276,8 @@ State of translations <./Administration/stateTranslations.md>
 :caption: Sandbox
 
 Sandbox <./Sandbox/sandbox1.md>
+Crowdin Test <./Sandbox/crowdintest.md>
+
 ```
 
 ```{note}

docs/CROWDIN/cs/preparing.md

@@ -264,7 +264,7 @@ The duration of insulin action is set to a single value in AAPS, because your pu
 #### **Glucose targets**
 Glucose targets are set according to your personal preferences. For example, if you are concerned about hypos at night, you may set your target slightly higher at 117/mg/dL (6.5 mmol/L) from 9 pm - 7am. If you want to make sure you have plenty of insulin on board (IOB) in the morning before bolusing for breakfast, you may set a lower target of 81 mg/dL (4.5 mmol/L) from 7 am - 8 am. A glucose target, particularly if it is only short-term (less than 4 hours in duration), does not need to be the *actual value* you expect or want your glucose level to get to, rather, it is a good way to tell AAPS to be more or less aggressive, while still keeping your glucose levels in range. The **figure below** shows an example of how the DIA and glucose targets could be set in an AAPS profile.
 
-![24-07-23, profile basics - DIA and target](https://github.com/openaps/AndroidAPSdocs/assets/94044064/f3904cc3-3d9e-497e-a3b6-3a49650053e6)
+![24-07-23, profile basics - DIA and target](./images/f3904cc3-3d9e-497e-a3b6-3a49650053e6.png)
 
 
 For the final three parameters, basal rates (BR), insulin sensitivity factors (ISF) and insulin-to-carb ratios (IC or ICR), the absolute values and trends in your insulin requirements vary significantly from person to person, depending on your biology, gender, age, fitness level etc. as well as shorter term factors like illness and recent exercise. For more guidance on this, the book [“Brights Spots and Landmines”](https://brightspotsandlandmines.org/Bright_Spots_and_Landmines_by_Adam_Brown.pdf) by Adam Brown is an excellent book to read.
@@ -297,7 +297,7 @@ Example: TDD = 40 U Approx ISF (mg/dl) = 1700/40 = 43 Approx ISF (mmol/L) = 94/4
 
 See the **figure below** for an example of how the basal rates and ISF values could be set in an AAPS profile.
 
-![24-07-23, profile basics - basal and ISF](https://github.com/openaps/AndroidAPSdocs/assets/94044064/55c8ed24-e24e-4caa-9c17-294fa93cb84a)
+![24-07-23, profile basics - basal and ISF](./images/55c8ed24-e24e-4caa-9c17-294fa93cb84a.png)
 
 #### **Insulin to Carb ratio (ICR)**
 
@@ -313,7 +313,7 @@ If your ICR is weaker, perhaps 1:20, you would only need 0.5U of insulin to cove
 
 As shown in the **figure below**, when entering these values into an AAPS profile, we just enter the final part of the ratio, so an insulin-to-carb ratio of 1:3.5 is entered simply as “3.5”.
 
-![24-07-23, profile basics - ICR](https://github.com/openaps/AndroidAPSdocs/assets/94044064/7741eefb-cae5-45c5-a9e5-8eae5ead3f48)
+![24-07-23, profile basics - ICR](./images/7741eefb-cae5-45c5-a9e5-8eae5ead3f48.png)
 
 
 #### **Why should I try to get my profile settings right? Can’t the loop just take care of it?**