On 25 July 2011 15:02, Arjuna Rao Chavala <[email protected]> wrote:

> Hi Vinod,
>
>  Thanks for your detailed explanation. Volt is proprietary software. Is it
> possible to transform so that it is compatible with fontforge.
>
>>
>> It is free tool for developing OpenType fonts. The fonts developed using
Volt do not become proprietary because the tool is. The Source version of
the font will be according to the Volt conventions and GUI but you can open
the binary form of the font in FontForge and make it into FontForge Source
form, I suppose. Prof Nagarjuna team developed all his fonts under
FontForge.

I remember that I had a showdown with Prof R K Joshi over this issue. At the
end when all the fonts were made using Volt, RK comes up with the idea that
now we will do it in FontForge as Volt is proprietary. Why did he not think
of this early in the project?

>
> I found out that CDAC's CD is not compatible with GPL. It prohibits
> commercial usage. There is no public site for tracking bugs and making
> revisions, nor there is any response when users suggest bugs and are ready
> to provide fixes.
>
>
>>
>> Show me where you found this in the IndiX site. Let me quote to you
excerpts from The IndiX Project LICENSE for software:
                      The IndiX Project LICENSE
                      -------------------------

                       Copyright 2004-2008 by
        Centre for Development of Advanced Computing, Mumbai


Introduction
============

  The IndiX  Project  is distributed   in  several archive packages;
  some of them may contain, in addition to the IndiX shaping engine,
  various tools and  contributions which rely on, or  relate to, the
  IndiX Project.

  This  license applies  to all  files found  in such  packages, and
  which do not  fall under their own explicit  license.  The license
  affects  thus  the  IndiX   shaping  engine,  the  test  programs,
  documentation and makefiles, at the very least.

  This  license   was  inspired  by  the  BSD,   Artistic,  and  IJG
  (Independent JPEG  Group) licenses, which  all encourage inclusion
  and  use of  free  software in  commercial  and freeware  products
  alike.  It is the same as the FreeType license, FT-license.txt. As
  a consequence, its main points are that:

    o We  don't  promise that  this software works.  However, we are
      interested in any kind of bug reports. (`as is' distribution)

    o You can  use this software for whatever you  want, in parts or
      full form, without having to pay us. (`royalty-free' usage)

    o You may not pretend that  you wrote this software.  If you use
      it, or  only parts of it,  in a program,  you must acknowledge
      somewhere in your documentation  that you've  used  the  IndiX
      code. (`credits')

  We  specifically  permit  and  encourage  the  inclusion  of  this
  software,  with  or without modifications, in commercial products,
  provided that all warranty or  liability claims are assumed by the
  product vendor.


Each font has a license which is  downloadable. Basically it says
that the font is GPL 2. No separate wording of the license
is given

The extract from the RaghuHindi license is:

Copyright

RaghuHindi font Original Version  1.00  (2005)  by  Centre  for  Development  of
Advanced Computing, Mumbai.

RaghuHindi  font  Original  Version  1.00 (2005) has been released under GNU GPL
Version 2.


Again we had a tough time getting the font design to be placed under GPL V2.

IndiX-2 project is completed and closed. Its products are available as
downloads but officially no more support is provided. But I still respond to
queries, and suggestions from a handful of  users. I actively try to promote
the viewpoint in the Unicode, OpenType and IndLinux public groups. I had
written several letters to Owen Taylor and later to Behdad Esfabod, but I am
disappointed that both of them did not reply.


>
>> Interesting idea, may be suitable for text  terminal as well in linux.
> Your approach seems to be updating XFree86 libraries. Will there be any
> conflict with Pango?  If it is possible to implement it as a pango module,
> without other changes, it will be useful, as we need to have one
> configurable library which can handle all the world's languages.
>
> XFree86 library update is what we had to do for implementing IndiX on Linux
distributions whose GUI is X11. The IndiX library has also been implemented
in other software like our printools. Interestingly, Mozilla browser worked
without any modifications on IndiX distribution (Knoppix with IndiX enable
XFree86 and IndiX fonts. This is the Live CD). So our approach is not
updating XFree86 libraries.

I believe that the Intelligent font approach would work with all complex
scripts. I am sure it works with the 9 Indic scripts. So modifying Pango or
ICU will only be a simplification. You can forget about parsing each
character in a syllable and tagging it with a four letter Feature tag.

vinod kumar
-- 
पृथिवी सस्यशालिनी
the earth be green
------------------------------------------------------------------------------
Storage Efficiency Calculator
This modeling tool is based on patent-pending intellectual property that
has been used successfully in hundreds of IBM storage optimization engage-
ments, worldwide.  Store less, Store more with what you own, Move data to 
the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/
_______________________________________________
IndLinux-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/indlinux-group

Reply via email to