Adobe DTP and Punjabi/Indic Rendering Fix

I have issue with Panjabi rendering issue with Adobe Desktop Publishing (DTP) apps since long time and always require help. But finally I was able to sort it myself as below:

I used Adobe InDesign Application to create PDF from Panjabi text.

1. Text addition with default setting (without any change)

Rendering issue

 

2. Selected Paragraph Box and opened Paragraph Style Options -> Justification -> Composer – Adobe Paragraph Composer

default setting

 

3. Change above setting to

elected Paragraph Box and opened Paragraph Style Options -> Justification -> Composer – Adobe world-Ready Paragraph Composer

 

Required setting

 

4. Rendering after make change.

Correct Rendering

 

5. Compare side by side

Left – Adobe Paragraph Composer (default)

Right – Adobe world-Ready Paragraph Composer (changed for Indian language)

Compare side by side

 

6. Following is addition setting, which is not going to change rendering, but good to have.

Addition Setting

 

7. Finally, created pdf file with Adobe indesign opened with Adobe Acrobat Reader.

Final PDF image.

Note:
If you have Adobe Illustrator, then need to make following setting to try Panjabi/Punjabi (or any Indian) language.

• Click on Edit > Preferences > Type
•  Select Show Indic Options.
• Select paragraph , Ctrl+T and select Middle Eastern & South Asian Every-line Composer

 

Detailed setting from Adobe: https://helpx.adobe.com/ca/illustrator/using/asian-scripts.html

 

 

 

 

 

Test Google Fonts for Gurmukhi Script (Punjabi) – Prepare

Testing Google (not limited to) fonts with Linux. UTRRS is tool, which I am going to use to compare feature and verify shapes.

Google Noto Fonts: http://www.google.com/get/noto

Gurmukhi Fonts: http://www.google.com/get/noto/#/family/noto-sans-guru

Download from here: http://www.google.com/get/noto/pkgs/NotoSansGurmukhi-hinted.zip

Which font to selected – Note for Developer:

Use unhinted fonts for Android and Mac (Android and Mac ignore hinting information embedded in fonts).
Use hinted fonts for other platforms.

1. Unzip file

2. install

$  sudo cp NotoSansGurmukhi* /usr/share/fonts/google-noto/
$ fc-cache /usr/share/fonts/google-noto/

3. Confirm if it is working for your Script

$ fc-list |grep Gurmukhi
/usr/share/fonts/google-noto/NotoSansGurmukhi-Bold.ttf: Noto Sans Gurmukhi:style=Bold
/usr/share/fonts/google-noto/NotoSansGurmukhiUI-Bold.ttf: Noto Sans Gurmukhi UI:style=Bold
/usr/share/fonts/google-noto/NotoSansGurmukhiUI-Regular.ttf: Noto Sans Gurmukhi UI:style=Regular
/usr/share/fonts/google-noto/NotoSansGurmukhi-Regular.ttf: Noto Sans Gurmukhi:style=Regular

4. Open UTRRS: http://utrrs-testing.rhcloud.com/

5. Select Language from Left

6. Add font name in “Please enter font family name” (same as Bold text in Step 3)

 

Now you are ready to do Testing for Fonts with UTRRS.

Reference is Image data

Character/Text is data with Selected fonts (Noto Sans Gurmukhi)

Compare Reference with Character (for Code Ponits, GSUB, GPOS)

with Next post try to put information regarding Gurmukhi Fonts and some comparsion with Lohit on Fedora 20/21

CLDR – help to fix your Locale/Language Data

CLDR is Common Locale Data Repository.

Why is it important to me?

Are you using  any of MS Windows, Apple Mac, Linux (Ubuntu, Fedora, Red Hat, Debian) Operating system for Desktop/Laptop in you native Langauge?

Are you using iPhone, iPad, iPod, Android, Windows Phones?

Are you using any Google Services?

 

then this is Locale Repo, from where you Language Data is coming, which includes Date, Time format/name (like Mon, Tuesday or May 28, 2014 or 28 May, 2014). Here you can decide how it will look like.

Even if you don’t want to provide new entry, you can choose and Vote.

 

 

Fedora 19 i18n and Translation Test day

Fedora 19 Alpha released and it is best time to test translation and i18n feature, so that bugs can be timely fixed before release.

FLTG  team providing support for Translation Test Day and I18N Test Day by add, review test cases, search features and communicate between various groups.

for Translation Test Day, we add few more gnome applications (like gnome-initial setup) and remove features those are no more available or default in Fedora 19 (like ibus, which is not part of gnome desktop). Translation Test Matrix is improved, while Report Page and Feedback page is created. Anaconda, have major in-complete translation for almost in all language, while gnome-initial-setup, gnome-clock etc application those are new in gnome-3.8 are also have English interface.

Fedora i18n Test Day (May 02, 2013) is upcoming, where tester can get time to review feature for gnome-ibus integration, new shortcuts to Enable/Disable input (check i18n Meeting log for detail).

Major Rendering issue for Indic locales detected (Hindi, Punjabi confirmed and bug already filed) during pre-test activity. Actually this issue already reported for Anaconda (lorax) here, but but with gnu-free-fonts have bugs for Indic locales and set default for Monospace instead of Lohit fonts (as lohit is no monospace), now gnome desktop effecting by this. During i18n Meeting it was found that Either disable gnu-free-fonts for Indic language (those are effected), which is easy way or disable monospace for Indic

lokalize Junk data with qt 4.7.1 – workaround 2 (fedora)

when lokalize crash problem was fixed, then New problem arrived – Junk data in translated field

(check video here)

Steps to Reproduce:
1. run lokalize with translation file (PO file)
2. input something in local language (other than English)
3. Use BackSpace to delete some (not all)
5. Page Down (Move to next string)
6. Page Up (Move back to original String


Actual results:
Junk data inserted in text field automatically, which is not typed

Expected results:
Only Text should be there, which is typed, works fine with BackSpace

KDE bug 249373, kde-i18n mailing list discussion

OpenSUSE, kbuntu and Arch Linux user confirmed that problem.

Fedora workaround for this is below (on Fedora 14):
1) yum remove qt (it will remove whole kde, will not effect much if you are using other than KDE desktop)
2) yum remove kdelibs-common
3) Disable fedora-updates.repo (/etc/yum.repos.d/fedora-updates.repo)  (enabled=0)
4) yum install kdesdk (or other package which you want to install for kde)

Now your lokalize should work normal (qt-4.7.0-3.fc14.x86_64 from fedora 14 Released repo), but note 
that you are not going to get any update for your system (which includes security fixes also)

Nokia provide fix (Crash issue) for qt-4.7.2, but that patch was backport to 4.7.1 for many
distribution. Nobody respond to bug yet (from Nokia).

					

is Nokia preparing for Indian Language Input?

in NDTV’s Cellguru show, I just watched that Nokia show some demo for Indian language input. Video is available here, Few screen-shot for Nokia is below:

Finally Nokia is doing something for Indian languages on high-end phone. Symbian 3 already updated to support Malayalam and Gurmukhi (Punjabi), (other Indian locales are already supported). Nokia took much time to support, but if they bring this year or early next year, then also they can be first to support Indian Languages on Mobile with input. (Apple iPhone 4 has Rendering, font support, but not Input). android still not ready to rendering any Indian locale.

But still Nokia has PLAN, and there is no news from Nokia itself (officially), so ‘who knows tomorrow’

Yahoo IM got better Indic Rendering, but still minor update need for Punjabi…

Final release of Yahoo! Messenger (10.0.0.1258-in), it

provided support for Punjabi Language to input, specially I tested

for Punjabi (Gurmukhi) and Hindi. Rendering for Hindi is

quite good, but rendering for Punjabi need to improve, while type in

input box, it is good enough for Chat Box, but while type, it shows

space more than actual. (try to type with ka+Halant + Ra + SPACE + Ka)

Adding video about it, (Thanks to CamStudio),

surely Yahoo! IM has great improvement for Indic Languages, but Punjabi

still have some issue.

Chrome – test Drive…

Google chrome released long time back, I never tried it, but after using some mobile services and read about N900 + Chrome, I thought to test run. Finally start with Mac OS version, then tried on Linux (Fedora x86_64 RPM build by google), and Finally on Windows. It imported all data from Firefox on All platforms very easily , no error, and look was same on all OS, Same feel.

Book Mark Sync was quick feature, which I liked most as Firefox, need to install Weave and then it ask Few more username and password and PIN, then start sync, but for Chrome, someone need only Google a/c and it is done. But what I missed is Merge feature, which works better on Firefox (it ask what to merge), but chrome don’t. You have to merge or not sync at all. Secondly not sure, but I found it is not syncing Password and Browser history like Mozilla Weave

Overall smooth ride, cool look, faster loading, interface than Firefox.

for i18n/l10n point, it is not available in my language (Punjabi), for which I pushed Issue. For Indic, it is available in Bengali, Gujarati, Hindi, Marathi, Oriya, Tamil, Telugu.

it is Open Source, so got en-GB file to translate, start work if I can push to Google, where I am not sure whether they accept code or not.

KDE 4.4 and Indian Calendar System

I have never seen anywhere such a system,

but in KDE 4.4, in which Indian Calendar system

can be choose at Desktop system. 

In kde, choose systemsettings->Regional & Language

->Language-> Time and Date.

There is  Indian Calendar, so after login and logout,

you can check it.

Following image has enough detail about it.

KDE 4.4 with Phalgun Month

Month: Phalgun
Day: Som (Monday)
Year: 1931

with time, software becoming more useful and more
close not only to hi-fi people, but general public.
After all those are for them, by them.

N900 with Punjabi support….

I got N900 for Testing Punjabi on it.
While need to install fonts, I was not
clear about rendering after installing
fonts. it is based on Maemo Linux, so
you can install/use application easily

After install openssl-client/server,
scp lohit-punjabi fonts from fedora
machine to N900 and ‘fc-cache’,
run ‘fennec’.

While after reboot, I can see the
Punjabi in mail and other places
(no interface translation available yet).
Most Important thing was Rendering,
which is just working and good enough
to use. fonts was installed on N810, but
there is Punjabi Rendering was broken

More Screenshot you can check here

from i18n Point of view, following task with status:
—
-Fonts- Working – Need to package
-Rendering – Working – Nothing to Done
-Input – Need to Work – Need to Package
—

Now Android:
No Indian Language is supported as such, but

got a chance to check Samsung Galaxy Spica

It has Hindi Interface, but Rendering broken.
Same as Apple iPhone.

Now it seems Nokia should work fast, but less
hard to provide Indian language as Rendering is
working and just installing fonts can
help to enable support.