indic-computing-devel Mailing List for The Indic-Computing Project (Page 3)
Status: Alpha
Brought to you by:
jkoshy
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(14) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(25) |
Feb
(90) |
Mar
(41) |
Apr
(16) |
May
(8) |
Jun
|
Jul
(37) |
Aug
(35) |
Sep
(62) |
Oct
(37) |
Nov
(22) |
Dec
(7) |
2003 |
Jan
(16) |
Feb
(19) |
Mar
(10) |
Apr
(5) |
May
(26) |
Jun
(11) |
Jul
(35) |
Aug
(4) |
Sep
(14) |
Oct
(5) |
Nov
(5) |
Dec
(10) |
2004 |
Jan
(25) |
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(10) |
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
(9) |
Dec
|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2006 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
From: Sumedh T. <sum...@ya...> - 2004-01-09 02:50:45
|
> Just googling 'mozilla devanagari' works as well ('ctl' is > not > likely to known to most people.). Of course, this is not to > say > that we don't need a good FAQ-like document. > > Jungshik Ofcourse you guys know better and .. I was able to get this working on my system with these assorted websites. But I think as more and more people are using Linux and have just basic knowledge of compiling etc.. A very compehensive FAQ/HOWTO will help these people who are not technical like we are. e.g. is the post from that archeology website where the person gave up after trying couple of times. These people may not necessarily get the difference between core X and XFT etc. I was able to get it working with bits of information from different places and it didn't work at first shot. Would be awesome if there is a FAQ that details how exactly to build it in first shot... that way more people will get onboard. Hope you get my point .. thanx! Sumedh __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Jungshik S. <js...@ma...> - 2004-01-09 00:23:52
|
On Fri, 9 Jan 2004, Jungshik Shin wrote: > On Thu, 8 Jan 2004, Sumedh Thakar wrote: > > Jungshik, Prabhat, Alok and others, you guys are doing a great > > job, please keep it up. Just so that others go through a less > > painful process than I did I have written down what I did and > P.S. If you google 'mozilla devanagari ctl', the second hit > is a thread on linux-utf8 mailing list with all the details. Just googling 'mozilla devanagari' works as well ('ctl' is not likely to known to most people.). Of course, this is not to say that we don't need a good FAQ-like document. Jungshik |
From: Jungshik S. <js...@ma...> - 2004-01-09 00:19:05
|
On Thu, 8 Jan 2004, Sumedh Thakar wrote: > I finally got this working with the TTF font on my redhat9.0 > system. its the latest 1.7a .. interestingly enough I was > getting the gmodule error etc. when I did the standard > ./configure make and make install. But when i used the gmake -f > client.mk build .. things stared working fine. The other mistake > I was making was that I had installed the font for the core X > and was doing the build for XFT. once i installed the fonts for > xconfig it works like a charm. The only thing is that the font Well, it does not work for 'justified' text. > size is small. Do you guys know why Open Type fonts still don't > work on linux? It does work if you apply the latest patch for bug 215219 (http://bugzilla.mozilla.org/show_bug.cgi?id=215219)? It works even for justified text. That's the only way Mozilla can render justified text written in complex script. You have to compile Mozilla with GTK2 + Xft (you do not need 'enable-ctl' although it won't hurt except in terms of the code size now that you managed to compile gtk2 + xft + ctl). With that patch, Mozilla relies on Pango (installed on your Linux) and can render as many complex scripts as supported by Pango (except for Hebrew and Arabic that are implemented internally in Mozilla.) > Jungshik, Prabhat, Alok and others, you guys are doing a great > job, please keep it up. Just so that others go through a less > painful process than I did I have written down what I did and Alok, why don't you update your page as I wrote you a week ago? Then, I'll refer to it in the international release notes. Jungshik P.S. If you google 'mozilla devanagari ctl', the second hit is a thread on linux-utf8 mailing list with all the details. |
From: Sumedh T. <sum...@ya...> - 2004-01-08 19:32:28
|
I finally got this working with the TTF font on my redhat9.0 system. its the latest 1.7a .. interestingly enough I was getting the gmodule error etc. when I did the standard ./configure make and make install. But when i used the gmake -f client.mk build .. things stared working fine. The other mistake I was making was that I had installed the font for the core X and was doing the build for XFT. once i installed the fonts for xconfig it works like a charm. The only thing is that the font size is small. Do you guys know why Open Type fonts still don't work on linux? Jungshik, Prabhat, Alok and others, you guys are doing a great job, please keep it up. Just so that others go through a less painful process than I did I have written down what I did and what were the problems, you can update your HowTo or something with this if needed so that its available through google search. Thanks again. Here is what i had to do if you guys want to post this as the latest info on one of the sites. *** install gtk-2.0-devl, glib-2.0-devl, pango, IDL and all the related packages. 1) pull the mozilla cvs tree starting with the client.mk file. setenv CVSROOT :pserver:ano...@cv...:/cvsroot cvs login password: anonymous) (You only need to login once) cvs co mozilla/client.mk cd mozilla ***before pulling the rest of the tree do the following. 2) create the ~/.mozconfig file with the options you want. in my case # sh # Build configuration script # # See http://www.mozilla.org/build/unix.html for build instructions. # # Options for client.mk. mk_add_options MOZ_MAKE_FLAGS=-j4 # Options for 'configure' (same as command-line options). # Do these to get a good ctl xft build ac_add_options --with-pthreads ac_add_options --enable-default-toolkit=gtk2 ac_add_options --enable-xft ac_add_options --enable-ctl # These are as per your preference ac_add_options --disable-composer ac_add_options --disable-debug ac_add_options --disable-mailnews ac_add_options --disable-ldap ac_add_options --disable-xprint ac_add_options --enable-crypto ac_add_options --disable-jsd *** I couldn't get the ctl to work well with a manual build using ./configure command and the above options. So create the above file that works best. *** Now pull the rest of the tree and do the compile. 3) gmake -f client.mk checkout (only first time. After that you can drop the 'checkout' at the end) 4) Just to be sure, you can build again using gmake -f client.mk build 5) get the two Saraswati fonts TTF from SUN. **very important install the fonts for the fontconfig/XFT system and not just the core X fonts if you do the --enable-xft build. Typical location for XFT font installation is /usr/share/fonts/ and use the fc-cache to update the font cache. 6) Now you can fire up the new mozilla binary from mozilla/dist/bin and in the font preferences change the fonts to 'Saraswati' for Unicode and Devnagri. and disable the 'let documents use their own fonts'. If you don't see the font in the font list, then the font is not in the right path. The test ofcourse is to go check the BBC website. Enjoy! - Sumedh __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Prabhat <pra...@su...> - 2004-01-06 23:07:49
|
ah!, Disable SUNCTL's gmodule checking in configure. I have'nt tried trunk build lately but this could be the problem you are facing. You will require no special support. prabhat Sumedh Thakar wrote: >Ok I got the latest CVS as of 12/31. I tired to compile with the >following options .. > >--enable-ctl --enable-xft --disable-composer --disable-mailnews >--enable-crypto --disable-debug --enable-optimize >--enable-default-toolkit=gtk2 > >And i keep getting the following message .. > >checking for libIDL-2.0 >= 0.8.0... yes >checking LIBIDL_CFLAGS... -I/usr/local/include/glib-2.0 >-I/usr/local/lib/glib-2.0/include -I/usr/include/libIDL-2.0 >checking LIBIDL_LIBS... -L/usr/local/lib -lIDL-2 -lglib-2.0 >configure: error: Cannot build ctl without gmodule support in >glib. > > >i have glib-2.3.1 and gtk+-2.3.1 >I have redhat9.0 > >do I need to do anything special for the gmodule support in >glib? pkg-config shows me gmodule-2.0 and glib-2.0 is installed. > >Sumedh >--- Jungshik Shin <js...@ma...> wrote: > > >>On Fri, 2 Jan 2004, Jungshik Shin wrote: >> >> >> >>>Alok Kumar wrote: >>> >>> >>>> --- Sumedh Thakar <sum...@ya...> wrote: > I >>>> >>>> >>tried >> >> >>>>1.5 with enable-ctl but the hindi >>>> >>>> >>>> >>>>>doesn't show correctly. The only thing i can think of is >>>>> >>>>> >>the >> >> >>>>>font I downloaded in TTF format as against the PCF as >>>>> >>>>> >>mentioned. >> >> >>>>While I do have the font in pcf format, I wonder if the >>>> >>>> >>ttf fonts are >> >> >>>>also >>>>supposed to work? >>>> >>>> >>> TTF should work, too. There are two different ways. The >>> >>> >>easier of >> >> >>>two is to build your Mozilla with Xft and CTL enabled. Then, >>> >>> >>do the >> >> >>>following: >>> >>> >> For an Xft build, you need to download the latest trunk >>source from >>the cvs. Alternatively, you can apply the patch at >>http://bugzilla.mozilla.org/show_bug.cgi?id=203406 if you want >>to build a Mozilla with 1.6branch source. >> >> Jungshik >> >> > > >__________________________________ >Do you Yahoo!? >Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes >http://hotjobs.sweepstakes.yahoo.com/signingbonus > > |
From: Sumedh T. <sum...@ya...> - 2004-01-06 22:57:25
|
Ok I got the latest CVS as of 12/31. I tired to compile with the following options .. --enable-ctl --enable-xft --disable-composer --disable-mailnews --enable-crypto --disable-debug --enable-optimize --enable-default-toolkit=gtk2 And i keep getting the following message .. checking for libIDL-2.0 >= 0.8.0... yes checking LIBIDL_CFLAGS... -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/include/libIDL-2.0 checking LIBIDL_LIBS... -L/usr/local/lib -lIDL-2 -lglib-2.0 configure: error: Cannot build ctl without gmodule support in glib. i have glib-2.3.1 and gtk+-2.3.1 I have redhat9.0 do I need to do anything special for the gmodule support in glib? pkg-config shows me gmodule-2.0 and glib-2.0 is installed. Sumedh --- Jungshik Shin <js...@ma...> wrote: > > On Fri, 2 Jan 2004, Jungshik Shin wrote: > > > Alok Kumar wrote: > > > --- Sumedh Thakar <sum...@ya...> wrote: > I > tried > > > > > 1.5 with enable-ctl but the hindi > > > > > >>doesn't show correctly. The only thing i can think of is > the > > >>font I downloaded in TTF format as against the PCF as > mentioned. > > > > > While I do have the font in pcf format, I wonder if the > ttf fonts are > > > also > > > supposed to work? > > > TTF should work, too. There are two different ways. The > easier of > > two is to build your Mozilla with Xft and CTL enabled. Then, > do the > > following: > > For an Xft build, you need to download the latest trunk > source from > the cvs. Alternatively, you can apply the patch at > http://bugzilla.mozilla.org/show_bug.cgi?id=203406 if you want > to build a Mozilla with 1.6branch source. > > Jungshik __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: jkoshy@FreeBSD.ORG (J. Koshy) - 2004-01-03 16:42:00
|
cherry> Koshy, could you please post the exact diff to the share/mk tree cherry> which I sent you ? Forwarded. Regards, Koshy <jk...@fr...> ------- Forwarded Message Message-ID: <118...@we...> Date: Wed, 13 Aug 2003 21:05:14 +0600 (LKT) Subject: patches. From: "Cherry George Mathew" <ch...@fr...> To: jk...@fr... Reply-To: ch...@fr... User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: multipart/mixed;charset=iso-8859-1; boundary="----=_20030813210514_32452" X-Priority: 3 Importance: Normal Status: R - ------=_20030813210514_32452 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit here's a few patches in the doc/share/mk subdirectory Check it out and give me feedback. I have to work on: Webmake for debian peps for debian and yes, bsd make for debian. Will update. Cherry. PS: The id header is from my local versioning on emacs (RCS). I don't know if it will cause problems for you. - -- - ------=_20030813210514_32452 Content-Type: text/plain; name="doc.docbook.mk.diff" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="doc.docbook.mk.diff" *** /tmp/doc.docbook.mk.~1.1~1973TcB Wed Aug 13 16:49:47 2003 - --- /tmp/doc.docbook.mk1973gmH Wed Aug 13 16:49:47 2003 *************** *** 1,4 **** ! # $Id: doc.docbook.mk,v 1.1 2003/08/13 08:00:39 cherry Exp $ # # $FreeBSD: doc/share/mk/doc.docbook.mk,v 1.68 2002/06/04 11:40:17 nik Exp $ # - --- 1,4 ---- ! # $Id: doc.docbook.mk,v 1.2 2003/08/13 10:32:39 cherry Exp $ # # $FreeBSD: doc/share/mk/doc.docbook.mk,v 1.68 2002/06/04 11:40:17 nik Exp $ # *************** *** 129,144 **** FREEBSDCATALOG= ${DOC_PREFIX}/share/sgml/catalog LANGUAGECATALOG=${DOC_PREFIX}/${LANGCODE}/share/sgml/catalog ! ISO8879CATALOG= ${PREFIX}/share/sgml/iso8879/catalog .if ${STYLESHEET_TYPE} == "dsssl" ! DOCBOOKCATALOG= ${PREFIX}/share/sgml/docbook/catalog .elif ${STYLESHEET_TYPE} == "xsl" DOCBOOKCATALOG= ${PREFIX}/share/xml/docbook/catalog .endif ! DSSSLCATALOG= ${PREFIX}/share/sgml/docbook/dsssl/modular/catalog ! COLLATEINDEX= ${PREFIX}/share/sgml/docbook/dsssl/modular/bin/collateindex.pl XSLTPROC?= ${PREFIX}/bin/xsltproc XSLHTML?= ${DOC_PREFIX}/share/xsl/freebsd-html.xsl - --- 129,149 ---- FREEBSDCATALOG= ${DOC_PREFIX}/share/sgml/catalog LANGUAGECATALOG=${DOC_PREFIX}/${LANGCODE}/share/sgml/catalog ! #ISO8879CATALOG= ${PREFIX}/share/sgml/iso8879/catalog ! ISO8879CATALOG= ${PREFIX}/share/sgml/entities/sgml-iso-entities-8879.1986/cat alog .if ${STYLESHEET_TYPE} == "dsssl" ! DOCBOOKCATALOG= ${PREFIX}/share/sgml/docbook/dtd/generalized.cat ! # TODO: Which version of XML ? Debian comes with v3 -> v4.2 .elif ${STYLESHEET_TYPE} == "xsl" DOCBOOKCATALOG= ${PREFIX}/share/xml/docbook/catalog + #DOCBOOKCATALOG= ${PREFIX}/share/sgml/docbook/dtd/xml/X.X/docbook.cat .endif ! #DSSSLCATALOG= ${PREFIX}/share/sgml/docbook/dsssl/modular/catalog ! DSSSLCATALOG= ${PREFIX}/share/sgml/docbook/stylesheet/dsssl/modular/catalog ! #COLLATEINDEX= ${PREFIX}/share/sgml/docbook/dsssl/modular/bin/collateindex.pl ! COLLATEINDEX= ${PREFIX}/bin/collateindex.pl XSLTPROC?= ${PREFIX}/bin/xsltproc XSLHTML?= ${DOC_PREFIX}/share/xsl/freebsd-html.xsl *************** *** 151,157 **** - --- 156,167 ---- -c ${DSSSLCATALOG} -c ${ISO8879CATALOG} \ -c ${DOCBOOKCATALOG} -c ${JADECATALOG} \ ${EXTRA_CATALOGS:S/^/-c /g} + + .if defined(CANONICALOBJDIR) SGMLFLAGS+= -D ${CANONICALOBJDIR} + .endif + + JADEOPTS= ${JADEFLAGS} ${SGMLFLAGS} ${CATALOGS} KNOWN_FORMATS= html html.tar html-split html-split.tar \ *************** *** 205,211 **** PDFTEX?= ${PREFIX}/bin/pdftex GROFF?= groff TIDY?= ${PREFIX}/bin/tidy ! TIDYOPTS?= -i -m -raw -preserve -f /dev/null ${TIDYFLAGS} HTML2TXT?= ${PREFIX}/bin/links HTML2TXTOPTS?= -dump ${HTML2TXTFLAGS} HTML2PDB?= ${PREFIX}/bin/iSiloBSD - --- 215,222 ---- PDFTEX?= ${PREFIX}/bin/pdftex GROFF?= groff TIDY?= ${PREFIX}/bin/tidy ! #TIDYOPTS?= -i -m -raw -preserve -f /dev/null ${TIDYFLAGS} ! TIDYOPTS?= -i -m -raw -xml -f /dev/null ${TIDYFLAGS} HTML2TXT?= ${PREFIX}/bin/links HTML2TXTOPTS?= -dump ${HTML2TXTFLAGS} HTML2PDB?= ${PREFIX}/bin/iSiloBSD - ------=_20030813210514_32452 Content-Type: text/plain; name="doc.images.mk.diff" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="doc.images.mk.diff" *** /tmp/doc.images.mk.~1.1~19735AB Wed Aug 13 16:44:56 2003 - --- /tmp/doc.images.mk1973GLH Wed Aug 13 16:44:56 2003 *************** *** 1,4 **** ! # $Id: doc.images.mk,v 1.1 2003/08/13 10:35:58 cherry Exp $ # # $FreeBSD: doc/share/mk/doc.images.mk,v 1.16 2002/02/06 16:26:41 bmah Exp $ # - --- 1,4 ---- ! # $Id: doc.images.mk,v 1.2 2003/08/13 10:37:21 cherry Exp $ # # $FreeBSD: doc/share/mk/doc.images.mk,v 1.16 2002/02/06 16:26:41 bmah Exp $ # *************** *** 123,130 **** EPSTOPDFOPTS?= ${EPSTOPDFFLAGS} PS2EPS?= ${PREFIX}/bin/ps2epsi PIC2PS?= ${GROFF} -p -S -Wall -mtty-char -man ! FIG2EPS?= ${X11BASE}/bin/fig2dev -L eps ! FIG2PNG?= ${X11BASE}/bin/fig2dev -L png # Use suffix rules to convert .scr files to .png files .SUFFIXES: .scr .pic .png .eps .fig - --- 123,132 ---- EPSTOPDFOPTS?= ${EPSTOPDFFLAGS} PS2EPS?= ${PREFIX}/bin/ps2epsi PIC2PS?= ${GROFF} -p -S -Wall -mtty-char -man ! #FIG2EPS?= ${X11BASE}/bin/fig2dev -L eps ! FIG2EPS?= ${PREFIX}/bin/fig2dev -L eps ! #FIG2PNG?= ${X11BASE}/bin/fig2dev -L png ! FIG2PNG?= ${PREFIX}/bin/fig2dev -L png # Use suffix rules to convert .scr files to .png files .SUFFIXES: .scr .pic .png .eps .fig - ------=_20030813210514_32452 Content-Type: text/plain; name="doc.project.mk.diff" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="doc.project.mk.diff" *** /tmp/doc.project.mk.~1.1~ Wed Aug 13 16:48:56 2003 - --- /tmp/doc.project.mk Wed Aug 13 16:48:56 2003 *************** *** 1,4 **** ! # $Id: doc.project.mk,v 1.1 2003/08/13 09:42:15 cherry Exp $ # # $FreeBSD: doc/share/mk/doc.project.mk,v 1.12 2002/02/25 14:24:51 murray Exp $ # - --- 1,4 ---- ! # $Id: doc.project.mk,v 1.2 2003/08/13 10:34:58 cherry Exp $ # # $FreeBSD: doc/share/mk/doc.project.mk,v 1.12 2002/02/25 14:24:51 murray Exp $ # *************** *** 65,71 **** ALL_FORMATS= html html.tar html-split html-split.tar txt rtf ps pdf tex dvi tar pdb # User-modifiable ! LOCALBASE?= /usr/local PREFIX?= ${LOCALBASE} PRI_LANG?= en_US.ISO8859-1 - --- 65,72 ---- ALL_FORMATS= html html.tar html-split html-split.tar txt rtf ps pdf tex dvi tar pdb # User-modifiable ! #LOCALBASE?= /usr/local ! LOCALBASE?= /usr PREFIX?= ${LOCALBASE} PRI_LANG?= en_US.ISO8859-1 - ------=_20030813210514_32452-- ------- End of Forwarded Message |
From: Cherry G. M. <ber...@ya...> - 2004-01-03 07:26:16
|
Dear Alok, List, First of all, apologies for the delay. My shell a/c admin and the lists.sf.net admin had a difference of opinion over the last month. And I was left out in the cold. So its back to good old web-based email for some time now..... >> Dear Cherry, and list, >> dependancy. Do tell me if you find one. Can move this >> discussion to indic-computing-devel, btw ? HTH, [...] >Incidentally, uname -a would never tell me I'm using a redhat distro. [...] >So how does a shell script know which distro it's being run on? On RedHat Linux systems, the rc.sysinit script verifies that its working on an RH system like this: ____________________________________________________ # Print a text banner. echo -en $"\t\tWelcome to " if LC_ALL=C grep -q "Red Hat" /etc/redhat-release ; then [ "$BOOTUP" = "color" ] && echo -en "\\033[0;31m" echo -en "Red Hat" [ "$BOOTUP" = "color" ] && echo -en "\\033[0;39m" PRODUCT=`sed "s/Red Hat \(.*\) release.*/\1/" /etc/redhat-release` echo " $PRODUCT" else PRODUCT=`sed "s/ release.*//g" /etc/redhat-release` echo "$PRODUCT" fi if [ "$PROMPT" != "no" ]; then echo -en $"\t\tPress 'I' to enter interactive startup." echo sleep 1 fi ______________________________________________________ >Have been banking on deb2rpm once Cherry gets it going. Cherry, would the output of your efforts be a .deb? Yes, that's the idea. When the .deb gets included in the apt-get system, dependencies get resolved automatically, which is the objective of the effort in the first place - a tool _chain_. Sorry about the late reply once again. Haven't looked at the sources in a while. Koshy, could you please post the exact diff to the share/mk tree which I sent you ? Thanks, Best Wishes, Cherry. __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ |
From: Jungshik S. <js...@ma...> - 2004-01-02 16:26:07
|
On Fri, 2 Jan 2004, Jungshik Shin wrote: > Alok Kumar wrote: > > --- Sumedh Thakar <sum...@ya...> wrote: > I tried > > > 1.5 with enable-ctl but the hindi > > > >>doesn't show correctly. The only thing i can think of is the > >>font I downloaded in TTF format as against the PCF as mentioned. > > > While I do have the font in pcf format, I wonder if the ttf fonts are > > also > > supposed to work? > TTF should work, too. There are two different ways. The easier of > two is to build your Mozilla with Xft and CTL enabled. Then, do the > following: For an Xft build, you need to download the latest trunk source from the cvs. Alternatively, you can apply the patch at http://bugzilla.mozilla.org/show_bug.cgi?id=203406 if you want to build a Mozilla with 1.6branch source. Jungshik |
From: Jungshik S. <js...@ma...> - 2004-01-02 14:59:05
|
On Fri, 2 Jan 2004, Jungshik Shin wrote: > If you still have a problem, launch Mozilla under hi_IN.UTF-8 > (hi_IN.utf8) locale. That is, set your locale to that > before launching Mozilla. > > $ LC_ALL=hi_IN.UTF-8 mozilla If you don't like launching Mozilla under hi_IN locale (for instance, you're in UK and you prefer en_UK.UTF-8), there are two ways: A. set LC_CTYPE=hi_IN.UTF-8, but set LANG to en_UK.UTF-8 (do not define other LC* variables unless you want to override LANG) B. 'enlighten' your friends and other web developers that it's always a good practice to specify the language of the content in html and xhtml. See http://www.w3.org/International (tips and faqs) as to how to specify the language of your web content I wrote a few times to BBC to specify 'lang=hi' in their BBC Hindi site and was finally told that they would in a couple of weeks. > BTW, you may try my patch for bug 215219 > (http://bugzilla.mozilla.org/show_bug.cgi?id=215219). It doesn't rely > on Sun fonts but take advantage of opentype fonts. You have to build a > mozilla with 'gtk2' and 'xft' (but ctl is NOT necessary). If you need this patch, Mozilla doesn't need the help of 'lang/xml:lang' (or the locale), but still it's a good practice to specify the language of web contents. Jungshik |
From: Jungshik S. <js...@ma...> - 2004-01-02 14:51:18
|
Alok Kumar wrote: > Hi Sumedh, > > --- Sumedh Thakar <sum...@ya...> wrote: > I tried > 1.5 with enable-ctl but the hindi > >>doesn't show correctly. The only thing i can think of is the >>font I downloaded in TTF format as against the PCF as mentioned. > While I do have the font in pcf format, I wonder if the ttf fonts are > also > supposed to work? > The problem has been reported elsewhere as well: > <http://archaeology.artefact.org.nz/archives/000091.html> > TTF should work, too. There are two different ways. The easier of two is to build your Mozilla with Xft and CTL enabled. Then, do the following: 1. put Saraswati fonts into one of directories looked into by fontconfig. 2. Launch Mozilla 3. go to Edit | Pref | Appearance | Font| Devanagari and set all four categories to Saraswati. 4. Also make sure that 'allow documents to use other fonts' is NOT checked If you still have a problem, launch Mozilla under hi_IN.UTF-8 (hi_IN.utf8) locale. That is, set your locale to that before launching Mozilla. $ LC_ALL=hi_IN.UTF-8 mozilla For an X11core font build, you need to do the following: 1. download sun.unicode.india-0.enc file from Xfree86 cvs (web interface or cvs command can be used) : see bug http://bugs.xfree86.org/show_bug.cgi?id=939 [1] 2. gzip and install it in /usr/X11R6/lib/fonts/encodings/large 3. put the Sun Indic TTF in a directory 4. run mkfontscale and mkfontdir (it'll add -altsys-saraswati5-medium-r-normal--0-0-0-0-p-0-iso10646-1 and antoher for bold) 5. add to fonts.scale and fonts.dir -altsys-saraswati5-medium-r-normal--0-0-0-0-p-0-sun.unicode.india-0 6. restart your X font server - give it a HUP signal - (if you use one) or your Xserver (if you don't use an x font server) 7. configure mozilla the way described above for Xft build. BTW, you may try my patch for bug 215219 (http://bugzilla.mozilla.org/show_bug.cgi?id=215219). It doesn't rely on Sun fonts but take advantage of opentype fonts. You have to build a mozilla with 'gtk2' and 'xft' (but ctl is NOT necessary). Jungshik [1] You don't need to download it, but that way it's easier (for an alternative, read my comment in the bug) and a bit faster. Besides, if you have a new version of mkfontscale (that knows about sun.unicode.india-0, you don't have to take step 5) P.S. Printing only works with Xprint. However, when my patch for bug 208213 (http://bugzilla.mozilla.org/show_bug.cgi?id=208213) is landed, printing with freetype2 should work as well. |
From: <al...@ya...> - 2004-01-02 14:14:00
|
Hi Sumedh, --- Sumedh Thakar <sum...@ya...> wrote: > I tried compiling mozilla 1.5 with enable-ctl but the hindi > doesn't show correctly. The only thing i can think of is the > font I downloaded in TTF format as against the PCF as mentioned. > While I do have the font in pcf format, I wonder if the ttf fonts are also supposed to work? The problem has been reported elsewhere as well: <http://archaeology.artefact.org.nz/archives/000091.html> Perhaps Prabhat could throw some light on this. Also, while we're at it, <http://jsecom15.sun.com/ECom/EComActionServlet?StoreId=8&PartDetailId=INDIAN-FONT-G-F&transactionId=Try&LMLoadBalanced=> has changed from the pcf download site to the ttf download site. I remember having requested a download of the ttf versions myself, but not at the expense of the pcf's! Prabhat, if you could let us know the location of the pcf download, if it is distinct from this one, it would be great. Searching via google or via the Sun website search didn't help(no results are returned for hindi font). Sumedh, let's wait till Prabhat replies, it may take a couple of days since the weekend follows. Regards Alok ________________________________________________________________________ Yahoo! India Mobile: Download the latest polyphonic ringtones. Go to http://in.mobile.yahoo.com |
From: Dr. U.B. P. <pav...@vi...> - 2004-01-01 04:52:15
|
Hi all, I wish a very happy and fruitful new year 2004 for all Indic-ers. Let us hope to see something really great in this year of Science Regards, Pavanaja http://www.bhashaindia.com/ |
From: jkoshy@FreeBSD.ORG (J. Koshy) - 2003-12-30 09:20:29
|
> -D \ This part is definitely wrong. '-D ' has to be followed by a directory name. Basically, this facility (-D) allows the generated HTML files to be created in a directory other than where the sources are present. The rest of the command line is clearly out of sync from this point onwards since jade takes the next option '-c' as the directory name. "$INDIC/share/mk/doc.docbook.mk" defines SGMLFLAGS as follows doc.docbook.mk:159:SGMLFLAGS+= -D ${CANONICALOBJDIR} CANONICALOBJDIR is defined in "/usr/share/mk/bsd.obj.mk" .if defined(MAKEOBJDIRPREFIX) CANONICALOBJDIR:=${MAKEOBJDIRPREFIX}${.CURDIR} .else CANONICALOBJDIR:=/usr/obj${.CURDIR} .endif You could work around the problem by (a) defining CANONICALOBJDIR in the environment, (b) or wrapping line 159 in doc.docbook.mk with a `.if defined(CANONICALOBJDIR)'. This may not be the only issue though: you really should have a compatible set of BSD make "system" rules (i.e. /usr/share/mk/bsd.*.mk) also. Perhaps Cherry can speak about how he handled these dependencies in his Debian 'port' of the toolchain. Regards, Koshy <jk...@fr...> |
From: <alo...@so...> - 2003-12-30 03:53:59
|
Hello friends, (1) I'm running bmake on the handbook makefile. Attempting this command[1], gave this error[2] /usr/local/bin/jade:E: cannot find "-c"; tried "-c", "-c/-c" is the first error message. I suspect that jade needs a -c <something> argument, which is provided, but is garbled because of what's coming before it. If I put the -c arguments before everything else, I get a different set of errors. The -ioutput.html line looks fishy to me. So does -D <nothing> . Any clues? (2) realpath is not around in redhat 8.0. share/mk/doc.images.mk has this line _GSFP!= realpath ${DOC_PREFIX}/share/fonts Is it ok if we just assign ${DOC_PREFIX}/share/fonts to _GSFP to avoid using realpath? Many thanks in advance Alok [1] The command is (line breaks are mine) /usr/local/bin/jade \ -V html-index \ -ioutput.html \ -d /home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl \ -ioutput.html.images \ -i chap.index \ -i chap.introduction \ -i chap.tutorial \ -i chap.locales \ -i chap.x-indic \ -i chap.std.intro \ -i chap.std.iscii \ -i chap.std.isclap \ -i chap.std.isfoc \ -i chap.std.ksclp \ -i chap.std.unicode \ -i chap.script.intro \ -i chap.script.devanagari \ -i chap.script.gujarati \ -i chap.script.gurmukhi \ -i chap.script.kannada \ -i chap.script.malayalam \ -i chap.script.tamil \ -i chap.script.telugu \ -i chap.script.urdu \ -i chap.lang.intro \ -i chap.lang.assamese \ -i chap.lang.hindi \ -i chap.lang.gujarati \ -i chap.lang.kannada \ -i chap.lang.kashmiri \ -i chap.lang.konkani \ -i chap.lang.malayalam \ -i chap.lang.manipuri \ -i chap.lang.marathi \ -i chap.lang.nepali \ -i chap.lang.oriya \ -i chap.lang.punjabi \ -i chap.lang.sindhi \ -i chap.lang.tamil \ -i chap.lang.telugu \ -i chap.lang.urdu \ -i chap.bibliography \ -i chap.eresources \ -D \ -c /home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../en_US.ISO8859-1/share/sgml/catalog \ -c /home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/catalog \ -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ -c /usr/local/share/sgml/iso8879/catalog \ -c /usr/local/share/sgml/docbook/catalog \ -c /usr/local/share/sgml/jade/catalog \ -t sgml /home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/book.sgml \ > /dev/null [2] This command gives the error: /usr/local/bin/jade:E: cannot find "-c"; tried "-c", "-c/-c" /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/catalog:1:2:E: character "-" not allowed in prolog /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/catalog:8:2:E: character "-" not allowed in prolog /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/catalog:15:2:E: character "-" not allowed in prolog /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/catalog:24:1:E: character """ not allowed in prolog /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/catalog:32:2:E: character "-" not allowed in prolog /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/catalog:37:5:E: character "a" not allowed in prolog /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/catalog:46:2:E: character "-" not allowed in prolog /usr/local/bin/jade:E: cannot find "-c"; tried "-c", "-c/-c" /usr/local/bin/jade:/usr/local/share/sgml/docbook/dsssl/modular/catalog:1:0:E: character "O" not allowed in prolog /usr/local/bin/jade:/usr/local/share/sgml/docbook/dsssl/modular/catalog:12:2:E: character "l" not allowed in prolog /usr/local/bin/jade:/usr/local/share/sgml/docbook/dsssl/modular/catalog:23:2:E: this is not an SGML document /usr/local/bin/jade:/usr/local/share/sgml/docbook/dsssl/modular/catalog:23:2:E: cannot continue because of previous errors /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:6:73:W: cannot generate system identifier for public text "-//James Clark//DTD DSSSL Style Sheet//EN" /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:8:0:E: reference to entity "STYLE-SHEET" for which no system identifier could be generated /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:6:0: entity was defined here /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:8:0:E: DTD did not contain element declaration for document type name /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:7:0:E: notation "DSSSL" for entity "indic-computing.dsl" undefined /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:10:12:E: element "STYLE-SHEET" undefined /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:11:27:E: there is no attribute "USE" /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:11:36:E: element "STYLE-SPECIFICATION" undefined /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:12:29:E: element "STYLE-SPECIFICATION-BODY" undefined /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:16:29:E: there is no attribute "ID" /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:16:48:E: there is no attribute "DOCUMENT" /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:16:69:E: element "EXTERNAL-SPECIFICATION" undefined /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:17:13:E: end tag for "EXTERNAL-SPECIFICATION" omitted, but its declaration does not permit this /usr/local/bin/jade:/home/alok/de/indic-computing/doc/en_US.ISO8859- 1/books/handbook/../../../share/sgml/default.dsl:16:2: start tag was here /usr/local/bin/jade:E: specification document does not have the DSSSL architecture as a base architecture -- alok_kumar ऍट softhome डॉट net http://devanaagarii.net/hi/alok/blog Can't see Hindi? http://devanaagarii.net http://groups.yahoo.com/group/linux-bangalore-hindi/ Discuss devanagari at http://groups.yahoo.com/group/devanaagarii/ |
From: <alo...@so...> - 2003-12-25 00:03:13
|
Dear Cherry, and list, > dependancy. Do tell me if you find one. Can move this > discussion to indic-computing-devel, btw ? HTH, Good idea. This is with reference to <https://sourceforge.net/tracker/?func=detail&atid=421536&aid=844834&group_id=38057> We're looking for bmake on debian/rh. If it's already there in some form or the other(maybe known by another name) we can avoid having to build it in the documentation toolchain. Does anyone know of any? Incidentally, uname -a would never tell me I'm using a redhat distro. The uname output for me is Linux localhost.localdomain 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux So how does a shell script know which distro it's being run on? Have been banking on deb2rpm once Cherry gets it going. Cherry, would the output of your efforts be a .deb? Haven't been doing much on the indic front lately, hope to correct that, the vested interest being getting the devanagari script docs checked in. I already have more for review. आलोक -- alok_kumar ऍट softhome डॉट net http://devanaagarii.net/hi/alok/blog Can't see Hindi? http://devanaagarii.net http://groups.yahoo.com/group/linux-bangalore-hindi/ Discuss devanagari at http://groups.yahoo.com/group/devanaagarii/ |
From: <kut...@ya...> - 2003-12-09 17:51:45
|
http://www.economist.com/printedition/PrinterFriendly.cfm?Story_ID=2246308 MONITOR Open source's local heroes Dec 4th 2003 From The Economist print edition Software: If the commercial sort does not speak your language, open-source software may well do so instead ITS POPULARITY is growing around the world, but open-source software has particular appeal in developing countries. In China, South Korea, India, Brazil and other countries, governments are promoting the use of such software which, unlike the proprietary kind, allows users to inspect, modify and freely redistribute its underlying programming instructions. The open-source approach has a number of attractions. Adopting open-source software can reduce costs, allay security concerns and ensure there is no danger of becoming too dependent on a foreign supplier. But there is another benefit, too: because it can be freely modified, open-source software is also easier to translate, or localise, for use in a particular language. This involves translating the menus, dialogue boxes, help files, templates and message strings to create a new version of the software. Large software vendors have little incentive to support any but the most widely spoken languages. Microsoft, for example, provides its Windows 2000 operating system in 24 languages, and Windows XP in 33. The company also supports over 20 languages in the latest version of its Office software suite. Yet for many languages, commercial vendors conclude that producing a localised product is not economically viable. The programmers who produce open-source software operate by different rules, however. The leading desktop interfaces for the open-source Linux operating systemKDE and GNOMEare, between them, available in more than twice as many languages as Windows. KDE has already been localised for 42 languages, with a further 46 in the pipeline. Similarly, Mozilla, an open-source web browser, now speaks 65 languages, with 34 more to follow. OpenOffice, the leading open-source office suite, is available in 31 languages, including Slovenian, Basque and Galician, and Indian languages such as Gujarati, Devanagari, Kannada and Malayalam. And another 44 languages including Icelandic, Lao, Latvian, Welsh and Yiddish are on the way. Localising software is a tedious job, but some people are passionate enough about it to resort to unusual measures. The Hungarian translation of OpenOffice was going too slowly for Janos Noll, founder of the Hungarian Foundation for Free Software. So he built some web-based tools to distribute the workload and threw a pizza party in the computer room at the Technical University of Budapest. Over a dozen people worked locally, with about 100 Hungarians submitting work remotely over the web. Most of the worktranslating over 21,000 text stringswas completed in three days. Dwayne Bailey of translate.org.za, an open-source translation project based in South Africa, says localising open-source programs into Zulu, Xhosa, Venda, Sesotho and other African languages makes computers more accessible. With translated software, these languages are suddenly players in the modern world. Neville Alexander, a former South African freedom-fighter, agrees. An English-only or even an English-mainly policy necessarily condemns most people, and thus the country as a whole, to a permanent state of mediocrity, since people are unable to be spontaneous, creative and self-confident if they cannot use their first language, he says. Open source opens doors A similar approach is being taken in India, where there are 18 official languages and over 1,000 regional dialects. Shikha Pillai is one of the leaders of a team in Bangalore that is translating open-source software, including OpenOffice, into ten Indian dialects. She, too, feels that introducing Indian languages will help to foster a far deeper penetration of information technology. Localisation makes IT accessible to common people, she says. And Indian-language enabled software could revolutionise the way our communications work; even the way computers are used in India. In May, Thailand's government launched a subsidised people's PC that runs LinuxTLE, a Thai-language version of Linux. In September, Japan said it would join a project established by China and South Korea to develop localised, open-source alternatives to Microsoft's software. Computer users around the world are discovering that open-source software speaks their language. ________________________________________________________________________ Yahoo! India Mobile: Download the latest polyphonic ringtones. Go to http://in.mobile.yahoo.com |
From: Dr. U.B. P. <pav...@vi...> - 2003-12-09 14:54:19
|
<?xml version="1.0" ?><html> <head> <title></title> </head> <body> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Bhasha India is giving you an opportunity to win an all expenses paid trip to Microsoft Office in Redmond, USA to attend the Global Development and Deployment Conference in the month of February 2004! All you need to do is to prove and showcase your talent in Indian Language Software Development and win name, fame and glory! </span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Check out http://www.bhashaindia.com/ </span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Good Luck!!! </span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Rgds, </span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Pavanaja -----------------------------------------------------</span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Dr. U.B. Pavanaja</span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Editor, Vishva Kannada</span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">World's first Internet magazine in Kannada</span></font></p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">http://www.vishvakannada.com/</span></font></p> <p><br/> </p> <p><font face="Times New Roman" size="3"><span style="font-size:12pt">Note: I don't worry about pselling mixtakes</span></font></p> <p></p> </body> </html> |
From: jkoshy@FreeBSD.ORG (J. Koshy) - 2003-12-03 06:14:40
|
> I'm wondering, have you integrated the changes to the doc/* tree yet ? No. If you are referring to the diff to doc/share/mk/*.mk---that was fairly intrusive and broke building the doc/ tree under BSD. I've been planning to rework the Makefiles in the share/mk directory to cleanly separate the path/filename specification bits from the rest of the make rules; this turns out to be un-straightforward the way the .mk files are currently written. We also need a way of separating the OS dependent bits from the rest of the make rules --- what does the output of `uname -a` look like on a Debian box? [RH/SuSE/Mandrake users, could you please post this for your systems too?] jk> 'cd' to src/package-definitions/doc-toolchain/debian, jk> and type 'make package' to have 'make' generate the final I'd like to add the 'source' parts of your Debian packaging effort to the Indic tree. Which files in the tarball are 'source' (i.e., used to generate the tarball)? Regards, Koshy <jk...@fr...> |
From: Dr. U.B. P. <pav...@vi...> - 2003-12-02 17:58:47
|
------- Forwarded message follows ------- Subject: [indic] Oriya: unusual conjuncts Date sent: Tue, 2 Dec 2003 09:41:35 -0800 From: "Peter Constable" <pet...@mi...> To: "Indic Unicode" <In...@un...> I have various questions regarding Oriya conjuncts. I posted this to the Unicode list yesterday, but thought I should try here instead. On pages 56 -57 of the TDIL newsletter from April 2002 (http://tdil.mit.gov.in/ori-guru-telu.pdf), there are various conjuncts listed that are unusual in that the shapes that make up the conjunct are quite different from the nominal characters that supposedly underlie the conjunct and from the pronunciation. Relevant portions from that newsletter are provided in the attached files, Oriya_unusual_conjuncts_1.png to Oriya_unusual_conjuncts_4.png. These show the conjunct and the underlying nominal characters underlying each conjunct. That source doesn't give indication of the pronunciation, but that the nominal character sequences described matches pronunciation is shown for at least two of the conjuncts by samples from the book "Oriya Self-Taught", in the attached file Oriya_unusual_conjuncts_5.png. Another unusual conjunct from that book is shown in Oriya_unusual_conjuncts_6.png. So, my question is how should these conjucts be encoded? - using characters suggested by the shapes; thus the 2nd conjunct in Oriya_unusual_conjuncts_1.png would be < nya, virama, tha, virama, cha > Or - according to pronunciation, following the sequences shown in the TDIL document; thus, the 2nd conjunct in Oriya_unusual_conjuncts_1.png would be encoded as < nya, virama, cha> Peter Peter Constable Globalization Infrastructure and Font Technologies Microsoft Windows Division ------- End of forwarded message ------------------------------------------------------------ Dr. U.B. Pavanaja Editor, Vishva Kannada World's first Internet magazine in Kannada http://www.vishvakannada.com/ Note: I don't worry about pselling mixtakes |
From: Cherry G. M. <ch...@sd...> - 2003-12-02 14:03:32
|
On Mon, 1 Dec 2003, Joseph Koshy wrote: > Let me clarify the goals a bit: > > Goal 1: To create the necessary src infrastructure that allows us > to be able to cvs checkout an Indic-Computing source tree, > 'cd' to src/package-definitions/doc-toolchain/debian, > and type 'make package' to have 'make' generate the final > .debs that we upload to the SF.net file release > system. > This is the stuff that I'd been asking about for a long while. I was wondering why on earth anybody would want to make the tools from a CVS source checkout. hmm.... now it makes sense. > > Goal 2: To create/modify/maintain the necessary infrastructure in > 'doc/*' so that a user who, having installed the necessary [...] > We are nearly there at Goal 2 for Debian systems that install your I'm wondering, have you integrated the changes to the doc/* tree yet ? If so is there a specific tag that needs to be pulled down ? I remember our earlier discussion about focusing on getting the documentation to be compiled and worry about source integration later. Just wondering..... Thanks for the updates. BTW, this is also a call for folk who want to try out building the doc-toolchain into rpms. Best, Cherry. -- ch...@sd... Homepage - http://cherry.freeshell.org |
From: jkoshy@FreeBSD.ORG (J. Koshy) - 2003-12-01 15:22:04
|
> Sure thing now. I should focus on making some Makefiles to be included in > the downloadable listed on sf.net. Let me clarify the goals a bit: Goal 1: To create the necessary src infrastructure that allows us to be able to cvs checkout an Indic-Computing source tree, 'cd' to src/package-definitions/doc-toolchain/debian, and type 'make package' to have 'make' generate the final .debs that we upload to the SF.net file release system. Goal 1': -ditto- but to make .rpms. Note that we are creating the .debs, or .rpms in this step, not installing anything on the build host. The build host could perhaps be a FreeBSD system which runs Linux software quite well. Goal 2: To create/modify/maintain the necessary infrastructure in 'doc/*' so that a user who, having installed the necessary indic-computing .deb/.rpm/.whatever packages would be able to type 'make' (or 'freebsdmake') and have the system generate the complete Indic-Computing documentation set. We are nearly there at Goal 2 for Debian systems that install your ".deb" packages. However, the procedure you followed to create these ".deb"s has still to be automated (i.e. we want others to replicate/maintain your work) --- hence Goal 1. Hope this clarifies. Regards, Koshy <jk...@fr...> |
From: Cherry G. M. <ch...@sd...> - 2003-12-01 07:36:53
|
On Tue, 25 Nov 2003, Joseph Koshy wrote: > Now that your exams and other interrupts are over ... can we get > back to the Indic toolchain packaging thing? > Sure thing now. I should focus on making some Makefiles to be included in the downloadable listed on sf.net. Then we can get the tools to compile with make install; The make system should take care of identifiying the system ( Debian/ Red Hat/ What not ) and issue corresponding pkg level commands. We'll start with Debian though. Nothing like apt-get ;-) Best, Cherry. PS: Should start coding once I get rid of my current RH installation ( at last! ) and get my NetBSD s/m up and running to taste. AFter that Debian needs to be installed..... OK its a private todo. I'm just griping ;-) -- ch...@sd... Homepage - http://cherry.freeshell.org |
From: Alok K. <alo...@so...> - 2003-11-19 00:53:06
|
Hi, > > I suspect this comes at the first occurrence of a .include statement > in the makefile. bmake : http://www.crufty.net/help/sjg/bmake.html , successfully built bmake from source, the README was good. Thanks to Tapan for pointing this out. More questions, of course, will follow. Alok -- http://9211.blogspot.com Can't see Hindi? http://geocities.com/alkuma/seehindi.html http://groups.yahoo.com/group/linux-bangalore-hindi/ Discuss devanagari at http://groups.yahoo.com/group/devanaagarii/ alok_kumar ऍट softhome डॉट net |
From: Aseem A. <asa...@cs...> - 2003-11-17 00:24:59
|
* Alok Kumar <alo...@so...> [2003-11-15 21:00 PST]: > Hi, > I'm in the process of building the handbook on redhat, and eventually > creating the rpms for others to be be able to do that. > > Now, when I run make using the handbook makefile, which is doc/en*/ > books/handbook/Makefile, I get > Makefile:137: *** missing separator. Stop. while I not a 'handbook' expert nor do I know for a fact whether the following will actually solve your problem, but a very common mistake is to use spaces while listing rules in Makefiles. For example target: dependencies_whatever cc -whatever ^^^^^^^^ <---- this should be a tab instead of spaces. HTH. -- "Where the clear stream of reason has not lost its way into the dreary desert sand of dead habit" -- Geetanjali |