[Bf-translations-dev] Updated default font

[Dalai Felinto]

Bastien,

I thought Sergey idea was to replace only the missing Persian
characters into our Droid Sans bundle.
I found strange that Droid does not have Persian as a separate .ttf.
If they really can't be found I think it's totally doable to do them
manually (as Amin just suggested while I was typing here ;)

--
Dalai

2011/11/21 Bastien Montagne <montagne29 at wanadoo.fr>:
> Hi Yousef,
>
> Unfortunately, no, Persian is one of the language supported by the arabic
> unicode script. It shares most of its glyphs with "regular" arabic, and just
> has a few specificities... which aren’t currently supported by droidsans.
> And as said, mixing existing droid glyphs with dejavu for missing ones is
> just ugly, and source of endless problems... I found no other arabic ttf
> font suitable, but if you have a nice an complete one in mind, I could try
> to incorporate it.
>
> Regards,
> Bastien
>
> Le 22/11/2011 00:18, Yousef Hurfoush a écrit :
>
> why changing the Arabic font? doesn't Persian have a separate chars set from
> Arabic, why to change both ?
> the previous font was nearly flawless (are their any Arabic Chars missed )
> and more uniform in displaying than the new one!
>
> i don't see the need for changing it to DejaVuSans.
>
>>and we can’t mix both fonts in a same script
> surly that would be a hustle and miss the font itself.
>
> Regards
> Yousef Harfoush
>
> bat3a at msn.com
>
>
> ________________________________
> Date: Mon, 21 Nov 2011 21:01:35 +0100
> From: montagne29 at wanadoo.fr
> To: bf-translations-dev at blender.org
> Subject: Re: [Bf-translations-dev] Updated default font
>
> Hi,
>
> I’ve tried to get an enhanced version of that font, with quite mitigated
> success... Nepali (i.e. devanagari) is quite easy, but adding the missing
> persian glyphs is very tricky.
>
> Finally, I did the following:
> * Base font: my Debian DejaVuSans.ttf
> * Merged into: current Blender’s "droidsans.ttf" (which already contains
> many dejavu stuff…).
> * Merged into and scaled up 250%: samyak-devanagari.ttf
>
> Now I have that:
> * Arabic: http://www.pasteall.org/pic/21210 (left: old, right: new)
> * Persian: http://www.pasteall.org/pic/21212 (left: old, right: new)
> * Nepali: http://www.pasteall.org/pic/21211
>
> I fear arabic DejaVuSans is somewhat smaller that Droid one… but more
> complete, and we can’t mix both fonts in a same script (arabic), it would be
> far too messy imho…
>
> Waiting for your comments!
>
> Best regards,
> Bastien
>
> Le 18/11/2011 18:04, Sergey Sharybin a écrit :
>
> Hi all,
> I was reported that there are some issues with Persian language. Tried to
> resolve this.
> Well, at least ugly squares gone away, but now this glyphs are used from
> DejavySans font instead of DroidSans and they're looking a bit differ here.
> Unfortunately, i've got no idea if they are easy to read, so can somebody
> confirm that it's readable?
> Also Nepali support should been added, can somebody test this too?
> One more thing to test: font shouldn't have any noticeable difference from
> default font with English interface.
> Here's link to new
> font: http://download.blender.org/ftp/incoming/droidsans.ttf.gz
> Thanks,
>
> --
> With best regards, Sergey Sharybin
>
>
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>
>
> _______________________________________________ Bf-translations-dev mailing
> list Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>
>
> _______________________________________________
> Bf-translations-dev mailing list
> Bf-translations-dev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-translations-dev
>
>