Re: FAQ
Paul A. Rubin wrote: > 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. 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
Re: FAQ
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
Re: FAQ
On 8/5/2010 2:19 AM, Jürgen Spitzmüller wrote: Also, please watch out for outdated information. Can we define a criterion for "outdated"? And should attempt to fix it or delete it? For instance, LyX/LyXOnUbuntu starts with a comment about LyX 1.5.3 on Ubuntu Hardy. Leave it for the one or two people who steadfastly refuse to update a working system, or get rid of it? (I would vote for the latter, but I'm not entirely comfortable about deleting someone else's entries. If I find something I myself posted that is obsolete, I'll cheerfully recycle the bytes.) Something like Tips/MathMacros needs to be updated (since we now have menu and toolbar control over macros), but I would think the existing content could be kept after verifying that it still works, even if it is arguably not the most efficient approach anymore. /Paul (who will fiddle with both those pages when time permits)
Re: FAQ
Richard Heck wrote: > Did some...will try to do more later. Thanks. I proceed myself from time to time. Jürgen
FAQ
Since it's a rainy day today, I've started to give the FAQ section on the wiki a somewhat sensible structure. Until now, the FAQ was organized with reference to some file FAQ.lyx that isn't existing anymore since a long time, some random thematic pages (with very different style) and a big "unsorted" page. Many of the answers are outdated, there are user edits such as "I tried your answer and it didn't work for me", etc. In other words: It's a big, big mess. My plan is to organize the FAQ related to larger thematic units. That's what I have started, but very much is still left to do. Please, if you find some time, help rearranging the pages so that it finally becomes a useful source of information. What needs to be done: * Move contents from general pages (such as http://wiki.lyx.org/FAQ/Running, http://wiki.lyx.org/FAQ/Using, http://wiki.lyx.org/FAQ/Unsorted and http://wiki.lyx.org/FAQ/Unsorted1) to thematic pages such as http://wiki.lyx.org/FAQ/Tables. The former pages should ideally be deleted eventually. * Integrate specific pages such as http://wiki.lyx.org/FAQ/MultipleAuthors into larger thematic units (these pages can be (:Include:)ed and then removed from the PageList) * All FAQs should be presented as FAQs, i.e. in the form - How can I do this? Do the following: ... IMHO, extended HowTos are not FAQs. Also things like: "John Doe wrote on lyx-users: ..." are not appropriate. * User comments such as "I tried your answer and it didn't work for me" do not belong to the FAQ. We should look if these concerns can be dealt with in the answer and remove such comments. In general, we should aim at a somewhat consistent style. Also, please watch out for outdated information. Thanks, Jürgen
FAQ/ERT now requires a password (Was: [LyX wiki] recent notify posts)
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 that password. The password is not intended to be especially secret, so if you would like to edit one of the following pages, as on the users' or the developers' list for the password: * http://wiki.lyx.org/LyX/Welcome * http://wiki.lyx.org/Windows/Windows * http://wiki.lyx.org/Windows/LyX145 * http://wiki.lyx.org/Windows/LyX151 * http://wiki.lyx.org/Windows/LyX152 * http://wiki.lyx.org/PmWiki/* * http://wiki.lyx.org/FAQ/ERT Most developers should have access to the password, it's stored in the file /home/lyx/www/pmwiki/passwords.txt on 'aussie' (a.k.a. lyx.org) Best regard, Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: Obsolete information in the FAQ?
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
Obsolete information in the FAQ?
Hi, In sub-section 1.4 it is written that LyX needs XServer in order to have it work on a Windows machine. As far as I can remember I didn't install any XServer software when I installed LyX on a windows machine. Is this information provided in the FAQ.lyx is correct regarding the newer versions of LyX? I see that this FAQ was written originally for version 1.0. Sincerely, Ran Rutenberg
Re: PO files FAQ
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 :) >><< The wiki page now embeds the latest version from SVN. /C -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: PO files FAQ
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 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, and KDE, it is necessary to use LC_ALL. Ex: > a) KDE_LANG=xx_CC lyx > b) LC_ALL=xx_CC lyx That should be filed as a mandriva bug. It should not be needed to set KDE_LANG. Only setting LANG (or LC_MESSAGES or LC_ALL) should work. Georg
Re: PO files FAQ
> What page? It's possible to automatically have the wiki page embed > something from SVN. http://wiki.lyx.org/Devel/POFAQ pavel
Re: PO files FAQ
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 with your comments against that file. i was looking in wiki and the file is little obsolete there. somebody wrote, that this page should be generated from the current version in svn, however actually it is not. What page? It's possible to automatically have the wiki page embed something from SVN. /C -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: PO files FAQ
> 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 was looking in wiki and the file is little obsolete there. somebody wrote, that this page should be generated from the current version in svn, however actually it is not. pavel
Re: PO files FAQ
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, and KDE, it is necessary to use LC_ALL. Ex: a) KDE_LANG=xx_CC lyx b) LC_ALL=xx_CC lyx 2) In order to test the translation it is necessary to test if the language use to make the translation is accepted by lyx. I.e. if the language is in the text file "languages". 3) If the language used to make the translation is in the text file "languages", it is not necessary to compile lyx. In this case is enough to compile the po file, with the command "msgfmt" that is part of the gettext packet. http://www.gnu.org/software/gettext/manual/html_mono/gettext.html http://gnuwin32.sourceforge.net/packages/gettext.htm Bye Ramon
Re: PO files FAQ
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 repository. No need to delete anything. However, if the name of the page is modified, please fix the link or ask me to fix the link. (Personally I like README.localization). cheers /Christian -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: PO files FAQ
>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 know ... winning the price for misusing cat :) > Uwe: > But not everything. Provide a patch to the current version: > http://www.lyx.org/trac/browser/lyx-devel/trunk/README.po-files > and I will commit this immediately. ok, attached patch including remarks from ran. pavel --- README.localization 2007-02-24 18:50:42.0 +0100 +++ README.localization.new 2007-02-24 19:09:09.0 +0100 @@ -18,8 +18,10 @@ http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC222 -If you want to start from scratch than you should obtain a copy of the lyx.pot -file. +If you want to start from scratch then you should obtain a copy of the lyx.pot +and name it after your language. German would be for example de.po and Polish +pl.po. This file is generated in the "po" directory of the source tree during +the compilation. 2) HOW DO I EDIT PO FILES? @@ -33,14 +35,14 @@ 3) WHAT DO I NEED TO TRANSLATE? -If your using a simple text editor you should translate the strings that appear -in the msgid line and write the translation into the msgstr line. Note that a -"#, fuzzy" line is just a hint for translation from compiler - in order to get -the translation of the current item working you have to delete this line. It is -recommended that you would take a look at another .po file - that way you can -get an idea of what to do. If your using a specialized po editor then you will -see in it the untranslated strings and a place to write your translation for -them. +If you are using a simple text editor you should translate the strings that +appear in the msgid line and write the translation into the msgstr line. Note +that a "#, fuzzy" line is just a hint for translation from compiler - in order +to get the translation of the current item working you have to delete this +line. It is recommended that you would take a look at another .po file - that +way you can get an idea of what to do. If your using a specialized po editor +then you will see in it the untranslated strings and a place to write your +translation for them. 4) WHAT SHOULD I DO WITH THE '&', '|', '$, AND '%' CHARACTERS? @@ -70,7 +72,7 @@ In order to test your translation you need to obtain the LyX sources (from the SVN repository) and replace the existing .po with yours. Afterwards, you should compile and install LyX (check the INSTALL file for your OS). If you don't -install LyX it won't work. For running LyX with your translation, use the +install LyX it won't work. In order to run LyX with your translation, use the appropriate LANG variable: On Linux: LANG=xx_CC lyx @@ -79,6 +81,13 @@ xx stands for your language code. CC stands for your country code. So to get, e.g., Czech, the code is "cs_CZ". +The most comfortable way to see your updated translation while editing, is +running (in linux): +1. "make xx.po" in po directory to compile updated xx.po translation +2. "make install" in root lyx tree to copy xx.gmo into the appropriate location + (or do it by hand...) + + 7) REFERENCES For some basic idea on how the translation works, you can look at
Re: PO files FAQ
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
Re: PO files FAQ
Pavel Sanda schrieb: i made small changes. see attached patch. I added most of the changes: http://www.lyx.org/trac/changeset/17318 But not everything. Provide a patch to the current version: http://www.lyx.org/trac/browser/lyx-devel/trunk/README.po-files and I will commit this immediately. regards Uwe
Re: PO files FAQ
Ran Rutenberg schrieb: I wrote a small FAQ for the po files. I would be glad if someone could have a glance at it, check that everything is OK and then upload it. I checked the file, modified it a bit and uploaded it under the name README.po-files: http://www.lyx.org/trac/changeset/17316 http://www.lyx.org/trac/browser/lyx-devel/trunk/README.po-files JMarc, could this also be added to branch? regards Uwe
Re: PO files FAQ
> 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 you need to edit it an xx.po file where xx stands for your language's two letter -code. German would be for example de.po and Polish pl.po. -If you want to start from scratch than you should obtain a copy of the lyx.pot file. +code. For list of country codes look at: +http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC222 +If you want to start from scratch than you should obtain a copy of the lyx.pot and +name it after your language. German would be for example de.po and Polish pl.po. +This file is generated in the "po" directory of the source tree during the compilation. 2) HOW DO I EDIT PO FILES? @@ -23,18 +26,17 @@ many tools to assist the translator. - 3) WHAT I NEED TO TRANSLATE? If your using a simple text editor you should translate the strings that appear in the msgid line -and write the translation into the msgstr line. You can also add "#, fuzzy" in order to mark a -translation as fuzzy. It is recommended that you would take a look at another .po file - that -way you can get an idea of what to do. -If your using a specialized po editor then you will see in it the untranslated strings and a +and write the translation into the msgstr line. Note that "#, fuzzy" line is just a hint +for translation from compiler - in order to get the translation of the current item working +you have to delete this line. It is recommended that you would take a look at another .po file - +that way you can get an idea of what to do. +If you are using a specialized po editor then you will see in it the untranslated strings and a place to write your translation for them. - 4) WHAT SHOULD I DO WITH THE '&', '|', '$, AND '%' CHARACTERS? '&' stands for underlined characters (shortcut) in dialog boxes. @@ -46,30 +48,36 @@ and resolve possible conflicts of the same shortcut chars in one menu... - 5) WHAT IS pocheck.pl AND HOW DO I USE IT? This is a small script located in the PO directory of the source that helps you find common errors in your translation. In order to use this script you have to have perl. -6) HOW CAN I TEST MY TRANSLATION? +6) HOW CAN I TEST MY TRANSLATION? In order to test your translation you need to obtain the LyX source (from the SVN) and replace the existing .po with yours. Afterwards, you should compile and install (if you don't install it won't work) LyX (check the INSTALL file for your OS). -Now, run LyX using the appropriate LANG variable: +For running LyX with your translation, use the appropriate LANG variable: In Linux: LANG=xx_CC lyx In MS Windows you need to change the bat file and write: set LANG=xx_CC xx stands for your language code. CC stands for your country code. +Most comfortable way to see your updated translation during the editation, is running(linux): +1. "make xx.po" in po directory to compile updated xx.po translation +2. "make install" in root lyx tree to copy xx.gmo into the appropriate location (or do it +by hand...) +7) REFERENCES +For basic idea how the translation works you can look http://en.wikipedia.org/wiki/Gettext . +Just for detailed reference you can look at http://www.gnu.org/software/gettext/manual/gettext.html . Written by Ran Rutenberg 2007 -I greatly appreciate all those who helped me and assisted me in this subject. \ No newline at end of file +I greatly appreciate all those who helped me and assisted me in this subject.
Re: PO files FAQ
On Sat, 24 Feb 2007, Ran Rutenberg 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 wrote a small FAQ for the po files. I would be glad if someone could have a glance at it, check that everything is OK and then upload it. I'm unfortunately of no use looking at it (no knowledge of po-files). However, I'd like to suggest that you place it on the wiki? If nothing else as an easy way to let other look at it and comment on it. Later on it might be better of in SVN of course. Perhaps placing it on a page (which you'll be creating) called http://wiki.lyx.org/Devel/FAQ Best regards /Christian Ps. If you're putting on the wiki and need assistance, just ask me. PPS. Later on when it's in SVN, we can still have the wiki page automatically pull the content from SVN and embed it in the page. -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
PO files FAQ
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 a small FAQ for the po files. I would be glad if someone could have a glance at it, check that everything is OK and then upload it. Sincerely, Ran Rutenberg PO FAQ Description: Binary data
About the FAQ
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 to a thread-view, use LyxDocThreadRoot:603 - all these kinds of links (called inter-links) are documented here: http://wiki.lyx.org/pmwiki.php/Site/InterLinks We have them for all lists AFAIK. -- Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Re: FAQ
On Wed, 12 Feb 2003, John Weiss wrote: > On Tue, Feb 11, 2003 at 05:28:30PM +0100, Christian Ridderström wrote: > 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 of the two 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 it, anyway) so that someone with CVS access > can commit it after an editorial once-over. My goal isn't really to write a new FAQ.lyx, although the wiki started a while ago when I actually did make some changes to FAQ.lyx and sent it in and so on. The problem with that was that the cycle time is really slow (an editorial once-over, or peer review, is of course necessary for the FAQ.lyx since that's distributed with lyx) and then I continue talking about this and that :-) so I've put it here instead: http://ev-en.org/wiki/moin.cgi/LyxDocFuture /Christian
Re: FAQ
On Tue, Feb 11, 2003 at 05:28:30PM +0100, Christian Ridderström wrote: > Hi > > As you (ought to) know, I've more or less arbitrarily been writing > down some of the questions and answers I've seen on the user's list here: > http://ev-en.org/wiki/moin.cgi/LyxFAQ [snip!] > 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 *FAQ.lyx* would be one of the two "moving-target" members of the docs. It would shift, change, rearrange as needed and as things moved out of the FAQ into the manuals. 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 access can commit it after an editorial once-over. -- John Weiss
Re: FAQ
On Wed, 12 Feb 2003, robin wrote: > No objections. I think a section on layout would catch a lot of questions. Uhmm.. I'm not sure I understand... you mean section like: "Questions on layout using Lyx" hmm.. what kind of questions are you thinking about here? Questions about the layout-files? Or how to actually change the layout of the document? /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: FAQ
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 in mind is more complicated: I wanted to get the output as > a .lyx file... I think there are two different ways of looking at this... do we want something offline but browsable, or something offline and printable? If it's enough to be able to browse it, then this should work. For printing on the other hand, you'd need to pull in all the links etc. > OK, how could I get the text version of a given entry, say LyXFAQ? I > can see it when pressing 'edit', but I don't sem to be able to > download it. The format seems simple enough that it could be > have to admit that this wiki thing is kind of new to me. Yeah, it's new to me too. You get the raw format as I wrote in my first post. The raw format can be acquired like this: wget 'http://ev-en.org/wiki/moin.cgi/LyxFAQ?action=raw' Tonight I'll surf around to see what kind of converters are available. /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Re: FAQ
> "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 program. Christian> Yes, I think that's quite possible, especially since the Christian> format is quite trivial. The raw format can be acquired Christian> like this: Christian> wget Christian> 'http://ev-en.org/wiki/moin.cgi/LyxWikis?action=raw' Oops, I should not read your messages in reverse order. I have the info I need now. Christian> However, I think we _really_ ought to have a wiki at Christian> www.lyx.org, rather than at www.ev-en.org for Christian> backup-reasons if nothing else. You ought to talk to Lars about this. Christian> All I know about this site is that the owner didn't mind me Christian> putting the wiki's there when I asked him (in fact, a long Christian> while ago he created the first few lyx wikis there and sent Christian> a mail to the user's list). This is Baruch Even's site. He is in particular the author of the new graphics inset that appeared in 1.2.0. JMarc
Re: FAQ
> "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> this will create a snapshot structure of all the wikis in Christian> $LYXDIR |-- doc | `-- wiki | |-- img | `-- moin.cgi Christian> (here's where the actual wikis are) 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 in mind is more complicated: I wanted to get the output as a .lyx file... OK, how could I get the text version of a given entry, say LyXFAQ? I can see it when pressing 'edit', but I don't sem to be able to download it. The format seems simple enough that it could be translated to latex or to lyx. I would think such a tool already exists, but the moinmoin page is not very helpful in that respect. I have to admit that this wiki thing is kind of new to me. JMarc
Re: FAQ
On 12 Feb 2003, Jean-Marc Lasgouttes wrote: >> Taking a snapshot of lyx wiki Here is a better solution (assuming that you can write to $LYXDIR/doc) cd $LYXDIR # i.e. to .../share/lyx wget -r -P doc -nh -nH -k -p -R '*\?*' http://ev-en.org/wiki/moin.cgi/LyxWikis this will create a snapshot structure of all the wikis in $LYXDIR |-- doc | `-- wiki | |-- img | `-- moin.cgi(here's where the actual wikis are) and you don't have to post-parse the files since wget does that at end for you (I think it's the switch -P combined with -k that fixes this). A link in LyxWikis will now look like this: LyxFAQ i.e. it will have a relative path, so it doesn't matter where $LYXDIR actually is. There will still be paths that doesn't work, such as: EditText but they wont work properly without a cgi-script anyway. So, to sum it up. It ought to be really easy to send this stuff with any lyx installation doing as I've described above. Then it's just a matter of informing the user that if he opens an URL such as this: file://localhost/usr/local/share/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 to the pages we want to be exported. /Christian -- Christian Ridderström, +46-8-790 91 37 http://www.md.kth.se/~chr Mechatronics lab, Dept. of Machine Designhttp://www.md.kth.se
Re: FAQ
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 program. Yes, I think that's quite possible, especially since the format is quite trivial. The raw format can be acquired like this: wget 'http://ev-en.org/wiki/moin.cgi/LyxWikis?action=raw' > I think that there is some interest in having the FAQ available in a > format that does not require a network connection. It is seems also > that your wiki is bound to be more updated than FAQ.lyx. But it would > be nice to be able to take 'snapshots' of the wiki and put them in the > distribution. I played a little bit with this and the following takes a snapshot: ~>wget -r -k -p -R '*?*' http://ev-en.org/wiki/moin.cgi/LyxWikis where all links with ? are avoided. This will however dump all wikis, but since most of the content is related to lyx that is not a big problem. The result will end up in a catalog structure: $HOME/ev-en.org and unfortunately all the links will be wrong. This fixes that: perl -i.bak -pe "s|/wiki/|$HOME/ev-en.org/wiki/|" ev-en.org/wiki/moin.cgi/* and you know have a snapshot of the wiki that you can navigate with a browser. Of course, it's likely we don't want to have the snapshop in our home directory... but where to put it is a bit of a problem. Hmm... I'll play around with it and let you know, I ought to be able to fix it somehow. However, I think we _really_ ought to have a wiki at www.lyx.org, rather than at www.ev-en.org for backup-reasons if nothing else. All I know about this site is that the owner didn't mind me putting the wiki's there when I asked him (in fact, a long while ago he created the first few lyx wikis there and sent a mail to the user's list). Oh, and if we run our own wiki server, we could probably choose one that is capable of exporting html-trees properly, or xml for that matter. Unfortunately I don't know much about wiki servers, except they come in a wide variety. /Christian -- Christian Ridderström, +46-8-790 91 37 http://www.md.kth.se/~chr Mechatronics lab, Dept. of Machine Designhttp://www.md.kth.se
Re: FAQ
>>>>> "Christian" == Christian Ridderström <[EMAIL PROTECTED]> writes: Christian> PS. The reason I'm asking about objection to moving new Christian> questions into the prior categories is that it will Christian> definitely make this FAQ get a life separately from Christian> FAQ.lyx, and if FAQ.lyx is (ever) updated, this entire FAQ Christian> ought to be checked for questions that should go into Christian> FAQ.lyx, instead of just the category: *unsorted questions* Christian> DS Is it possible to export a Wiki to something that could in turn be transformed into a LyX doc? A kind of Wiki2lyx program. I think that there is some interest in having the FAQ available in a format that does not require a network connection. It is seems also that your wiki is bound to be more updated than FAQ.lyx. But it would be nice to be able to take 'snapshots' of the wiki and put them in the distribution. JMarc
Re: FAQ
Christian Ridderström wrote: Hi As you (ought to) know, I've more or less arbitrarily been writing down some of the questions and answers I've seen on the user's list here: http://ev-en.org/wiki/moin.cgi/LyxFAQ However, the unsorted questions are getting a bit too many now, so I'd like to do something about that. At first I just copied everything from FAQ.lyx, including the structure with the following categories: * Introduction and General Information * Internet Resources * Compatibility with other word/document processors * Obtaining and Compiling LyX * Questions about Evil Red Text (IMPORTANT!) * Questions Related to Using LyX * Questions Related to Using LyX * Questions Related to LyX on Windows * How to get further assistance * Administrative information and acknowledgments and added the category: * Unsorted questions. where I've been adding questions. After I while I also started adding separate pages for some of the answers (in an unstructured way) since the page was getting a bit long. Here are my questions: * Are there any objections to me moving questions into the priorly defined categories? * Do you have any ideas or opinions on new categories? * Any 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 for questions that should go into FAQ.lyx, instead of just the category: *unsorted questions* DS No objections. I think a section on layout would catch a lot of questions. Robin -- "A Perl script is "correct" if it gets the job done before your boss fires you." - Larry Wall Robin Turner IDMYO Bilkent Univeritesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin
FAQ
Hi As you (ought to) know, I've more or less arbitrarily been writing down some of the questions and answers I've seen on the user's list here: http://ev-en.org/wiki/moin.cgi/LyxFAQ However, the unsorted questions are getting a bit too many now, so I'd like to do something about that. At first I just copied everything from FAQ.lyx, including the structure with the following categories: * Introduction and General Information * Internet Resources * Compatibility with other word/document processors * Obtaining and Compiling LyX * Questions about Evil Red Text (IMPORTANT!) * Questions Related to Using LyX * Questions Related to Using LyX * Questions Related to LyX on Windows * How to get further assistance * Administrative information and acknowledgments and added the category: * Unsorted questions. where I've been adding questions. After I while I also started adding separate pages for some of the answers (in an unstructured way) since the page was getting a bit long. Here are my questions: * Are there any objections to me moving questions into the priorly defined categories? * Do you have any ideas or opinions on new categories? * Any opinions etc on where 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 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 for questions that should go into FAQ.lyx, instead of just the category: *unsorted questions* DS -- Christian Ridderström http://www.md.kth.se/~chr
Re: Suggestion: LyX math mode font fixing procedure into 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 an online FAQ for lyx, feel free to add more stuff tips about Qt. http://ev-en.org/wiki/moin.cgi/LyxFAQ#line270 /Christian -- Christian Ridderström http://www.md.kth.se/~chr
Suggestion: LyX math mode font fixing procedure into FAQ
Hello, I had trouble with LyX 1.3.0 with Qt frontend having problems with the math mode fonts displaying garbage. However, after reading the INSTALL file and installing the latex-ttf-fonts-0.1.tar.gz (and rebooting X) I got everything working. 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. Basically the procedure went like: 1. Fetch the latex-ttf-fonts-0.1.tar.gz from ftp.lyx.org/pub/contrib 2. Install the package (make install as root) 3. Reboot X (I did run mkttfdir in the /usr/share/fonts/latex-ttf-fonts directory but it didn't seem to do anything) 4. Behold! Math mode fonts work. I spent two days laughing of joy for anti-aliased fonts in Qt LyX and at the same time crying because the math mode font was "broken". But now it works like a charm. The editor I so dearly love got more than twice better! Thank you all very much. Regards, Jani Nurminen -- PGP Key ID 0x6EE92B3E - http://www.lut.fi/~jnurmine/ Numb, adj., devoid of sensation... Number, comparative of numb.
Re: FAQ: comandline lyx->ps
You'll get more replies I expect if you post to the lyx-users list rather than to lyx-docs. Very few people read this list. Anyway, both for you and for the FAQ maintainer ;-) (arg == "-x" || arg == "--execute") // Execute commands (arg == "-e" || arg == "--export") // buffer-export + argv[i+1] (arg == "--import") // "buffer-import " + argv[i+1] + argv[i+2] These should also go in the man page. I'd suggest that lyx --export ps file.lyx would do the trick. The nice thing is: you no longer need an X-server for this to work. Angus On Thursday 30 November 2000 16:18, Gregor von Laszewski wrote: > Unfortunatly the FAQ does not contain an example on how to convert a lyx > file directly to postscript from the command line. I see the example for > latex, but ps requires me to specify a filename. > > It would be nice to add this to the FAQ and send me the solution. > > Thanks > > Gregor
FAQ: comandline lyx->ps
Unfortunatly the FAQ does not contain an example on how to convert a lyx file directly to postscript from the command line. I see the example for latex, but ps requires me to specify a filename. It would be nice to add this to the FAQ and send me the solution. Thanks Gregor
FAQ
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 do better. -Amir
