FontLab Forum
2010-09-02, 13:59:55 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the FontLab forum, read how to use it! Update: Archives from old MSN forums are now available on our forum.
 
   Home   Help Search Calendar Downloads Tags Login Register  
Del.icio.us Digg FURL FaceBook Stumble Upon Reddit SlashDot

Pages: [1]
  Print  
Author Topic: juktakshar problem in bengali font  (Read 1253 times)
potasiyam
Newbie
*

Karma: +0/-0
Bangladesh Bangladesh

Posts: 2


View Profile Email
« on: 2010-02-03, 19:05:28 »

I am developing a bengali font where i wanted to add this lookup স ্ প ্ ল -> স্প্ল (combining sa halant pa halant la).
But only স ্ প -> স্প (স্ প -> স্প) or প ্ ল -> প্ল (প্ ল -> প্ল) is posible with 'pres', not স ্ প ্ ল -> স্প্ল (স্প ্ ল -> স্প্ল or স্ প্ল -> স্প্ল)
It can not be use used with blwf and blws because of .
so what is the method for স্প্ল?

add:
1. I am working with 'beng', what should i change if i want to add 'bng2' support?
2. Volt comes with sample 'Mangal' font to understand the deva features. But Hindi & Bengali has lots of differences. Is there any Bengali sample font for volt?
« Last Edit: 2010-02-04, 13:26:57 by potasiyam » Logged
Andrew Glass (Microsoft)
Team: Microsoft
Jr. Member
****

Karma: +0/-0
United States United States

Posts: 6


View Profile
« Reply #1 on: 2010-03-29, 00:56:40 »

Perhaps you have done a half form substitution prior to pres? In which case the pres lookup should be something along the lines of: bn_half_sa bn_half_pa bn_la -> bn_s_p_la

Also be sure that this lookup comes before bn_half_pa bn_la -> bn_s_p_la.

There are two lookups that need to be changed for bng2 tags: blwf and pstf. The key difference is that for bng2 halanth has not been re-ordered. So where beng has bn_ba bn_halanth -> bn_ba_phala; bng2 has bn_halanth bn_ba -> bn_ba_phala. The same difference applies to the pstf lookup.

Unfortunately the Bengla fonts have not been licensed for distribution as a sample font for Volt.

I hope the above explanation helps!
Logged
OldKnip
Jr. Member
**

Karma: +0/-0
Germany Germany

Posts: 8


View Profile
« Reply #2 on: 2010-03-29, 06:55:25 »

My Bengali font has only <beng> lookups and works correctly under Word 7 though <blwf> and <pstf> features are using lookups with reordered halant!
Logged
OldKnip
Jr. Member
**

Karma: +0/-0
Germany Germany

Posts: 8


View Profile
« Reply #3 on: 2010-04-14, 10:23:19 »

I should perhaps have added "why?" to my last message to induce someone to give me an explanation.  Wink
Meanwhile I've added <bng2> to my <beng> font and made a font with only <bng2>. I've tried out these 3 fonts both on a Windows XP Professional and a Windows 7 Professional machine with the following results:

- <beng>+<bng2> font works on both machines, as expected.
- <bng2> font works only under Windows 7, as expected.
- <beng> font font works on both machines, unexpected for Windows 7 (as stated in my last message).

Can anybody tell me why <bng2> should be needed?
Logged
SpaceyT-17
Newbie
*

Karma: +0/-0
United Kingdom United Kingdom

Posts: 2



View Profile
« Reply #4 on: 2010-04-15, 21:25:21 »

@OldKnip:
It seems that Microsoft has retained the old layout algorithm for handling the beng script tag, while also including the algorithm for bng2. It must be to preserve backward compatibility. However, I honestly can't see why the bng2 script tag was introduced at all, since the new features like cjct are called by the beng algorithm. I've tested this on the Uniscribe included with Vista SP2 some time ago, but not with the version bundled in Windows 7.

@potasiyam:
You can open the Vrinda in Fontlab Studio demo version, which can generate a human-readable listing of compiled OT data. I've used it myself to get an example.
« Last Edit: 2010-04-15, 22:39:01 by SpaceyT-17 » Logged
OldKnip
Jr. Member
**

Karma: +0/-0
Germany Germany

Posts: 8


View Profile
« Reply #5 on: 2010-04-16, 06:21:23 »

Thanks, SpaceyT!
Meanwhile I've tested all my other Indic OT fonts under Windows 7. There were no rendering problems with (Bengali), Devanagari, Gujarati, Kannada, Oriya, Tamil and Telugu! Only Sinhala was not rendered properly; there was not even a glyph reordering with this script.

Microsoft says in its description of the new features: "While Indic fonts made according to the earlier recommendations will still function properly in the new versions of Uniscribe, font developers may choose to update their fonts, particularly if they wish to avoid certain limitations of the earlier implementation."

So it seems, that adding the new methods to the old ones is more or less superfluous. I'd like to know, what are the "certain limitations of the earlier implementation"?
« Last Edit: 2010-04-16, 06:23:06 by OldKnip » Logged
potasiyam
Newbie
*

Karma: +0/-0
Bangladesh Bangladesh

Posts: 2


View Profile Email
« Reply #6 on: 2010-05-01, 17:30:08 »

Perhaps you have done a half form substitution prior to pres? In which case the pres lookup should be something along the lines of: bn_half_sa bn_half_pa bn_la -> bn_s_p_la

Also be sure that this lookup comes before bn_half_pa bn_la -> bn_s_p_la.

There are two lookups that need to be changed for bng2 tags: blwf and pstf. The key difference is that for bng2 halanth has not been re-ordered. So where beng has bn_ba bn_halanth -> bn_ba_phala; bng2 has bn_halanth bn_ba -> bn_ba_phala. The same difference applies to the pstf lookup.

Unfortunately the Bengla fonts have not been licensed for distribution as a sample font for Volt.

I hope the above explanation helps!

Thanks Andrew.
It seems your method is the right way. I solved it temporarily with adding a second pres with bn_half_sa bn_p_la -> bn_s_p_la

I have decided to add bng2 features to my font. So I need to understand all the changes from beng and totally new features. Is there any complete documentation for bng2?
Logged
Tags:
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!