german translations #17
Comments
|
**UPDATE 04 : 20 JUIN : 18h00 - à faire sur la nouvelle version 0620 **
For the 181B display you have the option to add model: 181B or model: 181D |
But due to the fact that the underlaying "HA" is capable to deal with it on a user level and not on an installation level it should work out of the box but it does not in multiple occasions cause it is running in US mode I guess. If I ask you a lot others can ask that too and it is easier to have a list of things in mind that are not working as hoped cause I guess that you would prefer then french "1 999 kcal" over the crazy german "1.999 kcal" even thought the amount stays the same may be a tiny french champaign compared to a big german beer but the energy amount will stay the same ... Regardless all these points I had been working on an updated list for this github page which I will check once again. If things might appear again or differently be aware that this new list should be a kind of overall status report cause we are working on the card itself in general and the translation topics in parallel. But the new one will have a stronger separation into translations, general stuff and things to not forget like decimals / thousand separators and so on. I guess you might call on HA for "CARD EXPERTISE NEEDED: how to adjust / handle with separators " or so cause someone might know, same for the question if customizeable cards can not get its own name in the title bar and why not. Therefore that "type" should allow to change that title bar even to "custom: Lovealce Body Mi Scale (0621) Card Configuration" Once again, this is my reply to your thoughts above while I had been working on the next "stage" since I was able to get it working and therefore called by me the 0620 late night edition. Please give the new version a version number 0620-hh where hh stands for the hour of release to differentiate between those cause right now I was not sure how to call that and went for the 0620 late night edition cause before I could not get it to work. Therefore you should add that release number additionally at the end of the last configuration line here after the word verfügbar in brackets like "... verfügbar [0621-18]." or "... available [0621-18]."
Finally: do not be astonished with the next comment cause for example I have already "developed" this last sentence further cause in that current shape it is not as good as it should be but I will explain it there again and did not want to mix my reply to your status up with my upcoming comment. |
EVALUATION OF LATE NIGHT BUILT 0620First note goes to the built number: 0620-hh should be the new sheme where hh are representing the hour of release cause I had yesterday only gotten 0620s I will start with pure translation points except that I wanted to start from top to bottom and therefore begin with a non translation issue but a more general one which you had already answered and I added your reply as state: not possible yet. I. TRANSLATIONS#1 For me it should be the spot #1 for the BUILT number like cause I was struggling a lot what code my card was relying on which is very frustrating to not be able to get behind which code is running except by differentiating that due to its translation errors #2 I guess we need to call that "STATUS: unbekannt" (means "STATE: unknown") Search for And regarding "unknown" you have to implement that on your own as "State: unknown" - for german "STATUS: unbekannt" #3 After being unsatisfied with the previoius term (which is right but feels weird to read and explain) we now could go the technical way which would mean a "Sensor - user name" combination or much easier "Please choose your scale account [mandatory] !" You have a scale and even if you are alone the system it can only work if you have created at least 1 account in that bodymiscale.yaml file - can you tell me that a second user has to be added in that file too ? #4 For me it is not about "pic" but about a "background pic" cause the figures will lay in front that (background image). #5 This means "Offer detailed measurement results (lower part - press power button to show)" As said before it would be nice if there is a way to add a carriage return line feed / new line after "... anbieten" #6 Previous "Schaltfläche" means a (bigger) switch area like 'cancel' or so, but what you mean is that U spot / button which is called in german "Schalter" / button and where I added (U) cause it looks like an "U" in a white circle switch. #7 I had to change the terms inside to "Power Button" (the translation "Einschaltknopf" sounds weird in that context cause it would mean to turn the whole scale on / off which it does not do). Therefore I still suggest to use any different kind of button instead that particular turn on / off button which will cause questions. I still recommand an icon that represents to hide / unfold something like a triangle or twister ᐅ to press for more details and if that had been pressed I suggest to replace that previous ᐅ with the opposite twister / triangle like this ▼ cause this switch has a toggling meaning to show or hide details. #8 which means QUESTION: I have deleted the word "actions" cause I was not sure if there are any actions available or not and if actions have to be mentinoned there cause usually it will cause questions like "What actions ?" I'd prefer the short and simple one cause that would work better on tablet or smartphones too and would not lead to ask what other "actions" are available. UPDATE: 21st 17:00 II. GENERAL CONFIGURATIONThis chapter is beyond translations, more integral questions in general like in which order why option should appear or even been hidden cause it makes no sense to offer switches that will not be shown if the general symbol bar is off, but that explanation will follow below. Just an example that you first need a symbol bar that is turned on to then make those other switches available. I. Why is that important ? II. III.
Therefore can you please add an empty line (or separator line out of ----) above the first switch which is followed by this line IV. It will make it a lot easier in the beginning to understand where the targets of the upper half are and what each switch is for while we both do it know now blindly due to daily training but the average user will struggle which swtich is what for (therefore I had pointed out where those things are located). V. But that LAST SWITCH "show symbol bar" has to be the first choice in the lower section cause without showing the symbol bar switches 4 and 5 are useless to click on and therefore should stay hidden / unavailable, right ? Only once "symbol bar" is activated the other 2 switches should appear cause only then they can work. I chose "offer button for more measurement details" cause you only offer a button which has to be pressed to show further measurement details. This is not a general switch to always show the measurement details. "show" instead "offer" will be misunderstood cause if you would activate that switch "show button for more measurement details" people will mostly only read and expect "show more measurement details" VI. Search for VII. Isn't a switch a better solution to chose between 2 models where '181D' should be the default setting? By default it is turned of and therefore it will run as a model 181D user. That typing solution is not ideal and it would never be my first choice even though you read the initial value out of the yaml file and you might write that value back too. Such switch would work at least right now a lot better and looks nicer too for sure. AND: a switch does not need the additional "mandatory" term too cause with a switch the card would start by default as 181D. VIII. BMI should be followed by III. POINTS TO NOT FORGET1. VARIABLE OR LABEL NAME with TYPO 2. ALL ABOUT FIGURES AND FORMATS
3. Aligned lines for Status (upper left) |
|
Great work. Let me move your post to the card github so we have a better chance of getting other opinions and help on the card. |
**UPDATE 05: 21 th of JUNE: 'background picture version' **
Okay, you had developed it further regarding scale number and background image or so, but here is bug I explain in point 2.
**UPDATE 04: 20 th of JUNE: 6 pm - to do's on the new version 0620 **
I guess this will be a shorter list of what is left to be done
OLD: Search for STATUS WAAGE and replace that whole line by what I had written in the list
"show_state": "Status anzeigen (Symbole links oben)"
I added the description to make clear what it is for "(icon/s upper left)"
ATTENTION: If you agree that you will end up with max 1 symbol shown at a time for the scale states then you have to take the following line cause that would mean a singular icon and therefore "Symbol" instead of Plural "Symbole" right now where you show scale and warning sign together. If you will endup with 1 sign at a time then this would be the right line:
"show_state": "Status anzeigen (Symbol links oben)"
OLD: Please do a search and replace for "Nicht verfügbar" by "nicht verfügbar" cause that appears quite often.
OLD: search for "kein" or "none" and replace the word "kein" bei "keine" caue no and none are different, same for kein / keine
OLD: Search for "Körpger..." and delete that "g" which is a typo.
NEW: Now search for "Körperwert und" and replace "Körperwert" by the infiltrated german word "Power Button"
OLD: Try to add your "Body Mi Scale Card" to the "add card dialog" cause it is missing even though not important right now, but looks a lot better for sure
OLD: just a kind reminder that you wanted to adjust the kg decimals to just 2 for both / all weights cause currently they are different from 0 to 2 and that does not look very well.
OLD: metabolism figure should be formated with a dot for the usual 1.000 + kcal cause it looks a lot nicer and is not a year.
Finally try to make the folloing fit in 2 lines as the pic i created shows and please replace "Button" by "Power Button"
If possible do the same for the warning error in case we get 2 messages that do not fit in 1 line cause they are so much easier to read and understand then a broken line.
Final point I hope: the details shown by a press of the power button should only display what can be available on that particular model. i do not need a 181B series of labels where the data are described as not available. Hide the unavailable pieces if possible.
So far, so good - except I can not check those values I do not have so maybe you can send me a screenshot when you use that development template and get the german UI. I mean just the body details you can show by the power button.
**UPDATE 04: 20 th of JUNE: 5 pm - can not find any changes right now **
I just checked it and not a lot has changed or maybe I got the wrong file or do I have to completely reboot the pi 4?
all the "Nicht verfügbar" still there instead of "nicht ..." and "kein" in the top or status area instead of "keine" in the sense of "no warning messages" . So I assume my update by copy the raw from github into the js file did not really work out with just a docker stop homeassistant and docker restart homeassistant.
UPDATE 03: 20 th of JUNE: missing translations proven and corrected
Ok, that was an easy on for me and I hope for you too cause it is only about 7 terms with minor changes.
ATTENTION:
#1 I simply translated and did not look for the key question if it might fit or not cause that has to be done in the next dev version but I guess you can see in most cases german words or terms are longer measured by letters.
#2 You should change a variable or label name I guess cause yours is wrong and might cause other issues.
"Lack-exerscise": the last should be "exercise" without that "s" before the "cise"
#3 tiny topic: search for Geschlecht and then you should find "männl" which needs to be "männl." - the dot is missing which allows us to shorten it from mänlich to männl. but only with a dot at the end.
Terms to exchange have NO LEADING'#'
UPDATE 02: 19 th of JUNE: some translation improvements
Meanwhile I came across a few points that do not really work out regarding translation.
To avoid unnecessary double work you can search for the word 'IMPROVED'
ATTENTION: above that IMPROVED you will find a changed line / term cause I had found typos and other smaller points or shortened terms like 'stoffwechselbedingtes Körperalter' in the hope that it fits in 1 line - with 2 lines it did not look good.
FINAL 3 POINTs
the label "BMI-Label" of the lower / hidden section with the details is NOT covered at all in the translation file you had sent to me and also not its values as can be seen in this example screenshot "Leichtes Übergewicht" which has to be "leichtes" cause I was wondering why I had written with a capital letter.
And there is another phrase missing in that file cause I am wondering myself about the spelling of those translations and why I had done it that way. So I do a search through the translation file for "Nicht verfügbar" with a capital "N" in the beginning. It is not in that file. So there might be more words missing a translation. here the final 3 tasks to not forget.
#1 Please change the term "BMI-Label" in the german version into "BMI Klassifikation"
#2 Also change at least its value "Leichtes" into "leichtes" and send me the other german values to crosscheck those too
#3 Finally do a search and replace for "Nicht verfügbar" with "nicht verfügbar".
UPDATE: 01 16th of JUNE: DONE
First task: please change and release the current one in 2 major points cause they disturb germans for sure cause now it shows 'average 200 cm' due to translation error and 'Nice: male' cause gender has been mis translated.
FIRST STATUS: 15 th of JUNE
Please read my translation comments directly below the german line term just to think about if maybe some english terms should be adopted or expanded too.
Then THANKS A LOT for the body-miscale-dev.js piece you created for me cause that way I can play around without damaging anything except my own config.
To get your translation file back you simply have to delete all the empty lines and those that begin with #
As said on the home assistant forum here is a long version of my thoughts to explain why some points felt a bit misleading / to short in english.
Regarding organisational structure of my comments. For a better comparison I first had added the english original quote as a comment and sometimes also the first Body Scale App results to get a history what I changed from where to what.
The first translations you had send as german version are partly false, partly not understandable or misleading, but 60% were good, but as you had explained later that those german terms were from the app.
Therefore I hope you take the time to read these comments cause some might usefull to adopt to the english version too and most likely french, but it will of cause be a struggle regarding space if you focus on Smartphone developement.
The text was updated successfully, but these errors were encountered: