-
-
Notifications
You must be signed in to change notification settings - Fork 977
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Umlauts (UTF-8) in notifications #212
Comments
For now, only the character a-z, A-Z and 1-9 are included in the font. Other characters like é, è, ê, ä, ö, ü,... are not included, but can be included easily, which will make notification easier to read :) |
As I had pointed out in issue #461, in my country we use an RTL language, and unfortunately, we use a completely different script, with many not understanding English, so transliteration is not a real option in my country. This would mean that we will need lightweight fonts, in addition to possible solutions (like loading from external storage). |
We need more language support. I just tried using Pinetime in Taiwan. It has no support for Chinese characters. If the message is English the message comes through. If the message is all Chinese with no English the notification is sent, but it is 100% empty. Wife loves the Pinetime, but this one major issue is a major issue for non-English speakers. |
I will rephrase here the reply I wrote under a PR that intended on extending the symbol range. Including more and more characters using the current method is not sustainable. There are many languages that should be included but building them into the firmware consumes space much better spent elsewhere. PRs extending the symbol range without using the external filesystem not be merged in the current state. I think it's very clear that this feature is in high demand and there's not much need for further advocacy, so leave a thumbs up instead. If someone does start implementing it and wants to discuss that, then that's of course fine. |
Support for larger loadable fonts would be great. But in the meantime, where could we apply translations? ä => ae, ö = >oe, å => aa, ü => ue, ... |
@ptman if you're using Gadgetbridge, there's an option for transliteration in the settings. |
Yeah but German doesn't work correct. "ä" ist going to be "a" instead of "ae". The same with other umlauts. This is a known bug of Gadgetbridge. |
I also have this issue when reading messages. It would be nice if Transliteration was enabled by default or if the app detects your location and turns it on accordingly. |
Hmm... Now that we have support for resources on the external flash, could that be used for adding additional languages without flashing forks of the main firmware? |
@tootbrute I've just created a traditional Chinese fork. If you're still interested in PineTime, please visit |
omg yes. my wife can stop bothering me then. I assume that fonts will come to the main fork....eventually. I assume that European languages will be prioritized though. I'll check out your fork. Thank you! |
I can see that the international characters support is limited by amount of device memory. What about adding conditional compiling and build special image for language group. For example |
@Boteium can you update to the latest version of infinitime? i would be willing to pay you directly or donate to an open-source project like this one, Infintime? it doesn't look like languages are coming very quickly to infintime. |
@tootbrute I'll find time to do it after the new year eve. I do have a latest personal build so it shouldn't be difficult. |
Because this thread is still getting new activities, I would like to promote my pull requests. |
not sure. how to check? i see they changed in 2021? https://www.ncartron.org/infinitime-blue-purple-elderberry---stability-amp-metronome-app.html i think my pinetime is only about 1.5 years old, so should be the new one. |
On the About page, in the Accel. field, it says what accelerometer you have. |
Unfortunately, that's likely to be caused by a hardware issue like the accelerometer being broken :-(... You can try running the battery down completely, sometimes that can help. |
I have the same issue (happened after an update several months ago), and tried that, but it never ended up working again. |
There is also transliteration in Amazfish. Right now, It needs to be turned on manually. |
With #2217 on the way (not merged yet), we can now get notifications from Apple devices. But there is no companion in between. The notifications are send directly from the OS. To support at least some characters, we would need an on-watch translation layer. |
I think it would be worth looking into diacritic support for latin languages, the amount of extra space needed might be relatively manageable and it provides support to many languages at once. For non-latin scripts though it's much more problematic space-wise, and loading a full system font into memory from the external flash is a no go as well. Loading into memory could work just for the notification screen though as there is a lot of free heap on this screen. Loading specific characters on demand could be possible but will probably lead to terrible performance when an entire message requires such characters. |
yes, it's certainly possible to include common latin characters. that does not comsume much storage space anyway. however, our watch has very little amount of ram. so, it would be nice to let users choose what characters to include. on demand loading is certain possible and I believe many other proprietary watches run on the nordic hardware are doing exactly this. as for our watches, we use lvgl. the official lvgl font engine load the entire font into ram and does not have on demand support. to implement this, one would need to write a custom lvgl font engine to fetch the characters on demand. it is possible but not easy. i believe pr 1773 is the first step toward support multiple languages becuase this is the simplest implementation compare to on demand loading. it would be nice to have some insight from the maintainer so that we could improve this pr to meet this project's merge standard. |
I didn't know about this PR! #1773 looks like a good implementation of fonts just for notifications, which to be honest probably covers 95% of the usecase for expanded language support currently. The fallback system looks good. I think the only challenge is making language packs available and allowing the user to select them. Or maybe lets keep it super simple and just allow one at a time? Either way probably best to discuss in the thread In this case I think extending the inbuilt font won't be needed |
The only other external text inputs are in the music app, right? |
I think so? In that case there are just two locations to consider |
Currently Umlauts (ä, ö, ü) don't seem to work the notifications. I guess this is true for not just Umlauts, but other letters as well (ß, å, etc). Would be good especially for European users.
The text was updated successfully, but these errors were encountered: