[NTG-context] No full Unicode-Support in ConTeXt?

2013-11-24 Thread H. Özoguz

Hello there,

I wonder why working with fonts is soo hard in ConText (much easier in 
Word or CorelDraw).


See this following font (free, opensource): 
http://fonts.qurancomplex.gov.sa/wp-content/uploads/2012/06/UthmanTN1-Ver10.zip


And try now this Context-Code:

\definefont[arabic][file:UthmanTN1Ver10.ttf*arabic at 15pt]


\starttext

\arabic\setupalign[r2l]


مِن قَبْلُ هُدًى لِّلنَّاسِ وَأَنزَلَ ٱلْفُرْقَانَۗ إِنَّ ٱلَّذِينَ كَفَرُوا بِـَٔايَـٰتِ ٱللَّهِ لَهُمْ عَذَابٌ شَدِيدٌۗ 
وَٱللَّهُ عَزِيزٌ ذُو ٱنتِقَامٍ


\stoptext


You see, this little signs above the letters are vanished in the PDF. 
But they are set in CoreDraw (for example). Why, what is the problem?


Similar problems you can see with another font, no problem in CorelDraw, 
but problems in ConText.

Hope for help.

Thank you very much.

Huseyin









___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] No full Unicode-Support in ConTeXt?

2013-11-24 Thread Hans Hagen

On 11/24/2013 4:41 PM, H. Özoguz wrote:

Hello there,

I wonder why working with fonts is soo hard in ConText (much easier in
Word or CorelDraw).

See this following font (free, opensource):
http://fonts.qurancomplex.gov.sa/wp-content/uploads/2012/06/UthmanTN1-Ver10.zip


And try now this Context-Code:

\definefont[arabic][file:UthmanTN1Ver10.ttf*arabic at 15pt]


\starttext

\arabic\setupalign[r2l]


شَدِيدٌۗ
وَٱللَّهُ عَزِيزٌ ذُو ٱنتِقَامٍ

\stoptext


You see, this little signs above the letters are vanished in the PDF.
But they are set in CoreDraw (for example). Why, what is the problem?

Similar problems you can see with another font, no problem in CorelDraw,
but problems in ConText.
Hope for help.


not at all, as you show way more input here as in the jpeg ... so first 
make a minimal example


also another font is not revealing either

anyway,

\definefont[arabic][file:arabtype.ttf*arabic at 15pt]

\starttext
\arabic\setupalign[r2l] شَدِيدٌۗ
\stoptext

shows me a little sign above the word

Hans




-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] No full Unicode-Support in ConTeXt?

2013-11-24 Thread Hans Hagen

On 11/24/2013 6:09 PM, Hans Hagen wrote:


shows me a little sign above the word


the only issue i see is that this otf font has 2048 units and gets 
scaled wrong (in luatex's backend probably)


definefont[arabica][file:uthmantn1-ver10.otf*arabic at 45pt]
\definefont[arabicb][file:arabtype.ttf*arabic at 45pt]

\starttext
\setupalign[r2l]
\arabica شَدِيدٌۗ\par
\arabicb شَدِيدٌۗ\par
\page
\showotfcomposition{file:uthmantn1-ver10.otf*arabic}{r2l}{شَدِيدٌۗ}
\page
\showotfcomposition{file:arabtype.ttf*arabic*arabic}{r2l}{شَدِيدٌۗ}
\stoptext

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] No full Unicode-Support in ConTeXt?

2013-11-24 Thread Khaled Hosny
On Sun, Nov 24, 2013 at 06:31:27PM +0100, Hans Hagen wrote:
 On 11/24/2013 6:09 PM, Hans Hagen wrote:
 
 shows me a little sign above the word
 
 the only issue i see is that this otf font has 2048 units and gets scaled
 wrong (in luatex's backend probably)

It is actually a TTF font but the extension confuses ConTeXt (we
discussed this very issue before).
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] No full Unicode-Support in ConTeXt?

2013-11-24 Thread Hans Hagen

On 11/24/2013 6:38 PM, Khaled Hosny wrote:

On Sun, Nov 24, 2013 at 06:31:27PM +0100, Hans Hagen wrote:

On 11/24/2013 6:09 PM, Hans Hagen wrote:


shows me a little sign above the word


the only issue i see is that this otf font has 2048 units and gets scaled
wrong (in luatex's backend probably)


It is actually a TTF font but the extension confuses ConTeXt (we
discussed this very issue before).


afaik it passes the right unit value so the backend gets confused ... 
okay, we could probably specify a font to be truetype when units ~= 1000 
but still ... i have no problem with forcing


if units ~= 1000 and format ~= truetype then
properties.format = truetype
end

if we can assume all opentype fonts to be 1000

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] No full Unicode-Support in ConTeXt?

2013-11-24 Thread Khaled Hosny
On Sun, Nov 24, 2013 at 06:48:05PM +0100, Hans Hagen wrote:
 On 11/24/2013 6:38 PM, Khaled Hosny wrote:
 On Sun, Nov 24, 2013 at 06:31:27PM +0100, Hans Hagen wrote:
 On 11/24/2013 6:09 PM, Hans Hagen wrote:
 
 shows me a little sign above the word
 
 the only issue i see is that this otf font has 2048 units and gets scaled
 wrong (in luatex's backend probably)
 
 It is actually a TTF font but the extension confuses ConTeXt (we
 discussed this very issue before).
 
 afaik it passes the right unit value so the backend gets confused ... okay,
 we could probably specify a font to be truetype when units ~= 1000 but still
 ... i have no problem with forcing
 
 if units ~= 1000 and format ~= truetype then
 properties.format = truetype
 end
 
 if we can assume all opentype fonts to be 1000

No we can't. What we really need is a way for the fontloader to expose
the format in the font table, because it already knows it.

Regards,
Khaled
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] No full Unicode-Support in ConTeXt?

2013-11-24 Thread Hans Hagen

On 11/24/2013 6:50 PM, Khaled Hosny wrote:

On Sun, Nov 24, 2013 at 06:48:05PM +0100, Hans Hagen wrote:

On 11/24/2013 6:38 PM, Khaled Hosny wrote:

On Sun, Nov 24, 2013 at 06:31:27PM +0100, Hans Hagen wrote:

On 11/24/2013 6:09 PM, Hans Hagen wrote:


shows me a little sign above the word


the only issue i see is that this otf font has 2048 units and gets scaled
wrong (in luatex's backend probably)


It is actually a TTF font but the extension confuses ConTeXt (we
discussed this very issue before).


afaik it passes the right unit value so the backend gets confused ... okay,
we could probably specify a font to be truetype when units ~= 1000 but still
... i have no problem with forcing

if units ~= 1000 and format ~= truetype then
 properties.format = truetype
end

if we can assume all opentype fonts to be 1000


No we can't. What we really need is a way for the fontloader to expose
the format in the font table, because it already knows it.


ok, so we need a format key in the raw font table (truetype or 
opentype)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___