Skip to content
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

No support for no Nastaliq for Urdu #39

Open
GoogleCodeExporter opened this issue May 9, 2015 · 20 comments
Open

No support for no Nastaliq for Urdu #39

GoogleCodeExporter opened this issue May 9, 2015 · 20 comments

Comments

@GoogleCodeExporter
Copy link

You have supported Urdu in the form of the Arabic Nashq script which is not the 
correct way to do it.

There is a writeup on this by Ali Eteraz (Twitter:@eteraz) here - 
https://medium.com/@eteraz/the-death-of-the-urdu-script-9ce935435d90

Examples of Nastaliq fonts: http://urdu.ca/1 (direct link: 
http://urdu.ca/UrduFonts.zip) or  http://www.urdujahan.com/font.html. 

Original issue reported on code.google.com by s...@lambdacurry.com on 16 Jul 2014 at 6:25

@GoogleCodeExporter
Copy link
Author

We are working on a Noto Nastaliq as well. So stay tuned.

Original comment by tha...@google.com on 16 Jul 2014 at 6:42

  • Changed state: Invalid

@GoogleCodeExporter
Copy link
Author

Issue 40 has been merged into this issue.

Original comment by tha...@google.com on 16 Jul 2014 at 6:44

@GoogleCodeExporter
Copy link
Author

Until you're done working on a nastaliq script can you take Urdu, Persian, and 
Shahmukhi Punjabi OUT of the Naskh category. They don't belong there.

Original comment by Ete...@gmail.com on 16 Jul 2014 at 4:12

@GoogleCodeExporter
Copy link
Author

This is from leading scripts and fonts authority Thomas Milo:

"Mopping up all variants of islamic script with one fake naskh or "Eurabic" is 
as mad as combining Cyrillic, Greek and Latin, and then force everybody to 
write their languages in the resulting "Cygretin" script."

Original comment by Ete...@gmail.com on 16 Jul 2014 at 5:01

@GoogleCodeExporter
Copy link
Author

Reopening the bug, and confirming the need for a Nastaliq font for Urdu and 
other languages of South Asia. We are already working on a Nastaliq font. Stay 
tuned.

Original comment by roozbeh@google.com on 16 Jul 2014 at 5:25

  • Changed state: Started
  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Dear Project Members,

Thanks for checking in!

I am curious, what do you mean by "working on." Are you developing your own or 
licensing one from somewhere? Would be grateful if you can tell us what you're 
doing so we can be of assistance.

Original comment by Ete...@gmail.com on 17 Jul 2014 at 2:47

@GoogleCodeExporter
Copy link
Author

Unfortunately we can't really comment more on unreleased products. We are 
planning to cover all of Unicode and support all languages using those 
codepoints.

Original comment by stua...@google.com on 17 Jul 2014 at 6:17

@GoogleCodeExporter
Copy link
Author

But have, in the mean time, Urdu and related languages been taken out of the 
OpenType command table format {script/feature/lookup} mappings for Naskh, as 
the Naskh typeface is clearly the wrong one for the Urdu script?

Original comment by niho...@gmail.com on 6 Aug 2014 at 10:44

@GoogleCodeExporter
Copy link
Author

Getting Urdu out of Naskh font doesn't fix any problem; as such it's working as 
intended.

Regarding Persian: I believe Iranian's prefer Persian on their phone to be in 
Naskh style, not Nastaliq.  And definitely not an Urdu-style Nastaliq.

Original comment by behdad@google.com on 24 Oct 2014 at 2:24

@GoogleCodeExporter
Copy link
Author

We're happy to announce that we just pushed an early experimental version of 
Noto Nastaliq Urdu. The font can be downloaded from 
https://noto.googlecode.com/git/fonts/alpha/NotoNastaliqUrduDraft.ttf.

There are some known issues that we are getting fixed (such as the shape of the 
Urdu digit 7), but please download the font, test it, and tell us about it, so 
we can know about the issues early and get them fixed.

Original comment by roozbeh@google.com on 24 Oct 2014 at 2:41

@GoogleCodeExporter
Copy link
Author

The Nukta for the Pe in the screenshot is messed up. Should I open another 
issue?

Original comment by deepak.j...@gmail.com on 2 Nov 2014 at 11:37

Attachments:

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Yes, please open a new issue.

Original comment by roozbeh@google.com on 2 Nov 2014 at 8:05

@GoogleCodeExporter
Copy link
Author

In the new issue you create, please also specify what platform you are testing 
on.

Original comment by behdad@google.com on 2 Nov 2014 at 9:34

@GoogleCodeExporter
Copy link
Author

Original comment by roozbeh@google.com on 16 Jan 2015 at 5:53

@GoogleCodeExporter
Copy link
Author

Original comment by roozbeh@google.com on 16 Jan 2015 at 5:54

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

I checked this font, which is great.

There are some problems though – it is a work in progress anyway – when I'm 
trying to write in Pashto as some letter only exist in this language (I'm 
thinking of the  "ې" in a middle of a word for example). I hope they will be 
fixed.

Thanks for your hard work.

Original comment by monzoste...@gmail.com on 27 Mar 2015 at 10:54

@GoogleCodeExporter
Copy link
Author

Please file new bugs about each problem, provide the exact sequence of letters 
that doesn't work correctly, and attach a screenshot of the incorrect 
rendering.  Thanks.

Original comment by beh...@chromium.org on 1 Apr 2015 at 8:53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant