Windows installer for LyX 2.0.4
I now finished the new Windows installer. It is the merge of my old one and Joost's. I already have released a test version some weeks ago to be able to iron out some remaining issues. The last step was to enable the support for installing LyX without admin privileges. This is now also possible thanks to the new ImageMagick versions. You find it here: https://sourceforge.net/projects/lyxwininstaller/files/LyXWinInstaller/2.0.4/ We could also put it on our FTP server. I'll announce it this time also on the users list to get some feedback. regards Uwe
Re: [LyX master] CJK support for tex2lyx
Am 25.06.2012 09:27, schrieb Vincent van Ravesteijn:
Could you please indicate what "as good as possible" means
Supporting the language change commands but not the document language.
and why we can't set the document
language ? I know I can figure that out myself, but it would be much easier if
you described it in
the commit log while you are at the subject.
Have a look at the CJK.tex file I committed. You can see from my comment there and the LaTeX code
why this is not possible:
% It is impossible to get the document language because the document could
start with a command,
% whitespace, and English word or whatever and the rest is in Japanese.
Checking for the first CJK
% environment is no solution because the document could be English and contain
only some Japanese.
I don't know whether we settled to use metadata to enable LyX-LaTeX roundtrips,
buf if we do so,
would it be an idea to set some LyX metadata to allow a succesfull roundtrip
for CJK languages ?
I came up with this idea once but Georg objected and while developing tex2lyx I also came to the
conclusion that such metadata would be a hack. Roundtrips are not useful unless you need the TeX
file. But plain TeX might complain about additional comments. But while thinnking about it for CJK
that would be the only solution.
+/**
+ * supported CJK encodings
+ */
+const char * const supported_CJK_encodings[] = {
+"EUC-JP", "KS", "GB", "UTF8", 0};
+
+/**
+ * the same as supported_CJK_encodings with .lyx names
+ * please keep this in sync with supported_CJK_encodings line by line!
+ */
+const char * const coded_supported_CJK_encodings[] = {
+"japanese-cjk", "korean", "chinese-simplified", "chinese-traditional", 0};
What does "coded_supported_CJK_encodings" mean, what is 'coded' about it?
Coded by LyX.
These relations aren't bijective. "chinese-traditional" might imply "UTF8", but
"UTF8" does not
imply "chinese-traditional" right ?
Correct. When writing traditional Chinese LyX uses UTF8, but this encoding is of course also valid
for other languages. The problem is that the CJK package is not designed to distinguish between
languages as it doesn't provide the features of babel.
If so, CJK2lyx function is wrong.
It is not wrong. LyX treats everything in CJK-UTF8 as Chinese traditional. If you want in LyX write
Korean using UTF8 you also have to select Chinese as language to get the UTF8 encoding.
This is quite strange but the origins of this code comes from CJK-LyX which was once developed by
CJK native speakers to get LyX working with CJK. In LyX 1.4 we incorporated CJK-LyX and since then
we use this language coding. But as native speakers developed this, we can assume that the coding is
sensible.
What about all other encodings supported by CJK ? Below you hardcode that if
SJIS, JIS or Big5 is
defined we use utf8 instead.
SJIS and big5 are not supported by LyX and also not by iconv, see Lars's
comment in unicode.cpp.
We therefore output these cases as ERT as always.
Why are the following entries in lib/encodings not supported ?
# For japanese
Encoding jis JIS "Japanese (CJK) (JIS)" ISO-2022-JP variable CJK
End
# For traditional chinese
Encoding euc-tw EUC-TW "Chinese (traditional) (EUC-TW)" EUC-TW variable CJK
End
Good question. I also wondered about this. Therere is no reason not to support these encodings. I'll
have a look.
As Pavel already said, please don't make member variables public just because
it is easy. Not only
did Pavel suggest to use get** and set** methods, these methods are already
there, and you even
already use them in your code.
I'll correct this soon. I had not time to react until now.
+else if (name == "CJK") {
+// the scheme is \begin{CJK}{encoding}{mapping}{text}
+// It is impossible to decide if a CJK environment was in its own
paragraph or within
+// a line. We therefore always assume a paragraph since the latter is
a rare case.
Why is this impossible ?
I don't know how this should be possible. You can have
CJKCJK
or
CJK CJK
or
CJK
CJK
or
CJK
CJK
And there could also be some things around it. It would be really hard to get it right for all
possible cases if not impossible to handle them all.
+// SJIS and BIG5 don't work with LaTeX according to the comment in
unicode.cpp
The comment in unicode.cpp just points to the comments in lib/encodings.
Hmm, right.
But I meant
// Furthermore, all encodings that use shifting (like SJIS) do not work with
// iconv_codecvt_facet.
Koji sent me an example file and the JIS input method is quite strange. But that doesn't matter
here, it is only an additional info.
+// JIS does not work with LyX's encoding conversion
+if (encoding != "SJIS"&& encoding != "BIG5"&& encoding != "JIS")
+p.setEncoding(encoding);
+else
+p.setEncoding("utf8");
Ugh.. hardcoding.
Why not? We have to use UTF8 and nothing else.
+
Re: LyX 2.0.4 Source Available
Am 26.06.2012 um 16:19 schrieb Richard Heck: > On 06/26/2012 09:28 AM, Stephan Witt wrote: >> Am 25.06.2012 um 15:35 schrieb Richard Heck: >> >>> I have put source tarballs, etc, here: >>>http://frege.brown.edu/lyx/ >>> Please check compilation on your platform. Packagers should prepare >>> binaries. >> It works on Mac OS X too. BTW, the tar.gz seems to be broken (truncated). >> > It's fine on the server, and verifies. Indeed. I don't know what happened at download time. Now it is ok. Stephan
Re: [LyX master] BufferParams: Remove superfluous '\n'
Am 25.06.2012 11:29, schrieb Vincent van Ravesteijn: commit 8941e980b957e716746b3dfb7e01de80c5631236 Author: Vincent van Ravesteijn Date: Mon Jun 25 11:24:04 2012 +0200 BufferParams: Remove superfluous '\n' This extra '\n' seems to have been an unintended side-effect of d7eaaba9 (Juergen Spitzmueller, "support for CJK font argument"; Jun 5 2008). Thanks. regards Uwe
Re: [LyX master] removed unused includes
On Tue, Jun 26, 2012 at 10:41:57PM +0200, Uwe Stöhr wrote: > The branch, master, has been updated. > > - Log - > > commit a6e42e50791d8c4c9d34771c2b864d565fb1cf48 > Author: Uwe Stöhr > Date: Tue Jun 26 22:41:53 2012 +0200 > > removed unused includes > > these files don't use the debug.h and also don't contain commented out > debug code Please revert this. It makes debugging via lyxerr<< twice as hard. Pavel
Cross-session instant preview cache
Hi, if you have a lot of instant preview insets in a document, generating all of them requires some time. The LyX GUI doesn't freeze but still it'd be nice to have all the images immediately available, in particular if you just restarted LyX and you want to reopen a document. Do you think it'd be possible to keep some sort of IP cache in a cross-session way? Maybe with a size limit or maybe enabling it explicitly per-document. Bye! Ale
Re: rtf2latex2e 2-2-0 released, includes LyX Metafile to EPS converter
On Tue, Jun 26, 2012 at 7:17 PM, Wilfried wrote: > For the _Unix_ version we haven't yet found a better converter as in > rtf2latex2e version 2-0-1. We are experimenting with jodconverter which > in turn uses parts of OpenOffice for the conversion. It works with some > versions of OpenOffice / LibreOffice, with others it doesn't. > Unless we find a more reliable free metafile2eps/pdf converter for Unix, > we cannot release the current rtf2latex2e version for Unix. > A random idea: if you can make it work (somewhat) reliably with, say, LibreOffice >= 3.5.2, then I personally see no issues with releasing rtf2latex2e while making clear that it would work only with that version of LibreOffice or later. My 00.02€ Liviu
Re: Unable to Push New Tag
On 06/26/2012 02:37 PM, Vincent van Ravesteijn wrote: Op 26-6-2012 20:32, Richard Heck schreef: On 06/26/2012 12:20 PM, Vincent van Ravesteijn wrote: Op 26-6-2012 17:48, Richard Heck schreef: Anyone know how to fix this? Or am I doing something wrong? Richard You need to have permissions to "create a new branch". Find the gitolite.conf file in the gitolite-admin.git repo and give yourself rights (RW -> RWC). I found one at ~git/.gitolite/conf/gitolite.conf, but changing it seems to have no effect. Looks as if one is supposed to clone and then push that repo, which only Lars seems to have the right to do. Lars, can you give some of the rest of us admin access, to make these kinds of changes? Richard Yes, it will update the rights when pushing. If you check the hook that is being run, you can see what you have to do manually. I don't think I have access rights sufficient to make these changes. Richard
Re: Unable to Push New Tag
Op 26-6-2012 20:32, Richard Heck schreef: On 06/26/2012 12:20 PM, Vincent van Ravesteijn wrote: Op 26-6-2012 17:48, Richard Heck schreef: Anyone know how to fix this? Or am I doing something wrong? Richard You need to have permissions to "create a new branch". Find the gitolite.conf file in the gitolite-admin.git repo and give yourself rights (RW -> RWC). I found one at ~git/.gitolite/conf/gitolite.conf, but changing it seems to have no effect. Looks as if one is supposed to clone and then push that repo, which only Lars seems to have the right to do. Lars, can you give some of the rest of us admin access, to make these kinds of changes? Richard Yes, it will update the rights when pushing. If you check the hook that is being run, you can see what you have to do manually. Vincent
Re: Unable to Push New Tag
On 06/26/2012 12:20 PM, Vincent van Ravesteijn wrote: Op 26-6-2012 17:48, Richard Heck schreef: Anyone know how to fix this? Or am I doing something wrong? Richard You need to have permissions to "create a new branch". Find the gitolite.conf file in the gitolite-admin.git repo and give yourself rights (RW -> RWC). I found one at ~git/.gitolite/conf/gitolite.conf, but changing it seems to have no effect. Looks as if one is supposed to clone and then push that repo, which only Lars seems to have the right to do. Lars, can you give some of the rest of us admin access, to make these kinds of changes? Richard
Re: rtf2latex2e 2-2-0 released, includes LyX Metafile to EPS converter
Hello, some clarification. The previous _Windows_ version of rtf2latex2e could only convert wmf, not emf graphics. As the LyX metafile2eps converter converts both, I think it's worth to switch to the new _Windows_ version. For the _Unix_ version we haven't yet found a better converter as in rtf2latex2e version 2-0-1. We are experimenting with jodconverter which in turn uses parts of OpenOffice for the conversion. It works with some versions of OpenOffice / LibreOffice, with others it doesn't. Unless we find a more reliable free metafile2eps/pdf converter for Unix, we cannot release the current rtf2latex2e version for Unix. Wilfried I wrote: > Hello all, > as I am maintaining the Windows port of rtf2latex2e, > I was glad to find the Metafile to EPS converter at > http://wiki.lyx.org/Windows/MetafileToEPSConverter > and as that page sais it's under GPL, I decided to include it in the > rtf2latex2e distribution. > Please let me know whether there are any objections to this. > > I uploaded the updated package rtf2latex2e-2-2-0-Win.zip to > http://sourceforge.net/projects/rtf2latex2e > > AFAIK, rtf2latex2e is included in the LyX package. > As I am not sure where metafile2eps is installed with LyX, the LyX > developer who packages the LyX installer should make sure that in the > emf2eps.bat file of rtf2latex2e the path pointing to metafile2eps is > correct. -- Wilfried Hennings
Re: Unable to Push New Tag
Op 26-6-2012 17:48, Richard Heck schreef: Anyone know how to fix this? Or am I doing something wrong? Richard You need to have permissions to "create a new branch". Find the gitolite.conf file in the gitolite-admin.git repo and give yourself rights (RW -> RWC). Vincent
Unable to Push New Tag
../lyx/lyx-devel/ [⚡ 2.0.x] > git push -n origin 2.0.4 To g...@git.lyx.org:lyx * [new tag] 2.0.4 -> 2.0.4 ../lyx/lyx-devel/ [⚡ 2.0.x] > git push origin 2.0.4 Counting objects: 1, done. Writing objects: 100% (1/1), 168 bytes, done. Total 1 (delta 0), reused 0 (delta 0) remote: C refs/tags/2.0.4 lyx rgheck DENIED by fallthru remote: error: hook declined to update refs/tags/2.0.4 To g...@git.lyx.org:lyx ! [remote rejected] 2.0.4 -> 2.0.4 (hook declined) error: failed to push some refs to 'g...@git.lyx.org:lyx' Anyone know how to fix this? Or am I doing something wrong? Richard
Binaries for 2.0.4
It appears all is well with the 2.0.4 tarballs. Please prepare binaries as usual. I'd like to announce the release at the end of the week. Richard
Re: LyX 2.0.4 Source Available
On 06/26/2012 09:28 AM, Stephan Witt wrote: Am 25.06.2012 um 15:35 schrieb Richard Heck: I have put source tarballs, etc, here: http://frege.brown.edu/lyx/ Please check compilation on your platform. Packagers should prepare binaries. It works on Mac OS X too. BTW, the tar.gz seems to be broken (truncated). It's fine on the server, and verifies. Richard
Re: [LyX master] tex2lyx: support fontspec scale option
Op 26-6-2012 0:46, Uwe Stöhr schreef:
The branch, master, has been updated.
- Log -
commit 2e8ed3b3b5b8edefc0dc2a888ac0fa314f87618e
Author: Uwe Stöhr
Date: Tue Jun 26 00:46:02 2012 +0200
tex2lyx: support fontspec scale option
@@ -1186,16 +1187,30 @@ void Preamble::parse(Parser & p, string
+ else if (t.cs() == "setsansfont" || t.cs() == "setmonofont") {
+ // LyX currently only supports the scale option
+ string scale;
+ if (p.hasOpt()) {
+ string fontopts = p.getArg('[', ']');
+ // check if the option contains a scaling, if
yes, extract it
+ string::size_type pos = fontopts.find("Scale");
+ if (pos != string::npos) {
+ string::size_type i =
fontopts.find(',');
+ if (i == string::npos)
+ scale =
scale_as_percentage(fontopts.substr(pos + 1));
+ else
+ scale =
scale_as_percentage(fontopts.substr(pos, i - pos));
+ }
+ }
If fontopts is "Mapping=tex-text,Scale=0.75", then i < pos, which is probably
not what you want.
Vincent
Re: rtf2latex2e 2-2-0 released, includes LyX Metafile to EPS converter
Wilfried wrote: > Hello all, > as I am maintaining the Windows port of rtf2latex2e, > I was glad to find the Metafile to EPS converter at > http://wiki.lyx.org/Windows/MetafileToEPSConverter > and as that page sais it's under GPL, I decided to include it in the > rtf2latex2e distribution. > Please let me know whether there are any objections to this. It was written by Joost Verburg, based on previous projects and its GPL-2 so you are free to use it in GPL-compatible way. > AFAIK, rtf2latex2e is included in the LyX package. > As I am not sure where metafile2eps is installed with LyX, the LyX I don't know either, windows guys would know... > developer who packages the LyX installer should make sure that in the > emf2eps.bat file of rtf2latex2e the path pointing to metafile2eps is > correct. You can file bug in our tracker in case something is wrong. Pavel
Re: LyX 2.0.4 Source Available
Am 25.06.2012 um 15:35 schrieb Richard Heck: > I have put source tarballs, etc, here: >http://frege.brown.edu/lyx/ > Please check compilation on your platform. Packagers should prepare binaries. It works on Mac OS X too. BTW, the tar.gz seems to be broken (truncated). Stephan
rtf2latex2e 2-2-0 released, includes LyX Metafile to EPS converter
Hello all, as I am maintaining the Windows port of rtf2latex2e, I was glad to find the Metafile to EPS converter at http://wiki.lyx.org/Windows/MetafileToEPSConverter and as that page sais it's under GPL, I decided to include it in the rtf2latex2e distribution. Please let me know whether there are any objections to this. I uploaded the updated package rtf2latex2e-2-2-0-Win.zip to http://sourceforge.net/projects/rtf2latex2e AFAIK, rtf2latex2e is included in the LyX package. As I am not sure where metafile2eps is installed with LyX, the LyX developer who packages the LyX installer should make sure that in the emf2eps.bat file of rtf2latex2e the path pointing to metafile2eps is correct. Regards -- Wilfried Hennings
Re: [LyX 2.0.x] Remerge strings.
Le 26/06/12 10:38, Kornel Benko a écrit : To answer myself ... we should back-port po/Rules-lyx. (The master-version is ok) Indeed, this is commit f0a66901. It should be backported when the tree is open again. JMarc
Re: Re: [LyX 2.0.x] Remerge strings.
Am Montag, 25. Juni 2012 um 17:15:06, schrieb Kornel Benko > Am Montag, 25. Juni 2012 um 14:29:27, schrieb Richard Heck > > The branch, 2.0.x, has been updated. > > > > - Log - > > > > commit 1a855429c4b2e9fd1ab894d6b3782ab8b54e0e66 > > Author: Richard Heck > > Date: Mon Jun 25 08:29:04 2012 -0400 > > > > Remerge strings. > > > > Remerged also with generated files (like ui_RefUi.h). We should exclude such > files from creating lyx**.pot. > > Or, alternatively, use cmake to remerge :) > > Kornel To answer myself ... we should back-port po/Rules-lyx. (The master-version is ok) Kornel signature.asc Description: This is a digitally signed message part.
