[l2h] Free Software Company
What I am giving below is off topic but relevant to everyone associated with free software. I hope most of you might have heard about Richard M. Stallman (RMS) and the Free Software Foundation (FSF), especially those aligned with TeX are no doubt allies of the free software movement ignited by RMS. An intense discussion is going on at [EMAIL PROTECTED] for the formation of a Free Software Company entirely owned by the free developers world wide (100,000 developers expected) to safeguard the moral, social and ethical foundations on which FSF was built up, to provide appropriate monetary compensation and quality life to a free software developer he deserves in all the fairness and to fight the merciless commerce of the proprietary software corporates. These being the primary objectives, Tony Stanco [EMAIL PROTECTED] (an associate of RMS, who moderates the list) describe it in the following way: 1. Proprietary code is the enemy. It must be destroyed for developers and the world to be free. Open source is an ally. 2. Developers can be paid salaries and/or stock options to work on free code without violating the core principles of free code. 3. Mergers and acquisitions of proprietary companies are not objectionable in defeating proprietary. 4. A company of free developers, by free developers, for free developers is an acceptable vehicle to achieve the ends of free code. 5. A requirement in the certificate of incorporation that all code owned by the company is licensed under GPL or other tying to FSF is appropriate to ensure that the core principles of free software are observed going forward and to protect from slipping back to proprietary. 6. A democratic, free developer run corporation does not require special safeguards to protect ordinary world citizens. As one of the developing nations, in India or in any developing nation, where automation has just started, Free Software Company and FSF have plenty of implications. 1. In the first place, our poor economy cant afford to the fancy prices of proprietary software (maybe due to the foriegn exchange conversion magic). 2. Free Software can meet any objective, functionality that is claimed by the proprietary. 3. The huge man power resources generated in each and every place of higher academic learning in this country get a chance to contribute to the free software movement, while he earns a substantially increased income comparable to his counterpart in any proprietary corporate, as an employee of the proposed company. The discussions tend to provide the standard wages in India as in any part of the world. That will surely solve the disturbing problems of migration in many an Indian family. 4. There are plenty of requirement for software in this country for meeting its target of total automation for which each and every government or other agencies stand for today. Free software can meet their objectives on sound moral, ethical and social foundations than any other proprietary corporate. A Case Study: The Govt. of Kerala has formed an IT mission to automate the 1000 and odd Gram Panchayats (the lowest unit of elected body at village level) of this state. It is a massive and aggressive project to bring details of all the citizens of this state into a huge database, each Panchayat becoming a resource center for the government and at the same time act as the information exchange medium between the public and the government. This is an ideal project for the free software movement. The government have earmarked around Rs. 800,000 per Panchayat for using proprietary software and related development as initial investment and Rs. 150,000 as annual recurring expenses. While this came as a proposal, the Linux Users and TeX Users Groups came forward to negotiate with the government to do the project at a cost of Rs. 150,000 per Panchyat as initial expenses and rs. 20,000 as recurring expenses. But we were turned down, just because, we were considered to be a group of free thinkers, whom no responsible government can rely upon. Had there been a corporate entity with FSF objectives to compete with the proprietary agencies, the public exchecquer would have saved millions of rupees, the developers in this or neighbouring states would have got employment. Still the project is not finalized due to the media stir we raised and the seminars of users groups wherein the government nominees were special invitees. To make matters difficult for the government, the Cochin Linux Users Group came up with a viable, stable, functional software model which the political bureaucracy cannot overlook or deny. The final decision was postponed and still lingering. That means we have not lost the race, the global Free Software Company can still fight it out once it is formally incorporated. Tens of thousands of projects are in the offing which we all can undertake. This is the
[l2h] newbie, problem with \url + lyx
I'm installing latex2html-99.2beta8 in RedHat 6.2. After I export *.lyx to *.tex, and convert it with latex2html, I always got errors like this. No implementation found for style `url' redefining command \url I checked in /usr/share/texmf/ls-R, url.sty is in /usr/share/texmf/tex/latex/html and /usr/share/texmf/tex/latex/misc Can someone tell me what's wrong with it ? -- -AZ- [EMAIL PROTECTED]
Re: [l2h] newbie, problem with \url + lyx
When I try, I use lyx to convert it to .tex. Then I use latex2html, it
makes my \url isn't convert to hyper-links. So although I add
\url{http://www.blah.com} will not be a hyper-links. Do you have any
solution to fix it ?
Thanks for your time.
It isn't an error message -- it's just a warning.
Only if there is something wrong with your output, related to URLs,
should there be any need to worry about this.
redefining command \url
I checked in /usr/share/texmf/ls-R, url.sty is in
/usr/share/texmf/tex/latex/html and /usr/share/texmf/tex/latex/misc
Can someone tell me what's wrong with it ?
With LaTeX, all extensions are loaded using \usepackage{ ..blah.. }
but with LaTeX2HTML, many LaTeX packages are implemented internally
using Perl coding;
e.g. generating hyperlinks is fundamental to HTML,
but it is just a fancy effect for LaTeX.
On the other hand, many LaTeX packages are quite irrelevant to
an HTML translation and need no implementation at all.
Thus the "no implementation" message just means that there is
no implementation for a particular \usepackage{...} .
Whether that is of concern is something that you can determine
only by looking at your HTML output.
Hope this helps,
Ross Moore
--
-AZ- [EMAIL PROTECTED]
--
-AZ-
[EMAIL PROTECTED]
Re: [l2h] newbie, problem with \url + lyx
I've had errors like this before. My Linux solution is to make a soft link as follows: ln -s /usr/share/texmf/tex/latex/html/url.sty url.tex L2H includes *.tex files but for some reason won't include *.sty files. Let me know how this works for you. Regards, Jerry Place Assoc. Prof. of Computer Science Computer Science Telecommunications Program U. of Missouri - Kansas City 5100 Rockhill Road Kansas City, MO 64110 USA On Wed, 13 Sep 2000, Arie Zanahar wrote: I'm installing latex2html-99.2beta8 in RedHat 6.2. After I export *.lyx to *.tex, and convert it with latex2html, I always got errors like this. No implementation found for style `url' redefining command \url I checked in /usr/share/texmf/ls-R, url.sty is in /usr/share/texmf/tex/latex/html and /usr/share/texmf/tex/latex/misc Can someone tell me what's wrong with it ? -- -AZ- [EMAIL PROTECTED]
Re: [l2h] newbie, problem with \url + lyx
Date: Wed, 13 Sep 2000 02:52:54 +0700 (JAVT)
From: Arie Zanahar [EMAIL PROTECTED]
To: Ross Moore [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: [l2h] newbie, problem with \url + lyx
When I try, I use lyx to convert it to .tex. Then I use latex2html, it
makes my \url isn't convert to hyper-links. So although I add
\url{http://www.blah.com} will not be a hyper-links. Do you have any
solution to fix it ?
Seems to be rather a Lyx question than a latex2html one, but...
here is what I understood about this problem.
Lyx produces its own encodeing for an url as:
\htmlurl[anchor]{URL}
This is very bad, as \htmlurl is defined also
in the html.sty package, required for LaTeX2HTML.
(as are many other commands with names starting \html).
Lyx should use the name \lyxurl or something else that is distinct to
its own name of Lyx.
Typographically, it prints anchor as is and URL with the url.sty
wrapping to avoid problems with long words.
Then to sort out the mess caused by the name clash, you will need
conditional code like the following in the document preamble:
%begin{latexonly}
\let\lyxurl\htmlurl % save a pointer to lyx's \htmlurl
%end{latexonly}
\usepackage{html}% ensure that html.sty is loaded
\begin{htmlonly}
\renewcommand{\htmlurl}[2][]{%
\htmladdnormallink{#1}{#2}}
\end{htmlonly}
%begin{latexonly}
\let\htmlurl\lyxurl % recover the pointer to lyx's \htmlurl
%end{latexonly}
Now you should be able to use \htmlurl
for all the hyperlinks, both with LyX and with LaTeX2HTML.
However...
... the optional argument is now *mandatory*.
LaTeX2HTML may not produce a link for \htmlurl{URL}
without any anchor text.
So everything is there to produce a good hypertext, but the
exported latex does not know \htmladdnormallink or its typographical
version \htmladdnormallinkfoot...
So two ways to deal with it:
- write e translator for \htmlurl to produce A HREF="URL"anchor/A
The above code effectively does this, by converting Lyx's use
of \htmlurl into a form that LaTeX2HTML already knows how to handle.
Also it opens up the full power of html.sty for markup
intended mainly for the HTML version of a document.
- process the lyx file to create the right code using html.sty
I have here a workaround using the second approach, which puts
a lot of ERT (i.e. plain (La)TeX commands) in the original LyX file.
Certainly it is good to use markup defined from html.sty
so that there are not too many (perhaps incompatible) styles
being used to markup URLs in LaTeX documents.
An alternative approach is to define your own command; e.g. \myurl
using conditional definitions:
\usepackage{html}
\begin{htmlonly}
% perhaps load HTML-specific definitions from a .tex file
% \input myHTMLdefs.tex
%
% or define \myurl here
\newcommand{\myurl}[2]{\htmladdnormallink{#1}{#2}}
%
\end{htmlonly}
%begin{latexonly}
% perhaps load Lyx-specific definitions from a .sty file
% \usepackage{myLyXdefs}
%
% or define \myurl here
\newcommand{\myurl}[2]{\lyxurl[#1]{#2}}
%
%end{latexonly}
(assuming \lyxurl is a pointer to the real macro expansion).
Hope this helps.
And this too.
Ross Moore
--
Jean-Pierre
