Re: LyX 1.6.0 is released
On 11/11/2008 08:36, Christian Ridderström wrote: On Tue, 11 Nov 2008, Abdelrazak Younes wrote: > You can download LyX 1.6.0 from http://www.lyx.org/Download The download page still had the link for 1.5.6 and the 1.6.0 release notes aren't yet up at the link below I've cleaned up things there. By the way, I've tried to add 1.6.0 to http://wiki.lyx.org/LyX/ReleaseNotes but track says that there is no 1_6_0 tag... and the wiki is deadly slow... Maybe it's a matter of updating the release instructions? No, it's just Jose copying & pasting things without verifying the contents ;-) Since 1.5.0 was released we've changed the backend of the web site, so maybe the instructions need to reflect this. Where are the instructions located? Somewhere in the wiki. Abdel.
Re: Update Turkish Translation
Hi Ibrahim, I can help on Turkish translation, if you wish.. It's been a while I didn't participate lyx.. Ugras On Thu, Nov 6, 2008 at 1:07 AM, H. İbrahim Güngör < [EMAIL PROTECTED]> wrote: > On Thursday 06 November 2008 00:56:03 Pavel Sanda wrote: > > H. ??brahim Güngör wrote: > > > Many fixes and translations are also included. > > > > > > http://sudrap.org/repository/users/igungor/applications/lyx/tr.po > > > > > > Please merge. > > > > its in. next time please start work from the current version in svn tree. > > > > pavel > > thanks for merge, please decide which way a newcomer translator must follow > to > update a po file. README.localizations *said* svn diff tr.po > tr.po.patch, > but then it's changed to "just send whole updated file". > > Regards > > H. İbrahim Güngör >
Re: LyX 1.6.0 is released
On Tue, 11 Nov 2008, Abdelrazak Younes wrote: > You can download LyX 1.6.0 from http://www.lyx.org/Download The download page still had the link for 1.5.6 and the 1.6.0 release notes aren't yet up at the link below I've cleaned up things there. Maybe it's a matter of updating the release instructions? Since 1.5.0 was released we've changed the backend of the web site, so maybe the instructions need to reflect this. Where are the instructions located? /Christian -- Christian Ridderström, +46-8-768 39 44http://www.md.kth.se/~chr
LyX 1.6.0 is released
Public release of LyX version 1.6.0 === We are pleased to announce the release of LyX 1.6.0. LyX is a document processor that encourages an approach to writing based on the structure of your documents, not their appearance. It is released under a Free Software / Open Source license. You can download LyX 1.6.0 from http://www.lyx.org/Download The source can be found at ftp://ftp.lyx.org/pub/lyx/stable and binary packages for the different systems can be found at ftp://ftp.lyx.org/pub/lyx/bin/1.6.0 LyX 1.6.0 is the culmination of 15 months of hard work and you can find an overview of the new features here: http://wiki.lyx.org/LyX/NewInLyX16 We hope you will enjoy the result! Known issues with LyX 1.6 compared to the previous stable release (LyX 1.5.6) can be found at http://wiki.lyx.org/LyX/ReleaseNotes If you think you found a bug in LyX 1.6.0, either e-mail the LyX developers' mailing list (lyx-devel at lists.lyx.org), or open a bug report at http://bugzilla.lyx.org 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). The LyX team. http://www.lyx.org
Re: 1.6.0rc5: lyx2lyx doesn't work
Richard Heck wrote: Paul A. Rubin wrote: I just discovered that LyX 1.6.0rc5 will not import *any* of my older (1.5.x) LyX documents (lyx2lyx always fails). This is on Win XP. Is this something that's known (and hopefully fixed)? I think we had another report like this, and I think it is fixed. Can you try running it from a terminal and let me know what the output is? rh If I run 'python /lyx2lyx ...' in a shell, the test file converts properly and there are no error messages. If I run LyX 1.6.0rc5 from a shell and try to open the test document, I get the following: 'import site' failed; use -v for traceback Traceback (most recent call last): File "C:/Program Files/LyX 1.6.0rc5/bin/../Resources/lyx2lyx/lyx2lyx", line 21 , in import optparse File "C:\Program Files\LyX 1.6.0rc5\bin\lib\optparse.py", line 69, in import sys, os File "C:\Program Files\LyX 1.6.0rc5\bin\lib\os.py", line 63, in import ntpath as path File "C:\Program Files\LyX 1.6.0rc5\bin\lib\ntpath.py", line 11, in import genericpath ImportError: No module named genericpath Error: Conversion script failed HTH, Paul
[solved] Re: LyX 1.6.0 needs to be delayed
Uwe Stöhr schrieb: The MiKTeX update is available fixing the problem. So LyX 1.6.0 for Windows can be published. regards Uwe
Re: [PATCH] Minor Renaming
José Matos wrote: On Monday 10 November 2008 08:33:33 Jean-Marc Lasgouttes wrote: Obviously I would not object. Even if we decide to change these methods later, we'll know at least what we are talking about. +1 Committed, then. rh
Re: Plans to announce LyX release 1.6.0
José Matos wrote: Is lyx-windows-deps-msvc2008.zip the same that is already in ftp.lyx.org/pub/contrib? It's an updated version, you can replace the existing file. Joost
Re: LyX 1.6.0 needs to be delayed
On Saturday 08 November 2008 23:10:48 Uwe Stöhr wrote: > Since yesterday MiKTeX is no longer usable. Its hyphenation pattern > handling is broken and you don't get any output of any TeX-file. > > I informed the MiKTeX developer and report back tomorrow when I hopefully > get some more infos. > > I'm alerting because we ship usually the latest MiKTeX with our Windows > installer and we recommend to update MiKTeX due to the amount of bugfixes > CTAN ships every month. I cannot remember a case like this that a MiKTeX > update breaks it completely but that is another proof of Murphy's law. It is always possible to distribute it with the previous changeset, no? I am preparing the announce in any case. I am populating the ftp server with the different packages. > regards Uwe -- José Abílio
Re: Debian packages will take some more time [was: Re: Plans to announce LyX release 1.6.0]
On Sunday 09 November 2008 17:44:18 Sven Hoexter wrote: > Beside that I've to thank you for your great cooperation. It's always a > pleasure to work with you guys as upstream devs. Thanks. You are welcome. :-) > Sven -- José Abílio
Re: Plans to announce LyX release 1.6.0
On Monday 10 November 2008 00:25:51 Joost Verburg wrote: > José Matos wrote: > > This way we would have binary packages for the users to try when they > > read the announce. Larger projects follow this scheme and I would like to > > give it a try this time. > > I've uploaded the Windows installers and a new dependency package to > http://www.lyx.org/~joost Done. Is lyx-windows-deps-msvc2008.zip the same that is already in ftp.lyx.org/pub/contrib? > Regards, Joost -- José Abílio
Re: [PATCH] Minor Renaming
On Monday 10 November 2008 08:33:33 Jean-Marc Lasgouttes wrote: > Obviously I would not object. Even if we decide to change these methods > later, we'll know at least what we are talking about. +1 > JMarc -- José Abílio
Re: Plans to announce LyX release 1.6.0
On Saturday 08 November 2008 19:04:01 Enrico Forestieri wrote: > I have placed a cygwin binary here: > http://www.lyx.org/~forenr/lyx-1.6.0-cygwin.tar.gz Done. > -- > Enrico -- José Abílio
Re: Plans to announce LyX release 1.6.0
On Saturday 08 November 2008 04:42:15 Bennett Helm wrote: > Could someone upload it to the server? Done. > Thanks. > > Bennett -- José Abílio
Re: Change tracking issues in RC5
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > It is again the spam filter getting mad. I restarted it, and things > seem to be better now. Thanks. I've entered them and added sample files. Unfortunately a few duplicates got created (the site was pretty slow and showed me errors so I retried). I've (hopefully) closed the duplicates.
Re: 1.6.0rc5: lyx2lyx doesn't work
Paul A. Rubin wrote: I just discovered that LyX 1.6.0rc5 will not import *any* of my older (1.5.x) LyX documents (lyx2lyx always fails). This is on Win XP. Is this something that's known (and hopefully fixed)? I think we had another report like this, and I think it is fixed. Can you try running it from a terminal and let me know what the output is? rh
1.6.0rc5: lyx2lyx doesn't work
I just discovered that LyX 1.6.0rc5 will not import *any* of my older (1.5.x) LyX documents (lyx2lyx always fails). This is on Win XP. Is this something that's known (and hopefully fixed)? /Paul
Re: Very small lyx.1 manpage fix
On Mon, Nov 10, 2008 at 03:35:22PM +0100, Jürgen Spitzmüller wrote: > Sven Hoexter wrote: > > Sure. Now diffed against the proper lyx.1in file. > > It's in (1.5.7 and 1.6.1). Thanks. Sven
Re: [Cvslog] r27373 - in /lyx-devel/branches/BRANCH_1_5_X: lib/layouts...
Richard Heck wrote: > OK. Feel free to revert. Done. Jürgen
Re: [Cvslog] r27373 - in /lyx-devel/branches/BRANCH_1_5_X: lib/layouts...
Jürgen Spitzmüller wrote:
rgheck wrote:
Author: rgheck
Date: Mon Nov 10 15:20:49 2008
New Revision: 27373
URL: http://www.lyx.org/trac/changeset/27373
Log:
AMS books can have an abstract. (Problem reported on user list.)
Actually I'd rather not include this in that late stage. At least with the
German translation, this raises some problems ("Abstract" and "Summary" share
the same translation, so we have two entries "Zusammenfassung" in the combo
with AMS book).
Since I do not know about the other languages (and don't have time to check),
I'd rather postpone this fix to 1.6.1 to give the translators the time to
check if there are similar ambiguities.
OK. Feel free to revert.
rh
Re: [Cvslog] r27373 - in /lyx-devel/branches/BRANCH_1_5_X: lib/layouts...
rgheck wrote:
> Author: rgheck
> Date: Mon Nov 10 15:20:49 2008
> New Revision: 27373
>
> URL: http://www.lyx.org/trac/changeset/27373
> Log:
> AMS books can have an abstract. (Problem reported on user list.)
Actually I'd rather not include this in that late stage. At least with the
German translation, this raises some problems ("Abstract" and "Summary" share
the same translation, so we have two entries "Zusammenfassung" in the combo
with AMS book).
Since I do not know about the other languages (and don't have time to check),
I'd rather postpone this fix to 1.6.1 to give the translators the time to
check if there are similar ambiguities.
Jürgen
Re: Very small lyx.1 manpage fix
Sven Hoexter wrote: > > Can you send this as an attachment? > > Sure. Now diffed against the proper lyx.1in file. It's in (1.5.7 and 1.6.1). Jürgen
Re: Plans to announce LyX release 1.6.0
On Mon, Nov 10, 2008 at 7:44 AM, Konrad Hofbauer <[EMAIL PROTECTED]> wrote: > Question: > In the user-directory, the examples-directory is empty. Is this how it is > supposed to be, or should we give the examples the same treatment as the > templates? > > As it is know, it is difficult to know about / find e.g. the > beamerlyxexample. The user has to dig into the Application bundle, which > most of them won't even know that this is possible/exists. > > But also this raises the question for me what distinguishes the examples > from the "specialized manuals" and the default templates. But I vaguely > remember there was a discussion about this not so long ago ... I haven't done anything there because I think we should have a proper solution: when launched, LyX should run a script that does some clean-up operations and creates softlinks from the user's directory to the relevant directories inside the LyX.app bundle. I'm attaching the crude script I came up with as a proof of concept, but it needs a proper developer to do it right. See the thread here: http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg133751.html Bennett lyx-start-script Description: Binary data
Re: Plans to announce LyX release 1.6.0
Bennett Helm wrote: Thanks, Konrad. I've put the packaged version here: http://edisk.fandm.edu/bennett.helm/LyX/LyX-1.6.0-Mac-Universal.dmg Thanks Bennett. One question about the installer (not sure how it is supposed to work): To simulate a new installation from scratch (for a new user), I moved all old 1.6 - user directories as well as the 1.5 user directory out of the way. The mac-installer then creates a new user-directory, with only the templates in there. The rest is put in place (the user directory being populated) at the first start of LyX. Question: In the user-directory, the examples-directory is empty. Is this how it is supposed to be, or should we give the examples the same treatment as the templates? As it is know, it is difficult to know about / find e.g. the beamerlyxexample. The user has to dig into the Application bundle, which most of them won't even know that this is possible/exists. But also this raises the question for me what distinguishes the examples from the "specialized manuals" and the default templates. But I vaguely remember there was a discussion about this not so long ago ... /Konrad
Re: Empty directory share/lyx/images/commands created on make install
"Sven Hoexter" <[EMAIL PROTECTED]> writes: > Hi, > currently make install creates an empty directory share/lyx/images/commands. > Is this done by intention or just something left over or should there be > some files in there? It is intended. This is where we can define icons for user-defined commands. JMarc
Re: Change tracking issues in RC5
baseliner <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > >> >> Please enter these two bugs in bugzilla if you do not get another answer. >> > Thanks JMarc.. I'm trying to login to bugzilla but it's timing out.. > tried a few times over the last 2 days. It is again the spam filter getting mad. I restarted it, and things seem to be better now. JMarc
export 1.6 UserGuide to 1.5 fails
I have just tested if 1.5.7svn reads the 1.6 UG and spotted a problem: The
import fails due to an InfoInset with the arg "self-insert \"". The
document.body[k][3:].strip().strip('"') operation removes all quotes and the
file ends up with an invalid backslash.
Attached is a working, but maybe not optimal fix for both 1.5.7svn and
1.6.1svn. However, importing still triggers a warning due to an unexepectedly
ended paragraph (which is an independent problem, AFAICS).
José?
Jürgen
Index: lib/lyx2lyx/lyx_1_6.py
===
--- lib/lyx2lyx/lyx_1_6.py (Revision 27371)
+++ lib/lyx2lyx/lyx_1_6.py (Arbeitskopie)
@@ -1220,7 +1220,9 @@
arg = ''
for k in range(i, j+1):
if document.body[k].startswith("arg"):
-arg = document.body[k][3:].strip().strip('"')
+# Generic, \" -> ":
+arg = wrap_into_ert(document.body[k][3:], r'\"', '"')
+arg = arg.strip().strip('"')
if document.body[k].startswith("type"):
type = document.body[k][4:].strip().strip('"')
# I think there is a newline after \\end_inset, which should be removed.
Patch to enable docbook
Hello, I'm an user of LyX for docbook document generation and I've found a bug in configure.py that prevents any docbook classes from being enabled. I just fixed it and works fine. Please find attached the patch file to be applied. Additionally, I also modified the configure.py, so that is enables docbook if xsltproc is available. xsltproc is the docbook processor I'm using for windows. It would be great if you could commit those changes to SVN. Best regards, Rafael. mypatch.diff.gz Description: GNU Zip compressed data
Re: lyx-advsearch: MainWorkArea
Tommaso Cucinotta wrote: Abdelrazak Younes ha scritto: Why is this distinction between normal and embedded work areas needed? Because certain operations may be meaningful only on main/document/non-embedded work-areas. For example, if I'm keeping the search dialog open and I decide to open a new document, I'd expect it to be loaded into the mainWorkArea, not the search one that has currently the focus. Similarly, saving the searchWorkArea contents may not be meaningful, or lead to unexpected results (for the normal user, at least). Further, when previewing, I wouldn't expect to get a preview of the searchWorkArea, even if I have it under focus, but I would expect a preview of the mainWorkArea (the document I'm working on). I don't know exactly what else requires this distinction, but I think there are a few places in the code where view_.currentWorkArea() should be replaced by view_.currentMainWorkArea(). OK, I understand your reasoning but I think I disagree. I'd prefer GuiView to not be aware of this distinction. Instead I would make the embedded workarea redirect the relevant information like bufferView() or buffer(). I am sure if this is easy to implement though... Because the focus automatically returns to the current work area after a dispatch. As you now make the distinction between normal and embedded work areas, the focus goes back to the main one. This is also strange: I do a view_.setCurrentWorkArea() in the dialog showEvent(), so, if at all the focus is forced to the currentWA after dispatch, it should anyway happen the right thing. I don't think view_.setCurrentWorkArea() will call setFocus() automatically, maybe that is your problem. However, I just fixed this issue in a way that you may not like: I'm posting a 100ms timer activating a function that invokes searchWorkArea_.setFocus() again. Right, I don't like it :-) - when the dialog opens up, the searchworkarea contents is again selected entirely, so starting to type whatever (after a Tab for gaining focus) deletes the last search text Try to set the cursor selection to false on open up (bufferView().cursor().setSelection() or something like that). Well, I meant this to be a feature (similar to what happens in many text editors): leaves you the freedom to easily modify the previous search text, or discard it entirely. OK, sorry, I thought you were complaining :-) Abdel.
Re: lyx-advsearch: MainWorkArea
Abdelrazak Younes ha scritto: Why is this distinction between normal and embedded work areas needed? Because certain operations may be meaningful only on main/document/non-embedded work-areas. For example, if I'm keeping the search dialog open and I decide to open a new document, I'd expect it to be loaded into the mainWorkArea, not the search one that has currently the focus. Similarly, saving the searchWorkArea contents may not be meaningful, or lead to unexpected results (for the normal user, at least). Further, when previewing, I wouldn't expect to get a preview of the searchWorkArea, even if I have it under focus, but I would expect a preview of the mainWorkArea (the document I'm working on). I don't know exactly what else requires this distinction, but I think there are a few places in the code where view_.currentWorkArea() should be replaced by view_.currentMainWorkArea(). Because the focus automatically returns to the current work area after a dispatch. As you now make the distinction between normal and embedded work areas, the focus goes back to the main one. This is also strange: I do a view_.setCurrentWorkArea() in the dialog showEvent(), so, if at all the focus is forced to the currentWA after dispatch, it should anyway happen the right thing. However, I just fixed this issue in a way that you may not like: I'm posting a 100ms timer activating a function that invokes searchWorkArea_.setFocus() again. - when the dialog opens up, the searchworkarea contents is again selected entirely, so starting to type whatever (after a Tab for gaining focus) deletes the last search text Try to set the cursor selection to false on open up (bufferView().cursor().setSelection() or something like that). Well, I meant this to be a feature (similar to what happens in many text editors): leaves you the freedom to easily modify the previous search text, or discard it entirely. T.
Re: [PATCH] Minor Renaming
rgheck <[EMAIL PROTECTED]> writes: > Anyone object to the attached? JMarc recently noted that this method is > misnamed. Obviously I would not object. Even if we decide to change these methods later, we'll know at least what we are talking about. JMarc
