Fixed
Status Update
Comments
gr...@google.com <gr...@google.com>
gr...@google.com <gr...@google.com> #2
I second.
the only thing that stops us is the file system permission set. The permission set
can be changed without compromising the system.
the only thing that stops us is the file system permission set. The permission set
can be changed without compromising the system.
gr...@google.com <gr...@google.com> #3
A concern here is that fonts that include many scripts tend to be large, but storage
space is scarce on current devices.
space is scarce on current devices.
gr...@google.com <gr...@google.com> #4
[Comment deleted]
gr...@google.com <gr...@google.com> #5
So why won't you just release the file permission (or directory in our case). Let the
user choose how to spend the little memory we have.
Doesn't it sound reasonable?
user choose how to spend the little memory we have.
Doesn't it sound reasonable?
gr...@google.com <gr...@google.com> #6
From what I understand, support for multiple languages is an inevitable stop in the
roadmap ahead (and partial support is planned for as early as q1 09) so this is
something that should be addressed and might as well be address now.
also, in the spirit of open source, the o.s. should allow access to fonts directory
so that developers (or users) can put in their own fonts (just like they would for
ringtones and backgrounds)
Just a thought...
roadmap ahead (and partial support is planned for as early as q1 09) so this is
something that should be addressed and might as well be address now.
also, in the spirit of open source, the o.s. should allow access to fonts directory
so that developers (or users) can put in their own fonts (just like they would for
ringtones and backgrounds)
Just a thought...
pa...@partners.mbank.pl <pa...@partners.mbank.pl> #7
Quote:"(and partial support is planned for as early as q1 09)" see cupcake
(http://source.android.com/roadmap/cupcake )
(
pa...@partners.mbank.pl <pa...@partners.mbank.pl> #8
hey elad
you said something about people did it before ?
can you please spacify how ?
you said something about people did it before ?
can you please spacify how ?
gr...@google.com <gr...@google.com> #9
See details at iandroid.co.il
In short, we just replaced the fonts with ones that support Hebrew and updated the OS
with the new fonts. There was a need though for administrative privileges.
In short, we just replaced the fonts with ones that support Hebrew and updated the OS
with the new fonts. There was a need though for administrative privileges.
ap...@google.com <ap...@google.com> #10
I truly think that I shouldn't have to root my G1 in order to add simple Hebrew reading
capabilities , please just add some language adding feature, i mean how hard would it
be to simply download and throw some fonts in a folder in response to a user selecting
them in the device?
every g1 user knows that system memory is scarce and can make his own decision on how
to allocate that memory. we all do that when it comes to managing applications on the
g1 anyway.
capabilities , please just add some language adding feature, i mean how hard would it
be to simply download and throw some fonts in a folder in response to a user selecting
them in the device?
every g1 user knows that system memory is scarce and can make his own decision on how
to allocate that memory. we all do that when it comes to managing applications on the
g1 anyway.
pa...@partners.mbank.pl <pa...@partners.mbank.pl> #11
What about the new HTC Hero, could this phone work with Hebrew?
gr...@google.com <gr...@google.com> #12
I confirm this issue on my HTC Hero, Both arabic and Hebrew are not displayed correctly.
people are rooting their devices just to add fonts
http://blog.amr-gawish.com/39/arabic-language-in-android/
people are rooting their devices just to add fonts
gr...@google.com <gr...@google.com> #13
So? Anybody will do something? I want to read hebrew texts! Why the "GOOGLE" can't put the normal
utf fonts in update?
utf fonts in update?
er...@gmail.com <er...@gmail.com> #14
Any progress on those Hebrew fonts? With root functionality disabled in the latest 1.5
version, is there any other way to add/replace fonts in /system/fonts?
version, is there any other way to add/replace fonts in /system/fonts?
Description
Jetpack Compose version: BOM 2024.12.01
Jetpack Compose component(s) used: Text in Material3
Android Studio Build: Meerkat Canary 9
Kotlin version: 2.1.0
Problem:
Since bumping target SDK to 35 we notice that some strings on some devices receive unintended line breaks even when the Text Composable is allowed to be as wide as it wants. Trying to force single line does not work either as setting
maxLines=1
clip the string rather than join to one line.Examples of problematic strings:
Steps to Reproduce or Code Sample to Reproduce:
Code: Attached minimal reproduction repo including our custom font
Device: Reproduced on Pixel 9 Pro XL real device and emulator using the font/display settings in attached screenshot. Also reported on but not verified: Pixel 8 Pro, Pixel Tablet
Summary of the reprod sample: Activity with the following XML:
...and the following sample code:
This will produce the result in attached screenshots.
Some findings from debugging the issue: