Re: instructions for upgrade from LyX 1.6.7 to 2.0 beta 1?
Am 11.11.2010 um 07:42 schrieb Justin Wood: > Hi gang. As LyX 2.0 beta 1 is now released, I thought I'd make the switch > over (OS X 10.6). Hi Justin, good to have brave users who are going to test beta release of LyX 2.0. But it's beta and not clear exactly when the release will happen. So I hope, you're using it with copies of your important documents. > It installs and runs fine, but as best I can tell there is no automated > import of LyX 1.6.7 settings. Yes, the automated import is on the agenda only. The needed scripts are unfinished or at least the integration of them. > Are there any (draft) instructions available for walking the upgrade path? > Are there any backwards compatibility issues or conflicts to watch out for, > or can the existing LyX-1.6 user directory pretty much just be copied across? Yes, there are backwards compatibility issues. I never did copy the user directory and the plan is to make the transition with the help of converter scripts. > Ditto for migrating actual documents. That is done automatically and should work. After saving the documents they'll have the new 2.0 format. In the near future LyX 1.6 will be able to read LyX 2.0 documents. That's not the case already. So, as said above, you should start with copies of your documents since there is no easy way to go back. > Thanks! And very much looking forward to using this shiny new creature. Have fun. Stephan
instructions for upgrade from LyX 1.6.7 to 2.0 beta 1?
Hi gang. As LyX 2.0 beta 1 is now released, I thought I'd make the switch over (OS X 10.6). It installs and runs fine, but as best I can tell there is no automated import of LyX 1.6.7 settings. Are there any (draft) instructions available for walking the upgrade path? Are there any backwards compatibility issues or conflicts to watch out for, or can the existing LyX-1.6 user directory pretty much just be copied across? Ditto for migrating actual documents. Thanks! And very much looking forward to using this shiny new creature.
Re: Fwd: Automating sequence of beamer exports to pdf
On 11/10/2010 06:52 PM, Venable wrote: However, my thought was that it would be simpler to do this in the .tex file that LyX generates, since these (I believe) are simpler files. So the idea would be to have the script export from LyX to tex, and then do something similar to what Richard's perl programs do to change the preamble in the tex file. The downside to this is that you then have to handle all the compilation manually, whereas LyX figures out for you how many times you have to run LaTeX, etc, etc. The changes to the LyX file won't be much more complicated than to a tex file. Richard
Re: where is the shortcut "CTRL+F" defined?
zhao_yunsong 163.com> writes: > > but this shortcut was binded to > \frac, I can not find where is this binded. The only place I can see where this occurs is in sciword.bind. Check Tools > Preferences > Editing > Shortcuts and look in the "Bind file" field. Is the bind file sciword? If so, try switching it to a different one (I use cua). /Paul
Cherokee & CTAN: directory: /tex-archive/macros/xetex/latex/polyglossia
I would like to use your package for Cherokee, but don't see that as a supported language. Is there a way to specify a generic UNICODE-RANGE -> FONT(s) mapping? This way any language could be supported without needing explicit named support. firmicus ατ gmx δοτ net http://www.ctan.org/tex-archive/macros/xetex/latex/polyglossia/
Fwd: Automating sequence of beamer exports to pdf
>>
>> First, I was thinking about a variant to the procedure Richard
>> developed, in which the changes were made in tex files rather than the
>> LyX file. The virtue of this would be that, since I work in LyX, there
>> would be fewer files propagated and I would be less likely to edit the
>> wrong one in the future. So what I had in mind was something like the
>> following:
>>
>> a. Work on the "slides" version in LyX, since as Richard points out
>> this is the baseline for the other two.
>>
>> b. Export this to tex, make the "handout" and "notes" changes directly
>> in tex, and pdflatex all three versions from the command line or
>> within the script.
>
> This works as long as what "makes changes" is a script and not your fingers on
> a keyboard. Well, I think this works.
Right, I should have been clearer. What I meant was that everything in
(b) would happen from a script.
> I don't know whether the elimination of
> Notes in the output happens at the LyX level or the LaTeX level. If the LaTeX
> level, then I'd imagine your plan works perfectly.
>
Whether or not notes appear is determined by the presence (or absence)
of a line in the preamble of the tex file.
If you want notes, you add
\setbeameroption{show notes}
If not, you erase this or comment it out.
This can be done in LyX by going to Document - Settings - LaTeX
Preamble and then place the line in the preamble. I usually put it
right under the \usetheme{} line but I'm not sure if this is required.
However, my thought was that it would be simpler to do this in the
.tex file that LyX generates, since these (I believe) are simpler
files. So the idea would be to have the script export from LyX to tex,
and then do something similar to what Richard's perl programs do to
change the preamble in the tex file.
Similarly for creating handouts - a perl script similar to Richard's
would change the purpose of the document from beamer (slides) to
handout. This could happen in LyX but it seems to me that it would be
more straightforward in tex.
Re: Foreign Language Support + Font Setup / fontwrap package for XeLaTex ?
Could provide an actual sample/step-by-step on the wiki and/or posted here?
I would much prefer to use the standard fonts for everything except Cherokee
UNICODE, at which point I need to use:
- Normal Cherokee: Digohweli
- Bold Cherokee: Aboriginal Serif or fake bold Digohweli
- Italic Cherokee: Aboriginal Sans or a fake italic Dighweli
On Wed, Nov 10, 2010 at 3:40 AM, Guenter Milde wrote:
> On 2010-11-10, Michael Joyner wrote:
> > On Tue, Nov 9, 2010 at 9:02 AM, Walter wrote:
>
> >> IMHO, the best possible solution for documents with heavy use of
> >> multilingual text would seem to be a combination of this type of
> >> solution (character styles with font associations), and automatic
> >> unicode block-based input classification. This would enable LyX to
> >> automatically change the default, available and/or recommended styles
> >> based on what kind of character was input.
>
> > What is needed is something like
> > http://www.ctan.org/tex-archive/macros/xetex/latex/fontwrap/ so that
> > fonts are *autoselected* based on UNICODE range unless otherwise
> > overridden.
>
> In my view, the better approch is autoselection of the the *language*
> (which you should set anyway for proper hyphenation and typography):
>
> * have a GUI option for secondary languages and associated Unicode-range
> or script,
>
> * let LyX change the text language based on the used script.
>
> Of course, this auto-language feature only works for languages using
> different scripts like English and Russian, but not English and German.
> However, in the second case the need for a font switch is less likely.
>
> Then, the language package (babel or polyglossia) can select the
> appropriate font.
>
> BTW: using the language package to select the font is already possible
> right now with some LaTeX-preamble code.
>
> All you have to do is setting the text language (it helps to bind
> often used languages to a key-combo).
>
> With XeTeX, disable "babel" in Tools>Settings>Language and follow the
> advise in polyglossia.pdf:
>
> With polyglossia it is possible to associate a specific font with any
> script or language that occurs in the document. That font should always
> be defined as \⟨script⟩font or \⟨language⟩font. For instance, if the
> default roman font defined by \setromanfont does not support Greek, then
> one can define the font used to display Greek with:
> \newfontfamily\greekfont[⟨options⟩]{⟨font⟩}.
> See the fontspec documentation for more information.
>
> Whenever a new language is activated, polyglossia will first check
> whether a font has been defined for that language or – for languages in
> non-Latin scripts – for the script it uses. If it is not defined, it
> will use the currently active font and will attempt to turn on the
> appropriate OpenType tags for the script and language used, in case
> these are available in the font, by means of fontspec’s
> \addfontfeature. If the current font does not appear to support the
> script of that language, an error message is displayed.
>
>
> Günter
>
>
--
---
- Learn to speak Cherokee: http://www.cherokeelessons.com/
- Cherokee Language Help BBS/Chat:
http://www.cherokeelessons.com/phpBB3/viewforum.php?f=6
- Cherokee Lessons PDF made with: http://www.lyx.org/
Re: Automating sequence of beamer exports to pdf
On Wednesday 10 November 2010 14:29:06 Venable wrote: > Thank you both for your suggestions. I will do my best to implement > them in spite of my meager programming skills. > > I have a couple of follow-up questions: > > First, I was thinking about a variant to the procedure Richard > developed, in which the changes were made in tex files rather than the > LyX file. The virtue of this would be that, since I work in LyX, there > would be fewer files propagated and I would be less likely to edit the > wrong one in the future. So what I had in mind was something like the > following: > > a. Work on the "slides" version in LyX, since as Richard points out > this is the baseline for the other two. > > b. Export this to tex, make the "handout" and "notes" changes directly > in tex, and pdflatex all three versions from the command line or > within the script. This works as long as what "makes changes" is a script and not your fingers on a keyboard. Well, I think this works. I don't know whether the elimination of Notes in the output happens at the LyX level or the LaTeX level. If the LaTeX level, then I'd imagine your plan works perfectly. > > Does this seem like a good approach? Any problems I should anticipate? > > Second, is there a way to get either of these approaches to run from a > keyboard shortcut within LyX? (For example, a function key.) I'm now going to put on my flame resistant suit, because what I'm about to say won't be popular on this list... I love LyX. Every book I've written this century has been authored in LyX. My courseware's Instructor Notes are written in LyX. I've contributed monetarily to LyX. To a great extent my business depends on LyX, and I'm eternally grateful. But in my opinion, LyX is the wrong place to use Beamer. In my opinion, LyX just obfuscates and complicates use of beamer. In my opinion, the tool you should use with Beamer is Vim, or Emacs, or Notepad. In my opinion a presentation's LaTeX source is much simpler and self-evident than the same presentation in LyX. The way I do Beamer is do it in LaTeX, and then use a script to convert it to PDF. You could use a similar script to output your three PDFs. See this URL for details: http://www.troubleshooters.com/lpm/201005/201005.htm SteveT Steve Litt Recession Relief Package http://www.recession-relief.US Twitter: http://www.twitter.com/stevelitt
Re: Automating sequence of beamer exports to pdf
Thank you both for your suggestions. I will do my best to implement them in spite of my meager programming skills. I have a couple of follow-up questions: First, I was thinking about a variant to the procedure Richard developed, in which the changes were made in tex files rather than the LyX file. The virtue of this would be that, since I work in LyX, there would be fewer files propagated and I would be less likely to edit the wrong one in the future. So what I had in mind was something like the following: a. Work on the "slides" version in LyX, since as Richard points out this is the baseline for the other two. b. Export this to tex, make the "handout" and "notes" changes directly in tex, and pdflatex all three versions from the command line or within the script. Does this seem like a good approach? Any problems I should anticipate? Second, is there a way to get either of these approaches to run from a keyboard shortcut within LyX? (For example, a function key.) Many thanks again.
Re: ANNOUNCE: LyX version 2.0.0 (beta 1)
On Wed, 10 Nov 2010 17:59:20 +0100 Pavel Sanda wrote: > We hope you will enjoy the result! Admirable... Unpacked, compiled, installed and it worked - just like that. Amazing job! I'll give it a larger workout later, but at first sight, noticed that tables don't seem to scroll around as much as before. Thanks for all the work! John
Re: where is the shortcut "CTRL+F" defined?
On 11/10/2010 10:09 AM, zhao_yunsong wrote: but this shortcut was binded to \frac, I can not find where is this binded. On what platform? ps, is there a tutorial that explans the bind file? No. rh
ANNOUNCE: LyX version 2.0.0 (beta 1)
Pre-release of LyX version 2.0.0 (beta 1) == We are pleased to announce the first public pre-release of LyX 2.0.0. Development moved to the beta phase which basically means we will no more include new features and focus on polishing the current ones. We are thus grateful for any feedback you sent us regarding the bugs you encounter while testing the beta release. Except trying new features this is also good time to check that your favorite old files works with the new release as expected. Please note that this release is for testing purposes only, users are encouraged to use current 1.6 stable release for any serious work. Tarballs can be found at ftp://ftp.lyx.org/pub/lyx/devel/ and binaries should follow soon. LyX 2.0.0 will be culmination of more than two years of hard work and you can find an overview of the new features here: http://wiki.lyx.org/LyX/NewInLyX20 If you think you found a bug in LyX 2.0.0, either e-mail the LyX developers' mailing list (lyx-devel at lists.lyx.org), or open a bug report at http://www.lyx.org/trac/wiki/BugTrackerHome If you have trouble using LyX or have a question, consult the documentation that comes with LyX and http://wiki.lyx.org. If you can't find the answer there, e-mail the LyX users' list (lyx-users at lists.lyx.org). We hope you will enjoy the result! The LyX team. http://www.lyx.org
Re: lyx2pdf (pdflatex) using different version of Miktex
Am 10.11.2010 15:31, schrieb Gert: I have a full version of Miktex 2.5 installed. MiKTeX 2.5 is no longer supported (since 2 years or so) by the MiKkTeX developers and thus also not by the LyX for Windows installers. You need at least MiKTeX 2.7. Note that you must uninstall 2.5 before, also check the registry that there are no leftovers from MiKTeX before installing 2.9 (2.5 had some bugs in this respect). I propose to do the following: - uninstall MikTeX 2.5 _completely_ - uninstall LyX _completely_ - open an Internet connection - install LyX 1.6.7 using the complete version of this installer: http://wiki.lyx.org/Windows/LyXWinInstaller This will automatically also install MiKTeX and configures it for LyX (installs all LaTeX-packages LyX supports). Will lyx2pdf run faster if I use Miktex basic install, which is much smaller. What do you mean with lyx2pdf? I don't know such a program. To generate PDF LyX uses the program pdflatex (or other programs in combination). All programs have the same speed because no matter how many LaTeX-packages are installed, only the ones used by a document are procesed. regards Uwe
Writer2LaTeX integration with LyX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I am in contact with Henrik Just, the developer of Writer2LaTeX, concerning implementation of comments and possibly track changes into the export from odt format to LaTeX. As I am using LyX, the second step is the import into LyX, and the import should be working fine as well. So the question he asked (see below our conversation) how LyX imports track changes. As I do not know the internals of LyX, I am posting the question here. I know that LyX has track changes, but I do not know if there is any mechanism to import them from a different format. If there is not, I think this would be a brilliant functionality to incorporate, especially in the light of co-operation with doc users: One could export the document to odt, convert it to doc an send it to them. They could use track changes and comments in the usual way, and via ooffice to convert the doc to an odt, Writer2LaTeX could be used to import the document including the track changes and comment into LyX. This functionality would bring us a huge step closer to simplifying the working together with non-LyX / LaTeX users and therefore make LyX much more interesting for the yet unconverted. So - can somebody shed some light on Hendrik's question, if and in which form LyX imports track change information? And if it does not - would there be somebody interested from the LyX side to bring this aspect forward? Cheers, Rainer P.S: at this URL, you can find the initial discussion which led to the question and the relevant mails: https://sourceforge.net/projects/writer2latex/forums/forum/919908/topic/3917061/index/page/1 2010-11-01 15:20:21 SAST Hi Rainer Of course author and date information should be added to comments, this change just made it into version 1.1.5, which is released today. It's already possible to configure the export of notes, for example w2l -notes marginpar document.odt to export as a marginpar. For details, see http://writer2latex.sourceforge.net/doc1.2/user-manual14.html#toc32 I didn't plan to convert track changes, but of course it would be possible. Can you give an example why this would be useful? Best regards Henrik 2010-11-05 23:47:34 SAST Hi Henrik Thanks for the update concerning the notes - that is really perfect (I like the marginpar and pdfannotation). Thanks a lot for that. Concerning track changes: I am using LyX for my writing, but (unfortunately) work together with users preferring word. Therefore my workflow is to export to odt, open on OO, save as doc --- get comments and track changes --- open in OO, and transcribe the changes into the original LyX document. If the export of track changes would work, I could Open the document in OO abd save as .odt, import into LyX (using w2l) and keep the track changes. This would be quite nice, because I guess I could convince my co-workers to use OO, but not LyX / LaTeX. Hope this clarifies my suggestion and gives a usefull usage example, Cheers, Rainer 2010-11-10 17:28:51 SAST Hi Rainer That's an interesting idea. I wonder in which form LyX will import track changes information? Best regards Henrik - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Natural Sciences Building Office Suite 2039 Stellenbosch University Main Campus, Merriman Avenue Stellenbosch South Africa Tel:+33 - (0)9 53 10 27 44 Cell: +27 - (0)8 39 47 90 42 Fax (SA): +27 - (0)8 65 16 27 82 Fax (D) : +49 - (0)3 21 21 25 22 44 Fax (FR): +33 - (0)9 58 10 27 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzavbEACgkQoYgNqgF2egpTKACePFTKqRiBxQSZxbhqO4U7YyXT dkgAoInIeN643G0E5L0cxRMRzYZYlyXx =xjYI -END PGP SIGNATURE-
Re: when supporting Sweave out of the box?
Le 10/11/2010 00:40, Paolo Cavatore a écrit : Any update about Sweave’s out of the box support? It is on track for 2.0. In upcoming 2.0 beta1 version you will find: - sweave module - automatic configuration of Sweave scripts - ability to find Sweave.sty even when LaTeX cannot - new Chunk layout where one does not need to type Ctrl-Enter to break lines (and correct translation of old documents created in 1.6 with the modules that got distributed) - handling of non-utf8 encodings (although I suspect I just found a bug there) What is missing: - documentation - ability to read files by giving a relative path name (work in progress) - testing. JMarc
lyx2pdf (pdflatex) using different version of Miktex
Hi, I have a full version of Miktex 2.5 installed. The install size is 888MB, and is over 40 000 files. Will lyx2pdf run faster if I use Miktex basic install, which is much smaller. I guess there will be less Latex classes to use, but the compiler probably checks only for the included classes and won't make a difference to the speed the pdf is generated. Any suggestions to increase the speed of the pdf generation (or Latex runs)? Maybe the use of a ramdisk somewhere? Thanks in advance, Gert
Re: where is the shortcut "CTRL+F" defined?
On 11/10/2010 08:42 AM, zhao_yunsong wrote: I want to change this shortcut to "find dialog", but can not find where it is defined. I have cheched all the files in the bind fold. In cua.bind, it is: \bind "C-f" "dialog-show findreplace" You can also change it through Tools>Preferences>Editing>Shortcuts. Richard
where is the shortcut "CTRL+F" defined?
I want to change this shortcut to "find dialog", but can not find where it is defined. I have cheched all the files in the bind fold. 2010-11-10 zhao_yunsong 发件人： Pavel Sanda 发送时间： 2010-11-10 20:25:44 收件人： lyx-users 抄送： 主题： Re: hiding the menu bar Jose Quesada wrote: > I've also added a shortcut to toggle the status bar. > Is there any way I could tell lyx to start up with both menu and status > hidden? i dont think so. pavel .
Re: Latex error
On 2010-11-09, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
> Günter, could you set up a document with this comparision and outline exactly
> where polyglossia and babel differ (in terms of what LyX must output/can
> support)?
> I do not have time to dive into the polylossia documentation right now,
> but if your statement is correct, it would be probably easier than I
> thought, and the documentation would help implementing it.
LyX-relevant differences between polyglossia and babel:
Package setup
=
Babel:
\usepackage[,]{babel}
* the language options can be given as global document options or
in the babel call.
* the *last* language becomes the document language.
Polyglossia:
\usepackage{polyglossia}
\setdefaultlanguage{}
\setotherlanguages{}
* The language options must be given in setup macros after loading
polyglossia.
(Earlier versions allowed also language-options with the *first*
language as document language, but this has been deprecated since
long and removed in the current polyglossia version.)
* Possibly, still add the document language (with the "babel name") to
the documentoptions if the "global" check box is checked (for use by
other packages).
Alternatively, disable this check box with XeTeX documents and
teach the users to add the document language "by hand" to the
custom document options.
Languages file
===
Some languages are not (yet) supported by polyglossia:
'af': 'afrikaans',
'de_at':'naustrian',
'de_at_1901': 'austrian',
'fr_ca':'canadien',
'grc_ibycus': 'ibycus', (Greek Ibycus encoding)
'sr-latn': 'serbian script=latin'
'vi': 'vietnam',
Some languages are new or differently named:
# code Polyglossia-name comment
'cop': 'coptic',
'de': 'german', # new spelling (de_1996)
'de_1901': 'ogerman', # old spelling
'dsb': 'lsorbian',
'el_polyton': 'polygreek',
'fa': 'farsi',
'grc': 'ancientgreek',
'hsb': 'usorbian',
'sh-cyrl': 'serbian', # Serbo-Croatian, Cyrillic script
'sh-latn': 'croatian', # Serbo-Croatian, Latin script
'sq': 'albanian',
'sr': 'serbian', # Cyrillic script (sr-cyrl)
'th': 'thai',
The "encoding" field of the "languages" is irrelevant:
always use UTF-8 (xetex)
The "latex options" should be ignored (or replaced by "polyglossia
options")
For use with polyglossia, we could consider either
* a modified copy of "languages"
* a second file only containing the languages with changes overwriting
the "languages" settings.
(shorter, but how can we disable languages then?)
I volunteer to prepare a "languages-polyglossia" (or similar called) file.
Günter
Re: hiding the menu bar
Jose Quesada wrote: > I've also added a shortcut to toggle the status bar. > Is there any way I could tell lyx to start up with both menu and status > hidden? i dont think so. pavel
Re: Fonts in LyX (and LaTeX and TeX)
On 2010-11-09, Rob Oakes wrote: > On Nov 9, 2010, at 1:33 PM, Guenter Milde wrote: >> There is preliminary XeTeX support in the development version. Not >> ready for the masses. > On this point, I have to disagree. > Preliminary as it might be, I've found it very stable. I've been using > LyX 2 for nearly a year, and have transitioned to using XeTeX for > everything. And quite frankly, I have fewer problems with LyX 2 than I > do with LyX 1.6. I am glad to hear this. It also explains your enthusiasm. Nevertheless: a development version is developing and hence can break your documents, stop working 3 hours before the deadline, ... Even if the second-latest snapshot worked fine. And there is a number of confirmed critical bugs that hold up the release of LyX 2. So, while I encourage people to try out LyX 2, I do not recommend it for "critical" work and would not call it "ready for the masses". Günter
Re: Foreign Language Support + Font Setup / fontwrap package for XeLaTex ?
On 2010-11-10, Michael Joyner wrote:
> On Tue, Nov 9, 2010 at 9:02 AM, Walter wrote:
>> IMHO, the best possible solution for documents with heavy use of
>> multilingual text would seem to be a combination of this type of
>> solution (character styles with font associations), and automatic
>> unicode block-based input classification. This would enable LyX to
>> automatically change the default, available and/or recommended styles
>> based on what kind of character was input.
> What is needed is something like
> http://www.ctan.org/tex-archive/macros/xetex/latex/fontwrap/ so that
> fonts are *autoselected* based on UNICODE range unless otherwise
> overridden.
In my view, the better approch is autoselection of the the *language*
(which you should set anyway for proper hyphenation and typography):
* have a GUI option for secondary languages and associated Unicode-range
or script,
* let LyX change the text language based on the used script.
Of course, this auto-language feature only works for languages using
different scripts like English and Russian, but not English and German.
However, in the second case the need for a font switch is less likely.
Then, the language package (babel or polyglossia) can select the
appropriate font.
BTW: using the language package to select the font is already possible
right now with some LaTeX-preamble code.
All you have to do is setting the text language (it helps to bind
often used languages to a key-combo).
With XeTeX, disable "babel" in Tools>Settings>Language and follow the
advise in polyglossia.pdf:
With polyglossia it is possible to associate a specific font with any
script or language that occurs in the document. That font should always
be defined as \⟨script⟩font or \⟨language⟩font. For instance, if the
default roman font defined by \setromanfont does not support Greek, then
one can define the font used to display Greek with:
\newfontfamily\greekfont[⟨options⟩]{⟨font⟩}.
See the fontspec documentation for more information.
Whenever a new language is activated, polyglossia will first check
whether a font has been defined for that language or – for languages in
non-Latin scripts – for the script it uses. If it is not defined, it
will use the currently active font and will attempt to turn on the
appropriate OpenType tags for the script and language used, in case
these are available in the font, by means of fontspec’s
\addfontfeature. If the current font does not appear to support the
script of that language, an error message is displayed.
Günter
