Replies: 11 comments
-
The OTA delivery sounds like it should be considered with care, as it'll allow Crowdin to track xDrip usage and add logic and a networked dependency to the live app, which would by definition increase probability of users experiencing issues with the live app. |
Beta Was this translation helpful? Give feedback.
-
I'm working on this issue and it works so far with the exception that it requires migration to AndroidX. I did this in my fork and I can upload screenshots. But the strings are not tagged yet. Investigating it.... |
Beta Was this translation helpful? Give feedback.
-
With the new years blog of Crowdin they announced the Appetize App. This is a much more elegant way. @jamorham Please can you install the Appetize app? I can provide the apk (requires the use Crowdin SDK ... and AndroidX). |
Beta Was this translation helpful? Give feedback.
-
That would be great help for the translators, because without the context many times I did not have any clue, what that string might mean. |
Beta Was this translation helpful? Give feedback.
-
That would just be enabled in a special build for translators and not the general app. |
Beta Was this translation helpful? Give feedback.
-
@tolot27 Is this something that needs to change in xDrip or something that needs to change in Crowdin? |
Beta Was this translation helpful? Give feedback.
-
I've tried creating screenshots for use in Crowdin. Unfortunately, xDrip still use a very old target API level and you cannot even get previous in the Android Studio design preview. I've already compiled a new xDrip version after migration to AndroidX, which is also used by the Crowdin SDK. This app can be used with the Appetize App but the later must be enabled at Crowdin which can be done only by @jamorham. I just have the managing role. |
Beta Was this translation helpful? Give feedback.
-
Thanks for explaining. |
Beta Was this translation helpful? Give feedback.
-
Hmm, not like here at GitHub. It is possible to comment on a string and flag it as an issue. But I don't understand what this has to do with this issue. Or do you just wan't to know how Crowdin works? |
Beta Was this translation helpful? Give feedback.
-
If there is an issue tracking mechanism inside Crowdin, considering this is a Crowdin issue, and the fix has to be implemented in Crowdin not in the xDrip code itself, I think it should be in there not in the xDrip set of issues. On the other hand, if there is no way to track Crowdin issues in Crowdin, then, I guess we have to have it here. There are too many open issues here and as a result the developers are not looking at them. This needs to change. I want to close any open issue that absolutely doesn't have to be open here for that reason. |
Beta Was this translation helpful? Give feedback.
-
This issue is not a Crowdin issue, it is an xDrip issue in xDrip code (it has to incorporate the Crowdin SDK which is already done by me) and of the xDrip maintainers. Crowdin cannot contribute anything to solve this issue. |
Beta Was this translation helpful? Give feedback.
-
Crowdin provides an Android SDK which allows different levels of integration and support for translators and users:
The biggest advantage: Automatic Screenshots and Real-Time Preview build for the development team and translators team.
Crowdin does not store any Personally Identifiable Information (PII) about the end-user but xDrip can integrate and additional opt-out option.
Beta Was this translation helpful? Give feedback.
All reactions