Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid custom font not mapping properly
    primarykey
    data
    text
    <p>I have to implement <code>Nepali Font</code> on my application and for that I have used unicode font named <code>DroidSansDevanagari-Regular.ttf</code>.The reason I have used this font is that on my <code>Rooted Galaxy S2 I900</code>,I have installed <code>Resurrection Remix 3.06 JB(AOKP)</code> which renders <code>Nepali Font</code> correctly. And under <code>system/fonts</code> folder I have found this <code>DroidSansDevanagari-Regular.ttf</code> font,which is responsible for displaying <code>Nepali Font</code>.</p> <p>Further I have used the correct way of using custom font </p> <pre><code> Typeface font = Typeface.createFromAsset(context.getAssets(), "fonts/DroidSansDevanagari- Regular.ttf"); someTextView.setTypeface(font); </code></pre> <p>And though my application displays the <code>Nepali Font</code> it doesn't correctly maps the font.Using same font I get correct mapping on <code>Rooted Galaxy S2</code> phone,but I can't get correct mapping on other phones. Let me illustrate this by picture</p> <p>Correct Mapping</p> <p><img src="https://i.stack.imgur.com/uyY8w.png" alt="Correct Mapping"></p> <p>InCorrect Mapping</p> <p><img src="https://i.stack.imgur.com/UXOxl.png" alt="enter image description here"></p> <p>So,my question is how to map the font in correct manner as done by my <code>Rooted Galaxy S2 phone</code>.For that do I have to look upon <code>AOKP</code> project and look upon <code>EditText</code> or <code>Typeface</code> classes.Please provide me guidance on how to correctly map the fonts on each and every device</p> <p>Thanks in advance</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload