really obsolete content and move info on recent versions
that is considered still relevant to appropriate (sub)sections on the same
page. I really put much effort in organizing the FAQ thematically and I'd like
to avoid unsorted pages whatsoever.
Jürgen
was dated.
I'd rather delete really obsolete content and move info on recent versions
that is considered still relevant to appropriate (sub)sections on the same
page. I really put much effort in organizing the FAQ thematically and I'd like
to avoid unsorted pages whatsoever.
Jürgen
What would you think about creating a section labeled Obsolete (or
something similar) and moving pages with archaic content to it? They
would still appear in searches, but hopefully the location would inform
the reader that the information was dated.
/Paul
What would you think about creating a section labeled "Obsolete" (or
something similar) and moving pages with archaic content to it? They
would still appear in searches, but hopefully the location would inform
the reader that the information was dated.
/Paul
Richard Heck wrote:
Did some...will try to do more later.
Thanks. I proceed myself from time to time.
Jürgen
Richard Heck wrote:
> Did some...will try to do more later.
Thanks. I proceed myself from time to time.
Jürgen
Hi,
On Thu, 28 Feb 2008, Apache wrote:
* http://wiki.lyx.org/FAQ.ERT . . . 2008-02-28 10:40 CET by jspitzm
Juergen has done a terrific job in revering spam, e.g. on the page
http://wiki.lyx.org/FAQ/ERT
I've now given in and changed it so that a password is required to edit
Hi,
On Thu, 28 Feb 2008, Apache wrote:
* http://wiki.lyx.org/FAQ.ERT . . . 2008-02-28 10:40 CET by jspitzm
Juergen has done a terrific job in revering spam, e.g. on the page
http://wiki.lyx.org/FAQ/ERT
I've now given in and changed it so that a password is required to edit
of LyX? I see that this FAQ was written originally for version 1.0.
Sincerely,
Ran Rutenberg
Ran Rutenberg schrieb:
I see that this FAQ was written originally for version 1.0.
Yes, the FAQ is completely out of date. But I don't think it's worth to update it, since the new
docs cover also the FAQ issues.
Uwe
of LyX? I see that this FAQ was written originally for version 1.0.
Sincerely,
Ran Rutenberg
Ran Rutenberg schrieb:
I see that this FAQ was written originally for version 1.0.
Yes, the FAQ is completely out of date. But I don't think it's worth to update it, since the new
docs cover also the FAQ issues.
Uwe
Hi,
I think it is a very good idea to write this FAQ, and to put it in the wiki.
So I would like to make some comments:
1) Not always LANG variable works. Sometimes is necessary to use another
variable. For example with Mandriva 2006 with KDE you need to use KDE_LANG,
and with Mandriva 2007
I think it is a very good idea to write this FAQ, and to put it in the wiki.
So I would like to make some comments:
the best would be if you get file from svn
http://www.lyx.org/trac/browser/lyx-devel/trunk/README.localization
and write the patch with your comments against that file.
i
On Mon, 5 Mar 2007, Pavel Sanda wrote:
I think it is a very good idea to write this FAQ, and to put it in the wiki.
So I would like to make some comments:
the best would be if you get file from svn
http://www.lyx.org/trac/browser/lyx-devel/trunk/README.localization
and write the patch
What page? It's possible to automatically have the wiki page embed
something from SVN.
http://wiki.lyx.org/Devel/POFAQ
pavel
Am Montag, 5. März 2007 20:34 schrieb Ramon Flores:
Hi,
I think it is a very good idea to write this FAQ, and to put it in the
wiki.
That would be the fourth place where this is documented. Please have a look
at this bug: http://bugzilla.lyx.org/show_bug.cgi?id=3314
So I would like
On Mon, 5 Mar 2007, Pavel Sanda wrote:
What page? It's possible to automatically have the wiki page embed
something from SVN.
http://wiki.lyx.org/Devel/POFAQ
I added this code to the wiki page
white-space=pre background-color=#ee
(:includesvn README.localization :)
Hi,
I think it is a very good idea to write this FAQ, and to put it in the wiki.
So I would like to make some comments:
1) Not always LANG variable works. Sometimes is necessary to use another
variable. For example with Mandriva 2006 with KDE you need to use KDE_LANG,
and with Mandriva 2007
> I think it is a very good idea to write this FAQ, and to put it in the wiki.
>
> So I would like to make some comments:
the best would be if you get file from svn
http://www.lyx.org/trac/browser/lyx-devel/trunk/README.localization
and write the patch with your comments against that
On Mon, 5 Mar 2007, Pavel Sanda wrote:
I think it is a very good idea to write this FAQ, and to put it in the wiki.
So I would like to make some comments:
the best would be if you get file from svn
http://www.lyx.org/trac/browser/lyx-devel/trunk/README.localization
and write the patch
> What page? It's possible to automatically have the wiki page embed
> something from SVN.
http://wiki.lyx.org/Devel/POFAQ
pavel
Am Montag, 5. März 2007 20:34 schrieb Ramon Flores:
> Hi,
>
> I think it is a very good idea to write this FAQ, and to put it in the
wiki.
That would be the fourth place where this is documented. Please have a look
at this bug: http://bugzilla.lyx.org/show_bug.cgi?id=3314
> So
On Mon, 5 Mar 2007, Pavel Sanda wrote:
What page? It's possible to automatically have the wiki page embed
something from SVN.
http://wiki.lyx.org/Devel/POFAQ
I added this code to the wiki page
>>white-space=pre background-color=#ee<<
(:includesvn README.localization
I wrote a small FAQ for the po files. I would be glad if someone could
have a glance at
i made small changes. see attached patch.
pavel
--- PO FAQ 2007-02-24 14:37:44.0 +0100
+++ PO FAQ.new 2007-02-24 14:38:38.0 +0100
@@ -10,9 +10,12 @@
1) WHERE DO I START?
The file
Uwe Stöhr a écrit :
JMarc, could this also be added to branch?
Yes, as soon as it has stabilized on trunk.
Thanks for doing it Ran.
JMarc
Ran:
It looks fine but there are a a few things I would consider to change in the
patch:
ran, maybe you can get in touch with diff and patch comands, you'll need it
in the future for sure :) e.g.:
diff -u README.localization README.localization.new updates.txt
or
cat updates.txt |patch ... i
On Sat, 24 Feb 2007, Jean-Marc Lasgouttes wrote:
Uwe Stöhr a écrit :
JMarc, could this also be added to branch?
Yes, as soon as it has stabilized on trunk.
As Ran had put the text here initially,
http://wiki.lyx.org/Devel/POFAQ
I simply added a link from that page into the SVN
> I wrote a small FAQ for the po files. I would be glad if someone could
> have a glance at
i made small changes. see attached patch.
pavel
--- PO FAQ 2007-02-24 14:37:44.0 +0100
+++ PO FAQ.new 2007-02-24 14:38:38.0 +0100
@@ -10,9 +10,12 @@
1) WHERE DO I START?
Th
Uwe Stöhr a écrit :
JMarc, could this also be added to branch?
Yes, as soon as it has stabilized on trunk.
Thanks for doing it Ran.
JMarc
>Ran:
>It looks fine but there are a a few things I would consider to change in the
>patch:
ran, maybe you can get in touch with diff and patch comands, you'll need it
in the future for sure :) e.g.:
"diff -u README.localization README.localization.new > updates.txt"
or
"cat updates.txt
On Sat, 24 Feb 2007, Jean-Marc Lasgouttes wrote:
Uwe Stöhr a écrit :
JMarc, could this also be added to branch?
Yes, as soon as it has stabilized on trunk.
As Ran had put the text here initially,
http://wiki.lyx.org/Devel/POFAQ
I simply added a link from that page into the SVN
On 2/13/07, Pavel Sanda [EMAIL PROTECTED] wrote:
it comes up in my mind - maybe you can shortly write your question and answers
as a small FAQ and append it to README file in the po directory, since the
informations are obsolete there. it could help to the next new translators
I wrote
On 2/13/07, Pavel Sanda <[EMAIL PROTECTED]> wrote:
it comes up in my mind - maybe you can shortly write your question and answers
as a small FAQ and append it to README file in the po directory, since the
informations are obsolete there. it could help to the next new translators
I
Hi
If we reach some clever conclusions about the FAQ, I've made a page a on
the wiki to put them:
http://wiki.lyx.org/pmwiki.php/DevelDoc/AboutTheFAQ
/Christian
PS. It's very convenient to refer to posts from the wiki using e.g.
LyxDocPost:603 (should go to this post)
To link
Hi
If we reach some clever conclusions about the FAQ, I've made a page a on
the wiki to put them:
http://wiki.lyx.org/pmwiki.php/DevelDoc/AboutTheFAQ
/Christian
PS. It's very convenient to refer to posts from the wiki using e.g.
LyxDocPost:603 (should go to this post)
To link
FAQ.lyx, and if FAQ.lyx is (ever) updated, this entire FAQ
ought to be checked for questions that should go into FAQ.lyx, instead of
[snip!]
Quick historical remark, Christian:
When I originally created FAQ.lyx (during the Great Doc Rewrite of
'96), my idea was that *FAQ.lyx* would be one
before I'd even started to use Lyx :-)
My suggestion to you, therefore, would be to do all of your editing in
your own version of FAQ.lyx and generate your text FAQ via
ASCII-export. You can then submit your FAQ.lyx modifications to the
DocTeam (what's left of it, anyway) so that someone with CVS
t; separately from FAQ.lyx, and if FAQ.lyx is (ever) updated, this entire FAQ
> ought to be checked for questions that should go into FAQ.lyx, instead of
[snip!]
Quick historical remark, Christian:
When I originally created FAQ.lyx (during the Great Doc Rewrite of
'96), my idea was that *
Wow... that's before I'd even started to use Lyx :-)
> My suggestion to you, therefore, would be to do all of your editing in
> your own version of FAQ.lyx and generate your text FAQ via
> ASCII-export. You can then submit your FAQ.lyx modifications to the
> DocTeam (what's left of
opinions etc on where the different questions should go?
PS. The reason I'm asking about objection to moving new questions into the
prior categories is that it will definitely make this FAQ get a life
separately from FAQ.lyx, and if FAQ.lyx is (ever) updated, this entire FAQ
ought to be checked
/lyx/doc/wiki/moin.cgi/LyxFAQ
he'll find a local copy of the FAQ.
Of course, at the moment everything gets passed along, so it might be
prudent to execute something like:
rm `grep -i -L lyx $LYXDIR/share/doc/wiki/moin.cgi/*`
or do it the otherway around, and add a certain text-tag
Christian == Christian Ridderström [EMAIL PROTECTED] writes:
Christian Here is a better solution (assuming that you can write to
Christian $LYXDIR/doc) cd $LYXDIR # i.e. to .../share/lyx wget -r -P
Christian doc -nh -nH -k -p -R '*\?*'
Christian http://ev-en.org/wiki/moin.cgi/LyxWikis
Christian
Christian == Christian Ridderström [EMAIL PROTECTED] writes:
Christian On 12 Feb 2003, Jean-Marc Lasgouttes wrote:
Christian == Christian Ridderström [EMAIL PROTECTED] writes:
Is it possible to export a Wiki to something that could in turn be
transformed into a LyX doc? A kind of Wiki2lyx
On 12 Feb 2003, Jean-Marc Lasgouttes wrote:
Christian == Christian Ridderström [EMAIL PROTECTED] writes:
Christian and you don't have to post-parse the files since wget does
Christian that at end for you (I think it's the switch -P combined
Christian with -k that fixes this).
What I had
opinions etc on where the different questions should go?
PS. The reason I'm asking about objection to moving new questions into the
prior categories is that it will definitely make this FAQ get a life
separately from FAQ.lyx, and if FAQ.lyx is (ever) updated, this entire FAQ
ought to be checked
l copy of the FAQ.
Of course, at the moment everything gets passed along, so it might be
prudent to execute something like:
rm `grep -i -L lyx $LYXDIR/share/doc/wiki/moin.cgi/*`
or do it the otherway around, and add a certain text-tag to the pages we
want to be exported.
/Chr
> "Christian" == Christian Ridderström <[EMAIL PROTECTED]> writes:
Christian> Here is a better solution (assuming that you can write to
Christian> $LYXDIR/doc) cd $LYXDIR # i.e. to .../share/lyx wget -r -P
Christian> doc -nh -nH -k -p -R '*\?*'
Christian>
> "Christian" == Christian Ridderström <[EMAIL PROTECTED]> writes:
Christian> On 12 Feb 2003, Jean-Marc Lasgouttes wrote:
>> > "Christian" == Christian Ridderström <[EMAIL PROTECTED]> writes:
>>
>> Is it possible to export a Wiki to something that could in turn be
>> transformed into a
On 12 Feb 2003, Jean-Marc Lasgouttes wrote:
> > "Christian" == Christian Ridderström <[EMAIL PROTECTED]> writes:
> Christian> and you don't have to post-parse the files since wget does
> Christian> that at end for you (I think it's the switch -P combined
> Christian> with -k that fixes this).
the different questions should go?
Anyway, I'm not in on how the FAQ was organized from the beginning,
so I'd appreciate some input and thoughts on this.
Go here:
http://ev-en.org/wiki/moin.cgi/LyxSandbox
to add your input.
/C
PS. The reason I'm asking about objection to moving new
the different questions should go?
Anyway, I'm not "in" on how the FAQ was organized from the beginning,
so I'd appreciate some input and thoughts on this.
Go here:
http://ev-en.org/wiki/moin.cgi/LyxSandbox
to add your input.
/C
PS. The reason I'm asking about objection to
On Sun, 9 Feb 2003, Jani Nurminen wrote:
Now, here's a suggestion: this process involving the latex-ttf-fonts-0.1.tar.gz
procedure could be mentioned in a more visible place, maybe in the LyX FAQ. I
assume that's the first place people will look for help.
I've added your tip to an online FAQ
On Sun, 9 Feb 2003, Jani Nurminen wrote:
> Now, here's a suggestion: this process involving the latex-ttf-fonts-0.1.tar.gz
> procedure could be mentioned in a more visible place, maybe in the LyX FAQ. I
> assume that's the first place people will look for help.
I've added your tip to
Was just glancing at the FAQ, and noticed that it says "there's probably
something that can do HTML-LaTeX." Certainly we (i.e., someone who's not
me) can do better than that!
I'll start off with http://html2latex.sourceforge.net, but I'll bet someone
searching the net carefully can
Was just glancing at the FAQ, and noticed that it says "there's probably
something that can do HTML->LaTeX." Certainly we (i.e., someone who's not
me) can do better than that!
I'll start off with http://html2latex.sourceforge.net, but I'll bet someone
searching the net carefully
56 matches
Mail list logo
