Fix for ps2pdf export of Tufte examples
Both the tufte-book and tufte-handout examples give many errors when I try to export to PDF with ps2pdf. These errors disappear if the nols document class option is specified. Is adding it OK or is there a better fix? Below is a description of what the nols option does: The nols option inhibits the letterspacing code. The Tufte-LATEX classes try to load the appropriate letterspacing package (either pdfTEX’s letterspace package or the soul package). If you’re using XeLaTeX with fontenc, however, you should configure your own letterspacing. (taken from tufte-latex.googlecode.com/git/sample-book.tex or tufte-latex.googlecode.com/files/sample-book-3.5.0.pdf) Scott
Re: Fix for ps2pdf export of Tufte examples
On Mon, Apr 8, 2013 at 4:25 AM, Jürgen Spitzmüller sp...@lyx.org wrote: Scott Kostyshak wrote: Both the tufte-book and tufte-handout examples give many errors when I try to export to PDF with ps2pdf. These errors disappear if the nols document class option is specified. Is adding it OK or is there a better fix? Below is a description of what the nols option does: The nols option inhibits the letterspacing code. The Tufte-LATEX classes try to load the appropriate letterspacing package (either pdfTEX’s letterspace package or the soul package). If you’re using XeLaTeX with fontenc, however, you should configure your own letterspacing. (taken from tufte-latex.googlecode.com/git/sample-book.tex or tufte-latex.googlecode.com/files/sample-book-3.5.0.pdf) I think letterspacing is an important part of the tufte design. So I would rather suggest to report this bug to the tufte class developers. Makes sense. I think the bug is well-known (googling suggests this). The last update to the code was a couple of years ago (https://code.google.com/p/tufte-latex/source/list) so this could be around for a while. I guess setting the default output format is the best we can do for now. I'll do that unless someone objects. Scott
Re: [LyX – The Document Processor] Your organization application has been accepted.
On Mon, Apr 8, 2013 at 3:17 PM, Liviu Andronic landronim...@gmail.com wrote: Dear all, Good news. LyX has been accepted for GSoC 2013! Now Stefano and I need to prepare the public profile for LyX, and soon we will hopefully have students contacting us on lyx-devel. The Student application period opens on April 22 and the deadline is on May 3. Please let us know if you have any suggestions on how best to proceed (student applications, mentorships, etc.). Regards, Liviu Great news! Thanks for helping with this, Liviu and Stefano. I only know of one student who might be interested. Zahari Dimitrov (zaha...@gmail.com) was interested in doing GSoC last year: http://article.gmane.org/gmane.editors.lyx.devel/140522/match= He has submitted a patch for LyX that was (after a year) applied: http://article.gmane.org/gmane.editors.lyx.devel/140174/match= Should I contact him and let him know? Best, Scott
Re: ps2pdf fails in export of doc/hu/Tutorial.lyx to PDF (ps2pdf)
On Mon, Apr 8, 2013 at 3:40 AM, Jürgen Spitzmüller sp...@lyx.org wrote: Scott Kostyshak wrote: If the choice is between (1) having both ps2pdf and pdflatex working without bookmarks or (2) setting the default to pdflatex and keeping the bookmarks I think I would favor (1). I guess that alternatively some \ifpdf vodoo could be used? But that seems like unncessary complication. I agree completely. It's in now. Thanks, Scott
Re: Fix for ps2pdf export of Tufte examples
On Mon, Apr 8, 2013 at 4:47 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: 08/04/2013 10:46, Scott Kostyshak: I guess setting the default output format is the best we can do for now. I'll do that unless someone objects. Go for it. Done. Thanks, Scott
can't export es/europeCV.lyx to pdf with LuaTeX
I get many UTF-8 errors. Any advice? Scott
Re: [LyX master] Hungarian Tutorial.lyx: revert last change
On Tue, Apr 9, 2013 at 3:17 PM, Uwe Stöhr uwesto...@lyx.org wrote: Hi Uwe, - this is not the way it goes, all Tutorials should stay identical as possible I agree. The key word here is as possible. This implies that there is some interpretation required. moreover there is no need to disable PDF bookmarks because the document compiles without problems compiles is not an absolute term. It does compile with pdflatex. It does not compile with ps2pdf. I am not sure how many people use ps2pdf these days but I thought it was more important to have it compile with both than to keep the bookmarks. If the first experience a user has is they open a manual and it does not compile, to me that is very bad. moreover I still manage the documentation and as long as there is no beta for LyX 2.1 please keep the fileformat of LyX 2.0 OK. - if you have problems compiling a file, report this as bug or the docmentation mailing list! or at least write me a mail I reported it to the development mailing list (to me these issues are slightly different than documentation, but I'm happy to start reporting them to the documentation list if that is better): http://comments.gmane.org/gmane.editors.lyx.devel/145647 I committed because another developer agreed. Scott
Re: Interested in GSOC Project: Horizontal scrollbar for tables and math and Some problems regarding the project
On Tue, Apr 9, 2013 at 11:38 PM, Hashini Senaratne hashz1...@gmail.com wrote: Hello all, This is regarding some problems that I came up with while trying to proceed with the mentioned project idea. Hope I can get some ideas and help from here. Hi Hashini, you found the right place. I am interested with the project: Horizontal scrollbar for tables and math that is mentioned under http://wiki.lyx.org/Devel/SummerOfCode2013Ideas. Basically I installed LyX Document processor to my system (Ubuntu 12.04 LTS) and experienced that problem. After that, I downloaded the source code from the Git repository and was able to compile it and finally run it after several attempts. The version 2.1.0 dev is now running on my system using the command line. Hope that is the latest version. Glad to see that you are all set up. I also use Ubuntu. Note that there are two ways to build LyX -- with autotools and with CMake. As I can see, in LyX if we print (/view as pdf) a document with a too wide table, the extra part is going to be cut out in the output. This will happen even if a horizontal bar is created to access the extended edges in the editing environment. Is there any solution that the organization has figured out for this issue? Or is that part also falling under to the same project? From what I understand, this has nothing to do with the project. I think the project is only about the LyX representation of a table and has nothing to do with LaTeX. To answer you question though: I have no experience with wide tables in LaTeX, but one solution would be to rotate it and if necessary use a long table. See the table settings (Edit Table Settings). If possible, please introduce me some introductory bugs that are easy to start with and related to this project. Note that I am not very experienced so if you are ever wondering should I do what Scott says or what X says?, do what X says. Especially if X is Jean-Marc. If you are looking for things to do (I'm not sure you should be at this point), are you familiar with Qt? I get the feeling that this is an ambitious project. It is also (in my experience) one of the most often requested feature enhancements. See the main bug report here: http://www.lyx.org/trac/ticket/1083 Note how old it is. Many reports have been marked as duplicates of that report. You should wait for advice from someone else, but here is a guess at something that might be useful to do: From what I understand, this project has to do with painting and Qt. So you could take a look at the bug reports that have to do with painting and Qt. To do this, do the following: 1. http://www.lyx.org/trac 2. click on View Tickets 3. click on Search for bugs 4. Click the empty box next to and and go to component. 5. Next to component is, click on the empty box and go to painter. Another component you could select is frontend-qt4. It has a lot more tickets but is more general. I would not recommend trying to solve those bugs, but maybe just viewing the conversations there will give you a feel for what painting concerns there are out there. Another idea is to try to get familiar with the code regarding the vertical scrollbar. Best, Scott
Re: Interested in GSOC Project: Horizontal scrollbar for tables and math and Some problems regarding the project
On Wed, Apr 10, 2013 at 2:12 AM, Hashini Senaratne hashz1...@gmail.com wrote: I used 'make' command to compile the system and I will like to learn about the both way. So I will do some search and get back to you if I fail after my attempts. Most devs use autotools so I don't know if you need to know how to use CMake but since you expressed interest, I'll give the steps. It is recommended to build it out-of-source, which means that the source directory is left untouched so that binaries aren't mixed in the same folder as source code. To do this, make a directory somewhere. Then do something like the following: mkdir ~/lyxbuild cd ~/lyxbuild cmake path to source folder make There is one more question. The version of the product that I have checkout from the GIT repository is 2.1.0 and I noticed that it is not released yet. Also, it has less menu items in edit mode (eg: view menu) than in the version 2.0.2. What is the current stable version and what is the version that I should have to start with developing? The git branch master is the development branch. It is what will soon become LyX 2.1. It is referred to as trunk around here. The branch 2.0.x is referred to often as branch and it is the next stable release, what will soon become 2.0.6. The stable release is only for bug fixes. A huge feature like a horizontal scrollbar should be developed on the unstable branch, master. You should make your own git branch from master. Let me know if you have any questions about git. I'm still learning my way with it but I've figured out a lot of things. Best, Scott
Re: Interested in GSOC Project: Horizontal scrollbar for tables and math and Some problems regarding the project
On Wed, Apr 10, 2013 at 3:07 AM, Hashini Senaratne hashz1...@gmail.com wrote: If you have some time could you please give me some more details about autotools that you are aware of, later. I do not want to keep on disturbing you. So, I prefer search by myself, before asking everything from you. Running './configure --help' gives a lot of useful information. For anything else, feel free to ask a specific question. Best, Scott
Re: DocBook converters (no knowledge of DocBook required)
On Mon, Apr 8, 2013 at 10:20 AM, José Matos jama...@lyx.org wrote:
The sgmltools (that I don't have installed) will most probably use the latex
way so I agree with you that the ps backend is the way to go (even if in the
end it is the same transformation path).
OK, it sounds like it makes sense to add support for PostScript as a backend.
Can you or Richard check the attached patch? I do not have confidence
in editing configure.py. I did test it and it works for me.
Scott
From fb7c59c175303c35f3bd18603779ec0db7cd19a3 Mon Sep 17 00:00:00 2001
From: Scott Kostyshak skost...@lyx.org
Date: Wed, 10 Apr 2013 21:56:18 -0400
Subject: [PATCH] Add a DocBook - PS converter
Before, the converter chain for DocBook - PDF (ps2pdf) was:
docbook - DVI
DVI - Postscript
Postscript - PDF (ps2pdf)
sgmltools has a backend for PostScript so the first two
steps in the above converter chain are now condensed into
one by adding the following converter for docbook - Postscript:
sgmltools -b ps $$i
---
lib/configure.py |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/configure.py b/lib/configure.py
index 62ed2b9..7687aff 100644
--- a/lib/configure.py
+++ b/lib/configure.py
@@ -962,7 +962,8 @@ def checkDocBook():
path, DOCBOOK = checkProg('SGML-tools 2.x (DocBook), db2x scripts or
xsltproc', ['sgmltools', 'db2dvi', 'xsltproc'],
rc_entry = [
r'''\converter docbookdvisgmltools -b dvi $$i
-\converter docbookhtml sgmltools -b html $$i ''',
+\converter docbookhtml sgmltools -b html $$i
+\converter docbookps sgmltools -b ps $$i ''',
r'''\converter docbookdvidb2dvi $$i
\converter docbookhtml db2html $$i ''',
r'''\converter docbookdvi
--
1.7.9.5
Re: DocBook converters (no knowledge of DocBook required)
On Mon, Apr 8, 2013 at 10:20 AM, José Matos jama...@lyx.org wrote: On Tuesday 02 April 2013 16:42:09 Scott Kostyshak wrote: FWIW I am using the db2xxx tools (db2dvi db2html db2pdf db2ps db2rtf) from the docbook-utils project http://sources.redhat.com/docbook-tools/ Ah, I had not seen that. I just installed them (in Ubuntu, the package is docbook-utils). when looking to my running instance of lyx (2.1-git) I see that I don't have neither db2pdf nor db2ps active so I expect this to be a missing implementation of the converters (on our part) rather than any problems in the those converters. You are right. Strangely we have support for db2html but none of the others. I tried to test docbook_article with db2pdf and I get errors. Here are a few: openjade:/tmp/lyx_tmpdir.n10355/lyx_tmpbuf2/docbook_article.sgml:113:68:E: element DUMMY undefined openjade:/tmp/lyx_tmpdir.n10355/lyx_tmpbuf2/docbook_article.sgml:114:6:E: element DUMMY undefined openjade:/tmp/lyx_tmpdir.n10355/lyx_tmpbuf2/docbook_article.sgml:114:83:E: end tag for FOOTNOTE which is not finished openjade:/tmp/lyx_tmpdir.n10355/lyx_tmpbuf2/docbook_article.sgml:121:89:E: element DUMMY undefined openjade:/tmp/lyx_tmpdir.n10355/lyx_tmpbuf2/docbook_article.sgml:121:169:E: end tag for FOOTNOTE which is not finished support/Systemcall.cpp (277): Systemcall: 'db2pdf docbook_article.sgml' finished with exit code 8 Error: Cannot convert file An error occurred while running: db2pdf docbook_article.sgml Note that I can export docbook_article with sgmltools. Does db2pdf work for you? If so, I can send a patch to add support but I will not be able to test it (at least not with docbook_article because of the errors above) so could you test it (assuming db2pdf works for you)? I agree that my explanation is a bit cryptic at points so I can expand further if you want to. Your explanation here is very clear. Thanks, Scott
[PATCH] Spelling: Postscript - PostScript
From what I understand, PostScript is the correct way to write it.
Does anyone have an opinion on this?
Scott
From 57122755eec3497c4bbe2215cc71b87be9ef8071 Mon Sep 17 00:00:00 2001
From: Scott Kostyshak skost...@lyx.org
Date: Wed, 10 Apr 2013 22:47:44 -0400
Subject: [PATCH] Spelling: Postscript - PostScript
---
lib/configure.py |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/configure.py b/lib/configure.py
index 62ed2b9..e1f0c21 100644
--- a/lib/configure.py
+++ b/lib/configure.py
@@ -572,12 +572,12 @@ def checkFormatEntries(dtl_tools):
'nedit', 'gedit', 'notepad', 'geany', 'leafpad', 'mousepad'],
rc_entry = [r'''\Format bibtex bibBibTeX %%
text/x-bibtex''' ])
#
-#checkProg('a Postscript interpreter', ['gs'],
+#checkProg('a PostScript interpreter', ['gs'],
# rc_entry = [ r'\ps_command %%' ])
-checkViewer('a Postscript previewer', ['kghostview', 'okular', 'evince',
'gv', 'ghostview -swap'],
+checkViewer('a PostScript previewer', ['kghostview', 'okular', 'evince',
'gv', 'ghostview -swap'],
rc_entry = [r'''\Format epseps EPS
%%vectorimage/x-eps
\Format eps2 epsEPS (uncropped)%%
vector
-\Format ps ps Postscript t %%
document,vector,menu=export application/postscript'''])
+\Format ps ps PostScript t %%
document,vector,menu=export application/postscript'''])
# for xdg-open issues look here:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg151818.html
# the MIME type is set for pdf6, because that one needs to be
autodetectable by libmime
checkViewer('a PDF previewer', ['pdfview', 'kpdf', 'okular', 'evince',
'kghostview', 'xpdf', 'acrobat', 'acroread', 'mupdf', \
--
1.7.9.5
Re: ps2pdf13 - ps2pdf14 ?
On Mon, Apr 8, 2013 at 2:04 AM, Jürgen Spitzmüller sp...@lyx.org wrote:
Scott Kostyshak wrote:
I don't have any particular reason for changing it and the safe thing
would be to leave it alone, but I'm curious what others think.
My vote would be to use plain ps2pdf without any format binding.
Sounds good to me. Do others have an opinion? Is the attached patch OK?
Scott
From 83b116bab57068fcdc88b96024c02acabc7e1e33 Mon Sep 17 00:00:00 2001
From: Scott Kostyshak skost...@lyx.org
Date: Wed, 10 Apr 2013 22:56:35 -0400
Subject: [PATCH] converter: change 'ps2pdf13' to 'ps2pdf'
ps2pdf by default produces the PDF 1.4 format. The PDF 1.3 format was
released in 2000. PDF 1.4 was released in 2001. LyX specified 1.3 as
the output version in 2002 (c1541c22), perhaps because at the time
PDF 1.4 was only a year old so some viewers did not support it.
---
lib/configure.py |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/configure.py b/lib/configure.py
index e1f0c21..3dbfc38 100644
--- a/lib/configure.py
+++ b/lib/configure.py
@@ -753,7 +753,7 @@ def checkConverterEntries():
checkProg('a RTF - HTML converter', ['unrtf --html $$i $$o'],
rc_entry = [ r'\converter rtf html%%' ])
# Do not define a converter to pdf6, ps is a pure export format
-checkProg('a PS to PDF converter', ['ps2pdf13 $$i $$o'],
+checkProg('a PS to PDF converter', ['ps2pdf $$i $$o'],
rc_entry = [ r'\converter ps pdf%% ' ])
#
checkProg('a PS to TXT converter', ['pstotext $$i $$o'],
--
1.7.9.5
Re: Interested in GSOC Project: Horizontal scrollbar for tables and math and Some problems regarding the project
On Thu, Apr 11, 2013 at 1:42 PM, Hashini Senaratne hashz1...@gmail.com wrote: I tried to go through the source code and tried to figure out how the vertical scrollbar has been implemented. I think this would be a bit difficult task, until I get familiar with the code. I was able to disable some functionality of the vertical scrollbar by commenting about 2 lines in the file GuiWorkArea.cpp under /src/frontends/qt4. Commenting out lines of code sounds like a great technique for learning. I had never thought about that! I think I have to spend more time with the code and identify related area. But still I could not identify most of them. Yes, it will probably take a lot of time. I think that doing whatever is the most fun/ least frustrating to get to know the code is the best. That could mean trying to solve a small bug or just experimenting. If you would find it helpful, we could choose a small bug to work on together. I have many small buglettes that I would like to someday address if you are looking for some, but if you have one that you would be interested in solving, that might be better. Let me know what would be best for you. Scott
Re: [LyX master] Hungarian Tutorial.lyx: revert last change
On Wed, Apr 10, 2013 at 10:37 AM, Guenter Milde mi...@users.sf.net wrote: On 2013-04-10, Kornel Benko wrote: Therefore explicitly setting the default for _this_ document is OK IMHO. Agreed. OK, I committed this at 18f5500a. There were two explicit +1's and Uwe says the document should be exported with pdflatex. The format is kept at 2.0's format. Scott
Re: Re: DocBook converters (no knowledge of DocBook required)
On Fri, Apr 12, 2013 at 6:31 PM, José Matos jama...@lyx.org wrote: On Wednesday 10 April 2013 22:05:09 Scott Kostyshak wrote: I have different errors since I only have docbook 4.5 installed. The patch attached fixes the first problem you describe the DUMMY references (pun intended). :-D I will try to chase and fix the others. Your patch does help. Here is the output I get now from db2pdf (exit code is 8): Using catalogs: /etc/sgml/catalog Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print Working on: docbook_article.sgml openjade:docbook_article.sgml:30:121:E: start tag for LISTITEM omitted, but its declaration does not permit this openjade:docbook_article.sgml:51:26:E: start tag for TITLE omitted, but its declaration does not permit this openjade:docbook_article.sgml:59:22:E: end tag for INLINEMEDIAOBJECT which is not finished openjade:docbook_article.sgml:60:6:E: document type does not allow element TITLE here; assuming missing BLOCKQUOTE start-tag openjade:docbook_article.sgml:60:15:E: document type does not allow element CAPTION here openjade:docbook_article.sgml:60:38:E: end tag for element CAPTION which is not open openjade:docbook_article.sgml:61:8:E: BLOCKQUOTE not finished but containing element ended openjade:docbook_article.sgml:63:26:E: start tag for TITLE omitted, but its declaration does not permit this openjade:docbook_article.sgml:71:22:E: end tag for INLINEMEDIAOBJECT which is not finished openjade:docbook_article.sgml:72:6:E: document type does not allow element TITLE here; assuming missing BLOCKQUOTE start-tag openjade:docbook_article.sgml:72:15:E: document type does not allow element CAPTION here openjade:docbook_article.sgml:72:47:E: end tag for element CAPTION which is not open openjade:docbook_article.sgml:73:8:E: BLOCKQUOTE not finished but containing element ended openjade:docbook_article.sgml:75:66:E: document type does not allow element INFORMALTABLE here openjade:docbook_article.sgml:104:15:E: document type does not allow element CAPTION here openjade:docbook_article.sgml:104:42:E: end tag for element CAPTION which is not open openjade:docbook_article.sgml:105:7:E: end tag for TABLE which is not finished openjade:docbook_article.sgml:113:62:E: character data is not allowed here openjade:docbook_article.sgml:114:68:E: end tag for FOOTNOTE which is not finished openjade:docbook_article.sgml:121:83:E: character data is not allowed here openjade:docbook_article.sgml:121:154:E: end tag for FOOTNOTE which is not finished Scott
Re: DocBook converters (no knowledge of DocBook required)
On Fri, Apr 12, 2013 at 6:56 PM, Richard Heck rgh...@lyx.org wrote: On 04/10/2013 10:01 PM, Scott Kostyshak wrote: On Mon, Apr 8, 2013 at 10:20 AM, José Matos jama...@lyx.org wrote: The sgmltools (that I don't have installed) will most probably use the latex way so I agree with you that the ps backend is the way to go (even if in the end it is the same transformation path). OK, it sounds like it makes sense to add support for PostScript as a backend. Can you or Richard check the attached patch? I do not have confidence in editing configure.py. I did test it and it works for me. That patch looks fine. But Jose is definitely the expert on docbook. OK, I will apply the patch then unless someone disagrees. José cannot test because he does not use sgmltools. Scott
Re: Interested in GSOC Project: Horizontal scrollbar for tables and math and Some problems regarding the project
On Fri, Apr 12, 2013 at 10:48 AM, Hashini Senaratne hashz1...@gmail.com wrote: Scott Kostyshak skostysh at lyx.org writes: Yes, it will probably take a lot of time. I think that doing whatever is the most fun/ least frustrating to get to know the code is the best. That could mean trying to solve a small bug or just experimenting. If you would find it helpful, we could choose a small bug to work on together. I have many small buglettes that I would like to someday address if you are looking for some, but if you have one that you would be interested in solving, that might be better. Let me know what would be best for you. I am really thankful to you if you can work with me to solve a simple bug, as you suggested. Do you have any bug in your mind, a little related to UI? Even if it is not, I like to learn from you in the way you suggested. Please guide me through this when you have time. OK, sounds good. I will go through my disorganized dump of notes this weekend and write up some descriptions of minor bugs. I'm sure I have something related to UI, but not sure how related to the part of UI you will need for the project. Then you can see if one of them looks interesting. Scott
Beamer goto buttons and text hyperlinks
Beamer buttons are used to reference one slide from another so that
you can jump around your presentation (useful if a viewer asks a
question about details, for example).
These buttons are pretty popular. For example, one of the beamer
examples has three of the goto buttons:
examples/beamerlyxexample1.lyx
To use one, you insert a label in a Beamer frame, and then when you
want to link to it, you use
\hyperlink{labelToRef}{\beamergotobutton{Text on Button}}
Buttons can be distracting to the audience (it's like showing someone
a box -- of course they want to know what's inside) so many presenters
use text hyperlinks. The text looks like other text so it does not
stand out but it can be clicked on just like a button and just like
one can click on a cross-reference in an article class.
I would like to add support to LyX for these buttons and would like
some advice. Below are a few implementation ideas:
a. This could be an option from the cross-reference menu (as part of
the Format combo box). One could select an existing label, select
button or text, and then enter what they would like to be displayed
(common strings are Details, Proof, Click here, or Back).
b. These could be custom insets defined in beamer.layout. Attached is
a patch that does this. The disadvantage of this approach is that the
user has to do more steps: click on insert custom insets Goto
Button; then insert the display text; then they have to remember to go
to Insert Target; and then they have to remember the name of the
label they want to reference.
c. There are a couple of hybrids of (a) and (b) that could be done.
For example, an option could be added to the Format combo box that
just inserts the label in a PassThru sense (that is, not embedded in
\ref{}). This would make the selection of the label easy and would not
require the hardcoding that a pure (a) solution would.
d. Another hybrid would be to allow a layout argument to be of type
cross-reference. This would give the user a dialog of the defined
labels to select from (similar to the cross-reference menu but more
simple because no options would need to be selected). It probably
doesn't make sense to implement this just for the insets I'm
proposing, and I struggle to think of other examples so this might not
be a good idea.
Any thoughts?
Scott
diff --git a/lib/layouts/beamer.layout b/lib/layouts/beamer.layout
index 6e0be1b..2d4607e 100644
--- a/lib/layouts/beamer.layout
+++ b/lib/layouts/beamer.layout
@@ -1528,6 +1528,36 @@ InsetLayout Flex:PresentationMode
MultiPartrue
End
+InsetLayout Flex:Goto_Button
+ LabelString Button
+ LatexTypenone
+ LyXType Custom
+ LeftDelim{\beamergotobutton{
+ RightDelim }}
+ Decoration Classic
+ MultiPar false
+ ForcePlain 1
+ PassThru 0
+ Spellcheck 1
+ ContentAsLabel 1
+ Argument 1
+Mandatory 1
+LabelStringTarget
+TooltipInsert the label of the slide to reference
+LeftDelim \hyperlink{
+RightDelim }
+ EndArgument
+End
+
+InsetLayout Flex:Goto_Text
+ CopyStyleFlex:Goto_Button
+ LabelString Goto Text
+ LeftDelim{
+ RightDelim }
+ Font
+Family sans
+ EndFont
+End
#
# FLOATS
Re: Re: DocBook converters (no knowledge of DocBook required)
On Sat, Apr 13, 2013 at 1:32 PM, José Matos jama...@lyx.org wrote: On Friday 12 April 2013 23:31:55 Scott Kostyshak wrote: OK, I will apply the patch then unless someone disagrees. José cannot test because he does not use sgmltools. Scott You can test easily if you create a new document from templates. There is a simple docbook template that will work after my last patch. Please try it. Sorry for the confusion. Yes, I've tested it. But I think Richard was suggesting that it would be better if you tested it. I agree, because all I basically check for is that it compiles without error and that the pdf looks normal to me. But in this case I think only me testing it is OK. I committed at 7309f018 Scott
Re: Re: Re: DocBook converters (no knowledge of DocBook required)
On Sat, Apr 13, 2013 at 2:16 PM, José Matos jama...@lyx.org wrote: On Friday 12 April 2013 23:30:16 Scott Kostyshak wrote: Your patch does help. Here is the output I get now from db2pdf (exit code is 8): Yes, I get the same. I think that the reasonable course of action is to update the docbook support for 4.5 (released in 2006). I will look in to this before lyx-2.1 release. There was someone interested in adding support for DocBook 5: http://www.lyx.org/trac/ticket/8444 Let me know if there's anything I can do to test. Scott
Re: Re: Re: Re: DocBook converters (no knowledge of DocBook required)
On Sat, Apr 13, 2013 at 2:32 PM, José Matos jama...@lyx.org wrote: The question between docbook 4 (mostly 4.5) and docbook 5 is the same that we are having in another thread regarding python. Interesting coincidence. I guess major releases are a good time to talk about changing version support. docbook 4(.5) is still widely used while at the same time the changes needed to change it in lyx are small. That is why IMHO it is a reasonable goal for lyx-2.1. The work needed to support docbook 5 suggest that this is a lyx-2.2 quest. All the arguments are IMHO, naturally. :-) Your argument makes sense to me. And you should decide because from what I understand you're the only one around here who knows something about DocBook and is willing to work on it. Scott
Re: [LyX master] Hungarian Tutorial.lyx: revert last change
On Sat, Apr 13, 2013 at 7:42 AM, Uwe Stöhr uwesto...@web.de wrote: Am 12.04.2013 09:48, schrieb Scott Kostyshak: OK, I committed this at 18f5500a. Thanks. Can you please also do the same for the files in branch? Yes, what is the protocol for doc files in branch. You are doc maintainer and Richard is branch maintainer. Should I get the approval of both? This affects other files to, right? This particular change no. But I've made several changes to the examples recently. Please don't forget to add an entry in the status.20x file. Thanks for the reminder. Scott
Re: Beamer goto buttons and text hyperlinks
On Sun, Apr 14, 2013 at 3:25 AM, Jürgen Spitzmüller sp...@lyx.org wrote: Scott Kostyshak wrote: Any thoughts? I'd go for a. My next set of questions then: 1. Are these used outside of Beamer? 2. If not, would I need to hardcode these options to only be enabled when Beamer is being used? Scott
examples/landslide.lyx: can't export with pdflatex because of bounding box
Exporting via ps2pdf works fine, but pdflatex and luatex fail. I think pdflatex fails because of converting the eps to pdf. I thought I had fixed a similar error before with the following: epstool --copy --bbox platypus.eps --output platypus2.eps But this did not help. Any ideas? Scott
templates/aa.lyx: inputenc option clash when export with pdflatex/ps2pdf
Exporting with luatex works fine. With pdflatex and ps2pdf I get an inputenc option clash. Note that examples/aa_sample.lyx exports with pdflatex and ps2pdf fine. Is there a fix? Scott
examples/es/europeCV.lyx: can't export with luatex
I get utf-8 and utf8x errors. Is there a fix for this while preserving export with pdflatex and latex? Scott
JASA.lyx: Error in latexParagraphs: You should not mix title layouts with normal ones.
I get the following error when exporting templates/JASA.lyx: output_latex.cpp (): Error in latexParagraphs: You should not mix title layouts with normal ones. Is there something in the layout that needs fixing? Scott
Re: Beamer goto buttons and text hyperlinks
On Sun, Apr 14, 2013 at 3:59 AM, Jürgen Spitzmüller sp...@lyx.org wrote: There is a ticket with a similar request, BTW, but it was resolved wontfix (and should be reopened IMHO): http://www.lyx.org/trac/ticket/8282 I hadn't seen that ticket. Thanks. Looking at the docs, I'd propose to make beamergotobutton a flex inset within beamer.layout. The hyperref inset should be turned into a collapsable inset (while the dialog is being kept, minus the name field), \hyperlink support should be added to this inset (and \hypertarget to the label inset). And finally, the url inset should be merged into the hyperref inset. I think I understand most of this. You're suggesting a collapsable inset because then the user can insert the beamergotobutton flex inset inside of it. The name field should be taken out because that is now the input to the collapsable inset. To edit the target of the hyperref, the user would right click on the collapsable inset and choose settings. After merging the URL inset into the hyperref inset, there will be four options: Web, Email, File, URL. Will the user be confused between Web and URL? IIUC, when the user makes a hyperlink, either a label or hypertarget label can be hyperlinked to. So all labels and hypertarget labels should be shown in the hyperref inset? And the cross-reference inset would not be untouched, right? Scott
Re: Beamer goto buttons and text hyperlinks
On Sun, Apr 14, 2013 at 5:26 AM, Jürgen Spitzmüller sp...@lyx.org wrote: Scott Kostyshak wrote: IIUC, when the user makes a hyperlink, either a label or hypertarget label can be hyperlinked to. So all labels and hypertarget labels should be shown in the hyperref inset? Yes. I think this is all starting to make sense. Thank you for the advice, Scott
Re: JASA.lyx: Error in latexParagraphs: You should not mix title layouts with normal ones.
On Mon, Apr 15, 2013 at 1:38 PM, Hashini Senaratne hashz1...@gmail.com wrote: Scott Kostyshak skostysh at lyx.org writes: I get the following error when exporting templates/JASA.lyx: output_latex.cpp (): Error in latexParagraphs: You should not mix title layouts with normal ones. Is there something in the layout that needs fixing? As you know I am new to development. I tried this and came up with the same error. Then removed the Acknowledgement part and exported to PDF(pdflatex). Then the error did not appear. Will this information help in anyway? Hi Hashini, Yes, this helps! First, it's helpful to know that you got the same error. It's common on this list and in bug reports to just see a message that says something like I can confirm the same behavior with LyX in up-to-date trunk on Ubuntu 12.04 and an updated TeX Live 2012 without trying to fix the bug. This shows that the bug is not just reproducible on my computer. Second you might have found what's triggering the error message. Since you narrowed it down to the Acknowledgments inset, I went to the layout file (lib/layouts/jasatex.layout) and looked at the definition. Everything looked pretty innocent to me. It was just copying another inset and there wasn't anything wrong with that inset (as you said, when you removed only the Acknowledgments inset the error goes away so everything else seems fine) so why would something be wrong? Because of the title part of the error message, the InTitle part stood out. I then thought it was strange that the Acknowledgments was copying InTitle 1 but was in category BackMatter. By overriding InTitle 1 and putting InTitle 0, the error goes away for me. I think the attached patch might be the correct thing to do. Since I know little about layouts (and even if I did), now we just wait for someone to come along to say whether this patch is the correct or incorrect thing to do. Thanks for the help, Scott From 734e1131885da7697d61b2e5856b4787cb9e1972 Mon Sep 17 00:00:00 2001 From: Scott Kostyshak skost...@lyx.org Date: Mon, 15 Apr 2013 17:06:23 -0400 Subject: [PATCH] Jjasatex.layout: fix a layout error 'Acknowledgments' does not belong in the title but did not override 'InTitle 1' inherited from 'Abstract'. Without this patch, the following error is given: output_latex.cpp (): Error in latexParagraphs: You should not mix title layouts with normal ones. Thanks to Hashini Senaratne for narrowing down the problem. --- lib/layouts/jasatex.layout |1 + 1 file changed, 1 insertion(+) diff --git a/lib/layouts/jasatex.layout b/lib/layouts/jasatex.layout index 1c6efa9..81a0bef 100644 --- a/lib/layouts/jasatex.layout +++ b/lib/layouts/jasatex.layout @@ -231,6 +231,7 @@ Style Acknowledgments CopyStyle Abstract LatexName acknowledgments CategoryBackMatter + InTitle 0 LabelType Above LabelString Acknowledgments Font -- 1.7.9.5
Re: JASA.lyx: Error in latexParagraphs: You should not mix title layouts with normal ones.
On Tue, Apr 16, 2013 at 3:03 AM, Hashini Senaratne hashz1...@gmail.com wrote: Scott Kostyshak skostysh at lyx.org writes: Yes it works for me too. I tried your patch. Thank you for confirming. Can anyone confirm that the patch is the right thing to do? If possible, please give me a place to study more about InTitles, Catogories,CopyStyles, etc and also differences among these types. On trunk (there have been significant improvements made by Jürgen for LyX 2.1), see the following: Help Customization 5.3 The layout file format I think the best way to learn is by experimenting. There are many great examples in the lib/layouts folder. Scott
Re: JASA.lyx: Error in latexParagraphs: You should not mix title layouts with normal ones.
On Tue, Apr 16, 2013 at 3:54 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Excellent detective work. This patch is the right one. Committed at 912cbcdb. Thanks, Scott
Re: GSoC idea for Layout Editor
On Thu, Apr 18, 2013 at 2:28 PM, Mayank Jha mayank25080...@gmail.com wrote: Thanks for referring me to the mailing-list history page! We would need a GUI interface which allows one to create document classes from the Latex classes without any prior knowledge of Latex or .layout files and at the same time enabling advanced users to tweak the .layout file by adding layout module created by them either with the help of the GUI interface or Latex code. Did I miss something ? Am I wrong somewhere ? Please let me know!! Hi Mayank, I'm not sure what you mean by which allows one to create document classes from the LaTeX class. From what I understand, the project is not about creating document classes. The second part of your sentence (tweaking .layout files) is what I understand the project to be. Everything else you put makes sense to me and it sounds like you did a good job of reading the documentation (note that the layout format has changed considerably since 2.0 so you should be reading it on your git checkout). Best, Scott
Re: GSoC idea for Layout Editor
On Thu, Apr 18, 2013 at 5:54 PM, Liviu Andronic landronim...@gmail.com wrote: On Thu, Apr 18, 2013 at 8:58 PM, Scott Kostyshak skost...@lyx.org wrote: On Thu, Apr 18, 2013 at 2:28 PM, Mayank Jha mayank25080...@gmail.com wrote: Thanks for referring me to the mailing-list history page! We would need a GUI interface which allows one to create document classes from the Latex classes without any prior knowledge of Latex or .layout files and at the same time enabling advanced users to tweak the .layout file by adding layout module created by them either with the help of the GUI interface or Latex code. Did I miss something ? Am I wrong somewhere ? Please let me know!! Hi Mayank, I'm not sure what you mean by which allows one to create document classes from the LaTeX class. Scott, It seems to me that this is an issue of vocabulary. What we call here a 'layout' may seem to a newcomer like a 'document class'. I think the confusion is natural, as layouts for LyX are bridges to LaTeX classes. I'm no expert in this but I would think that Mayank grasped the essentials on what we hope to get from this project. Ah, thanks for the clarification. I agree that he seems to have understood the goals. Scott
Re: GSOC 2014 Horizontal Scroll Bar
Hi Ben, It might be worth it to read through this recent email: http://comments.gmane.org/gmane.editors.lyx.devel/145717 See, in particular, JMarc's comment, containing the following I suuspect that a lot of work will be needed in our WorkArea widget to have it aware that it contains other Qt widgets (the scrollbars) Best, Scott On Thu, Apr 18, 2013 at 10:20 PM, Benjamin Le Cam b.le...@me.com wrote: Hi! The Horizontal Scroll Bar issue interests me. It looks like to be a major issue for many people so that would a great thing done. I already have a good background with Qt and so I'm wondering what there is no use of QScrollArea in order to have a horizontal scroll bar needed? I already had to deal with this kind of issue and this is mostly how I solved it. I also read in the mailing list that a person mentionned that it would require to use QPainter to draw a custom scrollbar. In my opinion this is not needed as Qt provides already some good widgets to handle this. So if you could tell me if I'm right/wrong and why this would take 12 weeks? I mean, is there any specific thing I should know about it? I have not looked at the code yet as I'm really busy with school this week but I'll take a look this week-end. So if someone could give more details that would be great. Thanks! Ben.
Re: [LyX master] Also put HTML on the clipboard when copying
On Fri, Apr 12, 2013 at 4:16 PM, Georg Baum b...@lyx.org wrote: The branch, master, has been updated. - Log - commit 0613a218aad1482ff3003a7cc4755c0b9651f3c2 Author: Georg Baum b...@lyx.org Date: Fri Apr 12 22:12:47 2013 +0200 Also put HTML on the clipboard when copying The HTML export is now mature enough so that it can be used to transfer formatted text to the clipboard. This enhances interoperability e.g. with office applications. I'm getting a SIGSEGV now. I can reproduce on Ubuntu 12.04 with the following: 1. Open the User's Guide, Additional Features, Embedded Objects, or Math manual. 2. Select all 3. Copy Below is the backtrace I get from following the above steps with the User's Guide: #0 0x00960b2a in lyx::Buffer::listMacroNames (this=0x0, macros=...) at /home/scott/lyxbuilds/master/build/src/Buffer.cpp:3259 #1 0x00bf3f83 in lyx::InsetMathHull::preparePreview (this=0x421abc0, pos=..., forexport=true) at /home/scott/lyxbuilds/master/build/src/mathed/InsetMathHull.cpp:599 #2 0x00bf48bd in lyx::InsetMathHull::loadPreview (this=0x421abc0, pos=...) at /home/scott/lyxbuilds/master/build/src/mathed/InsetMathHull.cpp:649 #3 0x00bfebc8 in lyx::InsetMathHull::xhtml (this=0x421abc0, xs=..., op=...) at /home/scott/lyxbuilds/master/build/src/mathed/InsetMathHull.cpp:2185 #4 0x00a4da02 in lyx::Paragraph::simpleLyXHTMLOnePar (this=0x421a780, buf=..., xs=..., runparams=..., outerfont=..., initial=0) at /home/scott/lyxbuilds/master/build/src/Paragraph.cpp:2939 #5 0x00b05825 in lyx::(anonymous namespace)::makeParagraphs (buf=..., xs=..., runparams=..., text=..., pbegin=..., pend=...) at /home/scott/lyxbuilds/master/build/src/output_xhtml.cpp:726 #6 0x00b06be8 in lyx::xhtmlParagraphs (text=..., buf=..., xs=..., runparams=...) at /home/scott/lyxbuilds/master/build/src/output_xhtml.cpp:1021 #7 0x00959696 in lyx::Buffer::writeLyXHTMLSource (this=0x45edbf0, os=..., runparams=..., output=lyx::Buffer::FullSource) at /home/scott/lyxbuilds/master/build/src/Buffer.cpp:1947 #8 0x00aedc77 in lyx::(anonymous namespace)::putClipboard ( paragraphs=..., docclass=..., plaintext=...) at /home/scott/lyxbuilds/master/build/src/CutAndPaste.cpp:484 #9 0x00af0799 in lyx::cap::copySelection (cur=..., plaintext=...) at /home/scott/lyxbuilds/master/build/src/CutAndPaste.cpp:935 #10 0x00aefc57 in lyx::cap::copySelection (cur=...) at /home/scott/lyxbuilds/master/build/src/CutAndPaste.cpp:837 #11 0x00bb6106 in lyx::Text::dispatch (this=0x26387b0, cur=..., cmd=...) at /home/scott/lyxbuilds/master/build/src/Text3.cpp:1292 #12 0x00d89a48 in lyx::InsetText::doDispatch (this=0x2638790, cur=..., cmd=...) at /home/scott/lyxbuilds/master/build/src/insets/InsetText.cpp:316 #13 0x00d368b2 in lyx::Inset::dispatch (this=0x2638790, cur=..., cmd=...) at /home/scott/lyxbuilds/master/build/src/insets/Inset.cpp:319 #14 0x00b2befb in lyx::Cursor::dispatch (this=0x35b8bf8, cmd0=...) at /home/scott/lyxbuilds/master/build/src/Cursor.cpp:409 #15 0x00e018a5 in lyx::frontend::GuiView::dispatchToBufferView ( this=0x16e9170, cmd=..., dr=...) at /home/scott/lyxbuilds/master/build/src/frontends/qt4/GuiView.cpp:3235 #16 0x00e04e1b in lyx::frontend::GuiView::dispatch (this=0x16e9170, cmd=..., dr=...) at /home/scott/lyxbuilds/master/build/src/frontends/qt4/GuiView.cpp:3774 Scott
GuiRef patches
Any comments on these?
Scott
From 699843541e552488f7cf7fdb3c348cb648e8944e Mon Sep 17 00:00:00 2001
From: Scott Kostyshak skost...@lyx.org
Date: Fri, 19 Apr 2013 07:48:26 -0400
Subject: [PATCH 1/4] GuiRef: only show No prefix if non-empty
If Group is checked, No prefix is shown only if there exists a
label with no prefix. Before, it was shown even when it was empty and
even when there were no labels at all.
---
src/frontends/qt4/GuiRef.cpp | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/src/frontends/qt4/GuiRef.cpp b/src/frontends/qt4/GuiRef.cpp
index c79dcb9..9e64750 100644
--- a/src/frontends/qt4/GuiRef.cpp
+++ b/src/frontends/qt4/GuiRef.cpp
@@ -350,19 +350,29 @@ void GuiRef::redoRefs()
QStringList refsStrings;
QStringList refsCategories;
vectordocstring::const_iterator iter;
+ bool noprefix = false;
for (iter = refs_.begin(); iter != refs_.end(); ++iter) {
QString const lab = toqstr(*iter);
refsStrings.append(lab);
- if (groupCB-isChecked() lab.contains(:)) {
- QString const pref = lab.split(':')[0];
- if (!pref.isEmpty() !refsCategories.contains(pref))
- refsCategories.append(pref);
+ if (groupCB-isChecked()) {
+ if (lab.contains(:)) {
+ QString const pref = lab.split(':')[0];
+ if (!refsCategories.contains(pref)) {
+ if (!pref.isEmpty())
+ refsCategories.append(pref);
+ else
+ noprefix = true;
+ }
+ }
+ else
+ noprefix = true;
}
}
// sort categories case-intensively
qSort(refsCategories.begin(), refsCategories.end(),
caseInsensitiveLessThan /*defined above*/);
- refsCategories.insert(0, qt_(No prefix));
+ if (noprefix)
+ refsCategories.insert(0, qt_(No prefix));
if (sortCB-isEnabled() sortCB-isChecked()) {
if(caseSensitiveCB-isEnabled() caseSensitiveCB-isChecked())
--
1.7.9.5
From cae16a25e077ecf373f3de34ec8dd540d0bebfbb Mon Sep 17 00:00:00 2001
From: Scott Kostyshak skost...@lyx.org
Date: Fri, 19 Apr 2013 07:48:15 -0400
Subject: [PATCH 2/4] GuiRef: do not hide labels that start with ':'
If a label starts with ':' and 'Group' is checked,
the label is now shown under No prefix instead of
not shown.
Note that labels starting with ':' can be valid in LaTeX.
---
src/frontends/qt4/GuiRef.cpp | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/frontends/qt4/GuiRef.cpp b/src/frontends/qt4/GuiRef.cpp
index 9e64750..15e6583 100644
--- a/src/frontends/qt4/GuiRef.cpp
+++ b/src/frontends/qt4/GuiRef.cpp
@@ -392,11 +392,11 @@ void GuiRef::redoRefs()
QString const ref = refsStrings.at(i);
if ((ref.startsWith(cat + QString(:)))
|| (cat == qt_(No prefix)
-!ref.contains(:))) {
- QTreeWidgetItem * child =
- new QTreeWidgetItem(item);
- child-setText(0, ref);
- item-addChild(child);
+ (!ref.mid(1).contains(:) ||
ref.left(1).contains(: {
+ QTreeWidgetItem * child =
+ new
QTreeWidgetItem(item);
+ child-setText(0, ref);
+ item-addChild(child);
}
}
refsCats.append(item);
--
1.7.9.5
From c654e5dad6cb9d08f388ab54a3b0379ea191a872 Mon Sep 17 00:00:00 2001
From: Scott Kostyshak skost...@lyx.org
Date: Fri, 19 Apr 2013 22:24:16 -0400
Subject: [PATCH 3/4] GuiRef: do not insert a category as a ref
Before, if a user had Group checked in GuiRef and double-clicked
on a category, that category would be inserted as a (broken)
reference. Now, when a category is double-clicked, nothing happens.
---
src/frontends/qt4/GuiRef.cpp |5 +
1 file changed, 5 insertions(+)
diff --git a/src/frontends/qt4/GuiRef.cpp b/src/frontends/qt4/GuiRef.cpp
index 15e6583..d3f68d5 100644
--- a/src/frontends/qt4/GuiRef.cpp
+++ b/src/frontends/qt4/GuiRef.cpp
@@ -162,6 +162,11 @@ void GuiRef::refSelected(QTreeWidgetItem * sel)
if (isBufferReadonly())
return;
+ if (sel-childCount()) {
+ sel
Re: Beamer goto buttons and text hyperlinks
On Sun, Apr 14, 2013 at 3:59 AM, Jürgen Spitzmüller sp...@lyx.org wrote: Looking at the docs, I'd propose to make beamergotobutton a flex inset within beamer.layout. The hyperref inset should be turned into a collapsable inset (while the dialog is being kept, minus the name field), \hyperlink support should be added to this inset (and \hypertarget to the label inset). And finally, the url inset should be merged into the hyperref inset. Do you think it's better to add \hyperlink support to the label inset or to make a separate, collapsable hypertarget inset? \hypertarget takes two arguments: the name and the text. The name could be set in the settings, and the text in the collapsable inset. How much of the Cross Reference inset should be copied to the hyperref inset? It seems like all of it, except the Format combo box. If we needed more room, we could also get rid of the filter, sort, etc. widgets, although they are just as relevant. Should labels and hypertargets have two separate tree widgets? Link type will now have four options: Web, Email, File, and the new one. What should the new one be called? text? hypertarget? When the new option is selected, the widgets copied over from the cross reference UI will be enabled. When one of the others is selected, they will be disabled. Any other thoughts? Scott
Re: [LyX master] Hungarian Tutorial.lyx: revert last change
On Tue, Apr 16, 2013 at 5:19 PM, Uwe Stöhr uwesto...@web.de wrote: Am 13.04.2013 20:45, schrieb Scott Kostyshak: Yes, what is the protocol for doc files in branch. You are doc maintainer and Richard is branch maintainer. Should I get the approval of both? For the doc files you can put it in if I give my OK - except Richard said explicitly no or branch is frozen. OK, it's in at 602fd0bb. This affects other files to, right? This particular change no. But I've made several changes to the examples recently. That is what I meant. To make sure, you are asking me to backport all of the recent changes I've made to the manuals and example files in trunk? Scott
Re: [LyX master] Also put HTML on the clipboard when copying
On Sat, Apr 20, 2013 at 7:15 PM, Richard Heck rgh...@lyx.org wrote: So what we really needed here is an updateMacros() call, but the other issue was that this only does what we need it to do---call recordLocation() to set docit_---if we are exporting the Buffer. So that had to be set, as well. The attached patch works for me, but there are some things about it that are a bit hackish at this point. I'll work on it a bit more and fix that problem. I tested after your recent commit (db358a43) and with the User's Guide open I do select all and copy, and I get The pasted branch Question is undefined. Do you want to add it to the document's branch list? Note that this message appears after a copy, before anything else. After clicking Add or Don't Add on the message box and the following ones, the copy seems to work. Then, if I do select all and copy again, I immediately get a SIGSEGV. Can anyone else reproduce this? Scott
Re: Interested in GSOC Project:
On Sun, Apr 21, 2013 at 11:04 AM, Hashini Senaratne hashz1...@gmail.com wrote: I was trying to sliding too long Labels for the past few days. I was able to learn many new things about painting methods and still interested to proceed with this project. After figuring out how the partial slides of current tables have been implemented (using the method void InsetTabular::resetPos(Cursor cur) const and also drwing methods of InsetTabular.cpp), I am trying to modify methods in other needed files. But I still did not find a way to how to activate an event that listen to mouse hovering. It seems like that LyX has not still used such actions. I am pleased if you can guide me with your experiences and knowledge. Hi Hashini, I need to look more at this code. Hopefully someone else has an answer to your question in the meantime. Also, I like to apply for this GSoC project. I went through the student application template that LyX has suggested. I like if I can submit it as a Wiki where I can update and modify with accordance to work I may do. Is it possible and what steps should I follow? If it is fine, is there a way to create a wiki page under LyX or is it okay to use other common wikis like mediawiki? I agree with Liviu's response to this question in the other thread. If it is not a good idea, in what format should I submit my application? I am asking about this from Jean too. I am not sure if he gets notifications for the mails under this thread. I think it is best not to duplicate conversations. People on this list generally find what's meant for them. If they don't, feel free to bump the email after a few days and explicitly CC them. Best, Scott
Re: GuiRef patches
On Sat, Apr 20, 2013 at 10:50 AM, Richard Heck rgh...@lyx.org wrote: On 04/20/2013 01:17 AM, Scott Kostyshak wrote: Any comments on these? Other than that they look good to me, no. They're in. Thanks, Scott
Re: [LyX master] Hungarian Tutorial.lyx: revert last change
On Sun, Apr 21, 2013 at 3:32 PM, Uwe Stöhr uwesto...@web.de wrote: Am 20.04.2013 07:51, schrieb Scott Kostyshak: To make sure, you are asking me to backport all of the recent changes I've made to the manuals and example files in trunk? I mean the changes where you encountered export problems and therefore set the default output format to pdf2. Ah, I'm glad I asked. OK I will look through the commits and cherry-pick the ones that set the default output format. I don't think it's always to pdf2. IIRC, some required format pdf. Scott
Re: [LyX master] Hungarian Tutorial.lyx: revert last change
On Mon, Apr 22, 2013 at 3:58 PM, Scott Kostyshak skost...@lyx.org wrote: On Sun, Apr 21, 2013 at 3:32 PM, Uwe Stöhr uwesto...@web.de wrote: Am 20.04.2013 07:51, schrieb Scott Kostyshak: To make sure, you are asking me to backport all of the recent changes I've made to the manuals and example files in trunk? I mean the changes where you encountered export problems and therefore set the default output format to pdf2. Ah, I'm glad I asked. OK I will look through the commits and cherry-pick the ones that set the default output format. I don't think it's always to pdf2. IIRC, some required format pdf. Done starting at edd91d5e. Scott
Re: Beamer goto buttons and text hyperlinks
On Tue, Apr 23, 2013 at 11:32 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 20/04/2013 09:06, Jürgen Spitzmüller a écrit : Scott Kostyshak wrote: Do you think it's better to add \hyperlink support to the label inset or to make a separate, collapsable hypertarget inset? \hypertarget takes two arguments: the name and the text. The name could be set in the settings, and the text in the collapsable inset. I'd prefer not to add too many different insets for similar functions. But the collapsable solution adds some convenience. We could maybe have an inset that is only a button when no extra text is needed and a collapsablme inset otherwise. Somethin in between InsetCommand and InsetCollapsable. I find this very interesting. If I understand correctly, it would work like this: When I go to insert label, it inserts a button and everything works exactly as it does now, except that if I click on the hypertarget checkbox in the label settings dialog, the button is now a collapsable inset. And if there is a selection, insert label can default to having the hypertarget checkbox checked and having that text put in the collapsable box. The current behavior when there is text selected is for the text to be deleted. Would we also want to do this for the cross ref inset? It could work in a similar way: there is a checkbox for hyperlink. If checked, the inset becomes a collapsable inset. Note that in this case more is done if hyperlinkCB is checked: the hypertargets would be shown along with the labels, either in the same tree widget (perhaps we could give the hypertargets a prefix so that when grouped it's easy to navigate) or there could be a split tree widget, more clearly separating labels from hypertargets. Jürgen, do you still prefer to have the cross ref code copied over to the hyperref inset? My hesitation is that there would be a lot of duplicate code. Also, I think that the text hyperlinks have more in common with references than they do with hrefs to web, emails, and files. However, I think your argument is that overloading the cross ref dialog would make the user experience more complicated and there would be a larger chance of a regression for this important part of the code. This makes sense to me also. Scott
Re: ps2pdf13 - ps2pdf14 ?
On Thu, Apr 11, 2013 at 5:20 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: 08/04/2013 08:04, Jürgen Spitzmüller: Scott Kostyshak wrote: I don't have any particular reason for changing it and the safe thing would be to leave it alone, but I'm curious what others think. My vote would be to use plain ps2pdf without any format binding. +1 It's in at 959d2c5. Scott
Re: [PATCH] Spelling: Postscript - PostScript
On Thu, Apr 11, 2013 at 3:46 AM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
11/04/2013 04:51, Scott Kostyshak:
From what I understand, PostScript is the correct way to write it.
Does anyone have an opinion on this?
Why not. If you go this way, git grep tells me that there are other places
needing attention.
Is the attached patch OK? I did not make the change in the translated
manuals. Should I? I don't know how the translation process works for
the manuals.
Scott
From d31db4ee94d433a9a57fe58e79a13a6f4e06ddb3 Mon Sep 17 00:00:00 2001
From: Scott Kostyshak skost...@lyx.org
Date: Wed, 10 Apr 2013 22:47:44 -0400
Subject: [PATCH] Spelling: Postscript - PostScript
---
lib/configure.py |6 +++---
lib/doc/EmbeddedObjects.lyx |2 +-
lib/doc/LaTeXConfig.lyx |2 +-
lib/doc/UserGuide.lyx |6 +++---
lib/examples/CV-image.eps |2 +-
lib/examples/ItemizeBullets.lyx |4 ++--
lib/examples/ca/ItemizeBullets.lyx|2 +-
lib/examples/es/ItemizeBullets.lyx|2 +-
lib/examples/fr/ListesPuces.lyx |2 +-
lib/examples/instant_preview.lyx |4 ++--
lib/examples/powerdot-example.lyx |4 ++--
lib/examples/seminar.lyx |4 ++--
lib/scripts/lyxpreview2bitmap.py |4 ++--
lyx.1in |2 +-
src/Length.h |2 +-
src/LyXAction.cpp |4 ++--
src/frontends/qt4/GuiDocument.cpp |2 +-
src/frontends/qt4/ui/PrefPrinterUi.ui |2 +-
src/graphics/GraphicsParams.cpp |4 ++--
src/graphics/epstools.cpp |2 +-
src/insets/InsetGraphics.cpp |4 ++--
src/tex2lyx/test/foo.eps |2 +-
22 files changed, 34 insertions(+), 34 deletions(-)
diff --git a/lib/configure.py b/lib/configure.py
index 946d8f7..3dbfc38 100644
--- a/lib/configure.py
+++ b/lib/configure.py
@@ -572,12 +572,12 @@ def checkFormatEntries(dtl_tools):
'nedit', 'gedit', 'notepad', 'geany', 'leafpad', 'mousepad'],
rc_entry = [r'''\Format bibtex bibBibTeX %%
text/x-bibtex''' ])
#
-#checkProg('a Postscript interpreter', ['gs'],
+#checkProg('a PostScript interpreter', ['gs'],
# rc_entry = [ r'\ps_command %%' ])
-checkViewer('a Postscript previewer', ['kghostview', 'okular', 'evince',
'gv', 'ghostview -swap'],
+checkViewer('a PostScript previewer', ['kghostview', 'okular', 'evince',
'gv', 'ghostview -swap'],
rc_entry = [r'''\Format epseps EPS
%%vectorimage/x-eps
\Format eps2 epsEPS (uncropped)%%
vector
-\Format ps ps Postscript t %%
document,vector,menu=export application/postscript'''])
+\Format ps ps PostScript t %%
document,vector,menu=export application/postscript'''])
# for xdg-open issues look here:
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg151818.html
# the MIME type is set for pdf6, because that one needs to be
autodetectable by libmime
checkViewer('a PDF previewer', ['pdfview', 'kpdf', 'okular', 'evince',
'kghostview', 'xpdf', 'acrobat', 'acroread', 'mupdf', \
diff --git a/lib/doc/EmbeddedObjects.lyx b/lib/doc/EmbeddedObjects.lyx
index 4dc2aa5..60ff0d3 100644
--- a/lib/doc/EmbeddedObjects.lyx
+++ b/lib/doc/EmbeddedObjects.lyx
@@ -41056,7 +41056,7 @@ You can export your document to PostScript using the
menu
\family sans
File\SpecialChar \menuseparator
Export\SpecialChar \menuseparator
-Postscript
+PostScript
\family default
.
You can view your document as PostScript via the
diff --git a/lib/doc/LaTeXConfig.lyx b/lib/doc/LaTeXConfig.lyx
index 53a123b..5a69841 100644
--- a/lib/doc/LaTeXConfig.lyx
+++ b/lib/doc/LaTeXConfig.lyx
@@ -6373,7 +6373,7 @@ Notes:
dvipost
\family default
is a post-processor for DVI files created by LaTeX and TeX.
- It is needed by LyX to generate DVI or Postscript output of change tracking
+ It is needed by LyX to generate DVI or PostScript output of change tracking
marks.
To work properly,
\family sans
diff --git a/lib/doc/UserGuide.lyx b/lib/doc/UserGuide.lyx
index 5caf0b1..75f7544 100644
--- a/lib/doc/UserGuide.lyx
+++ b/lib/doc/UserGuide.lyx
@@ -38667,7 +38667,7 @@ text
(ps2ascii)
\family default
- text format, the document will first be converted to Postscript format
+ text format, the document will first be converted to PostScript format
and then exported as text using the program
\family sans
ps2ascii
@@ -38676,7 +38676,7 @@ ps2ascii
\begin_layout Description
\family sans
-Postscript
+PostScript
\family default
PostScript format using the program
\family typewriter
@@ -38720,7 +38720,7 @@ PDF
\family default
or
\family sans
-Postscript
+PostScript
\family default
is missing, you need to update your LaTeX
Re: [LyX master] Audit all the LASSERT calls, and try to do something sensible at each failure.
On Thu, Apr 25, 2013 at 5:29 PM, Richard Heck rgh...@lyx.org wrote: The branch, master, has been updated. - Log - commit 1b1f8dd235ba8e168348cd23c824063f2595a0c5 Author: Richard Heck rgh...@lyx.org Date: Thu Apr 25 17:27:10 2013 -0400 Audit all the LASSERT calls, and try to do something sensible at each failure. There are several places I was not sure what to do. These are marked by comments beginning LASSERT: so they can be found easily. At the moment, they are at: Author.cpp:105: // LASSERT: What should we do here? Author.cpp:121: // LASSERT: What should we do here? Buffer.cpp:4525:// LASSERT: Is it safe to continue here, or should we just return? Cursor.cpp:345: // LASSERT: Is it safe to continue here, or should we return? Cursor.cpp:403: // LASSERT: Is it safe to continue here, or should we return? Cursor.cpp:1143:// LASSERT: There have been several bugs around this code, that seem CursorSlice.cpp:83: // LASSERT: This should only ever be called from an InsetMath. CursorSlice.cpp:92: // LASSERT: This should only ever be called from an InsetMath. LayoutFile.cpp:303: // LASSERT: Why would this fail? Text.cpp:995: // LASSERT: Is it safe to continue here? I'm getting an assertion now whenever I try to insert a table or graphics or float: ASSERTION false VIOLATED IN /home/scott/lyxbuilds/master/build/src/Paragraph.cpp:1853 Scott
Re: Changing sizes of GuiTabular combo boxes
On Thu, Apr 25, 2013 at 4:38 PM, Vincent van Ravesteijn v...@lyx.org wrote: Op 19-3-2013 8:43, Scott Kostyshak schreef: Make a table and go to the tabular settings. Toggle multicolumn or multirow and you'll see the combo boxes and the text box changing width because At Decimal Separator is no longer an option. This did not happen before. I think commit 6f157533 triggered this. I could not figure out how to prevent this behavior. Changing the horizontal policy did not seem to lead to a fix. If I set hAlignCO-setMinimumWidth() manually with a hard coded size then it works, but this is not a real solution. Any ideas? Thanks, Scott I fixed this at 262f58d. Works well. Thanks, Scott
Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error
On Thu, Apr 25, 2013 at 4:49 PM, Vincent van Ravesteijn v...@lyx.org wrote: Op 1-4-2013 6:07, Scott Kostyshak schreef: I think this is something I need to get used to: I would not have thought that this duplication of code (e.g. reparsing the string in the same way) was a good solution but I do see this a lot in C++ so it's something I need learn. What do you mean ? Checking whether a debug flag is valid and then setting that debug flag both involve looping through all the debug flags. When initially looking at this, the most natural thing seemed to me that there should be only one loop. But I think this separation of validation and processing is common in C++ and that I should learn to not worry about looping twice instead of once. Especially for such a small vector, this does not have any real performance issue. Besides performance though it still seems to me that the code could be more simple if there were just one loop. Is there a reason why it would be bad in this case to have one loop and throw an exception if a debug flag does not exist? Would it be reasonable to do a try/catch around lyxerr.setLevel(Debug::value(arg)) and obviate the need for Debug::isKnownValue(tmp) ? Scott
Re: \centerline{} support for wide graphics and tables
On Thu, Apr 25, 2013 at 3:33 PM, Vincent van Ravesteijn v...@lyx.org wrote:
Op 19-3-2013 4:35, Scott Kostyshak schreef:
When inserting a graphic or table whose width is larger than
\textwidth, the extra width spills over to the right margin. This
might be desired in some cases, but in other cases it is nice to
center the graphic or table on the page. Using \centerline{}, the
extra width is split evenly across the left and right margins.
The following .lyx file shows a couple of ways to address this:
http://paste.debian.net/242737/. One way is to sandwich the table or
graphic between '\centerline{' and '}' ERT boxes. Another way is to
use the adjustbox package. I'm not sure if there are advantages to one
over the other, but since \centerline does not require another
package, I propose to use it over the adjustbox package.
I would like to implement support for it in the tabular settings and
graphics settings as a check box.
The option could be labelled one of the following:
(1) center across both margins
(2) center on page across both margins
(3) center a wide table / center a wide graphic
It should be clear that this option is only used when the image is too wide.
If you want to implement this, you need to detect when an image is too
wide.. How do you plan to dot that ?
I was not planning on doing that. I was thinking that in many cases
the user knows when it is too large and would manually set this
option. There has been some very preliminary discussion (in the email
thread on the GSoC horizontal scrollbar project) of parsing the log
for specific overfull hboxes; but I do not think it makes sense to
automatically detect this and set \centerline without the user
knowing.
Scott
Re: Introducing myself to the community
On Fri, Apr 26, 2013 at 5:08 AM, Daan Janssens daan.co...@gmail.com wrote: Hello world! Sorry for filling you're inbox with this, but I would like to introduce myself properly, because I'm hoping for a long term relationship. My name is Daan Janssens and I'm in my 4th year of university majoring software engineering at the university of Antwerp, located in tiny Belgium. I won't start summing up all courses that I took, because I guess it's rather equivalent to any other first master year I guess. I do have 3 years of extinsive c++ learning experience and I'm also up to date with the majority of the new features of the c++11 standard. Perhaps the thing worth mentioning is my bachelor thesis, which was a project together with 4 other students, where we had to write increments on an already existing program that simulated virtual leaves, namely, how cells evolved in leafs. This was a project for the Biology department. And however the topic doesn't seem to match to Lyx, but the technology used did! We used Qt for GUI and threading, boost libraries and CMake, also GIT. So I guess the experience I got out of this could be very useful now! So what do I want to do as project? I want to write a 'Fast and useful toolbar customization dialog' For more information about the project, my motivation and driving force: please read my draft proposal, which I uploaded already. I'm hoping to get feedback on it soon, thanks in advance for reading it, cause I know it's quite big, but I really spend a lot of work on it :) If you got any question, feel free to ask. kind regards, Hi Daan, welcome! PS: is there a way to contact mentors without filling everyone's mailbox for every small question that I have, because irc seems quite dead to me. I think it is preferred to just send to the list. Even small questions are OK and others will probably benefit from the answers. Best, Scott
Re: \centerline{} support for wide graphics and tables
On Fri, Apr 26, 2013 at 10:46 AM, Vincent van Ravesteijn v...@lyx.org wrote: Op 26-4-2013 4:10, Scott Kostyshak schreef: On Thu, Apr 25, 2013 at 3:33 PM, Vincent van Ravesteijn v...@lyx.org wrote: Op 19-3-2013 4:35, Scott Kostyshak schreef: The option could be labelled one of the following: (1) center across both margins (2) center on page across both margins (3) center a wide table / center a wide graphic It should be clear that this option is only used when the image is too wide. If you want to implement this, you need to detect when an image is too wide.. How do you plan to dot that ? I was not planning on doing that. I was thinking that in many cases the user knows when it is too large and would manually set this option. There has been some very preliminary discussion (in the email thread on the GSoC horizontal scrollbar project) of parsing the log for specific overfull hboxes; but I do not think it makes sense to automatically detect this and set \centerline without the user knowing. Scott Usually we center images by centering the paragraph. This would then be another option that would confuse people, and I'm not overly enthusiastic about adding another option for a rare case that the user should try to avoid in the first place. Makes sense. A module would be a solution if someone wanted this built-in. Otherwise, I will forget about it. Scott
Re: [PATCH] (Incomplete) Nonexistent debug flag now throws an error
On Fri, Apr 26, 2013 at 10:54 AM, Vincent van Ravesteijn v...@lyx.org wrote: Op 26-4-2013 4:05, Scott Kostyshak schreef: On Thu, Apr 25, 2013 at 4:49 PM, Vincent van Ravesteijn v...@lyx.org wrote: Op 1-4-2013 6:07, Scott Kostyshak schreef: I think this is something I need to get used to: I would not have thought that this duplication of code (e.g. reparsing the string in the same way) was a good solution but I do see this a lot in C++ so it's something I need learn. What do you mean ? Checking whether a debug flag is valid and then setting that debug flag both involve looping through all the debug flags. When initially looking at this, the most natural thing seemed to me that there should be only one loop. But I think this separation of validation and processing is common in C++ and that I should learn to not worry about looping twice instead of once. Especially for such a small vector, this does not have any real performance issue. Besides performance though it still seems to me that the code could be more simple if there were just one loop. Is there a reason why it would be bad in this case to have one loop and throw an exception if a debug flag does not exist? Would it be reasonable to do a try/catch around lyxerr.setLevel(Debug::value(arg)) and obviate the need for Debug::isKnownValue(tmp) ? I hate throwing exceptions. Why? I have little experience with them so I don't know their disadvantages. If you can point me to a discussion of their faults, that would be great. I found some results by googling don't use exceptions c++ but I thought that you might have something in mind that's specific for this case. From what I remember, the authors of the Professional C++ book are in love with exceptions. I have no idea how highly/lowly regarded their opinions are. What is not simple about what I proposed ? simple wasn't the correct word. It is simple. It's just not what I would have first imagined because it duplicates code. What if how we loop through debug flags changes or there is a bug that is found in one of the loops? The other loop doesn't automatically change. Again, I'm not saying this is bad. I'm just trying to learn that this is not bad so that next time I come across such a problem I will recognize what the correct approach is. You shouldn't be worrying about performance in this kind of UI cases. It really doesn't care to do 40 checks compared to 20. The same holds for the issue in another thread about disabling controls on every character entered. In that box you typically enter a few characters, so a few extra loops are really not an issue.. never. I'm now convinced that performance is not an issue. I'm less convinced that readability and maintainability are better than using exceptions. I trust that you're right (and I see that what you're recommending here is common in many other parts of the code). I'm just trying to figure out why. What do you think of the most recent patch I posted? I think I implemented the important part of what you proposed. (http://permalink.gmane.org/gmane.editors.lyx.devel/145483) Thanks for the help, Scott
Re: [LyX master] Hungarian Tutorial.lyx: revert last change
On Tue, Apr 16, 2013 at 5:19 PM, Uwe Stöhr uwesto...@web.de wrote: This change should also go to branch: http://www.lyx.org/trac/changeset/912cbcdb/lyxgit (This was once my fault.) OK Richard? This is still pending. Should it go to branch? Scott
Re: Give me some bug please
On Sat, Apr 27, 2013 at 6:06 AM, Elmar Hinz t3el...@googlemail.com wrote: Hello, I practiced to complie the code with cmake. I set up my own LyX-mirror on github: https://github.com/t3elmar/Lyx By mirror do you mean that it will be updated automatically? Now I would like to fix some bugs. I am experienced with OOP and design patterns. I am not experienced with C++. Hence it should be some rather easy bugs just to get started. I have some buglettes in random notes that I wanted to eventually look at. I told someone else that I would organize them and post them. I will try to do that soon. I will put the 'easyfix' keyword on them in trac. These will be bugs that I think I will be able to guide someone to fixing if they get stuck. I am sure that there will be several that I misjudged and that are actually complicated bugs. But either (1) you'll learn stuff anyway or (2) someone will let us know that a bug is probably not an 'easyfix'. I'll try to do this within the next week. By the way, I is there an infrastucture for unit tests? Not really. There is structure for other kinds of tests though. There are export tests and autotests. Export tests test that a certain .lyx file can be exported in several formats (pdf via latex, pdf via pdflatex, pdf via luatex, and lyxhtml) with a zero error code return. Autotests try to simulate a user session. I think you need X installed. They open LyX and execute commands just like a user would. Since you are using CMake, maybe you can run the tests, although I don't know of anyone on a Mac who has done so. To try, run ctest. If the autotests fail, try to run only the export tests with ctest -R export. If you have an idea for implementing a unit test framework, I would be interested. I think it would be a lot of work though and that we aren't ready for it yet. Scott
Re: [LyX master] Also put HTML on the clipboard when copying
On Sun, Apr 21, 2013 at 3:22 PM, Georg Baum georg.b...@post.rwth-aachen.de wrote: Richard Heck wrote: There are a couple issues here. One is the problem of branches. Previously, we'd have pasted the copied paragraphs into the temporary Buffer, and with it whatever branch insets were in the copied material, not paying any attention at all to whether those branches existed, etc. I'm not sure what that would mean for what would end up on the clipboard. Probably we can just add a flag to the signature of pasteSelectionHelper() that means: don't ask about this, just do it (or not, which would be the old behavior). I'd simply create the branches. Does it have any drawback? The other issue is the sigsev. Here the problem is that the temporary Buffer we are using in putClipboard is static. So what we do to it remains from call to call. We clear the paragraphs, at the end of that routine, but we don't fully reset the Buffer's InsetText, which is why we get the crash. So if you remove the static keyword, the crash vanishes, but that does give a bit of a performance hit every time you copy something, because we have to create a new Buffer, with a new tempdir, and so forth. What we might want instead is a way to completely reset this temporary Buffer. Another option would be to keep the static (empty) Buffer and clone it each time, which ought to be cheap. I did this, and it works fine. By the way, I note that this copy is also very slow, because we are converting images to formats suitable for XHTML export, which never get used. We probably need another flag that means: don't do that, or bother creating math images, etc. We might also want to force math to be export as HTML, since the clipboard probably does not know what to do with MathML. I changed it to use MathML. Before copying HTML, only plaintext was copied, which did not play well to formulas at all. Now, there is at least the chance to recover formulas by applications that understand MathML (MS Office is supposed to understand it). If MathML is not understood, some applications (e.g. libreoffice) are still able to display the pure text, which is very similar to the plain text export. BTW, thanks for fixing the update problem. Is this still being worked on or is it supposed to be fixed? I still get SIGSEGVs. To reproduce, open Help Introduction, select all, and do ctrl + c and then ctrl + c again quickly after the first one. Or do ctrl + c, wait for the copy to finish, and then do ctrl + c twice more. Scott
Re: [LyX master] Also put HTML on the clipboard when copying
On Sun, Apr 28, 2013 at 4:26 PM, Vincent van Ravesteijn v...@lyx.org wrote: Op 28-4-2013 0:32, Scott Kostyshak schreef: On Sun, Apr 21, 2013 at 3:22 PM, Georg Baum georg.b...@post.rwth-aachen.de wrote: Richard Heck wrote: There are a couple issues here. One is the problem of branches. Previously, we'd have pasted the copied paragraphs into the temporary Buffer, and with it whatever branch insets were in the copied material, not paying any attention at all to whether those branches existed, etc. I'm not sure what that would mean for what would end up on the clipboard. Probably we can just add a flag to the signature of pasteSelectionHelper() that means: don't ask about this, just do it (or not, which would be the old behavior). I'd simply create the branches. Does it have any drawback? The other issue is the sigsev. Here the problem is that the temporary Buffer we are using in putClipboard is static. So what we do to it remains from call to call. We clear the paragraphs, at the end of that routine, but we don't fully reset the Buffer's InsetText, which is why we get the crash. So if you remove the static keyword, the crash vanishes, but that does give a bit of a performance hit every time you copy something, because we have to create a new Buffer, with a new tempdir, and so forth. What we might want instead is a way to completely reset this temporary Buffer. Another option would be to keep the static (empty) Buffer and clone it each time, which ought to be cheap. I did this, and it works fine. By the way, I note that this copy is also very slow, because we are converting images to formats suitable for XHTML export, which never get used. We probably need another flag that means: don't do that, or bother creating math images, etc. We might also want to force math to be export as HTML, since the clipboard probably does not know what to do with MathML. I changed it to use MathML. Before copying HTML, only plaintext was copied, which did not play well to formulas at all. Now, there is at least the chance to recover formulas by applications that understand MathML (MS Office is supposed to understand it). If MathML is not understood, some applications (e.g. libreoffice) are still able to display the pure text, which is very similar to the plain text export. BTW, thanks for fixing the update problem. Is this still being worked on or is it supposed to be fixed? I still get SIGSEGVs. To reproduce, open Help Introduction, select all, and do ctrl + c and then ctrl + c again quickly after the first one. Or do ctrl + c, wait for the copy to finish, and then do ctrl + c twice more. Scott I hope I fixed this issue today. Vincent Thanks Vincent, I no longer get a crash. I still have the following issues (let me know if I should open up tickets): - When selecting all and copying UserGuide.lyx, I get the dialogs mentioned before. - When selecting all and copying Addional.lyx, I get the following message: LyX does not know how to include non-LyX files when generating HTML output. Offending file: SpecialParagraphShape.tex - When selecting all and copying EmbeddedObjects.lyx, I get the following errors: File '/tmp/lyx_tmpdir.n11551/DummyTextDocument.txt' is not readable! support/FileName.cpp (732): File '/tmp/lyx_tmpdir.n11551/DummyTextDocument.txt' is not readable! support/FileName.cpp (732): File '/tmp/lyx_tmpdir.n11551/EmbeddedObjects.lyx' is not readable! Scott
Re: GSoC Project: Horizontal scrollbar in table and math
On Sun, Apr 28, 2013 at 9:28 PM, Mandeep Simak meghasi...@gmail.com wrote: Hello, I am Mandeep Kaur, student of GNDEC, Ldh pusuing B.Tech. in Information Technology. I know C++ and CGI with C++. I am currently working on project BaKaPlan i.e. in C++ using CGI https://github.com/GreatDevelopers/bakaplan/tree/Next I am interested in LyX project to add horizontal scrollbar in table and math. Can you guide me? Thanks. Hi Mandeep, welcome! Please see this lengthy thread for information on the horizontal scrollbar project: http://comments.gmane.org/gmane.editors.lyx.devel/145717 For the GSoC side of things, please see this link: http://www.google-melange.com/gsoc/org/google/gsoc2013/lyx Best, Scott
Re: DIFFICULTY WITH PASTING IMAGE IN LYX
On Wed, May 1, 2013 at 12:03 PM, Kamal Garg kmlgrg2...@gmail.com wrote: I know Only one way of pasting pictures in lyx, that is by selecting insert graphic option in toolbar.(shown in image) i am trying to copy image(*.jpg).but direct simple way:ctrl+c(copying ) from my folder of pictures and ctrl+v (paste)for pasting image in lyx is not working. Sir, if there is another way of doing the same,then let me know. Hi Kamal, It would be better if you reply within the same email thread (instead of creating a new one). You already posted an email and Vincent responded to it. What do you mean by not working? It's popping up that dialog because for LyX to include an image it has to first save it somewhere. So it might be asking you where to save it. Scott
Re: not available in lyx
Can you send a .lyx minimal example file (http://wiki.lyx.org/FAQ/MinimalExample) ? Scott On Wed, May 1, 2013 at 12:12 PM, Kamal Garg kmlgrg2...@gmail.com wrote: not available in lyx whixh i shown in image with black circle(i edit this image gimp image editor).so this image open only with it.
Re: [LyX master] Also put HTML on the clipboard when copying
On Mon, Apr 29, 2013 at 5:36 PM, Richard Heck rgh...@lyx.org wrote: On 04/29/2013 04:03 PM, Georg Baum wrote: - When selecting all and copying UserGuide.lyx, I get the dialogs mentioned before. This is known. I asked whether these branches should just be created, but got no reply so far. If the answer is yes, this problem is easy to fix. I would say yes, as well. Though we need, as I said before, some kind of flag to signal that we are copying, not exporting. We actually need the same flag, I think, for generation of ViewSource code. So it may be a more general issue. Or else maybe we already have some such flag we can use. I'm not sure. After your recent comment, this issue seems to have been solved. I'm not sure if the following is LyX's problem or not. If I open LyX from the terminal (on Ubuntu 12.04) and copy the User Guide and exit, the LyX window closes but LyX still hasn't exited (the terminal is still busy). After about 5 seconds I get the following message on the terminal QClipboard: Unable to receive an event from the clipboard manager in a reasonable time and then LyX exits. Now if I start LyX again and exit (without doing anything) I again get the pause and the QClipboard message. The only way I can get rid of this is to restart the computer or running the following command: killall gnome-settings-daemon Note that the copy also issued this message to the terminal: Warning: latex had problems compiling 0lyxpreview.tex Can anyone reproduce this? Is this a Qt bug? An Ubuntu bug? Scott
Re: Export XHTML and Branches
On Fri, May 3, 2013 at 8:47 AM, Richard Heck rgh...@lyx.org wrote: On 05/03/2013 03:03 AM, Jean-Louis GALLINARI wrote: There were some branch problems in earlier versions. Please try something more current. If Ubuntu does not have the current version, there is a PPA that provides it somewhere. http://wiki.lyx.org/LyX/LyXOnUbuntu#toc3 Scott
Re: Appendix sections are numbered incorrectly on screen (but do appear correctly on DVI/PDF)
On Fri, May 3, 2013 at 1:48 PM, José Matos jama...@lyx.org wrote: The problem is that the section counter is not reset when the appendix starts in the lyx view but it is reset in the output. Honestly I am not sure if we have changed anything here recently, so I am not sure if this a bug or a missing feature. :-) This is a regression. I will do a bisect. Scott
Re: Appendix sections are numbered incorrectly on screen (but do appear correctly on DVI/PDF)
On Fri, May 3, 2013 at 2:28 PM, Scott Kostyshak skost...@lyx.org wrote: On Fri, May 3, 2013 at 1:48 PM, José Matos jama...@lyx.org wrote: The problem is that the section counter is not reset when the appendix starts in the lyx view but it is reset in the output. Honestly I am not sure if we have changed anything here recently, so I am not sure if this a bug or a missing feature. :-) This is a regression. I will do a bisect. The bisect led me to the following commit: commit 894569e601ea1e0acb1adf92a0f168c10d6577dc Author: Richard Heck rgh...@lyx.org Date: Sat Jul 21 14:14:12 2012 -0400 Fix a long-standing FIXME by resetting only the counter for top-level sectioning when we see an appendix. This fixes bug #8271, whose root cause was the fact that we were resetting all the counters inside ERT. Note that this commit is also in branch, at ecb65e70 Scott
Server down?
The server is unresponsive for me. Can anyone else reproduce? Scott
Re: Server down?
On Mon, May 6, 2013 at 2:39 PM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 06/05/13 19:16, Scott Kostyshak a écrit : The server is unresponsive for me. Can anyone else reproduce? It wors for me. Is it better now? Yes, everything is working well now. Scott
Re: Beamer goto buttons and text hyperlinks
On Tue, Apr 23, 2013 at 11:32 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: We could maybe have an inset that is only a button when no extra text is needed and a collapsablme inset otherwise. Somethin in between InsetCommand and InsetCollapsable. How difficult would it be to implement this new inset? Scott
Re: DIFFICULTY WITH PASTING IMAGE IN LYX
On Wed, May 1, 2013 at 1:26 PM, Vincent van Ravesteijn v...@lyx.org wrote: Op 1-5-2013 18:03, Kamal Garg schreef: I know Only one way of pasting pictures in lyx, that is by selecting insert graphic option in toolbar.(shown in image) i am trying to copy image(*.jpg).but direct simple way:ctrl+c(copying ) from my folder of pictures and ctrl+v (paste)for pasting image in lyx is not working. Sir, if there is another way of doing the same,then let me know. This is indeed not working. It's a missing feature. It's probably not so difficult to implement. There is another way to do this. You can drag the image from the explorer onto the LyX window and paste it like this. Kamal, Can you file an enhancement request for this? http://www.lyx.org/trac Scott
R Journal template and layout
Can I commit a layout and template for the R Journal? Information on the journal is here: http://journal.r-project.org/ Yihui made the files and I've tweaked and tested them. They are here: https://github.com/yihui/lyx/blob/master/templates/RJournal.lyx https://github.com/yihui/lyx/blob/master/layouts/RJournal.layout Scott
Should the 2.1 milestone be dropped or changed to 2.2?
Now that LyX 2.1 is coming up, many tickets are being dealt with. For these tickets, if they aren't likely to make it into 2.1, the milestone is being dropped. Is this what's normally done? I was expecting the milestone to be changed to 2.2. Is it correct that the tickets with milestone 2.1 that don't make it into to 2.1 will not be treated like tickets with no milestone? Perhaps this is a good thing. This would force us to think about all of the milestones of all unmarked tickets. There are probably some old tickets that are being ignored that should have been marked with a milestone. Scott
Re: Should the 2.1 milestone be dropped or changed to 2.2?
On Mon, May 13, 2013 at 10:25 AM, Richard Heck rgh...@lyx.org wrote: On 05/13/2013 10:17 AM, Scott Kostyshak wrote: Perhaps this is a good thing. This would force us to think about all of the milestones of all unmarked tickets. There are probably some old tickets that are being ignored that should have been marked with a milestone. I think that's the idea: that we re-think all the targeted bugs and decide if they really should be targeted. In this case, it might be good to have a 'someday' milestone. Otherwise, there is no way to list in trac which tickets have a milestone that has been evaluated versus which tickets have not been evaluated. Many tickets without milestones were evaluated and decided as not being important for the near future. It should be able to mark these as such instead of using 'not marking them' to serve that function. Scott
Re: Should the 2.1 milestone be dropped or changed to 2.2?
On Mon, May 13, 2013 at 1:52 PM, Pavel Sanda sa...@lyx.org wrote: Scott Kostyshak wrote: Is it correct that the tickets with milestone 2.1 that don't make it into to 2.1 will not be treated like tickets with no milestone? It depends, many enhacenment bugs are there for years and no one is going to touch them. Milestone has some meaning if there is reason to believe that someone is working on it, I think the milestone should also be set if someone *should* be working on it. There are some bugs that I report/modify that are not in my comfort area of the code or are too advanced for me to fix. However, I think they should be fixed soon and I would like to be able to mark them as such. otherwise you have just zillion entries. After some threshold such milestone stops to have any meaning and thats what already happened with 2.1. Agreed. So if you see some bug you are particularly interested in and perhaps fix it, feel free to retarget 2.2. OK. Scott
Re: Should the 2.1 milestone be dropped or changed to 2.2?
On Mon, May 13, 2013 at 2:10 PM, Pavel Sanda sa...@lyx.org wrote: Scott Kostyshak wrote: I think the milestone should also be set if someone *should* be working on it. There are some bugs that I report/modify that are not I'm afraid that number of bugs that we consider *someone else* should really do it is already 4*zillion ;) But there should be some way to specify urgency. 'Priority' seems determined by other variables so is not used for this. Anyways, I won't fight this anymore, except that however milestone is used, I think it should be used the same by everyone. If there's inconsistent treatment across time (e.g. *if* in transition from 2.0 to 2.1 all tickets with milestone 2.0 are changed to 2.1 but in 2.1 to 2.2 all tickets with milestone 2.1 now have no milestone) or across people, then it's meaning becomes less useful. Scott
Re: #8675: Tex2lyx reports errors when importing latex from an internal disk mounted
On Thu, May 16, 2013 at 1:11 AM, Xavier Ouvrard Brunet xavier.ouvr...@libertysurf.fr wrote: #8675: Tex2lyx reports errors when importing latex from an internal disk mounted Since you're on Ubuntu, can you use the PPA to see if this is reproducible on the development versions Whith the build from May 15 2013 12:36, I can browse to the tex and it starts to open (it asks if I want to overwrite an already .lyx with the same name, but it's the same if there's not already a converted file), then I have : An error occured while running : /usr/bin/tex2lyx -f nameoffile.tex nameoffile.lyx If I put the tex file in home, then it works properly. Best regards, Xavier Thanks for doing that, Xavier. There should be more output written to STDERR that explains why tex2lyx is failing. Can you run LyX from the terminal and look at the output there after the error? Or look in View Messages inside LyX? If there is not a more informative error, you've discovered another bug. Can you please post the reply you sent by email directly to the tracker? Also, any other messages you have should be posted there. To do that, log in and click on the reply button here: http://www.lyx.org/trac/ticket/8675 Best, Scott
Re: #8675: Tex2lyx reports errors when importing latex from an internal disk mounted
On Thu, May 16, 2013 at 1:16 PM, Xavier Ouvrard Brunet xavier.ouvr...@libertysurf.fr wrote: On 16/05/2013 18:35, LyX Ticket Tracker wrote: #8675: Tex2lyx reports errors when importing latex from an internal disk mounted -+- Reporter: xouv | Owner: lasgouttes Type: defect | Status: new Priority: normal | Milestone: 2.0.7 Component: general | Version: 2.0.3 Severity: normal | Resolution: Keywords: | -+- Comment (by skostysh): Xavier, do you have write permissions to the internal disk? I wonder if you are running into #8236. I have permissions on it, it's where I store all my personnal data (it's a mounted partition from my internal disk). I didn't change anything apart upgrading from Ubuntu 12.04 to 13.04. On Data, I used to have : Owner : create and delete files Group : access files Others : access files I put : Owner : create and delete files Group : create and delete files Others : access files I know that in Ubuntu 12.10 they changed the point where the disks are mounted, putting it in \media\username\nameofmount. Before 12.10, it was : \media\nameofmount Best regards, Xavier Xavier, Can you please post to the LyX ticket all of the information you've written in emails? If not, your information might be lost in a few days. To do so, go here: http://www.lyx.org/trac/ticket/8675 Thanks, Scott
LyX convention for squash vs. merge/rebase?
I'm about to commit a layout and template for the R Journal. I'm not sure whether I should make one commit or a series of commits. On the one hand, a series of commits gives more information about how the layout and template were developed and the commits document the decisions that were made. My thought is that for this case I will commit the series because I'm not confident in all of the decisions I made. This way it will be easier for someone who knows more about layouts to correct a poor decision I made (e.g. revert one of the commits). On the other hand, I'm not sure the advantages of multiple commits are worth the extra noise. Is there any convention for this for LyX development? If not, any personal opinions or advice? The commit history for this specific case can be viewed here: https://github.com/yihui/lyx/commits/master/layouts Scott
Re: LyX convention for squash vs. merge/rebase?
On Thu, May 16, 2013 at 8:34 PM, Cyrille Artho c.ar...@aist.go.jp wrote: Hi Scott, IMHO many small commits are almost always a lot better. git bisect can be very useful in tracking down problems when you have many small commits. With a single huge commit, that feature is almost useless. This benefit alone outweighs the small drawback of having multiple commit messages. (If you used meaningful messages during your commits, they in themselves can also be helpful.) Thanks for your comments Cyrille. I committed the series here: 0d434033..43d71022 I'd still be interested in what others prefer for the future. Scott Scott Kostyshak wrote: I'm about to commit a layout and template for the R Journal. I'm not sure whether I should make one commit or a series of commits. On the one hand, a series of commits gives more information about how the layout and template were developed and the commits document the decisions that were made. My thought is that for this case I will commit the series because I'm not confident in all of the decisions I made. This way it will be easier for someone who knows more about layouts to correct a poor decision I made (e.g. revert one of the commits). On the other hand, I'm not sure the advantages of multiple commits are worth the extra noise. Is there any convention for this for LyX development? If not, any personal opinions or advice? The commit history for this specific case can be viewed here: https://github.com/yihui/lyx/commits/master/layouts Scott -- Regards, Cyrille Artho - http://artho.com/ They are ill discoverers that think there is no land, when they can see nothing but sea. -- Francis Bacon
Re: R Journal template and layout
On Sun, May 12, 2013 at 5:07 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 12/05/2013 07:22, Scott Kostyshak a écrit : Can I commit a layout and template for the R Journal? Information on the journal is here: http://journal.r-project.org/ Yihui made the files and I've tweaked and tested them. They are here: https://github.com/yihui/lyx/blob/master/templates/RJournal.lyx https://github.com/yihui/lyx/blob/master/layouts/RJournal.layout Yes, this makes sense. Committed in the following series: 0d434033..43d71022 Scott
Re: LyX convention for squash vs. merge/rebase?
On Fri, May 17, 2013 at 3:42 AM, Vincent van Ravesteijn v...@lyx.org wrote: A separate thing is that we might want to merge in such a change. That would cause the master branch to have much fewer commits (if you use --first-parent-only). OK, I would like to start doing this because it is the most informative of how the development happened. In addition to preserving the thought process, it also shows what commit I was working off of. Why would it be interesting what commit you were working off of ? I don't have any real examples in mind. But I figure it could be useful to know what features and bugs were present at the time a developer started the branch. It might explain why the developer made certain decisions (e.g. workarounds for bugs that were maybe fixed in the meantime). But I've seen some LyX developers express a distaste for an empty (which really it is not) merge commit. For example, in the following link at several points it recommends rebasing over merging: http://wiki.lyx.org/Devel/Git AFAICS it only mentions that you should not create a merge commit because you pulled the new master in. This is just an error, and these merges are only annoying. OK, I see the distinction now. Scott
Re: [LyX master] Fix assertion for InsetInfos of icon types
On Sun, Apr 28, 2013 at 3:50 PM, Vincent van Ravesteijn v...@lyx.org wrote:
The branch, master, has been updated.
- Log -
commit 361995459068a5e53b597f1195f7f29522714ec4
Author: Vincent van Ravesteijn v...@lyx.org
Date: Sun Apr 28 21:47:37 2013 +0200
Fix assertion for InsetInfos of icon types
InsetInfo inserted insets in its text without specifying a font. This
caused the fonlist to be incomplete and firing the assertion.
I cannot export the Spanish User Guide with pdflatex. A bisect led me here.
I get the errors
! Missing } inserted.
and then several
! Package amsmath Error: \acute allowed only in math mode.
I can post the diff of the before/after exported pdflatex files but it
is 800 lines. A lot of it is switching languages to English for the
includegraphics:
\item \textsf{Imprimir
\includegraphics{/home/scott/lyxbuilds/master/build/lib/images/buffer-write}}
---
\item \textsf{Imprimir \selectlanguage{english}%
\includegraphics{/home/scott/lyxbuilds/master/build/lib/images/buffer-write}\selectlanguage{spanish}%
}
Any thoughts?
Scott
Re: [LyX master] UserGuide.lyx: first step of revision
2013/4/16 Uwe Stöhr uwesto...@lyx.org: The branch, master, has been updated. - Log - commit 458b3bad107a988db4c0f963dde4576a3ae337d9 Author: Uwe Stöhr uwesto...@lyx.org Date: Wed Apr 17 01:13:49 2013 +0200 UserGuide.lyx: first step of revision - first step of the revision of the English UserGuide from John Hudson I get \endcsname errors when exporting the German User Guide to PDF with pdflatex. Bisect led me here. Scott
Re: examples/landslide.lyx: can't export with pdflatex because of bounding box
On Sun, Apr 14, 2013 at 3:38 AM, Scott Kostyshak skost...@lyx.org wrote: Exporting via ps2pdf works fine, but pdflatex and luatex fail. I think pdflatex fails because of converting the eps to pdf. I thought I had fixed a similar error before with the following: epstool --copy --bbox platypus.eps --output platypus2.eps But this did not help. Any ideas? Any thoughts? If not, I will set the default output to ps2pdf. Scott
font encoding problem with AEA template
The AEA template has the following instructions: Choose LaTeX font encoding to None (no fontenc) in menu Document=Settings=Fonts This gets rid of an error that I get if I do not do that (I can't find file `dcr10'.) but now I get the following error: ! LaTeX Error: Command \textquotedbl unavailable in encoding OT1. This happens because of the quotes in Do not use an Introduction heading. It seems several LyX users have had trouble with this template. The class file must be tricky. http://lyx.475766.n2.nabble.com/American-Economic-Association-class-td4394278.html http://comments.gmane.org/gmane.editors.lyx.general/67053 http://comments.gmane.org/gmane.editors.lyx.general/62367 http://comments.gmane.org/gmane.editors.lyx.general/73805 Any ideas? Scott
Re: examples/es/europeCV.lyx: can't export with luatex
On Sun, Apr 14, 2013 at 3:39 AM, Scott Kostyshak skost...@lyx.org wrote: I get utf-8 and utf8x errors. Is there a fix for this while preserving export with pdflatex and latex? Any ideas? Scott
Re: broken examples?
On Mon, Apr 8, 2013 at 12:35 AM, Scott Kostyshak skost...@lyx.org wrote:
On Mon, Feb 18, 2013 at 2:33 AM, Scott Kostyshak skost...@lyx.org wrote:
On Sun, Feb 17, 2013 at 8:57 AM, Jürgen Spitzmüller sp...@lyx.org wrote:
Scott Kostyshak wrote:
listerrors.lyx
ps2pdf works well
pdflatex and luatex fail (lots of undefined control sequences)
! Package hyperref Error: Wrong DVI mode driver option `ps2pdf',
(hyperref)because pdfTeX or LuaTeX is running in PDF mode.
The issue here is a hardcoded
\usepackage[ps2pdf,pdftitle={LyX listerrors re-
implemented},urlcolor=blue,linktocpage,letterpaper,colorlinks=true]{hyperref}
in the preamble. This is bound to fail with pdfTeX and luatex. I cannot
compile the document due to missing noweb.sty, but is the explicit driver
really needed? If so, the \ifpdf check from the ifpdf package should be
used.
If not, LyX's natie PDF support can be used.
I have no idea. I know nothing about noweb. I'm CC'ing Kayvan.
Scott
Kayvan,
Do you have any advice here? Is it intended to work only with plain LaTeX?
I set the default output format to ps2pdf at 7aba4d51. It seems that
this was the original intent.
Scott
Re: #2757: bibtex errors not reported
On Thu, Apr 25, 2013 at 10:18 AM, LyX Ticket Tracker t...@lyx.org wrote:
#2757: bibtex errors not reported
I wonder if this wasn't implemented because it doesn't fit exactly with
the purpose of ErrorListUi because the BibTeX errors are not associated
with lines in the LyX file. It seems like that would be the right place
though. scanLogFile() would need to be created and some minor tweaks might
be needed, such as changing the tooltip (for this particular case) from
{{{
Selecting an error will show the error message in the panel below,
and jump the cursor to the location in the document where the error
occured.
}}}
to
{{{
Selecting an error will show the error message in the panel below.
}}}
and no jump would be done.
Any thoughts on this?
Any thoughts on this?
Scott
Re: Re: DocBook converters (no knowledge of DocBook required)
On Fri, Apr 12, 2013 at 6:31 PM, José Matos jama...@lyx.org wrote: On Wednesday 10 April 2013 22:05:09 Scott Kostyshak wrote: The patch attached fixes the first problem you describe the DUMMY references (pun intended). :-D I will try to chase and fix the others. Hi José, here are some more errors for you to chase :) I get these when trying to export AGU_article.lyx to ps2pdf. Also note that another problem is that LyX hangs for me when trying to export AGU_article.lyx to ps2pdf. It would be nice if it exited with an error. /usr/bin/openjade:/tmp/tmpDEz69Q:6:1:E: cannot find AGU-Article-3.42.dtd; tried /tmp/AGU-Article-3.42.dtd, /tmp/lyx_tmpdir.n23782/lyx_tmpbuf0/AGU-Article-3.42.dtd, /usr/share/sgml/AGU-Article-3.42.dtd /usr/bin/openjade:/tmp/tmpDEz69Q:6:1:E: DTD did not contain element declaration for document type name /usr/bin/openjade:/tmp/tmpDEz69Q:10:18:E: there is no attribute LANG /usr/bin/openjade:/tmp/tmpDEz69Q:10:22:E: element AGU-ARTICLE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:11:7:E: element HEADER undefined /usr/bin/openjade:/tmp/tmpDEz69Q:13:26:E: there is no attribute JOURNAL-CODE /usr/bin/openjade:/tmp/tmpDEz69Q:13:47:E: there is no attribute ELECTRONIC-ONLY /usr/bin/openjade:/tmp/tmpDEz69Q:13:52:E: element AGU-JOURNAL undefined /usr/bin/openjade:/tmp/tmpDEz69Q:14:5:E: element ISSN undefined /usr/bin/openjade:/tmp/tmpDEz69Q:14:28:E: element CODEN undefined /usr/bin/openjade:/tmp/tmpDEz69Q:15:30:E: element SPECIAL-SECTION undefined /usr/bin/openjade:/tmp/tmpDEz69Q:16:8:E: element SS-CODE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:16:34:E: element SS-TITLE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:17:29:E: element AGU-VOLUME undefined /usr/bin/openjade:/tmp/tmpDEz69Q:18:7:E: element VOLUME undefined /usr/bin/openjade:/tmp/tmpDEz69Q:18:23:E: element YEAR undefined /usr/bin/openjade:/tmp/tmpDEz69Q:19:23:E: element AGU-ISSUE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:20:13:E: element ISSUE-NUMBER undefined /usr/bin/openjade:/tmp/tmpDEz69Q:20:40:E: element ISSUE-DAY undefined /usr/bin/openjade:/tmp/tmpDEz69Q:20:68:E: element ISSUE-MONTHS undefined /usr/bin/openjade:/tmp/tmpDEz69Q:21:21:E: element RECEIVED undefined /usr/bin/openjade:/tmp/tmpDEz69Q:22:4:E: element DAY undefined /usr/bin/openjade:/tmp/tmpDEz69Q:22:19:E: element MONTH undefined /usr/bin/openjade:/tmp/tmpDEz69Q:22:34:E: element YEAR undefined /usr/bin/openjade:/tmp/tmpDEz69Q:23:19:E: element REVISED undefined /usr/bin/openjade:/tmp/tmpDEz69Q:24:4:E: element DAY undefined /usr/bin/openjade:/tmp/tmpDEz69Q:24:17:E: element MONTH undefined /usr/bin/openjade:/tmp/tmpDEz69Q:24:31:E: element YEAR undefined /usr/bin/openjade:/tmp/tmpDEz69Q:25:19:E: element ACCEPTED undefined /usr/bin/openjade:/tmp/tmpDEz69Q:26:4:E: element DAY undefined /usr/bin/openjade:/tmp/tmpDEz69Q:26:17:E: element MONTH undefined /usr/bin/openjade:/tmp/tmpDEz69Q:26:31:E: element YEAR undefined /usr/bin/openjade:/tmp/tmpDEz69Q:27:25:E: element POSTING-ORDER undefined /usr/bin/openjade:/tmp/tmpDEz69Q:29:26:E: element AGU-PAGES undefined /usr/bin/openjade:/tmp/tmpDEz69Q:31:18:E: element WORDS undefined /usr/bin/openjade:/tmp/tmpDEz69Q:33:16:E: element FIGURES undefined /usr/bin/openjade:/tmp/tmpDEz69Q:35:17:E: element TABLES undefined /usr/bin/openjade:/tmp/tmpDEz69Q:37:18:E: element DATASETS undefined /usr/bin/openjade:/tmp/tmpDEz69Q:39:21:E: element COPYRIGHT undefined /usr/bin/openjade:/tmp/tmpDEz69Q:40:8:E: element ODE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:40:55:E: element YEAR undefined /usr/bin/openjade:/tmp/tmpDEz69Q:41:23:E: element IDENT-LINE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:43:21:E: element RUNHEAD undefined /usr/bin/openjade:/tmp/tmpDEz69Q:45:22:E: element INDEX-TERMS undefined /usr/bin/openjade:/tmp/tmpDEz69Q:47:11:E: element INDEX-TERM undefined /usr/bin/openjade:/tmp/tmpDEz69Q:48:5:E: element CODE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:48:21:E: element DSCR undefined /usr/bin/openjade:/tmp/tmpDEz69Q:49:24:E: element INDEX-TERM undefined /usr/bin/openjade:/tmp/tmpDEz69Q:50:5:E: element CODE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:50:18:E: element DSCR undefined /usr/bin/openjade:/tmp/tmpDEz69Q:51:36:E: element KEYWORDS undefined /usr/bin/openjade:/tmp/tmpDEz69Q:52:8:E: element KEYWORD undefined /usr/bin/openjade:/tmp/tmpDEz69Q:52:32:E: element KEYWORD undefined /usr/bin/openjade:/tmp/tmpDEz69Q:53:23:E: element SUP-MAT-REF undefined /usr/bin/openjade:/tmp/tmpDEz69Q:55:13:E: element SUP-MAT-NOTE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:57:6:E: there is no attribute ID /usr/bin/openjade:/tmp/tmpDEz69Q:57:13:E: element P undefined /usr/bin/openjade:/tmp/tmpDEz69Q:57:59:E: element CITE-OTHER undefined /usr/bin/openjade:/tmp/tmpDEz69Q:59:39:E: element SUP-MAT-REF undefined /usr/bin/openjade:/tmp/tmpDEz69Q:61:13:E: element SUP-MAT-NOTE undefined /usr/bin/openjade:/tmp/tmpDEz69Q:63:13:E: element P undefined /usr/bin/openjade:/tmp/tmpDEz69Q:63:80:E: element AFFILIATION undefined /usr/bin/openjade:/tmp/tmpDEz69Q:64:7:E
Re: font encoding problem with AEA template
On Sat, May 18, 2013 at 2:49 PM, Uwe Stöhr uwesto...@web.de wrote: Am 18.05.2013 02:45, schrieb Scott Kostyshak: I updated the file now according to the current AEA submission guidelines. For LyX 2.1 I also modified the layout file by adding the 4 missing styles required by the submission guidelines. I will now also update our Wiki page. Great, thanks for doing that! All tests pass. Scott
Re: examples/landslide.lyx: can't export with pdflatex because of bounding box
On Sat, May 18, 2013 at 10:01 PM, Uwe Stöhr uwesto...@web.de wrote: Am 18.05.2013 14:34, schrieb Uwe Stöhr: I can compile the file using pdflatex. After Kornel's mail I had a closer look ant it indeed failed on my laptop. It turned out that the additional graphics driver was the problem. dvips is already declared as driver in the layout file but the example file added it too. I committed the fix together with a better spacing of the image, please test if you can now also compile with pdflatex. Compiles fine with pdflatex and luatex. Thanks for the fix, Scott
Re: [LyX master] Fix assertion for InsetInfos of icon types
On Sun, May 19, 2013 at 7:21 AM, Vincent van Ravesteijn v...@lyx.org wrote: Op 17-5-2013 21:53, Scott Kostyshak schreef: On Sun, Apr 28, 2013 at 3:50 PM, Vincent van Ravesteijn v...@lyx.org wrote: I cannot export the Spanish User Guide with pdflatex. A bisect led me here. Any thoughts? Scott Fixed with f8a5d7c..30f5187. The tests pass, thanks. Scott
regression: Chinese tutorial no longer exports (missing babel and language option)
The commit that git bisect lead me to and the diff between the
pdflatex .tex files of before and after the following commit (which is
the same as the diff between the output from before and current trunk)
is pasted below. After adding the English class option and adding
babel to the preamble, the export works fine. Is this what should be
done to the document or is it an internal issue?
Scott
commit 566a5f2b7513ffbd75cc92f713dc2636f37e
Author: Juergen Spitzmueller sp...@lyx.org
Date: Mon Jul 23 11:36:55 2012 +0200
Fixes to the language package call
* Assure that really no language package is called when none is selected.
* Only call global custom package if global is desired.
This is a candidate for branch as well.
[diff from before and after when exporting to LaTeX (pdflatex)]
-\documentclass[12pt,a4paper,english,cjk]{book}
+\documentclass[12pt,a4paper,cjk]{book}
\usepackage[T1]{fontenc}
\usepackage{CJKutf8}
\setcounter{secnumdepth}{3}
\setcounter{tocdepth}{3}
\usepackage{color}
-\usepackage{babel}
\usepackage{pmboxdraw}
\usepackage{graphicx}
\usepackage{setspace}
Re: [LyX master] UserGuide.lyx: first step of revision
On Fri, May 17, 2013 at 5:47 PM, Scott Kostyshak skost...@lyx.org wrote: 2013/4/16 Uwe Stöhr uwesto...@lyx.org: The branch, master, has been updated. - Log - commit 458b3bad107a988db4c0f963dde4576a3ae337d9 Author: Uwe Stöhr uwesto...@lyx.org Date: Wed Apr 17 01:13:49 2013 +0200 UserGuide.lyx: first step of revision - first step of the revision of the English UserGuide from John Hudson I get \endcsname errors when exporting the German User Guide to PDF with pdflatex. Bisect led me here. I forgot to CC you on this Uwe. I'm still getting errors when trying to export the German user guide after your recent commit. This isn't urgent, but I just wanted to make sure you saw this. Scott
Re: [LyX master] Pass local font to arguments and assure pass_thru is inherited
On Wed, Nov 28, 2012 at 1:04 PM, Juergen Spitzmueller sp...@lyx.org wrote: The branch, master, has been updated. - Log - commit 53002538fa2f87ae732f9830f24bb819ed402a72 Author: Juergen Spitzmueller sp...@lyx.org Date: Wed Nov 28 19:02:07 2012 +0100 Pass local font to arguments and assure pass_thru is inherited Git bisect suggests that this broke the Hebrew Intro.lyx compilation. Attached is the diff of the exported LaTeX (pdflatex) files. Any ideas? Scott HebrewIntro.diff Description: Binary data
Re: [LyX master] Add autotests for #8684
On Tue, May 21, 2013 at 4:48 AM, Kornel Benko kor...@lyx.org wrote: Am Dienstag, 21. Mai 2013 um 00:52:53, schrieb Scott Kostyshak skost...@lyx.org The branch, master, has been updated. - Log - commit 060bac3401f7a6cc3911285ff36f0b7280af1459 Author: Scott Kostyshak skost...@lyx.org Date: Mon May 20 18:50:56 2013 -0400 Add autotests for #8684 (these should currently fail) It passes here if called the first time (because of lyx configuring shows too early, thus not yet accepting key strokes?) I cannot reproduce this. Do you mean that the window pops up asking if you want to create a directory? For me the directory already exists (after a fresh build): $ ls -aR autotests/out-home/ autotests/out-home/: . .. .lyx Or you mean only from the configure? $ rm -r autotests/out-home/.lyx/* $ ctest -R 8684 Test project /home/scott/lyxbuilds/master/CMakeBuild Start 138: autotests/bug-8684 1/1 Test #138: autotests/bug-8684 ...***Failed 18.45 sec I wonder why we have different behaviors. Perhaps configure takes longer for you. I could try to reproduce this by adding a sleep into configure.py (let me know if you want me to try this). Is your thought that it's a LyX bug or an autotest bug? If the Window is open and it is dropping keystrokes, it sounds like LyX's responsibility. Do you get the same false-positive with the other tests (when run on their own for the first time)? Scott
Re: Re: [LyX master] Add autotests for #8684
On Tue, May 21, 2013 at 1:00 PM, Kornel Benko kor...@lyx.org wrote: Am Dienstag, 21. Mai 2013 um 12:24:55, schrieb Scott Kostyshak skost...@lyx.org If I remove the .lyx directory I see following: # ctest -R 8684 Test project /usr/BUILD/BuildLyxGit Start 139: autotests/bug-8684 mmand-sequence change-next; change-reject; change-next 1/1 Test #139: autotests/bug-8684 ... Passed 84.27 sec 100% tests passed, 0 tests failed out of 1 Total Test time (real) = 84.79 sec 1.57 amd64.kornel 18:41 mmand-sequence change-next; change-reject; change-next mmand-sequence: Command not found. Exit 1 change-reject: Command not found. Exit 1 change-next: Command not found. Exit 1 . 1.) The dialog-window appears, informing about directory-creation 2.) This sequence is written to the console: mmand-sequence change-next; change-reject; change-next This is not recreating anything though, right? Because CMake creates the directory, this should never happen (unless you manually remove the directory). I modified the test, to create lyx-log1.txt and lyx-log2.txt. Ah, yes, good idea. Thanks for doing that (did you commit?). lyx-log1.txt ends prematurely ... +checking for package fourier [fourier]... yes +checking for package garamondx [garamondx]... no EOL OK so indeed the autotest is killing LyX so it is an autotest problem. I guess that is good news. The keys should only be sent once the LyX window is open. while lyx-log2.txt shows: Warning: Document class not available The selected document class IEEE Transactions requires external files that are not available. The document class can still be used, but the document cannot be compiled until the following prerequisites are installed: IEEEtran.cls See section 3.1.2.2 (Class Availability) of the User's Guide for more information. Makes sense. LyX is poorly configured at this point. The interesting thing is, that the next ctest call passes, although I get the crash. lyx-log1.txt: support/lassert.cpp (43): ASSERTION false VIOLATED IN /usr/src/lyx/lyx-git/src/CursorSlice.cpp:157 Assertion triggered in void lyx::doAssert(const char*, const char*, long int) by failing check false in file /usr/src/lyx/lyx-git/src/support/lassert.cpp:45 Buffer.cpp (1356): /usr/BUILD/BuildLyxGit/autotests/bug-8684.lyx.emergency I don't understand why this happens but it probably has to do with LyX being poorly configured. This was the first time I observed this. It it the first time you try to run one of the tests without configuring first? One solution is that before each autotest is run, check to see if LyX is configured. If not, run autotests/first-time. Scott
layout validations (was: Re: disable package)
On Tue, May 21, 2013 at 1:31 PM, Julien Rioux jri...@lyx.org wrote: On 21/05/2013 1:20 PM, Scott Kostyshak wrote: On Tue, May 21, 2013 at 12:53 PM, Julien Rioux jri...@lyx.org wrote: In document settings: Edit the local layout to tell LyX that we are providing bm ourself: Format 35 Provides bm true Note that (on 2.1git) LyX gives the following warning: LyX: Bad integer `true' [around line 2 of file /tmp/lyx_tmpdir.rDYhXLs25464/convert_layout.ELJOAZs25464 current token: 'true' context: ''] Changing true to 1 fixes this for me. Should the layout validator in Document Settings catch this (it currently does not)? I know it is not supposed to be too strict but wanted to check anyway. Scott That's just me writing this layout snippet from memory. The correct documented usage is indeed 1 or 0. Interestingly, if I replace by false, I get the same effect as if I had typed 1. LyX seems to accept anything different from 0 as true, while the script that updates the format from 35 to X seems stricter on this (X being, current LyX 2.1git format). Sending to lyx-devel to see if anyone has thoughts on this. I'm guessing that the validations are not in sync because when the layout is actually processed it is easier to be more strict. Scott
Re: [LyX master] UserGuide.lyx: first step of revision
On Tue, May 21, 2013 at 3:17 PM, Uwe Stöhr uwesto...@web.de wrote:
Am 21.05.2013 05:51, schrieb Scott Kostyshak:
Yes, I see the problem with pdflatex. When compiling I first get the
following error:
LyX's automatic index sorting algorithm faced
problems with the entry 'Auflistung'.
Please specify the sorting of this entry manually, as
explained in the User Guide.
Attached is the log.
But your logfile doesn't contain any error message.
It contains the following:
! Package enumitem Error: \csnameforeignlanguage \endcsname {ngerman}{labelinde
nt=0pt, labelsep=1cm, font=\itshape , style=nextline} undefined.
The index entry for Auflistung is in sec. 3.3.1 and contains - correctly -
a ligature break. I removed now the sansserif style for the ligature break.
I just committed the change to master - can you now compile the file?
I still get the same two (identical errors) and failure with pdflatex.
If I remove the Description Options inset containing labelindent=0pt,
labelsep=1cm, font=\itshape, style=nextline (after Ionizing
radiation) it appears to compile fine.
Scott
