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

Feat: Add support for the text_indopak_nastaleeq field. #24

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

hkamran2
Copy link
Contributor

@hkamran2 hkamran2 commented Feb 26, 2025

Problem

When using the text_indopak field the API doesn't return the surah ending characters correctly.

image

Solution

Add support for the text_indopak_nastaleeq field that the API supports. This field, instead of the text_indopak, is useful when the using the nastaleeq font as it correctly provides each verse's end characters.

image

Note

I've not introduce text_indopak_nastaleeq for the Word fields type. Looking at the API, I think that's not supported (which makes complete sense) and hence, I've just added it for the text field.

The SDK currently does not support the text_indopak_nastaleeq field. This field, instead of the text_indopak, is useful when the using the nastaleeq font as it correctly provides each verse's end characters.
Copy link

vercel bot commented Feb 26, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 26, 2025 11:06pm

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

Successfully merging this pull request may close these issues.

1 participant