LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Having *finally* managed to persuade LyX to generate bibliographies at all, I now find that LyX seemingly cannot handle characters with diacritic marks (i.e. UniCode) in .bib files when exporting them to PDF, etc. Unfortunately this really has to work for me as it will be the case with a very large number of European, etc., author's names and so on. If this is how it is meant to be or the way it is, *please* add some information to this effect in the tutorial and user guide or somewhere prominent, so that users needing this can quit early and look for another another solution. On the other hand, the internationalisation section of the features blurb mentions unicode compliance in passing... Does anyone have any remedies for this? Preferably simple: I am all out of time to do more of the kind of fiddling I have had to do so far. I've tried setting the language encoding to utf8, but it generates an empty document and complains that 'utf8.def' isn't present. Setting language encoding to 'Unicode (XeTeX) generates output (without crashing during the conversion), but the characters aren't correct. I can't generate plain text (ps2ascii) at all. Generating PostScript, generates output but also gets the characters wrong. And on it goes, randomly trying this, that and the other in vain attempts to make something work...! :-( Is there some version or other of the main LaTeX installation that I am supposed to be using? (And if that's the case, shouldn't LyX be check that it's a sane choice, etc?) Grant Jacobs -- --- Grant Jacobs Ph.D. BioinfoTools ph. +64 3 478 0095 (office, after 10am) PO Box 6129, or +64 27 601 5917 (mobile) Dunedin, gjac...@bioinfotools.com NEW ZEALAND. Bioinformatics tools: deriving knowledge from biological data Bioinformatics tools - software development - consulting - training 15 years experience in bioinformatics ready to solve your problem Check out the website for more details: http://www.bioinfotools.com The information contained in this mail message is confidential and may be legally privileged. Readers of this message who are not the intended recipient are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immed- iately and destroy the original message. This applies also to any attached documents.
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Grant Jacobs wrote: Having *finally* managed to persuade LyX to generate bibliographies at all, I now find that LyX seemingly cannot handle characters with diacritic marks (i.e. UniCode) in .bib files when exporting them to PDF, etc. Unfortunately this really has to work for me as it will be the case with a very large number of European, etc., author's names and so on. This is a BibTeX limitation. BibTeX is an old beast, the most recent release still predates the advent of unicode. Fact is that bibtex cannot deal with unicode (or any other multibyte encoding, for that matter) at all. There's noting that LyX can do here. You need to use another encoding for the bib file, such as latin1, and insert the non-supported characters by means of the respective macros. A decent bib file editor, such as JabRef or pybliographic, should actually handle this for you. If this is how it is meant to be or the way it is, *please* add some information to this effect in the tutorial and user guide or somewhere prominent, so that users needing this can quit early and look for another another solution. You are right, this needs to be documented in the UserGuide, sec. 6.5.2. CC:ing the documentation list. Jürgen PS.: please open a new thread for new topics.
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Jürgen Spitzmüller wrote: You need to use another encoding for the bib file, such as latin1, and insert the non-supported characters by means of the respective macros. Also look here for some further information: http://wiki.lyx.org/BibTeX/Tips#toc1 Jürgen
Re: Strategies for Writing Co-operation with Non-LyX Users?
Hello fellow humanists! What a luck! Only one of your colleagues use LaTeX and some use Oo? Only the editors use LaTeX? In my area and field (italian history of music), World and Word mean the same thing, and everything which happens to us, little insignificant mortal scholars, is because of the will of the Big Bill, who rescued our souls just a bunch of years ago out of the dark fogs of the ink and paper era and tought us the principle of the MS enlightment. My supervisor, known in our field for his above-average informatical knowledge with databases and so on, once called exotic some of my documents printed with Oo. I'm just starting publishing things in small, medium-size and large publications. Everywhere, when asked what if LaTeX?, after a what what? they always told me: please send us printed paper and .DOC in CD (!) or email if possible. There's no way to break the entire chain of MS rule, other than go straight, ignoring it. With my supervisor now I got back to paper: I print out my drafts, hand to him, get back the red pen corrections and type them into my LyX document. I love this: past and future altogether, but far away from the flattened MS present. But you were talking about Strategies. It's quite hard for me to have my docs converted to OO (something not working in my LyX install) so I can't help you with technical things. The best strategy is to spread the LyX verb. If you only convince one person, you'll be two instead of one, which is to double the effort. This is a long-term strategy. Another long-long-term strategy is to promote (and partecipate to) the developmente of LyX (and related sw) in a simplified and humanists-friendly (rather non-scientific friendly) direction, which is IMHO one of the primary goals of LyX. When I will able to show my colleagues some LyX versions with BibLaTeX (for humanist bibliographies) fully working, perfect Lilypond (a LaTeX-like music typesetter) integration without having to tweak code and so on, chances of victory will be for LyX. Till that day, no way. Peter was talking about google docs. document-sharing is IMHO the weakest battlefront for LyX (and for a lot of free software and projects), and the final battle will be fought there, but this is future, and it's out of this post. Still curious to hear some more opinions and experiences. Piero
Re: \usepackage[full]{textcomp} - where to set?
where can I tell Lyx once forever that it shall load the textcomp
package always with the option full, because this is required by
certain other packages?
You can pass the full option to DocumentSettingsClass Options.
Class options will be passed down to the packages by LaTeX.
Apparently not:
LaTeX Error: Option clash for package textcomp.
...textcomp\RequirePackage[full]{textcomp}\fi
The package textcomp has already been loaded with options:
[]
There has now been an attempt to load it with options
[full]
Adding the global options:
,full
to your \documentclass declaration may fix this.
Try typing return to proceed.
THis was the start of the source:
% Quellcode vorschauen
%% LyX 1.6.1 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[10pt,ngerman,full]{scrartcl}
\usepackage[osf]{mathpazo}
\renewcommand{\sfdefault}{cmbr}
\renewcommand{\ttdefault}{lmtt}
\renewcommand{\familydefault}{\sfdefault}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{geometry}
\geometry
{verbose,letterpaper,tmargin=2cm,bmargin=2cm,lmargin=2cm,rmargin=2cm}
\pagestyle{empty} \usepackage{array}
\usepackage{textcomp}
\makeatletter
Sincerely,
Wolfgang
RE: Re: Strategies for Writing Co-operation with Non-LyX Users?
Still curious to hear some more opinions and experiences. I'm succesfully spreading the word of LyX to my supervisors and colleagues. I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. Piero Vincent
Re: \usepackage[full]{textcomp} - where to set?
Wolfgang Keller wrote:
You can pass the full option to DocumentSettingsClass Options.
Class options will be passed down to the packages by LaTeX.
Apparently not:
LaTeX Error: Option clash for package textcomp.
...textcomp\RequirePackage[full]{textcomp}\fi
could you post a small example file? I'm unable to reproduce the problem.
Jürgen
Re: \usepackage[full]{textcomp} - where to set?
could you post a small example file? I'm unable to reproduce the
problem.
I've narrowed the source of the problem down to the use of a symbol I
use: \textopenbullet{}, together with the kpfonts.
The workaround is to use the ifsym package.
Try this:
% Quellcode vorschauen
%% LyX 1.6.1 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[10pt,ngerman,full]{scrartcl}
\usepackage[osf]{mathpazo}
\renewcommand{\sfdefault}{cmbr}
\renewcommand{\ttdefault}{lmtt}
\renewcommand{\familydefault}{\sfdefault}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{geometry}
\geometry
{verbose,letterpaper,tmargin=2cm,bmargin=2cm,lmargin=2cm,rmargin=2cm}
\pagestyle{empty} \usepackage{textcomp}
%% User specified LaTeX commands.
\usepackage{color}
\definecolor{grey}{gray}{0.3}
\usepackage{kpfonts}
%\renewcommand{\rmdefault}{uop}
\makeatother
\usepackage{babel}
\usepackage{babel}
\begin{document}
\textopenbullet{}
\end{document}
Re: Strategies for Writing Co-operation with Non-LyX Users?
Vincent van Ravesteijn - TNW wrote: Still curious to hear some more opinions and experiences. I'm succesfully spreading the word of LyX to my supervisors and colleagues. I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. It'd be nice to have a list of things people need for collaboration. I guess we've probably had that discussion before, but I've never thought it had a very good outcome. Richard
Re: Strategies for Writing Co-operation with Non-LyX Users?
I don't have a whole lot to add to what other people have said. The difficulties in using LyX for cross-program collaboration will depend very much upon your field. I wrote a paper a while back with someone who was using Word, or maybe even an old version of WordPerfect, but it was relatively painless, because there was almost no technical material in it. So I was able to export to RTF, he could do what he wanted and send it back marked with his changes in blue, and I could put those changes back into LyX. For our next paper, though, I was able to get him to use LyX. I've also managed to get several of my students using LyX. It takes time for them to adjust to a new way of working. But once they adjust, they are all very glad that they have. The problem, of course, is that people tend not to realize that there even could be another way of working, or that it might have real benefits. You don't realize until you stop using Word, etc, how much the program gets in the way of just writing. It sounds almost crazy, but it's true. Richard
Re: \usepackage[full]{textcomp} - where to set?
Wolfgang Keller wrote:
could you post a small example file? I'm unable to reproduce the
problem.
I've narrowed the source of the problem down to the use of a symbol I
use: \textopenbullet{}, together with the kpfonts.
You can disable the automatic textcomp loading of the kpfonts package with the
package option notextcomp (see the package documentation). If you keep the
full class option in LyX, textcomp will then be loaded with this option
nevertheless (even though kpfonts just doesn't recognize this).
Jürgen
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Mon, 26 Jan 2009 07:53:14 -0500 rgheck rgh...@bobjweil.com wrote: Vincent van Ravesteijn - TNW wrote: Still curious to hear some more opinions and experiences. I'm succesfully spreading the word of LyX to my supervisors and colleagues. I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. It'd be nice to have a list of things people need for collaboration. I guess we've probably had that discussion before, but I've never thought it had a very good outcome. Richard Personally, some way of compating/merging documents would be great. I don't know about others, but I know a lot of people who work with latex, very few with lyx. We also send out papers in latex. It's very difficult for me to do the work in lyx as I need to incorporate their changes that were done in latex somehow, and preferably do it without copying them over. The best solution would be if I could import the latex document back into lyx and then compare the two lyx files, although of course there are a lot of differences due to importing special stuff (don't remember sepecifics at the moment but I recall that a lot of things import as ert). I would even settle for just a proper tool to merge two lyx documents, most everything else can be achieved that way. Another nice things would be to be able to diff against version control (if the previous is possible then this will be a subset also)
Re: Strategies for Writing Co-operation with Non-LyX Users?
I had a few days back this problem: how to give my document to somebody for corrections (anything except .lyx or .tex). The other person did try to install lyx (on Kubuntu) but probably Kubuntu's repositories host a previous version of LyX and we all know that it costs some time to get all things working straight forward. I only want to say, as an end-user, that I don't even think to go back to OpenOffice for documents. Even if there are cooperation problems. While I agree, more or less, with Piero Faustini that _one_ way to push LyX further is to ignore other documents (especially .doc's) I still think that a tool should be interoperable meaning, except of getting it working on most operating systems, that it is able to handle most known/established document formats (painless import/export). Kind Regards, Nikos
Re: Strategies for Writing Co-operation with Non-LyX Users?
It'd be nice to have a list of things people need for collaboration. I guess we've probably had that discussion before, but I've never thought it had a very good outcome. The most importand would IMHO be to compare two documents and in some nice way, display differences so I can accept or reject them. Best would be if everything could be within lyx and never have to use latex or external tools. After this feature would be lyx having the possibility to save/open documents stored on a server. ftp, wiki,scp,subversion or what ever that will make it transparent. And when you are trying to save you see the differences between your version and the one on the server and you can check them and accept or reject and save a new version. Also make it possible to use what ever document format you want to store your LyX file in. Then you can open doc files and save them on an ftp server without problem :-) Nice! Well, it might require some configuration settings...
LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Thanks for explaining this. Its a damn nuisance I have admit, as I've spend a long time trying to resolve this when I have little time to spare really. I thought I was starting a new thread: I set a new subject line. Is there some other thing I am supposed to do to make that happen?? I'm not working via a web interface, and most list software I've used just works off the subject lines... If people are updating that part of the docs, it'd be good to see it *explain* how to make bibliographies work: the explanation currently there is leaving too much out. I'm too busy to help (grant application due, etc.) One thing that bothers me about this being a BibTeX issue, is that BibDesk writes these characters to RTF just fine. (It would tempt me to think that there might a work-around that gets this directly from BibDesk, avoiding BibTex.) I've tried saving the biblio as a RTF file from BibDesk, then importing that into a LyX document, but I got An error occurred on while running rtf2latex 'file'. (Feels like nothing wants to work over here!) Does rtf2latex suffer the same problem as BibTex? The idea was to set up a template in BibDesk to generate the right format, write that. In LyX, let LyX do the citations (which it seems to do OK, not that I can test it that well yet), import the RTF biblio (via BiBDesk) into the right place, and just delete the LyX-generated biblio from the final exported format using a PDF editor or whatnot. I would try the equivalent using HTML and importing that, but the formatting/styling in HTML might be even more limited. Grant Jacobs -- --- Grant Jacobs Ph.D. BioinfoTools ph. +64 3 478 0095 (office, after 10am) PO Box 6129, or +64 27 601 5917 (mobile) Dunedin, gjac...@bioinfotools.com NEW ZEALAND. Bioinformatics tools: deriving knowledge from biological data Bioinformatics tools - software development - consulting - training 15 years experience in bioinformatics ready to solve your problem Check out the website for more details: http://www.bioinfotools.com The information contained in this mail message is confidential and may be legally privileged. Readers of this message who are not the intended recipient are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immed- iately and destroy the original message. This applies also to any attached documents.
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Mon, Jan 26, 2009 at 3:42 PM, A B gentosa...@gmail.com wrote: It'd be nice to have a list of things people need for collaboration. I guess we've probably had that discussion before, but I've never thought it had a very good outcome. The most importand would IMHO be to compare two documents and in some nice way, display differences so I can accept or reject them. Best would be if everything could be within lyx and never have to use latex or external tools. After this feature would be lyx having the possibility to save/open documents stored on a server. ftp, wiki,scp,subversion or what ever that will make it transparent. And when you are trying to save you see the differences between your version and the one on the server and you can check them and accept or reject and save a new version. Also make it possible to use what ever document format you want to store your LyX file in. Then you can open doc files and save them on an ftp server without problem :-) Nice! Well, it might require some configuration settings... These are very interesting and useful points, but they a different problem: the original poster explicitly asked on how to co-operate with non-LyX users. I think that both should be addressed, but the non-LyX users is the one to be addressed here. We should probably develop two lists... So, here are my points: As I had some problems exporting into doc/rtf including pictures, I am following the approach of sending my collaborators the .pdf and an .rtf (or doc based on the pdf) (ignore the formating). Obviously, I am loosing the track changes (which would be nice to have) and have to incorporate the comments manually. But if it would be possible to import an rtf/doc/odf text only including changes, that would solve many problems (no idea if this is possible). Cheers Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Faculty of Science Natural Sciences Building Private Bag X1 University of Stellenbosch Matieland 7602 South Africa
RE: Strategies for Writing Co-operation with Non-LyX Users?
While I agree, more or less, with Piero Faustini that _one_ way to push LyX further is to ignore other documents (especially .doc's) I still think that a tool should be interoperable meaning, except of getting it working on most operating systems, that it is able to handle most known/established document formats (painless import/export). Even if we can get LyX to handle 'all' document formats, saving your work as e.g. MS Word format, will inevitably reduce the representation of the document. That is, not all options of LyX are supported in the MS Word format and vice versa. Thus, painless import/export won't be possible. Maybe we should find a way to perfectly support content-only collaboration: Usually only one author governs the layout, so when you share your document with a co-author, you only want him or her to edit the content. Ideally: you save your document as plain text, your co-authors can open this plain text in their own editor, edit the text, give back another plain text file and you now want to merge this plain text file with your LyX file and accept/reject the changes. Vincent
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Grant Jacobs wrote:
One thing that bothers me about this being a BibTeX issue, is that
BibDesk writes these characters to RTF just fine. (It would tempt me to
think that there might a work-around that gets this directly from
BibDesk, avoiding BibTex.)
0) You have not understood the concept behind BibDesk - it's only a
sophisticated frontend to the database (bib) file that bibtex uses. Try
to read up on this.
1) You can enter the TeX-replacements for the special characters in the
bib-file (or in Bibdesk) instead of the unicode characters.
See http://www.bibtex.org/SpecialSymbols/
Since you say it is mostly for European author names, this should be enough.
2) Make sure you use a recent version of BibDesk. Also, TeXLive-2008 and
LyX 1.6.1 won't hurt.
3) BibDesk takes care of these characters automatically:
If I enter åland sørenson as author, the bib-file that Bibdesk 1.3.19
creates looks like this:
%% Created for khofbaue at 2009-01-26 15:14:23 +0100
%% Saved with string encoding Unicode (UTF-8)
@phdthesis{sorenson:uq,
Author = {s{\o}renson, {\aa}land},
Title = {testing}}
So even though the file is saved in Unicode, Bibdesk replaces the
characters by their corresponding latex macros (where possible, I
assume), and everything just works in LyX.
HTH,
Konrad
P.S. Forget the path via RTF!
Re: How to make Lyx recognize packages installed by Miktex (on ubuntu)?
I have Tex-Live but not the tex live package manager. Since the package manager is not part of the ubuntu repos yet (as in that I can install it via apt-get install), I didn't bother with installing it yet. When it's part of ubuntu I will start using it probably. E. Kaplan wrote: Just curious-- if you have Tex-Live, why do you also need Miktex? rintcius wrote: I finally found a solution. I created a link from .miktex to a texmf directory. Then texhash. After this (and a reconfigure) Lyx recognizes the packages. Rintcius
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Make sure you have 'Unicode to TeX Conversion' enabled in BibDesk's 'Files' Preferences !!! HTH, Konrad
Exporting Hebrew tex file under OS-X
When I try to export Hebrew LyX file into TeX file, It's print out an error: basic_filebuf::_M_convert_to_external conversion error (Lyx 1.6 On Os X) What can I do? Thanks, Ronen.
Re: Exporting Hebrew tex file under OS-X
Ronen Abravanel wrote: What can I do? Provide a very small minimal LyX file that shows the error (and hope that somebody competent looks at it) ... /Konrad
RE: Strategies for Writing Co-operation with Non-LyX Users?
On Mon, 2009-01-26 at 15:29 +0100, Vincent van Ravesteijn - TNW wrote: [...] Maybe we should find a way to perfectly support content-only collaboration: Usually only one author governs the layout, so when you share your document with a co-author, you only want him or her to edit the content. Ideally: you save your document as plain text, your co-authors can open this plain text in their own editor, edit the text, give back another plain text file and you now want to merge this plain text file with your LyX file and accept/reject the changes. Vincent Yep, exactly that. I agree 100%. Nikos
Re: Strategies for Writing Co-operation with Non-LyX Users?
Maybe we should find a way to perfectly support content-only collaboration: Usually only one author governs the layout, so when you share your document with a co-author, you only want him or her to edit the content. Ideally: you save your document as plain text, your co-authors can open this plain text in their own editor, edit the text, give back another plain text file and you now want to merge this plain text file with your LyX file and accept/reject the changes. Vincent Yep, exactly that. I agree 100%. Nikos I would also agree to 100% or more if it were not for real world experience of co-operation. Plain text is far from unproblematic. There is only a small fraction of people that can save something as plain text without having to call a friend. Then comes the interesting problem of opening a plain text file (created in unix) in windows.. ouch.. you need some structure (sections, title, etc.) to work. The fine tuning can be done later perhaps. I managed this once with RTF but I hate to do that ever again.
MS Word to LyX
LyX is really a great way to write math. Therefore I would like to convert my old MS Word documents -- with a lot of equation in Equation Editor -- to LyX (these are documents I continually revise). Any advise about this? I found two commercial packages for conversion to LaTeX: Grind EQ and Word2Tex. They are expensive, and the results are so-so. Definitely requires a lot of hand editing of the LaTeX code. Any experiences with these programs? It appears to me the results from Word2Tex is a little more faithful to the source, but it's hard to evaluate from the trial version.
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 02:42:25 am Jürgen Spitzmüller wrote: I have convinced some colleagues to use LyX or LaTeX, but since people in the humanities are often technically rather unskilled, this usually entails a significant amount of personal administration service, and you need to find the time for that. Hi Jürgen, Have you ever supplied your colleagues with a layout file containing all the environments and character styles they'll need for their document? I think even the most non-technical person would find LyX trivial to use if he/she never had to make an environment or character style. Of course, installation of LyX is still a problem, but with Windows can't you just create an installer to do it? SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
RE: Re: Strategies for Writing Co-operation with Non-LyX Users?
Vincent van Ravesteijn - TNW wrote: I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. Having just finished editing a book, I think there is two phases in collaborative work 1) you divide the writing (you do chapter 1, I'll write chapter 2) the multiple steps of editing and ironing the text between the editor, the authors and the publisher For 1) Everybody can write in his favorite software and you can import the doc file in LyX without much problems For 2) what would be needed is a good cross-platform customized pdf reader with annotations possibilities and a way to link these annotations to the lyx document. I have used for my project Foxit which is not free but works with Wine on Linux. Foxit has a very bad interface. Sadly annotations support in poppler is unfinished. Cheers, Charles -- http://www.kde-france.org
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 08:33:32 am Nikos Alexandris wrote: I only want to say, as an end-user, that I don't even think to go back to OpenOffice for documents. Even if there are cooperation problems. Is it just me, or is OpenOffice terrible about styles? One day when mad at LyX, I briefly tried writing a 2nd edition of a book in OpenOffice (the first edition had been in MSWord from 1999). My styles didn't copy over, then when I manually put in styles they intermittently vanished. OO is great for a 2 page letter, but it's a horror movie when writing a book. After that foray into OO, I got really serious about learning to program LaTeX environments and commands, and their counterparts in LyX. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 09:29:16 am Vincent van Ravesteijn - TNW wrote: While I agree, more or less, with Piero Faustini that _one_ way to push LyX further is to ignore other documents (especially .doc's) I still think that a tool should be interoperable meaning, except of getting it working on most operating systems, that it is able to handle most known/established document formats (painless import/export). Even if we can get LyX to handle 'all' document formats, saving your work as e.g. MS Word format, will inevitably reduce the representation of the document. That is, not all options of LyX are supported in the MS Word format and vice versa. Thus, painless import/export won't be possible. Maybe we should find a way to perfectly support content-only collaboration: Styles give you content-only collaboration. If you can find a way of converting an MS Word doc, including its styles, into a LyX doc, including styles, and vice versa, neither side needs to forego layout. So for instance, if the MS Word author has a paragraph in his mycode style, convert it to LyX in the mycode environment. Then it's just a matter of making the two environments look somewhat similar. When I was assigned main authorship of Samba Unleashed, Sams Publishing sent me (and all the contributing authors) the MSWord equivalent of a layout file (I think they called it a style file), and a 4 page document on what styles to use when. They forbid formatting without styles, and IIRC strongly recommended against my making my own styles. The result was that my choice of styles was dictated by the style guide, and once I got used to the style guide, I didn't need to think about formatting at all -- I became a content-only author, which pleased both Sams and me. At the start of a project with some using MSWord and some using LyX, it wouldn't be that difficult to supply the LyXers with a complete layout file and style guide, and the Worders with a complete style file and identical style guide. Once done, as long as the LyX import and export preserved paragraph and character styles, it would be pretty easy. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Strategies for Writing Co-operation with Non-LyX Users?
Steve Litt wrote: Have you ever supplied your colleagues with a layout file containing all the environments and character styles they'll need for their document? I think even the most non-technical person would find LyX trivial to use if he/she never had to make an environment or character style. yes. Actually, I think that teaching people the advantages of semantic markup is one major task. The problem is that people actually like finger- painting. And LyX/LaTeX just isn't designed for that. Of course, installation of LyX is still a problem, but with Windows can't you just create an installer to do it? Of course. Jürgen
Re: Strategies for Writing Co-operation with Non-LyX Users?
My own problems with using Lyx for a committee-composed documents are much more prosaic: 1. It is difficult to tell which is newly inserted text vs deleted text-- it is all blue on my screen 2. There is no tracking of who changed what, as is nicely done in MS WORD 3. There are no keyboard shortcuts for accepting/rejecting changes, making the process tedious 4. Inserting notes into the text is not as nicely done as it used to be in previous version of MS WORD-- it is simply hard to see where the notes are, or what is their contents. That being said, the tracking of changes is the MAIN reason I use Lyx in the first place, since, in general, I prefer Latex with Kile (under Linux) or WinEdt (under Windows), but Latex does not provide convenient ways of tracking changes, as far as I know. E. Kaplan Steve Litt wrote: On Monday 26 January 2009 09:29:16 am Vincent van Ravesteijn - TNW wrote: While I agree, more or less, with Piero Faustini that _one_ way to push LyX further is to ignore other documents (especially .doc's) I still think that a tool should be interoperable meaning, except of getting it working on most operating systems, that it is able to handle most known/established document formats (painless import/export). Even if we can get LyX to handle 'all' document formats, saving your work as e.g. MS Word format, will inevitably reduce the representation of the document. That is, not all options of LyX are supported in the MS Word format and vice versa. Thus, painless import/export won't be possible. Maybe we should find a way to perfectly support content-only collaboration: Styles give you content-only collaboration. If you can find a way of converting an MS Word doc, including its styles, into a LyX doc, including styles, and vice versa, neither side needs to forego layout. So for instance, if the MS Word author has a paragraph in his mycode style, convert it to LyX in the mycode environment. Then it's just a matter of making the two environments look somewhat similar. When I was assigned main authorship of Samba Unleashed, Sams Publishing sent me (and all the contributing authors) the MSWord equivalent of a layout file (I think they called it a style file), and a 4 page document on what styles to use when. They forbid formatting without styles, and IIRC strongly recommended against my making my own styles. The result was that my choice of styles was dictated by the style guide, and once I got used to the style guide, I didn't need to think about formatting at all -- I became a content-only author, which pleased both Sams and me. At the start of a project with some using MSWord and some using LyX, it wouldn't be that difficult to supply the LyXers with a complete layout file and style guide, and the Worders with a complete style file and identical style guide. Once done, as long as the LyX import and export preserved paragraph and character styles, it would be pretty easy. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Strategies for Writing Co-operation with Non-LyX Users?
Ehud Kaplan wrote: 1. It is difficult to tell which is newly inserted text vs deleted text-- it is all blue on my screen This is a bug we are aware of. It will be fixed in the next release (1.6.2), most likely. 2. There is no tracking of who changed what, as is nicely done in MS WORD This is supposed to work. LyX tracks the author name, and as of 1.6.0, you can allocate different colors to different authors (which is actually the source of the bug mentioned in #1). 3. There are no keyboard shortcuts for accepting/rejecting changes, making the process tedious you can allocate shortcuts in the preferences dialog (EditShortcuts). The corresponding functions are change-accept, change-reject and change-next. 4. Inserting notes into the text is not as nicely done as it used to be in previous version of MS WORD-- it is simply hard to see where the notes are, or what is their contents. Could you elaborate a bit? Jürgen
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 10:52:49 am Jürgen Spitzmüller wrote: Steve Litt wrote: Have you ever supplied your colleagues with a layout file containing all the environments and character styles they'll need for their document? I think even the most non-technical person would find LyX trivial to use if he/she never had to make an environment or character style. yes. Actually, I think that teaching people the advantages of semantic markup is one major task. The problem is that people actually like finger- painting. And LyX/LaTeX just isn't designed for that. Then somebody must write a document explaining why fingerprinting is bad, and styles are good. I'm behind on all my work right now, but if I get an opportunity I'll write such a document. Please remind me every few months. Thanks SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 11:07:41 am you wrote: 3. There are no keyboard shortcuts for accepting/rejecting changes, making the process tedious When I wrote Samba Unleashed there was no such shortcut either. In fact, when the editor took issue with a sentence, it was posed as a query, as in wouldn't this sentence be better in the past tense?. I would then respond in one of two ways: 1) Write that I agreed with the query and change the text, or 2) Write that I disagreed with the query, state my reasons, leave the text alone, and see what the editor said. Either way there was no need for a shortcut, maybe because I didn't get that many queries. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: MS Word to LyX
Anders Host-Madsen wrote: LyX is really a great way to write math. Therefore I would like to convert my old MS Word documents -- with a lot of equation in Equation Editor -- to LyX (these are documents I continually revise). Any advise about this? I found two commercial packages for conversion to LaTeX: Grind EQ and Word2Tex. They are expensive, and the results are so-so. Definitely requires a lot of hand editing of the LaTeX code. Any experiences with these programs? It appears to me the results from Word2Tex is a little more faithful to the source, but it's hard to evaluate from the trial version. OpenOffice will export LaTeX. You should be able to load your Word docs there, and then export. Might be no worse. You WILL have to do hand editing, one way or the other. There's just no way around it. There's also the free wvLatex program that you can try. I don't know if it runs on Windows. See here: http://wvware.sourceforge.net/ But if it doesn't, that's a good reason to dual boot Linux. ;-) rh
Re: Strategies for Writing Co-operation with Non-LyX Users?
Thanks, Jurgen. Your comments were helpful. As for the inserted comments (item #4), sometimes one needs to insert comments for one's colleagues while editing a text. I tried to insert a Lyx note or a comment, and although they showed up in the Lyx file, they did not show up in the output file, even though I checked the Show changes in output. By the way, checking this option produced many errors in going to pdflatex, but worked fine (with the exception of the comments) when producing a dvi file, which could then be pdf'ed without problems. EK Jürgen Spitzmüller wrote: Ehud Kaplan wrote: 1. It is difficult to tell which is newly inserted text vs deleted text-- it is all blue on my screen This is a bug we are aware of. It will be fixed in the next release (1.6.2), most likely. 2. There is no tracking of who changed what, as is nicely done in MS WORD This is supposed to work. LyX tracks the author name, and as of 1.6.0, you can allocate different colors to different authors (which is actually the source of the bug mentioned in #1). 3. There are no keyboard shortcuts for accepting/rejecting changes, making the process tedious you can allocate shortcuts in the preferences dialog (EditShortcuts). The corresponding functions are change-accept, change-reject and change-next. 4. Inserting notes into the text is not as nicely done as it used to be in previous version of MS WORD-- it is simply hard to see where the notes are, or what is their contents. Could you elaborate a bit? Jürgen -- Ehud Kaplan, Ph.D. Jules and Doris Stein Research to Prevent Blindness Professor Director, The laboratory of Visual Neuroscience Departments of Neuroscience, Ophthalmology, Structural Chemical Biology, The Mount Sinai School of Medicine One Gustave Levy Place NY, NY, 10029
Re: MS Word to LyX
Richard Heck rgh...@... writes: OpenOffice will export LaTeX. You should be able to load your Word docs there, and then export. Might be no worse. You WILL have to do hand editing, one way or the other. There's just no way around it. I tried to install open office (neo office). It does convert to LaTeX. But the issue is that it seems the philosophy in the OO converter is to make the typeset LaTeX document look like the OO document, rather than conveying the meaning/contents of the document -- WYSIWYG rather than WYSIWYM. The results is terrible, terrible LaTeX code. Maybe there is some option to set so that it's converted to nice latex code, that does not try to reproduce the formatting of the OO document? At least the commercial programs produce LaTeX code that reproduce the meaning of the original document fairly.
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Jan 26, 2009, at 1:07 PM, Ehud Kaplan wrote: Thanks, Jurgen. Your comments were helpful. As for the inserted comments (item #4), sometimes one needs to insert comments for one's colleagues while editing a text. I tried to insert a Lyx note or a comment, and although they showed up in the Lyx file, they did not show up in the output file, even though I checked the Show changes in output. Convert it to a Greyed Out comment by right-clicking on the note box. This will show up in output. The Note only shows up in LyX...
Re: Strategies for Writing Co-operation with Non-LyX Users?
Thanks. This does not seem the most intuitive menu entry I suppose I must read the manual! James C. Sutherland wrote: On Jan 26, 2009, at 1:07 PM, Ehud Kaplan wrote: Thanks, Jurgen. Your comments were helpful. As for the inserted comments (item #4), sometimes one needs to insert comments for one's colleagues while editing a text. I tried to insert a Lyx note or a comment, and although they showed up in the Lyx file, they did not show up in the output file, even though I checked the Show changes in output. Convert it to a Greyed Out comment by right-clicking on the note box. This will show up in output. The Note only shows up in LyX... -- Ehud Kaplan, Ph.D. Jules and Doris Stein Research to Prevent Blindness Professor Director, The laboratory of Visual Neuroscience Departments of Neuroscience, Ophthalmology, Structural Chemical Biology, The Mount Sinai School of Medicine One Gustave Levy Place NY, NY, 10029
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Since writing below I have found a work-around, which I hope will continue working on the biblio files: In BibDesk, convert the bibtex database into bibtex. This seems a little daft at first, but I picked this up on reading that on importing and exporting BibDesk converts umlauts, etc. into the LaTeX equivalent. My guess was that by converting to the same format, would have the effect of standardising the umlauts, etc. I have a suspicion that the software I used to gather the references doesn't know the LaTeX encodings for the umlauts, etc. and just left them in their original UniCode. For developers: Is there any sense in having bibtex convert files in the same way as I have (i.e. from bibtex to bibtex) to standardise the files before LyX takes them up? While redundant for many users, it might catch non-standard things and may make this just work, at least for the situation I have. This may also provide a means of testing that the bibliography is in a standard (or understandable) format and report a meaningful error if it's not. (The current error messages are a tad too geeky for non-programmers, etc.) I haven't time to do let them know right now, but BibDesk ideally should let users know that on loading a database, it had to convert some stuff, i.e. that the internal version of it is tainted with respect to the disk version, so that users are warned/asked to save the conversions, etc.--? Perhaps even insist that they do it immediately after loading it. You're welcome to read the rest, I might as well let it stand in case it's of use to anyone, but what's above it the nutshell take. Grant Grant Jacobs wrote: One thing that bothers me about this being a BibTeX issue, is that BibDesk writes these characters to RTF just fine. (It would tempt me to think that there might a work-around that gets this directly from BibDesk, avoiding BibTex.) 0) You have not understood the concept behind BibDesk - it's only a sophisticated frontend to the database (bib) file that bibtex uses. Try to read up on this. Actually I do understand it ;-) No offence, but if you knew the effort I have put into this, telling me to Try to read up on this is a bit rich! :-) 1) You can enter the TeX-replacements for the special characters in the bib-file (or in Bibdesk) instead of the unicode characters. See http://www.bibtex.org/SpecialSymbols/ Since you say it is mostly for European author names, this should be enough. Doing this manually is not a practical option. [Resolved above, though] 2) Make sure you use a recent version of BibDesk. Also, TeXLive-2008 and LyX 1.6.1 won't hurt. LyX is 1.6.1 as the subject line says, BibDesk is the latest version. Tex will be a little older (I have TexLive-2008 on disk, but I wanted to leave installation of that until later, as I didn't wanted a messed-up installation delaying me even more!) HTH, In an indirect way: it lead to seeing the comment about BiBDesk converting on importing and exporting, etc. in a doc on the web. Long story. Konrad P.S. Forget the path via RTF! OK. Bit surprised though: there is an exporter for it in BibDesk and an importer in LyX, so in principle it should work, right? (But obviously not for some reason...!) At 3:32 PM +0100 26/1/09, Konrad Hofbauer wrote: Make sure you have 'Unicode to TeX Conversion' enabled in BibDesk's 'Files' Preferences !!! Obviously :-) (I've already been all over the Preferences of both programs looking for likely things, googling, etc. I make a point of trying hard myself before resorting to forums. Among others things, the back-and-forth in forums takes a lot of time. I've put literally hours into this. I hope you can my perspective: I really expected this to just work as BibDesk must be used by most LyX users and UniCode is so universal now... and all the rest. Fair point about bibtex's age, though. [See my comment about the file format though, para. 3 above.]) Grant -- --- Grant Jacobs Ph.D. BioinfoTools ph. +64 3 478 0095 (office, after 10am) PO Box 6129, or +64 27 601 5917 (mobile) Dunedin, gjac...@bioinfotools.com NEW ZEALAND. Bioinformatics tools: deriving knowledge from biological data Bioinformatics tools - software development - consulting - training 15 years experience in bioinformatics ready to solve your problem Check out the website for more details: http://www.bioinfotools.com The information contained in this mail message is confidential and may be legally privileged. Readers of this message who are not the intended recipient are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immed- iately and destroy the original message.
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Grant Jacobs wrote: I have a suspicion that the software I used to gather the references doesn't know the LaTeX encodings for the umlauts, etc. and just left them in their original UniCode. Ah ... I assumed your bibtex files initially came from BibDesk. Maybe it's time to switch to a reference manager with better Latex-support. (Do you hear me shouting 'BibDesk' ? ;) ) For developers: I'm not, nevertheless I throw in my 2 cents... ;) Is there any sense in having bibtex convert files in the same way as I have (i.e. from bibtex to bibtex) to standardise the files before LyX takes them up? While redundant for many users, it might catch non-standard things and may make this just work, at least for the situation I have. This is probably something that bibtex should take care of, not LyX. If you know of an existing script or library that already does that, it might be considered in LyX. This may also provide a means of testing that the bibliography is in a standard (or understandable) format and report a meaningful error if it's not. (The current error messages are a tad too geeky for non-programmers, etc.) Unfortunately, one could say that about almost every Latex error message. :( Actually I do understand it ;-) No offence, but if you knew the effort I have put into this, telling me to Try to read up on this is a bit rich! :-) No offense here either, I just did not get why you would want to _export_ from BibDesk, if BibDesk's native file format is exactly what LyXbibtex want (and works). P.S. Forget the path via RTF! OK. Bit surprised though: there is an exporter for it in BibDesk and an importer in LyX, so in principle it should work, right? The LyX-importer (if you have the right external tool installed) is for text, only, and not for references/citations. I've put literally hours into this. This happens ... (same here on other issues, usually LaTeX-limitations). I hope you can my perspective: I really expected this to just work as BibDesk must be used by most LyX users and UniCode is so universal now... and all the rest. At least, now you know that simply saving in BibDesk solves the problem. Fixed for once and forever. :) /Konrad
Re: MS Word to LyX
Anders Host-Madsen wrote: I tried to install open office (neo office). It does convert to LaTeX. But the issue is that it seems the philosophy in the OO converter is to make the typeset LaTeX document look like the OO document, rather than conveying the meaning/contents of the document -- WYSIWYG rather than WYSIWYM. The results is terrible, terrible LaTeX code. Maybe there is some option to set so that it's converted to nice latex code, that does not try to reproduce the formatting of the OO document? At least the commercial programs produce LaTeX code that reproduce the meaning of the original document fairly. To get all the power of the openoffice - latex converter you have to use it from the command line and tweak configuration files. Google for writer2latex. Nevertheless, I doubt that writer2latex converts very well equations in MsWord. Maybe you could try to export your equations to MathML and then convert the MathML to LaTeX. I do not know if MsWord can export to MathML. Cheers, Charles
How to shrink the size of math formulas?
Hello, is there a way of shrinking the overall size of a math formula, either displayed or inline? I am trying to stay within a page limit for a paper, and I could do with shrinking the formulas (as they would appear in the final output - I don't care too much what size they look in Lyx - so if i have to hack some Tex that is ok). I guess the same question applies to code (Lyx-Code) cheers
Re: Strategies for Writing Co-operation with Non-LyX Users?
Ehud Kaplan wrote:
Thanks, Jurgen. Your comments were helpful.
As for the inserted comments (item #4), sometimes one needs to insert
comments for one's colleagues while editing a text.
I tried to insert a Lyx note or a comment, and although they showed up
in the Lyx file, they did not show up in the output file, even though I
checked the Show changes in output.
I see. LyX notes are actually not designed for that kind of task. As James
wrote, we have greyed out notes, although this is not everyone's taste.
Attached are two alternatives:
1. a module that lets you insert todo notes, as seen here:
ftp://dante.ctan.org/tex-
archive/macros/latex/contrib/todonotes/todonotesexample.pdf
You need the todonotes package for this
2. a module that lets you insert real PDF annotations (that display in Adobe
reader, but not in some other PDF viewers). This uses the pdfcomment package.
These modules need to be saved in your local LyX directory (in the layouts
folder), then they can be selected in DocumentModules after LyX has been
reconfigures (EditReconfigure).
By the way, checking this option produced many errors in going to
pdflatex, but worked fine (with the exception of the comments) when
producing a dvi file, which could then be pdf'ed without problems.
Do you have an example file for this? We have reworked the PDF output of
change tracking markup for 1.6.2, and this is likely to be much more robust.
Jürgen
#\DeclareLyXModule{Todo-notes}
#DescriptionBegin
#Displays the LyX notes in the output. A list of todo notes can be produced
#by inserting \listoftodos in ERT.
#DescriptionEnd
# Author: Juergen Spitzmueller sp...@lyx.org
Format 11
Preamble
\RequirePackage{todonotes}
EndPreamble
InsetLayout Note:Comment
LabelString comment/todo
LatexType command
LatexName todo
MultiPar false
End
#\DeclareLyXModule{PDF comments}
#DescriptionBegin
#Inserts annotations to the PDF file.
#DescriptionEnd
# Author: Juergen Spitzmueller sp...@lyx.org
Format 11
InsetLayout PDF-Annotation
LyXType custom
LabelString PDF
LatexType command
LatexName pdfcomment
Decorationclassic
LabelFont
Color magenta
SizeSmall
EndFont
MultiPar false
OptionalArgs 1
Preamble
\RequirePackage{pdfcomment}
EndPreamble
End
InsetLayout PDF-Margin
LyXType custom
LabelString PDF (margin)
LatexType command
Decorationclassic
LatexName pdfmargincomment
LabelFont
Color green
SizeSmall
EndFont
MultiPar false
OptionalArgs 1
Preamble
\RequirePackage{pdfcomment}
EndPreamble
End
Re: Strategies for Writing Co-operation with Non-LyX Users?
Jürgen Spitzmüller wrote:
1. a module that lets you insert todo notes, as seen here:
ftp://dante.ctan.org/tex-
archive/macros/latex/contrib/todonotes/todonotesexample.pdf
You need the todonotes package for this
Try the attached instead.
Jürgen
#\DeclareLyXModule{TODO notes}
#DescriptionBegin
#Inserts TODO-notes in the output. A list of todo notes can be produced
#by inserting \listoftodos in ERT.
#DescriptionEnd
# Author: Juergen Spitzmueller sp...@lyx.org
Format 11
InsetLayout TODO
LyXType custom
LabelString TODO
LatexType command
LatexName todo
Decorationclassic
LabelFont
Color magenta
SizeSmall
EndFont
MultiPar false
OptionalArgs 1
Preamble
\RequirePackage{todonotes}
EndPreamble
End
LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Having *finally* managed to persuade LyX to generate bibliographies at all, I now find that LyX seemingly cannot handle characters with diacritic marks (i.e. UniCode) in .bib files when exporting them to PDF, etc. Unfortunately this really has to work for me as it will be the case with a very large number of European, etc., author's names and so on. If this is how it is meant to be or the way it is, *please* add some information to this effect in the tutorial and user guide or somewhere prominent, so that users needing this can quit early and look for another another solution. On the other hand, the internationalisation section of the features blurb mentions unicode compliance in passing... Does anyone have any remedies for this? Preferably simple: I am all out of time to do more of the kind of fiddling I have had to do so far. I've tried setting the language encoding to utf8, but it generates an empty document and complains that 'utf8.def' isn't present. Setting language encoding to 'Unicode (XeTeX) generates output (without crashing during the conversion), but the characters aren't correct. I can't generate plain text (ps2ascii) at all. Generating PostScript, generates output but also gets the characters wrong. And on it goes, randomly trying this, that and the other in vain attempts to make something work...! :-( Is there some version or other of the main LaTeX installation that I am supposed to be using? (And if that's the case, shouldn't LyX be check that it's a sane choice, etc?) Grant Jacobs -- --- Grant Jacobs Ph.D. BioinfoTools ph. +64 3 478 0095 (office, after 10am) PO Box 6129, or +64 27 601 5917 (mobile) Dunedin, gjac...@bioinfotools.com NEW ZEALAND. Bioinformatics tools: deriving knowledge from biological data Bioinformatics tools - software development - consulting - training 15 years experience in bioinformatics ready to solve your problem Check out the website for more details: http://www.bioinfotools.com The information contained in this mail message is confidential and may be legally privileged. Readers of this message who are not the intended recipient are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immed- iately and destroy the original message. This applies also to any attached documents.
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Grant Jacobs wrote: Having *finally* managed to persuade LyX to generate bibliographies at all, I now find that LyX seemingly cannot handle characters with diacritic marks (i.e. UniCode) in .bib files when exporting them to PDF, etc. Unfortunately this really has to work for me as it will be the case with a very large number of European, etc., author's names and so on. This is a BibTeX limitation. BibTeX is an old beast, the most recent release still predates the advent of unicode. Fact is that bibtex cannot deal with unicode (or any other multibyte encoding, for that matter) at all. There's noting that LyX can do here. You need to use another encoding for the bib file, such as latin1, and insert the non-supported characters by means of the respective macros. A decent bib file editor, such as JabRef or pybliographic, should actually handle this for you. If this is how it is meant to be or the way it is, *please* add some information to this effect in the tutorial and user guide or somewhere prominent, so that users needing this can quit early and look for another another solution. You are right, this needs to be documented in the UserGuide, sec. 6.5.2. CC:ing the documentation list. Jürgen PS.: please open a new thread for new topics.
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Jürgen Spitzmüller wrote: You need to use another encoding for the bib file, such as latin1, and insert the non-supported characters by means of the respective macros. Also look here for some further information: http://wiki.lyx.org/BibTeX/Tips#toc1 Jürgen
Re: Strategies for Writing Co-operation with Non-LyX Users?
Hello fellow humanists! What a luck! Only one of your colleagues use LaTeX and some use Oo? Only the editors use LaTeX? In my area and field (italian history of music), World and Word mean the same thing, and everything which happens to us, little insignificant mortal scholars, is because of the will of the Big Bill, who rescued our souls just a bunch of years ago out of the dark fogs of the ink and paper era and tought us the principle of the MS enlightment. My supervisor, known in our field for his above-average informatical knowledge with databases and so on, once called exotic some of my documents printed with Oo. I'm just starting publishing things in small, medium-size and large publications. Everywhere, when asked what if LaTeX?, after a what what? they always told me: please send us printed paper and .DOC in CD (!) or email if possible. There's no way to break the entire chain of MS rule, other than go straight, ignoring it. With my supervisor now I got back to paper: I print out my drafts, hand to him, get back the red pen corrections and type them into my LyX document. I love this: past and future altogether, but far away from the flattened MS present. But you were talking about Strategies. It's quite hard for me to have my docs converted to OO (something not working in my LyX install) so I can't help you with technical things. The best strategy is to spread the LyX verb. If you only convince one person, you'll be two instead of one, which is to double the effort. This is a long-term strategy. Another long-long-term strategy is to promote (and partecipate to) the developmente of LyX (and related sw) in a simplified and humanists-friendly (rather non-scientific friendly) direction, which is IMHO one of the primary goals of LyX. When I will able to show my colleagues some LyX versions with BibLaTeX (for humanist bibliographies) fully working, perfect Lilypond (a LaTeX-like music typesetter) integration without having to tweak code and so on, chances of victory will be for LyX. Till that day, no way. Peter was talking about google docs. document-sharing is IMHO the weakest battlefront for LyX (and for a lot of free software and projects), and the final battle will be fought there, but this is future, and it's out of this post. Still curious to hear some more opinions and experiences. Piero
Re: \usepackage[full]{textcomp} - where to set?
where can I tell Lyx once forever that it shall load the textcomp
package always with the option full, because this is required by
certain other packages?
You can pass the full option to DocumentSettingsClass Options.
Class options will be passed down to the packages by LaTeX.
Apparently not:
LaTeX Error: Option clash for package textcomp.
...textcomp\RequirePackage[full]{textcomp}\fi
The package textcomp has already been loaded with options:
[]
There has now been an attempt to load it with options
[full]
Adding the global options:
,full
to your \documentclass declaration may fix this.
Try typing return to proceed.
THis was the start of the source:
% Quellcode vorschauen
%% LyX 1.6.1 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[10pt,ngerman,full]{scrartcl}
\usepackage[osf]{mathpazo}
\renewcommand{\sfdefault}{cmbr}
\renewcommand{\ttdefault}{lmtt}
\renewcommand{\familydefault}{\sfdefault}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{geometry}
\geometry
{verbose,letterpaper,tmargin=2cm,bmargin=2cm,lmargin=2cm,rmargin=2cm}
\pagestyle{empty} \usepackage{array}
\usepackage{textcomp}
\makeatletter
Sincerely,
Wolfgang
RE: Re: Strategies for Writing Co-operation with Non-LyX Users?
Still curious to hear some more opinions and experiences. I'm succesfully spreading the word of LyX to my supervisors and colleagues. I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. Piero Vincent
Re: \usepackage[full]{textcomp} - where to set?
Wolfgang Keller wrote:
You can pass the full option to DocumentSettingsClass Options.
Class options will be passed down to the packages by LaTeX.
Apparently not:
LaTeX Error: Option clash for package textcomp.
...textcomp\RequirePackage[full]{textcomp}\fi
could you post a small example file? I'm unable to reproduce the problem.
Jürgen
Re: \usepackage[full]{textcomp} - where to set?
could you post a small example file? I'm unable to reproduce the
problem.
I've narrowed the source of the problem down to the use of a symbol I
use: \textopenbullet{}, together with the kpfonts.
The workaround is to use the ifsym package.
Try this:
% Quellcode vorschauen
%% LyX 1.6.1 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[10pt,ngerman,full]{scrartcl}
\usepackage[osf]{mathpazo}
\renewcommand{\sfdefault}{cmbr}
\renewcommand{\ttdefault}{lmtt}
\renewcommand{\familydefault}{\sfdefault}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{geometry}
\geometry
{verbose,letterpaper,tmargin=2cm,bmargin=2cm,lmargin=2cm,rmargin=2cm}
\pagestyle{empty} \usepackage{textcomp}
%% User specified LaTeX commands.
\usepackage{color}
\definecolor{grey}{gray}{0.3}
\usepackage{kpfonts}
%\renewcommand{\rmdefault}{uop}
\makeatother
\usepackage{babel}
\usepackage{babel}
\begin{document}
\textopenbullet{}
\end{document}
Re: Strategies for Writing Co-operation with Non-LyX Users?
Vincent van Ravesteijn - TNW wrote: Still curious to hear some more opinions and experiences. I'm succesfully spreading the word of LyX to my supervisors and colleagues. I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. It'd be nice to have a list of things people need for collaboration. I guess we've probably had that discussion before, but I've never thought it had a very good outcome. Richard
Re: Strategies for Writing Co-operation with Non-LyX Users?
I don't have a whole lot to add to what other people have said. The difficulties in using LyX for cross-program collaboration will depend very much upon your field. I wrote a paper a while back with someone who was using Word, or maybe even an old version of WordPerfect, but it was relatively painless, because there was almost no technical material in it. So I was able to export to RTF, he could do what he wanted and send it back marked with his changes in blue, and I could put those changes back into LyX. For our next paper, though, I was able to get him to use LyX. I've also managed to get several of my students using LyX. It takes time for them to adjust to a new way of working. But once they adjust, they are all very glad that they have. The problem, of course, is that people tend not to realize that there even could be another way of working, or that it might have real benefits. You don't realize until you stop using Word, etc, how much the program gets in the way of just writing. It sounds almost crazy, but it's true. Richard
Re: \usepackage[full]{textcomp} - where to set?
Wolfgang Keller wrote:
could you post a small example file? I'm unable to reproduce the
problem.
I've narrowed the source of the problem down to the use of a symbol I
use: \textopenbullet{}, together with the kpfonts.
You can disable the automatic textcomp loading of the kpfonts package with the
package option notextcomp (see the package documentation). If you keep the
full class option in LyX, textcomp will then be loaded with this option
nevertheless (even though kpfonts just doesn't recognize this).
Jürgen
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Mon, 26 Jan 2009 07:53:14 -0500 rgheck rgh...@bobjweil.com wrote: Vincent van Ravesteijn - TNW wrote: Still curious to hear some more opinions and experiences. I'm succesfully spreading the word of LyX to my supervisors and colleagues. I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. It'd be nice to have a list of things people need for collaboration. I guess we've probably had that discussion before, but I've never thought it had a very good outcome. Richard Personally, some way of compating/merging documents would be great. I don't know about others, but I know a lot of people who work with latex, very few with lyx. We also send out papers in latex. It's very difficult for me to do the work in lyx as I need to incorporate their changes that were done in latex somehow, and preferably do it without copying them over. The best solution would be if I could import the latex document back into lyx and then compare the two lyx files, although of course there are a lot of differences due to importing special stuff (don't remember sepecifics at the moment but I recall that a lot of things import as ert). I would even settle for just a proper tool to merge two lyx documents, most everything else can be achieved that way. Another nice things would be to be able to diff against version control (if the previous is possible then this will be a subset also)
Re: Strategies for Writing Co-operation with Non-LyX Users?
I had a few days back this problem: how to give my document to somebody for corrections (anything except .lyx or .tex). The other person did try to install lyx (on Kubuntu) but probably Kubuntu's repositories host a previous version of LyX and we all know that it costs some time to get all things working straight forward. I only want to say, as an end-user, that I don't even think to go back to OpenOffice for documents. Even if there are cooperation problems. While I agree, more or less, with Piero Faustini that _one_ way to push LyX further is to ignore other documents (especially .doc's) I still think that a tool should be interoperable meaning, except of getting it working on most operating systems, that it is able to handle most known/established document formats (painless import/export). Kind Regards, Nikos
Re: Strategies for Writing Co-operation with Non-LyX Users?
It'd be nice to have a list of things people need for collaboration. I guess we've probably had that discussion before, but I've never thought it had a very good outcome. The most importand would IMHO be to compare two documents and in some nice way, display differences so I can accept or reject them. Best would be if everything could be within lyx and never have to use latex or external tools. After this feature would be lyx having the possibility to save/open documents stored on a server. ftp, wiki,scp,subversion or what ever that will make it transparent. And when you are trying to save you see the differences between your version and the one on the server and you can check them and accept or reject and save a new version. Also make it possible to use what ever document format you want to store your LyX file in. Then you can open doc files and save them on an ftp server without problem :-) Nice! Well, it might require some configuration settings...
LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Thanks for explaining this. Its a damn nuisance I have admit, as I've spend a long time trying to resolve this when I have little time to spare really. I thought I was starting a new thread: I set a new subject line. Is there some other thing I am supposed to do to make that happen?? I'm not working via a web interface, and most list software I've used just works off the subject lines... If people are updating that part of the docs, it'd be good to see it *explain* how to make bibliographies work: the explanation currently there is leaving too much out. I'm too busy to help (grant application due, etc.) One thing that bothers me about this being a BibTeX issue, is that BibDesk writes these characters to RTF just fine. (It would tempt me to think that there might a work-around that gets this directly from BibDesk, avoiding BibTex.) I've tried saving the biblio as a RTF file from BibDesk, then importing that into a LyX document, but I got An error occurred on while running rtf2latex 'file'. (Feels like nothing wants to work over here!) Does rtf2latex suffer the same problem as BibTex? The idea was to set up a template in BibDesk to generate the right format, write that. In LyX, let LyX do the citations (which it seems to do OK, not that I can test it that well yet), import the RTF biblio (via BiBDesk) into the right place, and just delete the LyX-generated biblio from the final exported format using a PDF editor or whatnot. I would try the equivalent using HTML and importing that, but the formatting/styling in HTML might be even more limited. Grant Jacobs -- --- Grant Jacobs Ph.D. BioinfoTools ph. +64 3 478 0095 (office, after 10am) PO Box 6129, or +64 27 601 5917 (mobile) Dunedin, gjac...@bioinfotools.com NEW ZEALAND. Bioinformatics tools: deriving knowledge from biological data Bioinformatics tools - software development - consulting - training 15 years experience in bioinformatics ready to solve your problem Check out the website for more details: http://www.bioinfotools.com The information contained in this mail message is confidential and may be legally privileged. Readers of this message who are not the intended recipient are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immed- iately and destroy the original message. This applies also to any attached documents.
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Mon, Jan 26, 2009 at 3:42 PM, A B gentosa...@gmail.com wrote: It'd be nice to have a list of things people need for collaboration. I guess we've probably had that discussion before, but I've never thought it had a very good outcome. The most importand would IMHO be to compare two documents and in some nice way, display differences so I can accept or reject them. Best would be if everything could be within lyx and never have to use latex or external tools. After this feature would be lyx having the possibility to save/open documents stored on a server. ftp, wiki,scp,subversion or what ever that will make it transparent. And when you are trying to save you see the differences between your version and the one on the server and you can check them and accept or reject and save a new version. Also make it possible to use what ever document format you want to store your LyX file in. Then you can open doc files and save them on an ftp server without problem :-) Nice! Well, it might require some configuration settings... These are very interesting and useful points, but they a different problem: the original poster explicitly asked on how to co-operate with non-LyX users. I think that both should be addressed, but the non-LyX users is the one to be addressed here. We should probably develop two lists... So, here are my points: As I had some problems exporting into doc/rtf including pictures, I am following the approach of sending my collaborators the .pdf and an .rtf (or doc based on the pdf) (ignore the formating). Obviously, I am loosing the track changes (which would be nice to have) and have to incorporate the comments manually. But if it would be possible to import an rtf/doc/odf text only including changes, that would solve many problems (no idea if this is possible). Cheers Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Faculty of Science Natural Sciences Building Private Bag X1 University of Stellenbosch Matieland 7602 South Africa
RE: Strategies for Writing Co-operation with Non-LyX Users?
While I agree, more or less, with Piero Faustini that _one_ way to push LyX further is to ignore other documents (especially .doc's) I still think that a tool should be interoperable meaning, except of getting it working on most operating systems, that it is able to handle most known/established document formats (painless import/export). Even if we can get LyX to handle 'all' document formats, saving your work as e.g. MS Word format, will inevitably reduce the representation of the document. That is, not all options of LyX are supported in the MS Word format and vice versa. Thus, painless import/export won't be possible. Maybe we should find a way to perfectly support content-only collaboration: Usually only one author governs the layout, so when you share your document with a co-author, you only want him or her to edit the content. Ideally: you save your document as plain text, your co-authors can open this plain text in their own editor, edit the text, give back another plain text file and you now want to merge this plain text file with your LyX file and accept/reject the changes. Vincent
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Grant Jacobs wrote:
One thing that bothers me about this being a BibTeX issue, is that
BibDesk writes these characters to RTF just fine. (It would tempt me to
think that there might a work-around that gets this directly from
BibDesk, avoiding BibTex.)
0) You have not understood the concept behind BibDesk - it's only a
sophisticated frontend to the database (bib) file that bibtex uses. Try
to read up on this.
1) You can enter the TeX-replacements for the special characters in the
bib-file (or in Bibdesk) instead of the unicode characters.
See http://www.bibtex.org/SpecialSymbols/
Since you say it is mostly for European author names, this should be enough.
2) Make sure you use a recent version of BibDesk. Also, TeXLive-2008 and
LyX 1.6.1 won't hurt.
3) BibDesk takes care of these characters automatically:
If I enter åland sørenson as author, the bib-file that Bibdesk 1.3.19
creates looks like this:
%% Created for khofbaue at 2009-01-26 15:14:23 +0100
%% Saved with string encoding Unicode (UTF-8)
@phdthesis{sorenson:uq,
Author = {s{\o}renson, {\aa}land},
Title = {testing}}
So even though the file is saved in Unicode, Bibdesk replaces the
characters by their corresponding latex macros (where possible, I
assume), and everything just works in LyX.
HTH,
Konrad
P.S. Forget the path via RTF!
Re: How to make Lyx recognize packages installed by Miktex (on ubuntu)?
I have Tex-Live but not the tex live package manager. Since the package manager is not part of the ubuntu repos yet (as in that I can install it via apt-get install), I didn't bother with installing it yet. When it's part of ubuntu I will start using it probably. E. Kaplan wrote: Just curious-- if you have Tex-Live, why do you also need Miktex? rintcius wrote: I finally found a solution. I created a link from .miktex to a texmf directory. Then texhash. After this (and a reconfigure) Lyx recognizes the packages. Rintcius
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Make sure you have 'Unicode to TeX Conversion' enabled in BibDesk's 'Files' Preferences !!! HTH, Konrad
Exporting Hebrew tex file under OS-X
When I try to export Hebrew LyX file into TeX file, It's print out an error: basic_filebuf::_M_convert_to_external conversion error (Lyx 1.6 On Os X) What can I do? Thanks, Ronen.
Re: Exporting Hebrew tex file under OS-X
Ronen Abravanel wrote: What can I do? Provide a very small minimal LyX file that shows the error (and hope that somebody competent looks at it) ... /Konrad
RE: Strategies for Writing Co-operation with Non-LyX Users?
On Mon, 2009-01-26 at 15:29 +0100, Vincent van Ravesteijn - TNW wrote: [...] Maybe we should find a way to perfectly support content-only collaboration: Usually only one author governs the layout, so when you share your document with a co-author, you only want him or her to edit the content. Ideally: you save your document as plain text, your co-authors can open this plain text in their own editor, edit the text, give back another plain text file and you now want to merge this plain text file with your LyX file and accept/reject the changes. Vincent Yep, exactly that. I agree 100%. Nikos
Re: Strategies for Writing Co-operation with Non-LyX Users?
Maybe we should find a way to perfectly support content-only collaboration: Usually only one author governs the layout, so when you share your document with a co-author, you only want him or her to edit the content. Ideally: you save your document as plain text, your co-authors can open this plain text in their own editor, edit the text, give back another plain text file and you now want to merge this plain text file with your LyX file and accept/reject the changes. Vincent Yep, exactly that. I agree 100%. Nikos I would also agree to 100% or more if it were not for real world experience of co-operation. Plain text is far from unproblematic. There is only a small fraction of people that can save something as plain text without having to call a friend. Then comes the interesting problem of opening a plain text file (created in unix) in windows.. ouch.. you need some structure (sections, title, etc.) to work. The fine tuning can be done later perhaps. I managed this once with RTF but I hate to do that ever again.
MS Word to LyX
LyX is really a great way to write math. Therefore I would like to convert my old MS Word documents -- with a lot of equation in Equation Editor -- to LyX (these are documents I continually revise). Any advise about this? I found two commercial packages for conversion to LaTeX: Grind EQ and Word2Tex. They are expensive, and the results are so-so. Definitely requires a lot of hand editing of the LaTeX code. Any experiences with these programs? It appears to me the results from Word2Tex is a little more faithful to the source, but it's hard to evaluate from the trial version.
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 02:42:25 am Jürgen Spitzmüller wrote: I have convinced some colleagues to use LyX or LaTeX, but since people in the humanities are often technically rather unskilled, this usually entails a significant amount of personal administration service, and you need to find the time for that. Hi Jürgen, Have you ever supplied your colleagues with a layout file containing all the environments and character styles they'll need for their document? I think even the most non-technical person would find LyX trivial to use if he/she never had to make an environment or character style. Of course, installation of LyX is still a problem, but with Windows can't you just create an installer to do it? SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
RE: Re: Strategies for Writing Co-operation with Non-LyX Users?
Vincent van Ravesteijn - TNW wrote: I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. Having just finished editing a book, I think there is two phases in collaborative work 1) you divide the writing (you do chapter 1, I'll write chapter 2) the multiple steps of editing and ironing the text between the editor, the authors and the publisher For 1) Everybody can write in his favorite software and you can import the doc file in LyX without much problems For 2) what would be needed is a good cross-platform customized pdf reader with annotations possibilities and a way to link these annotations to the lyx document. I have used for my project Foxit which is not free but works with Wine on Linux. Foxit has a very bad interface. Sadly annotations support in poppler is unfinished. Cheers, Charles -- http://www.kde-france.org
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 08:33:32 am Nikos Alexandris wrote: I only want to say, as an end-user, that I don't even think to go back to OpenOffice for documents. Even if there are cooperation problems. Is it just me, or is OpenOffice terrible about styles? One day when mad at LyX, I briefly tried writing a 2nd edition of a book in OpenOffice (the first edition had been in MSWord from 1999). My styles didn't copy over, then when I manually put in styles they intermittently vanished. OO is great for a 2 page letter, but it's a horror movie when writing a book. After that foray into OO, I got really serious about learning to program LaTeX environments and commands, and their counterparts in LyX. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 09:29:16 am Vincent van Ravesteijn - TNW wrote: While I agree, more or less, with Piero Faustini that _one_ way to push LyX further is to ignore other documents (especially .doc's) I still think that a tool should be interoperable meaning, except of getting it working on most operating systems, that it is able to handle most known/established document formats (painless import/export). Even if we can get LyX to handle 'all' document formats, saving your work as e.g. MS Word format, will inevitably reduce the representation of the document. That is, not all options of LyX are supported in the MS Word format and vice versa. Thus, painless import/export won't be possible. Maybe we should find a way to perfectly support content-only collaboration: Styles give you content-only collaboration. If you can find a way of converting an MS Word doc, including its styles, into a LyX doc, including styles, and vice versa, neither side needs to forego layout. So for instance, if the MS Word author has a paragraph in his mycode style, convert it to LyX in the mycode environment. Then it's just a matter of making the two environments look somewhat similar. When I was assigned main authorship of Samba Unleashed, Sams Publishing sent me (and all the contributing authors) the MSWord equivalent of a layout file (I think they called it a style file), and a 4 page document on what styles to use when. They forbid formatting without styles, and IIRC strongly recommended against my making my own styles. The result was that my choice of styles was dictated by the style guide, and once I got used to the style guide, I didn't need to think about formatting at all -- I became a content-only author, which pleased both Sams and me. At the start of a project with some using MSWord and some using LyX, it wouldn't be that difficult to supply the LyXers with a complete layout file and style guide, and the Worders with a complete style file and identical style guide. Once done, as long as the LyX import and export preserved paragraph and character styles, it would be pretty easy. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Strategies for Writing Co-operation with Non-LyX Users?
Steve Litt wrote: Have you ever supplied your colleagues with a layout file containing all the environments and character styles they'll need for their document? I think even the most non-technical person would find LyX trivial to use if he/she never had to make an environment or character style. yes. Actually, I think that teaching people the advantages of semantic markup is one major task. The problem is that people actually like finger- painting. And LyX/LaTeX just isn't designed for that. Of course, installation of LyX is still a problem, but with Windows can't you just create an installer to do it? Of course. Jürgen
Re: Strategies for Writing Co-operation with Non-LyX Users?
My own problems with using Lyx for a committee-composed documents are much more prosaic: 1. It is difficult to tell which is newly inserted text vs deleted text-- it is all blue on my screen 2. There is no tracking of who changed what, as is nicely done in MS WORD 3. There are no keyboard shortcuts for accepting/rejecting changes, making the process tedious 4. Inserting notes into the text is not as nicely done as it used to be in previous version of MS WORD-- it is simply hard to see where the notes are, or what is their contents. That being said, the tracking of changes is the MAIN reason I use Lyx in the first place, since, in general, I prefer Latex with Kile (under Linux) or WinEdt (under Windows), but Latex does not provide convenient ways of tracking changes, as far as I know. E. Kaplan Steve Litt wrote: On Monday 26 January 2009 09:29:16 am Vincent van Ravesteijn - TNW wrote: While I agree, more or less, with Piero Faustini that _one_ way to push LyX further is to ignore other documents (especially .doc's) I still think that a tool should be interoperable meaning, except of getting it working on most operating systems, that it is able to handle most known/established document formats (painless import/export). Even if we can get LyX to handle 'all' document formats, saving your work as e.g. MS Word format, will inevitably reduce the representation of the document. That is, not all options of LyX are supported in the MS Word format and vice versa. Thus, painless import/export won't be possible. Maybe we should find a way to perfectly support content-only collaboration: Styles give you content-only collaboration. If you can find a way of converting an MS Word doc, including its styles, into a LyX doc, including styles, and vice versa, neither side needs to forego layout. So for instance, if the MS Word author has a paragraph in his mycode style, convert it to LyX in the mycode environment. Then it's just a matter of making the two environments look somewhat similar. When I was assigned main authorship of Samba Unleashed, Sams Publishing sent me (and all the contributing authors) the MSWord equivalent of a layout file (I think they called it a style file), and a 4 page document on what styles to use when. They forbid formatting without styles, and IIRC strongly recommended against my making my own styles. The result was that my choice of styles was dictated by the style guide, and once I got used to the style guide, I didn't need to think about formatting at all -- I became a content-only author, which pleased both Sams and me. At the start of a project with some using MSWord and some using LyX, it wouldn't be that difficult to supply the LyXers with a complete layout file and style guide, and the Worders with a complete style file and identical style guide. Once done, as long as the LyX import and export preserved paragraph and character styles, it would be pretty easy. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Strategies for Writing Co-operation with Non-LyX Users?
Ehud Kaplan wrote: 1. It is difficult to tell which is newly inserted text vs deleted text-- it is all blue on my screen This is a bug we are aware of. It will be fixed in the next release (1.6.2), most likely. 2. There is no tracking of who changed what, as is nicely done in MS WORD This is supposed to work. LyX tracks the author name, and as of 1.6.0, you can allocate different colors to different authors (which is actually the source of the bug mentioned in #1). 3. There are no keyboard shortcuts for accepting/rejecting changes, making the process tedious you can allocate shortcuts in the preferences dialog (EditShortcuts). The corresponding functions are change-accept, change-reject and change-next. 4. Inserting notes into the text is not as nicely done as it used to be in previous version of MS WORD-- it is simply hard to see where the notes are, or what is their contents. Could you elaborate a bit? Jürgen
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 10:52:49 am Jürgen Spitzmüller wrote: Steve Litt wrote: Have you ever supplied your colleagues with a layout file containing all the environments and character styles they'll need for their document? I think even the most non-technical person would find LyX trivial to use if he/she never had to make an environment or character style. yes. Actually, I think that teaching people the advantages of semantic markup is one major task. The problem is that people actually like finger- painting. And LyX/LaTeX just isn't designed for that. Then somebody must write a document explaining why fingerprinting is bad, and styles are good. I'm behind on all my work right now, but if I get an opportunity I'll write such a document. Please remind me every few months. Thanks SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Monday 26 January 2009 11:07:41 am you wrote: 3. There are no keyboard shortcuts for accepting/rejecting changes, making the process tedious When I wrote Samba Unleashed there was no such shortcut either. In fact, when the editor took issue with a sentence, it was posed as a query, as in wouldn't this sentence be better in the past tense?. I would then respond in one of two ways: 1) Write that I agreed with the query and change the text, or 2) Write that I disagreed with the query, state my reasons, leave the text alone, and see what the editor said. Either way there was no need for a shortcut, maybe because I didn't get that many queries. SteveT Steve Litt Recession Relief Package http://www.recession-relief.US
Re: MS Word to LyX
Anders Host-Madsen wrote: LyX is really a great way to write math. Therefore I would like to convert my old MS Word documents -- with a lot of equation in Equation Editor -- to LyX (these are documents I continually revise). Any advise about this? I found two commercial packages for conversion to LaTeX: Grind EQ and Word2Tex. They are expensive, and the results are so-so. Definitely requires a lot of hand editing of the LaTeX code. Any experiences with these programs? It appears to me the results from Word2Tex is a little more faithful to the source, but it's hard to evaluate from the trial version. OpenOffice will export LaTeX. You should be able to load your Word docs there, and then export. Might be no worse. You WILL have to do hand editing, one way or the other. There's just no way around it. There's also the free wvLatex program that you can try. I don't know if it runs on Windows. See here: http://wvware.sourceforge.net/ But if it doesn't, that's a good reason to dual boot Linux. ;-) rh
Re: Strategies for Writing Co-operation with Non-LyX Users?
Thanks, Jurgen. Your comments were helpful. As for the inserted comments (item #4), sometimes one needs to insert comments for one's colleagues while editing a text. I tried to insert a Lyx note or a comment, and although they showed up in the Lyx file, they did not show up in the output file, even though I checked the Show changes in output. By the way, checking this option produced many errors in going to pdflatex, but worked fine (with the exception of the comments) when producing a dvi file, which could then be pdf'ed without problems. EK Jürgen Spitzmüller wrote: Ehud Kaplan wrote: 1. It is difficult to tell which is newly inserted text vs deleted text-- it is all blue on my screen This is a bug we are aware of. It will be fixed in the next release (1.6.2), most likely. 2. There is no tracking of who changed what, as is nicely done in MS WORD This is supposed to work. LyX tracks the author name, and as of 1.6.0, you can allocate different colors to different authors (which is actually the source of the bug mentioned in #1). 3. There are no keyboard shortcuts for accepting/rejecting changes, making the process tedious you can allocate shortcuts in the preferences dialog (EditShortcuts). The corresponding functions are change-accept, change-reject and change-next. 4. Inserting notes into the text is not as nicely done as it used to be in previous version of MS WORD-- it is simply hard to see where the notes are, or what is their contents. Could you elaborate a bit? Jürgen -- Ehud Kaplan, Ph.D. Jules and Doris Stein Research to Prevent Blindness Professor Director, The laboratory of Visual Neuroscience Departments of Neuroscience, Ophthalmology, Structural Chemical Biology, The Mount Sinai School of Medicine One Gustave Levy Place NY, NY, 10029
Re: MS Word to LyX
Richard Heck rgh...@... writes: OpenOffice will export LaTeX. You should be able to load your Word docs there, and then export. Might be no worse. You WILL have to do hand editing, one way or the other. There's just no way around it. I tried to install open office (neo office). It does convert to LaTeX. But the issue is that it seems the philosophy in the OO converter is to make the typeset LaTeX document look like the OO document, rather than conveying the meaning/contents of the document -- WYSIWYG rather than WYSIWYM. The results is terrible, terrible LaTeX code. Maybe there is some option to set so that it's converted to nice latex code, that does not try to reproduce the formatting of the OO document? At least the commercial programs produce LaTeX code that reproduce the meaning of the original document fairly.
Re: Strategies for Writing Co-operation with Non-LyX Users?
On Jan 26, 2009, at 1:07 PM, Ehud Kaplan wrote: Thanks, Jurgen. Your comments were helpful. As for the inserted comments (item #4), sometimes one needs to insert comments for one's colleagues while editing a text. I tried to insert a Lyx note or a comment, and although they showed up in the Lyx file, they did not show up in the output file, even though I checked the Show changes in output. Convert it to a Greyed Out comment by right-clicking on the note box. This will show up in output. The Note only shows up in LyX...
Re: Strategies for Writing Co-operation with Non-LyX Users?
Thanks. This does not seem the most intuitive menu entry I suppose I must read the manual! James C. Sutherland wrote: On Jan 26, 2009, at 1:07 PM, Ehud Kaplan wrote: Thanks, Jurgen. Your comments were helpful. As for the inserted comments (item #4), sometimes one needs to insert comments for one's colleagues while editing a text. I tried to insert a Lyx note or a comment, and although they showed up in the Lyx file, they did not show up in the output file, even though I checked the Show changes in output. Convert it to a Greyed Out comment by right-clicking on the note box. This will show up in output. The Note only shows up in LyX... -- Ehud Kaplan, Ph.D. Jules and Doris Stein Research to Prevent Blindness Professor Director, The laboratory of Visual Neuroscience Departments of Neuroscience, Ophthalmology, Structural Chemical Biology, The Mount Sinai School of Medicine One Gustave Levy Place NY, NY, 10029
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Since writing below I have found a work-around, which I hope will continue working on the biblio files: In BibDesk, convert the bibtex database into bibtex. This seems a little daft at first, but I picked this up on reading that on importing and exporting BibDesk converts umlauts, etc. into the LaTeX equivalent. My guess was that by converting to the same format, would have the effect of standardising the umlauts, etc. I have a suspicion that the software I used to gather the references doesn't know the LaTeX encodings for the umlauts, etc. and just left them in their original UniCode. For developers: Is there any sense in having bibtex convert files in the same way as I have (i.e. from bibtex to bibtex) to standardise the files before LyX takes them up? While redundant for many users, it might catch non-standard things and may make this just work, at least for the situation I have. This may also provide a means of testing that the bibliography is in a standard (or understandable) format and report a meaningful error if it's not. (The current error messages are a tad too geeky for non-programmers, etc.) I haven't time to do let them know right now, but BibDesk ideally should let users know that on loading a database, it had to convert some stuff, i.e. that the internal version of it is tainted with respect to the disk version, so that users are warned/asked to save the conversions, etc.--? Perhaps even insist that they do it immediately after loading it. You're welcome to read the rest, I might as well let it stand in case it's of use to anyone, but what's above it the nutshell take. Grant Grant Jacobs wrote: One thing that bothers me about this being a BibTeX issue, is that BibDesk writes these characters to RTF just fine. (It would tempt me to think that there might a work-around that gets this directly from BibDesk, avoiding BibTex.) 0) You have not understood the concept behind BibDesk - it's only a sophisticated frontend to the database (bib) file that bibtex uses. Try to read up on this. Actually I do understand it ;-) No offence, but if you knew the effort I have put into this, telling me to Try to read up on this is a bit rich! :-) 1) You can enter the TeX-replacements for the special characters in the bib-file (or in Bibdesk) instead of the unicode characters. See http://www.bibtex.org/SpecialSymbols/ Since you say it is mostly for European author names, this should be enough. Doing this manually is not a practical option. [Resolved above, though] 2) Make sure you use a recent version of BibDesk. Also, TeXLive-2008 and LyX 1.6.1 won't hurt. LyX is 1.6.1 as the subject line says, BibDesk is the latest version. Tex will be a little older (I have TexLive-2008 on disk, but I wanted to leave installation of that until later, as I didn't wanted a messed-up installation delaying me even more!) HTH, In an indirect way: it lead to seeing the comment about BiBDesk converting on importing and exporting, etc. in a doc on the web. Long story. Konrad P.S. Forget the path via RTF! OK. Bit surprised though: there is an exporter for it in BibDesk and an importer in LyX, so in principle it should work, right? (But obviously not for some reason...!) At 3:32 PM +0100 26/1/09, Konrad Hofbauer wrote: Make sure you have 'Unicode to TeX Conversion' enabled in BibDesk's 'Files' Preferences !!! Obviously :-) (I've already been all over the Preferences of both programs looking for likely things, googling, etc. I make a point of trying hard myself before resorting to forums. Among others things, the back-and-forth in forums takes a lot of time. I've put literally hours into this. I hope you can my perspective: I really expected this to just work as BibDesk must be used by most LyX users and UniCode is so universal now... and all the rest. Fair point about bibtex's age, though. [See my comment about the file format though, para. 3 above.]) Grant -- --- Grant Jacobs Ph.D. BioinfoTools ph. +64 3 478 0095 (office, after 10am) PO Box 6129, or +64 27 601 5917 (mobile) Dunedin, gjac...@bioinfotools.com NEW ZEALAND. Bioinformatics tools: deriving knowledge from biological data Bioinformatics tools - software development - consulting - training 15 years experience in bioinformatics ready to solve your problem Check out the website for more details: http://www.bioinfotools.com The information contained in this mail message is confidential and may be legally privileged. Readers of this message who are not the intended recipient are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immed- iately and destroy the original message.
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Grant Jacobs wrote: I have a suspicion that the software I used to gather the references doesn't know the LaTeX encodings for the umlauts, etc. and just left them in their original UniCode. Ah ... I assumed your bibtex files initially came from BibDesk. Maybe it's time to switch to a reference manager with better Latex-support. (Do you hear me shouting 'BibDesk' ? ;) ) For developers: I'm not, nevertheless I throw in my 2 cents... ;) Is there any sense in having bibtex convert files in the same way as I have (i.e. from bibtex to bibtex) to standardise the files before LyX takes them up? While redundant for many users, it might catch non-standard things and may make this just work, at least for the situation I have. This is probably something that bibtex should take care of, not LyX. If you know of an existing script or library that already does that, it might be considered in LyX. This may also provide a means of testing that the bibliography is in a standard (or understandable) format and report a meaningful error if it's not. (The current error messages are a tad too geeky for non-programmers, etc.) Unfortunately, one could say that about almost every Latex error message. :( Actually I do understand it ;-) No offence, but if you knew the effort I have put into this, telling me to Try to read up on this is a bit rich! :-) No offense here either, I just did not get why you would want to _export_ from BibDesk, if BibDesk's native file format is exactly what LyXbibtex want (and works). P.S. Forget the path via RTF! OK. Bit surprised though: there is an exporter for it in BibDesk and an importer in LyX, so in principle it should work, right? The LyX-importer (if you have the right external tool installed) is for text, only, and not for references/citations. I've put literally hours into this. This happens ... (same here on other issues, usually LaTeX-limitations). I hope you can my perspective: I really expected this to just work as BibDesk must be used by most LyX users and UniCode is so universal now... and all the rest. At least, now you know that simply saving in BibDesk solves the problem. Fixed for once and forever. :) /Konrad
Re: MS Word to LyX
Anders Host-Madsen wrote: I tried to install open office (neo office). It does convert to LaTeX. But the issue is that it seems the philosophy in the OO converter is to make the typeset LaTeX document look like the OO document, rather than conveying the meaning/contents of the document -- WYSIWYG rather than WYSIWYM. The results is terrible, terrible LaTeX code. Maybe there is some option to set so that it's converted to nice latex code, that does not try to reproduce the formatting of the OO document? At least the commercial programs produce LaTeX code that reproduce the meaning of the original document fairly. To get all the power of the openoffice - latex converter you have to use it from the command line and tweak configuration files. Google for writer2latex. Nevertheless, I doubt that writer2latex converts very well equations in MsWord. Maybe you could try to export your equations to MathML and then convert the MathML to LaTeX. I do not know if MsWord can export to MathML. Cheers, Charles
How to shrink the size of math formulas?
Hello, is there a way of shrinking the overall size of a math formula, either displayed or inline? I am trying to stay within a page limit for a paper, and I could do with shrinking the formulas (as they would appear in the final output - I don't care too much what size they look in Lyx - so if i have to hack some Tex that is ok). I guess the same question applies to code (Lyx-Code) cheers
Re: Strategies for Writing Co-operation with Non-LyX Users?
Ehud Kaplan wrote:
Thanks, Jurgen. Your comments were helpful.
As for the inserted comments (item #4), sometimes one needs to insert
comments for one's colleagues while editing a text.
I tried to insert a Lyx note or a comment, and although they showed up
in the Lyx file, they did not show up in the output file, even though I
checked the Show changes in output.
I see. LyX notes are actually not designed for that kind of task. As James
wrote, we have greyed out notes, although this is not everyone's taste.
Attached are two alternatives:
1. a module that lets you insert todo notes, as seen here:
ftp://dante.ctan.org/tex-
archive/macros/latex/contrib/todonotes/todonotesexample.pdf
You need the todonotes package for this
2. a module that lets you insert real PDF annotations (that display in Adobe
reader, but not in some other PDF viewers). This uses the pdfcomment package.
These modules need to be saved in your local LyX directory (in the layouts
folder), then they can be selected in DocumentModules after LyX has been
reconfigures (EditReconfigure).
By the way, checking this option produced many errors in going to
pdflatex, but worked fine (with the exception of the comments) when
producing a dvi file, which could then be pdf'ed without problems.
Do you have an example file for this? We have reworked the PDF output of
change tracking markup for 1.6.2, and this is likely to be much more robust.
Jürgen
#\DeclareLyXModule{Todo-notes}
#DescriptionBegin
#Displays the LyX notes in the output. A list of todo notes can be produced
#by inserting \listoftodos in ERT.
#DescriptionEnd
# Author: Juergen Spitzmueller sp...@lyx.org
Format 11
Preamble
\RequirePackage{todonotes}
EndPreamble
InsetLayout Note:Comment
LabelString comment/todo
LatexType command
LatexName todo
MultiPar false
End
#\DeclareLyXModule{PDF comments}
#DescriptionBegin
#Inserts annotations to the PDF file.
#DescriptionEnd
# Author: Juergen Spitzmueller sp...@lyx.org
Format 11
InsetLayout PDF-Annotation
LyXType custom
LabelString PDF
LatexType command
LatexName pdfcomment
Decorationclassic
LabelFont
Color magenta
SizeSmall
EndFont
MultiPar false
OptionalArgs 1
Preamble
\RequirePackage{pdfcomment}
EndPreamble
End
InsetLayout PDF-Margin
LyXType custom
LabelString PDF (margin)
LatexType command
Decorationclassic
LatexName pdfmargincomment
LabelFont
Color green
SizeSmall
EndFont
MultiPar false
OptionalArgs 1
Preamble
\RequirePackage{pdfcomment}
EndPreamble
End
Re: Strategies for Writing Co-operation with Non-LyX Users?
Jürgen Spitzmüller wrote:
1. a module that lets you insert todo notes, as seen here:
ftp://dante.ctan.org/tex-
archive/macros/latex/contrib/todonotes/todonotesexample.pdf
You need the todonotes package for this
Try the attached instead.
Jürgen
#\DeclareLyXModule{TODO notes}
#DescriptionBegin
#Inserts TODO-notes in the output. A list of todo notes can be produced
#by inserting \listoftodos in ERT.
#DescriptionEnd
# Author: Juergen Spitzmueller sp...@lyx.org
Format 11
InsetLayout TODO
LyXType custom
LabelString TODO
LatexType command
LatexName todo
Decorationclassic
LabelFont
Color magenta
SizeSmall
EndFont
MultiPar false
OptionalArgs 1
Preamble
\RequirePackage{todonotes}
EndPreamble
End
LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Having *finally* managed to persuade LyX to generate bibliographies at all, I now find that LyX seemingly cannot handle characters with diacritic marks (i.e. UniCode) in .bib files when exporting them to PDF, etc. Unfortunately this really has to work for me as it will be the case with a very large number of European, etc., author's names and so on. If this is "how it is meant to be" or "the way it is", *please* add some information to this effect in the tutorial and user guide or somewhere prominent, so that users needing this can "quit early" and look for another another solution. On the other hand, the "internationalisation" section of the "features" blurb mentions "unicode compliance" in passing... Does anyone have any remedies for this? Preferably simple: I am all out of time to do more of the kind of fiddling I have had to do so far. I've tried setting the language encoding to utf8, but it generates an empty document and complains that 'utf8.def' isn't present. Setting language encoding to 'Unicode (XeTeX) generates output (without "crashing" during the conversion), but the characters aren't correct. I can't generate plain text (ps2ascii) at all. Generating PostScript, generates output but also gets the characters wrong. And on it goes, randomly trying this, that and the other in vain attempts to make something work...! :-( Is there some version or other of the main LaTeX installation that I am "supposed" to be using? (And if that's the case, shouldn't LyX be check that it's a sane choice, etc?) Grant Jacobs -- --- Grant Jacobs Ph.D. BioinfoTools ph. +64 3 478 0095 (office, after 10am) PO Box 6129, or +64 27 601 5917 (mobile) Dunedin, gjac...@bioinfotools.com NEW ZEALAND. Bioinformatics tools: deriving knowledge from biological data Bioinformatics tools - software development - consulting - training 15 years experience in bioinformatics ready to solve your problem Check out the website for more details: http://www.bioinfotools.com The information contained in this mail message is confidential and may be legally privileged. Readers of this message who are not the intended recipient are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immed- iately and destroy the original message. This applies also to any attached documents.
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Grant Jacobs wrote: > Having *finally* managed to persuade LyX to generate bibliographies > at all, I now find that LyX seemingly cannot handle characters with > diacritic marks (i.e. UniCode) in .bib files when exporting them to > PDF, etc. Unfortunately this really has to work for me as it will be > the case with a very large number of European, etc., author's names > and so on. This is a BibTeX limitation. BibTeX is an old beast, the most recent release still predates the advent of unicode. Fact is that bibtex cannot deal with unicode (or any other multibyte encoding, for that matter) at all. There's noting that LyX can do here. You need to use another encoding for the bib file, such as latin1, and insert the non-supported characters by means of the respective macros. A decent bib file editor, such as JabRef or pybliographic, should actually handle this for you. > If this is "how it is meant to be" or "the way it is", *please* add > some information to this effect in the tutorial and user guide or > somewhere prominent, so that users needing this can "quit early" and > look for another another solution. You are right, this needs to be documented in the UserGuide, sec. 6.5.2. CC:ing the documentation list. Jürgen PS.: please open a new thread for new topics.
Re: LyX 1.6.1 on OS X unable to handle diacritic marks in .bib files
Jürgen Spitzmüller wrote: > You need to use another encoding for the bib file, such as latin1, and > insert the non-supported characters by means of the respective macros. Also look here for some further information: http://wiki.lyx.org/BibTeX/Tips#toc1 Jürgen
Re: Strategies for Writing Co-operation with Non-LyX Users?
Hello fellow humanists! What a luck! "Only" one of your colleagues use LaTeX and "some" use Oo? "Only" the editors use LaTeX? In my area and field (italian history of music), "World" and "Word" mean the same thing, and everything which happens to us, little insignificant mortal scholars, is because of the will of the Big Bill, who rescued our souls just a bunch of years ago out of the dark fogs of the ink and paper era and tought us the principle of the MS enlightment. My supervisor, known in our field for his above-average informatical knowledge with databases and so on, once called "exotic" some of my documents printed with Oo. I'm just starting publishing things in small, medium-size and large publications. Everywhere, when asked "what if LaTeX?", after a "what what?" they always told me: "please send us printed paper and .DOC in CD (!) or email if possible". There's no way to break the entire chain of MS rule, other than go straight, ignoring it. With my supervisor now I got back to paper: I print out my drafts, hand to him, get back the red pen corrections and type them into my LyX document. I love this: past and future altogether, but far away from the flattened MS present. But you were talking about Strategies. It's quite hard for me to have my docs converted to OO (something not working in my LyX install) so I can't help you with technical things. The best strategy is to spread the LyX verb. If you only convince one person, you'll be two instead of one, which is to double the effort. This is a long-term strategy. Another long-long-term strategy is to promote (and partecipate to) the developmente of LyX (and related sw) in a simplified and humanists-friendly (rather non-scientific friendly) direction, which is IMHO one of the primary goals of LyX. When I will able to show my colleagues some LyX versions with BibLaTeX (for humanist bibliographies) fully working, perfect Lilypond (a LaTeX-like music typesetter) integration without having to tweak code and so on, chances of victory will be for LyX. Till that day, no way. Peter was talking about google docs. document-sharing is IMHO the weakest battlefront for LyX (and for a lot of free software and projects), and the final battle will be fought there, but this is future, and it's out of this post. Still curious to hear some more opinions and experiences. Piero
Re: \usepackage[full]{textcomp} - where to set?
> > where can I tell Lyx once forever that it shall load the "textcomp"
> > package always with the option "full", because this is required by
> > certain other packages?
>
> You can pass the "full" option to Document>Settings>Class Options.
> Class options will be passed down to the packages by LaTeX.
Apparently not:
LaTeX Error: Option clash for package textcomp.
...textcomp\RequirePackage[full]{textcomp}\fi
The package textcomp has already been loaded with options:
[]
There has now been an attempt to load it with options
[full]
Adding the global options:
,full
to your \documentclass declaration may fix this.
Try typingto proceed.
THis was the start of the source:
% Quellcode vorschauen
%% LyX 1.6.1 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[10pt,ngerman,full]{scrartcl}
\usepackage[osf]{mathpazo}
\renewcommand{\sfdefault}{cmbr}
\renewcommand{\ttdefault}{lmtt}
\renewcommand{\familydefault}{\sfdefault}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{geometry}
\geometry
{verbose,letterpaper,tmargin=2cm,bmargin=2cm,lmargin=2cm,rmargin=2cm}
\pagestyle{empty} \usepackage{array}
\usepackage{textcomp}
\makeatletter
Sincerely,
Wolfgang
RE: Re: Strategies for Writing Co-operation with Non-LyX Users?
> Still curious to hear some more opinions and experiences. I'm succesfully spreading the word of LyX to my supervisors and colleagues. I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. > Piero Vincent
Re: \usepackage[full]{textcomp} - where to set?
Wolfgang Keller wrote:
> > You can pass the "full" option to Document>Settings>Class Options.
> > Class options will be passed down to the packages by LaTeX.
>
> Apparently not:
>
> LaTeX Error: Option clash for package textcomp.
>
> ...textcomp\RequirePackage[full]{textcomp}\fi
could you post a small example file? I'm unable to reproduce the problem.
Jürgen
Re: \usepackage[full]{textcomp} - where to set?
> could you post a small example file? I'm unable to reproduce the
> problem.
I've narrowed the source of the problem down to the use of a symbol I
use: \textopenbullet{}, together with the kpfonts.
The workaround is to use the ifsym package.
Try this:
% Quellcode vorschauen
%% LyX 1.6.1 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[10pt,ngerman,full]{scrartcl}
\usepackage[osf]{mathpazo}
\renewcommand{\sfdefault}{cmbr}
\renewcommand{\ttdefault}{lmtt}
\renewcommand{\familydefault}{\sfdefault}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\usepackage{geometry}
\geometry
{verbose,letterpaper,tmargin=2cm,bmargin=2cm,lmargin=2cm,rmargin=2cm}
\pagestyle{empty} \usepackage{textcomp}
%% User specified LaTeX commands.
\usepackage{color}
\definecolor{grey}{gray}{0.3}
\usepackage{kpfonts}
%\renewcommand{\rmdefault}{uop}
\makeatother
\usepackage{babel}
\usepackage{babel}
\begin{document}
\textopenbullet{}
\end{document}
Re: Strategies for Writing Co-operation with Non-LyX Users?
Vincent van Ravesteijn - TNW wrote: Still curious to hear some more opinions and experiences. I'm succesfully spreading the word of LyX to my supervisors and colleagues. I hope LyX will soon have some new features that will ease this collaboration. As we won't be able to implement everything, it would be nice to know which feature would satisfy most users. It'd be nice to have a list of things people need for collaboration. I guess we've probably had that discussion before, but I've never thought it had a very good outcome. Richard
Re: Strategies for Writing Co-operation with Non-LyX Users?
I don't have a whole lot to add to what other people have said. The difficulties in using LyX for cross-program collaboration will depend very much upon your field. I wrote a paper a while back with someone who was using Word, or maybe even an old version of WordPerfect, but it was relatively painless, because there was almost no technical material in it. So I was able to export to RTF, he could do what he wanted and send it back marked with his changes in blue, and I could put those changes back into LyX. For our next paper, though, I was able to get him to use LyX. I've also managed to get several of my students using LyX. It takes time for them to adjust to a new way of working. But once they adjust, they are all very glad that they have. The problem, of course, is that people tend not to realize that there even could be another way of working, or that it might have real benefits. You don't realize until you stop using Word, etc, how much the program gets in the way of just writing. It sounds almost crazy, but it's true. Richard
