From bvoisin at me.com Fri Apr 1 17:24:56 2011 From: bvoisin at me.com (Bruno Voisin) Date: Fri, 01 Apr 2011 17:24:56 +0200 Subject: [texworks] Message from TeXworks user In-Reply-To: References: Message-ID: <84FB290F-23A8-459B-945D-376A38530267@me.com> TeXworks is a front-end to a TeX distribution (ie TeX executables and support files). The message "pdflatex.exe has not been found" means you don't have such a distribution, or TeXworks can't find it. Obvious candidates on Windows are MikTeX and TeX Live , I think. Bruno Voisin Le 31 mars 2011 ? 22:42, Robin A a ?crit : > Bonjour j?ai install? le logiciel TeXworks sut mon ordinateur portable > > Mais malheureusement d?s que je veux pr?visualiser mon document un message d?erreur s?affiche ? le programme pdflatex.exe n?a pas ?t? trouv? ?. Que dois-je faire ? > > Merci de votre aide > > > > ----- configuration info ----- > TeXworks version : 0.4.0r759 (official) > Install location : C:/Program Files/TeXworks/TeXworks.exe > Library path : C:/Users/Robin/TeXworks\ > pdfTeX location : not found > Operating system : Windows Vista Service Pack 2, 32-bit > Qt4 version : 4.7.2 (build) / 4.7.2 (runtime) > ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From prernaatri at gmail.com Fri Apr 1 18:34:20 2011 From: prernaatri at gmail.com (Prerna Atri) Date: Fri, 1 Apr 2011 22:04:20 +0530 Subject: [texworks] Fink Package (for MAC OS X) TeXworks 0.3 - Build error Message-ID: Hi, We have been working on porting TeXworks ( version 0.3) as a package on Fink. We are using the following Fink packages for building TeXworks: - qt4-mac ( v 4.6.3-2) - poppler4-qt4-mac ( v 0.10.7-3) - fontconfig-config ( v 2.8.0-4) - poppler-data ( v 0.2.1-1) - hunspell ( v 1.2.12-1002) - poppler4-xpdf ( v 0.10.7-1) - libhunspell ( v 1.2.12-1002) When building TeXworks after installing the above metioned packages, we are getting the following failure: *CompileC obj/TeXworks.build/Default/TeXworks.build/Objects-normal/i386/TWApp.o src/TWApp.cpp normal i386 c++ com.apple.compilers.gcc.4_2* * cd /sw/src/fink.build/texworks-0.3-1/texworks-0.3* * setenv LANG en_US.US-ASCII* * /usr/bin/g++-4.2 -x c++ -arch i386 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -Os -mdynamic-no-pic -fvisibility=hidden -fvisibility-inlines-hidden -mmacosx-version-min=10.4 -gdwarf-2 -I/sw/src/fink.build/texworks-0.3-1/texworks-0.3/obj/TeXworks.build/Default/TeXworks.build/TeXworks.hmap -F/sw/src/fink.build/texworks-0.3-1/texworks-0.3/build/Default -I/sw/src/fink.build/texworks-0.3-1/texworks-0.3/build/Default/include -I/sw/lib/qt4-mac/include/QtUiTools -I/sw/lib/qt4-mac/include/QtCore -I/sw/lib/qt4-mac/include/QtGui -I/sw/lib/qt4-mac/include/QtXml -I/sw/lib/qt4-mac/include/QtScriptTools -I/sw/lib/qt4-mac/include/QtScript -I/usr/include -I/sw/include/poppler -I/sw/opt/kde4/mac/include/poppler/qt4 -I/sw/include/hunspell -I/sw/lib/fontconfig2/include -Imoc -Iui -I/usr/local/include -I/System/Library/Frameworks/CarbonCore.framework/Headers -I/usr/local/Qt4.7/mkspecs/macx-xcode -I/sw/src/fink.build/texworks-0.3-1/texworks-0.3/obj/TeXworks.build/Default/TeXworks.build/DerivedSources/i386 -I/sw/src/fink.build/texworks-0.3-1/texworks-0.3/obj/TeXworks.build/Default/TeXworks.build/DerivedSources -pipe -DTW_BUILD_ID=personal -DHAVE_POPPLER_XPDF_HEADERS -fexceptions -g -Wall -W -DQT_SCRIPT_LIB -DQT_SCRIPTTOOLS_LIB -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -c /sw/src/fink.build/texworks-0.3-1/texworks-0.3/src/TWApp.cpp -o /sw/src/fink.build/texworks-0.3-1/texworks-0.3/obj/TeXworks.build/Default/TeXworks.build/Objects-normal/i386/TWApp.o * * * */sw/src/fink.build/texworks-0.3-1/texworks-0.3/src/TWApp.cpp: In member function ?void TWApp::init()?:* */sw/src/fink.build/texworks-0.3-1/texworks-0.3/src/TWApp.cpp:159: error: no matching function for call to ?GlobalParams::GlobalParams(char*)?* */sw/include/poppler/GlobalParams.h:162: note: candidates are: GlobalParams::GlobalParams()* */sw/include/poppler/GlobalParams.h:157: note: GlobalParams::GlobalParams(const GlobalParams&)* *** BUILD FAILED *** * * * * *The following build commands failed:* *TeXworks:* * CompileC obj/TeXworks.build/Default/TeXworks.build/Objects-normal/i386/TWApp.o /sw/src/fink.build/texworks-0.3-1/texworks-0.3/src/TWApp.cpp normal i386 c++ com.apple.compilers.gcc.4_2* *(1 failure)* Please suggest any possible fixes for the above build failure. Thanks & Regards, Prerna Atri. -------------- next part -------------- An HTML attachment was scrubbed... URL: From suresh.amritapuri at gmail.com Fri Apr 1 22:06:37 2011 From: suresh.amritapuri at gmail.com (Suresh Kumar) Date: Fri, 1 Apr 2011 13:06:37 -0700 Subject: [texworks] auto completion Message-ID: Hi Is it possible to have auto completion in texworks now, similar to the one seen in texlipse+eclipse? thanks suresh -- R Suresh Kumar, http://www.m atrukripa.com Sarve bhavantu sukinaha (May everyone be happy) Sarve santu niramiyaha (May everyone be without affliction) Sarve bhadrani pashyantu (May everyone see only goodness) Ma kashchit dukha bhak bhavet (Let none be the victim of suffering) -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Sat Apr 2 12:36:26 2011 From: st.loeffler at gmail.com (=?windows-1252?Q?Stefan_L=F6ffler?=) Date: Sat, 02 Apr 2011 12:36:26 +0200 Subject: [texworks] Fink Package (for MAC OS X) TeXworks 0.3 - Build error In-Reply-To: References: Message-ID: <4D96FC2A.9030200@gmail.com> Hi, On 2011-04-01 18:34, Prerna Atri wrote: > We have been working on porting TeXworks ( version 0.3) as a package > on Fink. It's great to hear that there still is some progress with Tw on the Mac :). The latest version is labeled 0.5, though. > We are using the following Fink packages for building TeXworks: > > * qt4-mac ( v 4.6.3-2) > * poppler4-qt4-mac ( v 0.10.7-3) > * fontconfig-config ( v 2.8.0-4) > * poppler-data ( v 0.2.1-1) > * hunspell ( v 1.2.12-1002) > * poppler4-xpdf ( v 0.10.7-1) > * libhunspell ( v 1.2.12-1002) > Some of these seem outdated: * Qt - latest stable version: 4.7.2 (though the difference to the 4.6 series is probably not too important for Tw) * Hunspell - latest stable version: 1.3.1 (again, I don't think this is very relevant) * poppler - latest stable version: 0.16 (now, this is very relevant!) * poppler-data - latest stable version: 0.4.4 > When building TeXworks after installing the above metioned packages, > we are getting the following failure: > > //sw/src/fink.build/texworks-0.3-1/texworks-0.3/src/TWApp.cpp: In > member function ?void TWApp::init()?:/ > //sw/src/fink.build/texworks-0.3-1/texworks-0.3/src/TWApp.cpp:159: > error: no matching function for call to > ?GlobalParams::GlobalParams(char*)?/ > //sw/include/poppler/GlobalParams.h:162: note: candidates are: > GlobalParams::GlobalParams()/ > //sw/include/poppler/GlobalParams.h:157: note: > GlobalParams::GlobalParams(const GlobalParams&)/ > /** BUILD FAILED **/ This is a result of the ancient poppler version. In recent versions (I think from 0.12 on), the constructor of GlobalParams takes as argument the location of the private poppler directory. Note, however, that for this to be effective, you need to have a patched version of poppler, which I guess is not what you (initially) want with Fink, unless you have to. For more information, see src/TWApp.cpp (lines 148-152), as well as the lib-patches/ directory. The easiest solution would be to comment out the line QMAKE_CXXFLAGS += -DHAVE_POPPLER_XPDF_HEADERS in TeXworks.pro, though. This way, you will not be able to use a poppler-data/ directory alongside the TeXworks.app bundle, but poppler should look for the default ones in some system dependent global directory. In any case, you should check if this works properly (i.e., it picks up the files installed by poppler-data). HTH Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Sat Apr 2 12:38:18 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sat, 02 Apr 2011 12:38:18 +0200 Subject: [texworks] auto completion In-Reply-To: References: Message-ID: <4D96FC9A.1030901@gmail.com> Hi, On 2011-04-01 22:06, Suresh Kumar wrote: > Is it possible to have auto completion in texworks now, similar to the > one seen in texlipse+eclipse? Some form of auto completion is there (see the manual and/or the wiki http://code.google.com/p/texworks/wiki/CodeCompletion), but it works somewhat different than in eclipse, I think. A general evaluation of this is on my mid-term to long-term wishlist, though. HTH Stefan From suresh.amritapuri at gmail.com Sun Apr 3 03:09:39 2011 From: suresh.amritapuri at gmail.com (Suresh Kumar) Date: Sat, 2 Apr 2011 18:09:39 -0700 Subject: [texworks] auto completion In-Reply-To: <4D96FC9A.1030901@gmail.com> References: <4D96FC9A.1030901@gmail.com> Message-ID: Hi Thanks for the reply. Personally, I find the automatic completion, where eclipse adds \end{environment} once you type \begin{some environment} very fascinating. Again eclipse completes braces, $ etc. So I was trying to see if texworks does the same thing. suresh On Sat, Apr 2, 2011 at 3:38 AM, Stefan L?ffler wrote: > Hi, > > On 2011-04-01 22:06, Suresh Kumar wrote: > > Is it possible to have auto completion in texworks now, similar to the > > one seen in texlipse+eclipse? > > Some form of auto completion is there (see the manual and/or the wiki > http://code.google.com/p/texworks/wiki/CodeCompletion), but it works > somewhat different than in eclipse, I think. A general evaluation of > this is on my mid-term to long-term wishlist, though. > > HTH > Stefan > -- R Suresh Kumar, http://www.m atrukripa.com Sarve bhavantu sukinaha (May everyone be happy) Sarve santu niramiyaha (May everyone be without affliction) Sarve bhadrani pashyantu (May everyone see only goodness) Ma kashchit dukha bhak bhavet (Let none be the victim of suffering) -------------- next part -------------- An HTML attachment was scrubbed... URL: From suresh.amritapuri at gmail.com Sun Apr 3 07:32:02 2011 From: suresh.amritapuri at gmail.com (Suresh Kumar) Date: Sat, 2 Apr 2011 22:32:02 -0700 Subject: [texworks] auto completion In-Reply-To: <4D96FC9A.1030901@gmail.com> References: <4D96FC9A.1030901@gmail.com> Message-ID: Hi Much to my surprise I found that it is possible to do auto completion like in eclipse by configuring texworks. I found some scripts installed already in my linux machine which contains the line: bali:=\begin{align}#RET##INS##RET#\end{align}? What is this last big size bullet? What is its purpose? How this symbol is entered ? (it is not in my key board) thanks suresh ps. This set of macros makes texworks very very powerful I guess On Sat, Apr 2, 2011 at 3:38 AM, Stefan L?ffler wrote: > Hi, > > On 2011-04-01 22:06, Suresh Kumar wrote: > > Is it possible to have auto completion in texworks now, similar to the > > one seen in texlipse+eclipse? > > Some form of auto completion is there (see the manual and/or the wiki > http://code.google.com/p/texworks/wiki/CodeCompletion), but it works > somewhat different than in eclipse, I think. A general evaluation of > this is on my mid-term to long-term wishlist, though. > > HTH > Stefan > -- R Suresh Kumar, http://www.m atrukripa.com Sarve bhavantu sukinaha (May everyone be happy) Sarve santu niramiyaha (May everyone be without affliction) Sarve bhadrani pashyantu (May everyone see only goodness) Ma kashchit dukha bhak bhavet (Let none be the victim of suffering) -------------- next part -------------- An HTML attachment was scrubbed... URL: From suresh.amritapuri at gmail.com Sun Apr 3 08:22:06 2011 From: suresh.amritapuri at gmail.com (Suresh Kumar) Date: Sat, 2 Apr 2011 23:22:06 -0700 Subject: [texworks] git and texworks Message-ID: hi is it possible to use version control system while inside texworks? for example can we use git? thanks suresh -- R Suresh Kumar, http://www.m atrukripa.com Sarve bhavantu sukinaha (May everyone be happy) Sarve santu niramiyaha (May everyone be without affliction) Sarve bhadrani pashyantu (May everyone see only goodness) Ma kashchit dukha bhak bhavet (Let none be the victim of suffering) -------------- next part -------------- An HTML attachment was scrubbed... URL: From nishni_nowgorod at gaponline.de Sun Apr 3 09:51:08 2011 From: nishni_nowgorod at gaponline.de (Andreas Hirsch) Date: Sun, 03 Apr 2011 09:51:08 +0200 Subject: [texworks] auto completion In-Reply-To: References: <4D96FC9A.1030901@gmail.com> Message-ID: <4D9826EC.6060508@gaponline.de> Hi! quoting Suresh Kumar, [03.04.2011 07:32 +0100]: > Hi > Much to my surprise I found that it is possible to do auto completion like > in eclipse by configuring texworks. I found some scripts installed already > in my linux machine which contains the line: > > bali:=\begin{align}#RET##INS##RET#\end{align}? > > What is this last big size bullet? It is intended to reach the next editing point via I have a related question: Where ist a predifined completition for bite:=\begin{itemize}#RET#\item#RET##INS##RET#\end{itemize}? which expands to \begin{itemize} \item \end{itemize}? I would like to have it modified to \begin{itemize} \item \end{itemize} ? and tried therefore bit:=\begin{itemize}#RET#\item #INS#\end{abstract}#RET# ? which expands to the same as the original - or is it due to the fact that I could not override the predefined fils? Andreas -- 'People, it has been said, can be placed in three classes: the few who makes things happen, the many, watching things happen and the overwhelming majority who have no idea what is happening.' Nicolas Murray Butler -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From st.loeffler at gmail.com Sun Apr 3 10:00:07 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 03 Apr 2011 10:00:07 +0200 Subject: [texworks] git and texworks In-Reply-To: References: Message-ID: <4D982907.5050302@gmail.com> Hi, On 2011-04-03 08:22, Suresh Kumar wrote: > is it possible to use version control system while inside texworks? > for example can we use git? Yes, that should be possible. There is no direct interface for it in Tw (i.e., you don't have a menu item or something to run git commands directly), but it should pick up changes etc. that come from invoking git somewhere else (e.g., on the command line). There has been one bug report about Tw not properly handling commits in mercurial some time ago, but that should be fixed now. HTH Stefan From st.loeffler at gmail.com Sun Apr 3 10:07:53 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Sun, 03 Apr 2011 10:07:53 +0200 Subject: [texworks] auto completion In-Reply-To: <4D9826EC.6060508@gaponline.de> References: <4D96FC9A.1030901@gmail.com> <4D9826EC.6060508@gaponline.de> Message-ID: <4D982AD9.5050900@gmail.com> Hi, On 2011-04-03 09:51, Andreas Hirsch wrote: > quoting Suresh Kumar, [03.04.2011 07:32 +0100]: >> Hi >> Much to my surprise I found that it is possible to do auto completion like >> in eclipse by configuring texworks. I found some scripts installed already >> in my linux machine which contains the line: >> >> bali:=\begin{align}#RET##INS##RET#\end{align}? >> >> What is this last big size bullet? > It is intended to reach the next editing point via Exactly. For more information, see http://code.google.com/p/texworks/wiki/CodeCompletion The easiest way of inputting it will probably be copy/paste. > I have a related question: > > Where ist a predifined completition for > > bite:=\begin{itemize}#RET#\item#RET##INS##RET#\end{itemize}? > > which expands to > > \begin{itemize} > \item > > \end{itemize}? > > I would like to have it modified to > > \begin{itemize} > \item > \end{itemize} > ? > > and tried therefore bit:=\begin{itemize}#RET#\item > #INS#\end{abstract}#RET# ? > > which expands to the same as the original - or is it due to the fact > that I could not override the predefined fils? Yes, overriding it should be possible. The file where this is defined is /completion/tw-latex.txt [1]. Note that there are two entries, though: one for "bite", and one for "\bite". Maybe this causes some confusion. BTW: your alternative definition seems flawed (\end{abstract}, for one thing), but I assume that's for testing only. HTH Stefan [1] The location of the resources folder is system-dependent. See http://code.google.com/p/texworks/wiki/TipsAndTricks#Locating_and_customizing_TeXworks_resources From nishni_nowgorod at gaponline.de Sun Apr 3 10:42:10 2011 From: nishni_nowgorod at gaponline.de (Andreas Hirsch) Date: Sun, 03 Apr 2011 10:42:10 +0200 Subject: [texworks] auto completion In-Reply-To: <4D982AD9.5050900@gmail.com> References: <4D96FC9A.1030901@gmail.com> <4D9826EC.6060508@gaponline.de> <4D982AD9.5050900@gmail.com> Message-ID: <4D9832E2.907@gaponline.de> Hi Stefan, quoting Stefan L?ffler, [03.04.2011 10:07 +0100]: > On 2011-04-03 09:51, Andreas Hirsch wrote: >> I have a related question: >> >> Where ist a predifined completition for >> >> bite:=\begin{itemize}#RET#\item#RET##INS##RET#\end{itemize}? >> >> which expands to >> >> \begin{itemize} >> \item >> >> \end{itemize}? >> >> I would like to have it modified to >> >> \begin{itemize} >> \item >> \end{itemize} >> ? >> >> and tried therefore bit:=\begin{itemize}#RET#\item >> #INS#\end{abstract}#RET# ? >> >> which expands to the same as the original - or is it due to the fact >> that I could not override the predefined fils? > > Yes, overriding it should be possible. The files are coded 'readonly' so I had to change this first. > The file where this is defined is > /completion/tw-latex.txt [1]. Note that there are two > entries, though: one for "bite", and one for "\bite". Maybe this causes > some confusion. that's it: I have to comment out all occurences starting with bit or \bit > BTW: your alternative definition seems flawed (\end{abstract}, for one > thing), but I assume that's for testing only. a typo ;-) now things work _nearly_ als expected, the expanded text is: \begin{itemize} \item \end{itemize} ? Could it be solved that: - \end{itemize} goes into the next line but - no empty line is produced? I mean \begin{itemize} \item \end{itemize} ? and the cursor is placed behind item? TIA Andreas -- 'People, it has been said, can be placed in three classes: the few who makes things happen, the many, watching things happen and the overwhelming majority who have no idea what is happening.' Nicolas Murray Butler -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From st.loeffler at gmail.com Sun Apr 3 11:56:33 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Sun, 03 Apr 2011 11:56:33 +0200 Subject: [texworks] auto completion In-Reply-To: <4D9832E2.907@gaponline.de> References: <4D96FC9A.1030901@gmail.com> <4D9826EC.6060508@gaponline.de> <4D982AD9.5050900@gmail.com> <4D9832E2.907@gaponline.de> Message-ID: <4D984451.1050704@gmail.com> Hi, On 2011-04-03 10:42, Andreas Hirsch wrote: > now things work _nearly_ als expected, the expanded text is: > > \begin{itemize} > \item \end{itemize} > ? > > Could it be solved that: > > - \end{itemize} goes into the next line but > - no empty line is produced? > > I mean > > \begin{itemize} > \item > \end{itemize} > ? > > and the cursor is placed behind item? Sure. bit:=\begin{itemize}#RET#\item#INS##RET#\end{itemize}#RET#? Should do the trick. Note that #INS# only marks the cursor position, it doesn't insert anything (no spaces, newlines, etc.). HTH Stefan From nishni_nowgorod at gaponline.de Sun Apr 3 12:34:39 2011 From: nishni_nowgorod at gaponline.de (Andreas Hirsch) Date: Sun, 03 Apr 2011 12:34:39 +0200 Subject: [texworks] auto completion In-Reply-To: <4D984451.1050704@gmail.com> References: <4D96FC9A.1030901@gmail.com> <4D9826EC.6060508@gaponline.de> <4D982AD9.5050900@gmail.com> <4D9832E2.907@gaponline.de> <4D984451.1050704@gmail.com> Message-ID: <4D984D3F.5070609@gaponline.de> quoting Stefan L?ffler, [03.04.2011 11:56 +0100]: > On 2011-04-03 10:42, Andreas Hirsch wrote: >> now things work _nearly_ als expected, the expanded text is: >> >> \begin{itemize} >> \item \end{itemize} >> ? >> >> Could it be solved that: >> >> - \end{itemize} goes into the next line but >> - no empty line is produced? >> >> I mean >> >> \begin{itemize} >> \item >> \end{itemize} >> ? >> >> and the cursor is placed behind item? > > Sure. > bit:=\begin{itemize}#RET#\item#INS##RET#\end{itemize}#RET#? > Should do the trick. Note that #INS# only marks the cursor position, it > doesn't insert anything (no spaces, newlines, etc.). works! great! Thank You! Andreas -- 'People, it has been said, can be placed in three classes: the few who makes things happen, the many, watching things happen and the overwhelming majority who have no idea what is happening.' Nicolas Murray Butler -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From herbs at wideopenwest.com Sun Apr 3 13:42:54 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Sun, 3 Apr 2011 06:42:54 -0500 Subject: [texworks] auto completion In-Reply-To: <4D982AD9.5050900@gmail.com> References: <4D96FC9A.1030901@gmail.com> <4D9826EC.6060508@gaponline.de> <4D982AD9.5050900@gmail.com> Message-ID: <04AA4617-9777-4307-BAC6-23B4A286F784@wideopenwest.com> On Apr 3, 2011, at 3:07 AM, Stefan L?ffler wrote: > Hi, > > On 2011-04-03 09:51, Andreas Hirsch wrote: >> quoting Suresh Kumar, [03.04.2011 07:32 +0100]: >>> Hi >>> Much to my surprise I found that it is possible to do auto completion like >>> in eclipse by configuring texworks. I found some scripts installed already >>> in my linux machine which contains the line: >>> >>> bali:=\begin{align}#RET##INS##RET#\end{align}? >>> >>> What is this last big size bullet? >> It is intended to reach the next editing point via > > Exactly. For more information, see > http://code.google.com/p/texworks/wiki/CodeCompletion > The easiest way of inputting it will probably be copy/paste. > >> I have a related question: >> >> Where ist a predifined completition for >> >> bite:=\begin{itemize}#RET#\item#RET##INS##RET#\end{itemize}? >> >> which expands to >> >> \begin{itemize} >> \item >> >> \end{itemize}? >> >> I would like to have it modified to >> >> \begin{itemize} >> \item >> \end{itemize} >> ? >> >> and tried therefore bit:=\begin{itemize}#RET#\item >> #INS#\end{abstract}#RET# ? >> >> which expands to the same as the original - or is it due to the fact >> that I could not override the predefined fils? > > Yes, overriding it should be possible. The file where this is defined is > /completion/tw-latex.txt [1]. Note that there are two > entries, though: one for "bite", and one for "\bite". Maybe this causes > some confusion. > BTW: your alternative definition seems flawed (\end{abstract}, for one > thing), but I assume that's for testing only. > > HTH > Stefan > > [1] The location of the resources folder is system-dependent. See > http://code.google.com/p/texworks/wiki/TipsAndTricks#Locating_and_customizing_TeXworks_resources Howdy, On thing to note: There are lots of environments pre-defined in the completion file but certainly not any custom environments you may use. You can always add more to the completion file. However, in TeXShop (Mac only, and the basic design of Command Completion is based on the version there that) there is one other more general completion, for occasional use, to complete an arbitrary environment \begin{myenv} with an \end{myenv}. You first type the \begin{myenv} and press Esc (that would be Tab, the Command Completion trigger, in TeXworks) and the \end{myenv} gets put on the next line. It might be worthwhile to add that to TeXworks. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From warrence.stm at gmx.de Sun Apr 3 17:05:32 2011 From: warrence.stm at gmx.de (=?ISO-8859-1?Q?Stefan_M=FCller?=) Date: Sun, 03 Apr 2011 17:05:32 +0200 Subject: [texworks] git and texworks In-Reply-To: <4D982907.5050302@gmail.com> References: <4D982907.5050302@gmail.com> Message-ID: <4D988CBC.9020807@gmx.de> On 03.04.2011 10:00, Stefan L?ffler wrote: > Hi, > > On 2011-04-03 08:22, Suresh Kumar wrote: >> is it possible to use version control system while inside texworks? >> for example can we use git? > > Yes, that should be possible. There is no direct interface for it in Tw > (i.e., you don't have a menu item or something to run git commands > directly), but it should pick up changes etc. that come from invoking > git somewhere else (e.g., on the command line). > > There has been one bug report about Tw not properly handling commits in > mercurial some time ago, but that should be fixed now. Yes, this seems fixed and was due to mercurial changing the working files multiple times while committing (in some cases). Stefan > HTH > Stefan > From matthias.pospiech at gmx.de Sun Apr 3 21:02:08 2011 From: matthias.pospiech at gmx.de (Matthias Pospiech) Date: Sun, 03 Apr 2011 21:02:08 +0200 Subject: [texworks] Path for Scripts on Windows for Texlive and Miktex Message-ID: <4D98C430.1010809@gmx.de> An HTML attachment was scrubbed... URL: From matthias.pospiech at gmx.de Sun Apr 3 21:37:11 2011 From: matthias.pospiech at gmx.de (Matthias Pospiech) Date: Sun, 03 Apr 2011 21:37:11 +0200 Subject: [texworks] complete reference for magic comments Message-ID: <4D98CC67.5000309@gmx.de> An HTML attachment was scrubbed... URL: From schuster.wolfgang at googlemail.com Sun Apr 3 21:48:31 2011 From: schuster.wolfgang at googlemail.com (Wolfgang Schuster) Date: Sun, 3 Apr 2011 21:48:31 +0200 Subject: [texworks] complete reference for magic comments In-Reply-To: <4D98CC67.5000309@gmx.de> References: <4D98CC67.5000309@gmx.de> Message-ID: <97DA5082-59C8-4DD3-8E77-F1E287714441@googlemail.com> Am 03.04.2011 um 21:37 schrieb Matthias Pospiech: > I am trying to collect all necessary magic comments for a new template > for latex beginners. However google does not find them, and tw does not seem to > link on any page to a reference. > Therefore I would like to know if there is any complete reference for the magic comments. http://www.texdev.net/2011/03/24/texworks-magic-comments/ Wolfgang From matthias.pospiech at gmx.de Sun Apr 3 22:06:18 2011 From: matthias.pospiech at gmx.de (Matthias Pospiech) Date: Sun, 03 Apr 2011 22:06:18 +0200 Subject: [texworks] complete reference for magic comments In-Reply-To: <97DA5082-59C8-4DD3-8E77-F1E287714441@googlemail.com> References: <4D98CC67.5000309@gmx.de> <97DA5082-59C8-4DD3-8E77-F1E287714441@googlemail.com> Message-ID: <4D98D33A.1020407@gmx.de> An HTML attachment was scrubbed... URL: From schuster.wolfgang at googlemail.com Sun Apr 3 22:15:21 2011 From: schuster.wolfgang at googlemail.com (Wolfgang Schuster) Date: Sun, 3 Apr 2011 22:15:21 +0200 Subject: [texworks] complete reference for magic comments In-Reply-To: <4D98D33A.1020407@gmx.de> References: <4D98CC67.5000309@gmx.de> <97DA5082-59C8-4DD3-8E77-F1E287714441@googlemail.com> <4D98D33A.1020407@gmx.de> Message-ID: <5C6709A4-88A3-49A0-B9D6-0694BE8DC4AF@googlemail.com> Am 03.04.2011 um 22:06 schrieb Matthias Pospiech: > Am 03.04.2011 21:48, schrieb Wolfgang Schuster: >> >> Am 03.04.2011 um 21:37 schrieb Matthias Pospiech: >>> I am trying to collect all necessary magic comments for a new template >>> for latex beginners. However google does not find them, and tw does not seem to >>> link on any page to a reference. >>> Therefore I would like to know if there is any complete reference for the magic comments. >> http://www.texdev.net/2011/03/24/texworks-magic-comments/ > That was the only page I had found myself while searching for magic comments. > However it is far from a complete set. There is another one mentioned at the project wiki: http://code.google.com/p/texworks/wiki/TipsAndTricks#Using_the_outline_and_bookmarks_in_source_files Wolfgang -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Mon Apr 4 20:41:43 2011 From: st.loeffler at gmail.com (=?ISO-8859-15?Q?Stefan_L=F6ffler?=) Date: Mon, 04 Apr 2011 20:41:43 +0200 Subject: [texworks] Path for Scripts on Windows for Texlive and Miktex In-Reply-To: <4D98C430.1010809@gmx.de> References: <4D98C430.1010809@gmx.de> Message-ID: <4D9A10E7.5010604@gmail.com> Hi, On 2011-04-03 21:02, Matthias Pospiech wrote: > I would like to install some scripts, but on texlive and miktex tw is > located at > the main bin path and thus has no subdirs with scripts. > Therefore I would like to know where scripts are supposed to be located > in the case of miktex and texlive. scripts are usually not supposed to be located alongside the main application (unless special steps a taken, such as configuring portable mode). Scripts are always located in the "scripts" subdirectory of the resource folder. The resource folder, in turn, is located in a system-specific and configurable place. For the defaults, see http://code.google.com/p/texworks/wiki/TipsAndTricks#Locating_and_customizing_TeXworks_resources If you have the respective TeXworks executables installed, you can also use "Scripts > Scripting TeXworks > Show Scripts Folder" to determine the location. HTH Stefan PS: Both MiKTeX and TeXLive may have altered those default locations (usually to put the configuration files inside the texmf tree). This is better asked on the respective mailing lists, however, as that are distro-specific and not part of the "official" Tw code. -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Mon Apr 4 20:56:02 2011 From: st.loeffler at gmail.com (=?ISO-8859-15?Q?Stefan_L=F6ffler?=) Date: Mon, 04 Apr 2011 20:56:02 +0200 Subject: [texworks] New features and fixes to test Message-ID: <4D9A1442.9060707@gmail.com> Hi, following up on some recent discussions here on the mailing list, there have been some changes to Tw (up to r783). It would be great if you could test them (Windows builds are on GC, Ubuntu builds are uploaded to Launchpad and should be available soon, as always). Changes to test: - Functionalized PDF status bar widgets - double click on page number to open "goto" dialog; right click on zoom level to get some zoom options - "Help > Settings and Resources..." - new dialog that shows the locations where settings and resources are stored; also has links for easy access (except for the registry) - Test cases - PDF-related test cases have been added to svn (they are *not* distributed with the source/binary packages, however, as they are for testing purposes only) they are accessible via http://code.google.com/p/texworks/source/browse/trunk#trunk%2Ftestcases and there's also a README explaining how to use them Tw should pass all tests by default (on Windows and Ubuntu, where there are prebuilt binaries) Specialty for the Mac: - I've updated the poppler patches in lib-patches/. They should work with poppler 0.16.4, but I've only tested patching itself, as I can't build for the Mac. It would be great if someone could try building (the mac scheme should be picked up by default during ./configure) and ideally verify that fontconfig is not pulled in If you choose to test (some of) these changes, please report whether it works or not (or if it works partially/not entirely as expected). TIA Stefan PS: I intend to turn most (all?) of the recent changes into Tw 0.4.1 in the near future. From joseph.wright at morningstar2.co.uk Mon Apr 4 21:47:23 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Mon, 04 Apr 2011 20:47:23 +0100 Subject: [texworks] Large file issues? Message-ID: <4D9A204B.6040301@morningstar2.co.uk> Hello all, With large files (1000s of lines), I'm seeing two related issues: 1) If the file gets modified externally, TeXworks hangs on trying to reload. 2) If I try to alter the highlighting, same thing To be able to load the file, I then have to delete it from the recent files list (i.e. from the Registry on Windows or the plist on the Mac), otherwise I get a hang when I try to open it. I wonder if other people are seeing this issue. -- Joseph Wright From st.loeffler at gmail.com Tue Apr 5 19:18:31 2011 From: st.loeffler at gmail.com (=?windows-1252?Q?Stefan_L=F6ffler?=) Date: Tue, 05 Apr 2011 19:18:31 +0200 Subject: [texworks] Fink Package (for MAC OS X) TeXworks 0.3 - Build error In-Reply-To: References: <4D96FC2A.9030200@gmail.com> Message-ID: <4D9B4EE7.9080901@gmail.com> Hi, On 2011-04-05 16:44, Prerna Atri wrote: > Thanks for your valuable suggestions. We commented the compilation > flag used for enabling the poppler-xpdf headers and compiled TeXworks > source. The error reported earlier is no longer seen. That's good news. In the long run, I still think this should be re-enabled in the future, but for now every error that is gone is a good one ;). > However, we are currently facing the following failure on TeXworks > compilation. > / > / > / > /sw/src/fink.build/texworks-0.3-1/texworks-0.3/../../../../opt/kde4/mac/include/poppler/qt4/poppler-optcontent.cc:428:34: > error: poppler-optcontent.moc: No such file or directory > > The following build commands failed: > TeXworks: > CompileC > obj/TeXworks.build/Default/TeXworks.build/Objects-normal/i386/poppler-optcontent.o > /sw/src/fink.build/texworks-0.3-1/texworks-0.3/../../../../opt/kde4/mac/include/poppler/qt4/poppler-optcontent.cc > normal i386 c++ com.apple.compilers.gcc.4_2 > (1 failure) > / > > We searched for the .moc file but in vain. The poppler source folder > for 10.7 has only the poppler-optcontent.cc file, which makes a > reference to the poppler-optcontent.moc file, but we have not been > able to locate the actual file. Again the old reminders: Tw is currently at 0.5, not 0.3, and you should really use an up-to-date version of poppler! Anyway, I've looked at poppler 0.16.4, and the same file is still mentioned. Makefile.am (in the same directory) lists it as BUILT_SOURCES, so it's reasonable to assume it is an intermediate file produced on the fly. Indeed, there are also the following three lines in the same file: # This rule lets GNU make create any *.moc from the equivalent *.h .h.moc: $(AM_V_GEN) $(MOCQT4) -i $< -o $@ This suggests that you have to run Qt's moc to generate that file. Why this is not done automatically, however, is still a mystery to me. Speaking of mysteries - why does this error occur during the Tw build? Poppler is a dependency, but I'd expect it to be built/installed separately before Tw is touched for the first time. Related to this: if poppler is built as part of Tw (as opposed to separately), how is this done? For example, if it's not done using the usual ./configure && make, implicit rules like the .moc rule are easily missed. HTH Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Tue Apr 5 20:19:06 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 05 Apr 2011 20:19:06 +0200 Subject: [texworks] Fink Package (for MAC OS X) TeXworks 0.3 - Build error In-Reply-To: References: <4D96FC2A.9030200@gmail.com> <4D9B4EE7.9080901@gmail.com> Message-ID: <4D9B5D1A.1000506@gmail.com> Hi, On 2011-04-05 20:08, Prerna Atri wrote: > On Tue, Apr 5, 2011 at 10:48 PM, Stefan L?ffler > wrote: > > > Again the old reminders: Tw is currently at 0.5, not 0.3, and you > should really use an up-to-date version of poppler! > > > We are trying to port TeXworks as a package on Fink ( > http://www.finkproject.org/). According to Fink packaging policy, for > the installing the dependencies of the application we are trying to > port, we must use packages already on Fink. The versions we mentioned > for poppler and other dependencies are the latest ones currently > available on Fink. Hence, moving to a newer version of poppler ( > Hence, TW) is not feasible at the moment. There's not much difference between Tw 0.3 and 0.5 (at least if you use a recent revision of 0.3), it's just a naming convention. Re. poppler, I did note that you are using Fink and it only provides an old version. I was just suggesting that that should be updated eventually ;). > Anyway, I've looked at poppler 0.16.4, and the same file is still > mentioned. Makefile.am (in the same directory) lists it as > BUILT_SOURCES, so it's reasonable to assume it is an intermediate > file produced on the fly. Indeed, there are also the following > three lines in the same file: > # This rule lets GNU make create any *.moc from the equivalent *.h > .h.moc: > $(AM_V_GEN) $(MOCQT4) -i $< -o $@ > > This suggests that you have to run Qt's moc to generate that file. > Why this is not done automatically, however, is still a mystery to me. > > Speaking of mysteries - why does this error occur during the Tw > build? Poppler is a dependency, but I'd expect it to be > built/installed separately before Tw is touched for the first > time. Related to this: if poppler is built as part of Tw (as > opposed to separately), how is this done? For example, if it's not > done using the usual ./configure && make, implicit rules like the > .moc rule are easily missed. > > > As we mentioned above, poppler must be installed using the Fink > package which has already been built according to Fink packaging > policy. It could be possible that .moc files created in the process > are for some reason not available after installation. We shall try to > verify the same by installing poppler from source. This only emphasizes the point that most likely there are issues with poppler as provided by Fink (or as installed on your system). Normally, Tw shouldn't touch any sources of poppler, it only requires the header files and the libraries for linking. So it would probably be a good idea to track down the reason the build process tries to build (parts of) poppler. One wild guess would be that you don't have the qt4 backend for poppler (enabled by the --enable-poppler-qt4 configure switch), or Tw doesn't pick it up properly, anyway. HTH Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From prernaatri at gmail.com Tue Apr 5 16:44:19 2011 From: prernaatri at gmail.com (Prerna Atri) Date: Tue, 5 Apr 2011 20:14:19 +0530 Subject: [texworks] Fink Package (for MAC OS X) TeXworks 0.3 - Build error In-Reply-To: <4D96FC2A.9030200@gmail.com> References: <4D96FC2A.9030200@gmail.com> Message-ID: Hi Stefan, Thanks for your valuable suggestions. We commented the compilation flag used for enabling the poppler-xpdf headers and compiled TeXworks source. The error reported earlier is no longer seen. However, we are currently facing the following failure on TeXworks compilation. * * * /sw/src/fink.build/texworks-0.3-1/texworks-0.3/../../../../opt/kde4/mac/include/poppler/qt4/poppler-optcontent.cc:428:34: error: poppler-optcontent.moc: No such file or directory The following build commands failed: TeXworks: CompileC obj/TeXworks.build/Default/TeXworks.build/Objects-normal/i386/poppler-optcontent.o /sw/src/fink.build/texworks-0.3-1/texworks-0.3/../../../../opt/kde4/mac/include/poppler/qt4/poppler-optcontent.cc normal i386 c++ com.apple.compilers.gcc.4_2 (1 failure) * We searched for the .moc file but in vain. The poppler source folder for 10.7 has only the poppler-optcontent.cc file, which makes a reference to the poppler-optcontent.moc file, but we have not been able to locate the actual file. Thanks, Prerna Atri On Sat, Apr 2, 2011 at 4:06 PM, Stefan L?ffler wrote: > Hi, > > > On 2011-04-01 18:34, Prerna Atri wrote: > > We have been working on porting TeXworks ( version 0.3) as a package on > Fink. > > > It's great to hear that there still is some progress with Tw on the Mac :). > The latest version is labeled 0.5, though. > > > We are using the following Fink packages for building TeXworks: > > > - qt4-mac ( v 4.6.3-2) > - poppler4-qt4-mac ( v 0.10.7-3) > - fontconfig-config ( v 2.8.0-4) > - poppler-data ( v 0.2.1-1) > - hunspell ( v 1.2.12-1002) > - poppler4-xpdf ( v 0.10.7-1) > - libhunspell ( v 1.2.12-1002) > > > Some of these seem outdated: > * Qt - latest stable version: 4.7.2 (though the difference to the 4.6 > series is probably not too important for Tw) > * Hunspell - latest stable version: 1.3.1 (again, I don't think this is > very relevant) > * poppler - latest stable version: 0.16 (now, this is very relevant!) > * poppler-data - latest stable version: 0.4.4 > > > > When building TeXworks after installing the above metioned packages, we > are getting the following failure: > > */sw/src/fink.build/texworks-0.3-1/texworks-0.3/src/TWApp.cpp: In member > function ?void TWApp::init()?:* > */sw/src/fink.build/texworks-0.3-1/texworks-0.3/src/TWApp.cpp:159: error: > no matching function for call to ?GlobalParams::GlobalParams(char*)?* > */sw/include/poppler/GlobalParams.h:162: note: candidates are: > GlobalParams::GlobalParams()* > */sw/include/poppler/GlobalParams.h:157: note: > GlobalParams::GlobalParams(const GlobalParams&)* > *** BUILD FAILED *** > > > This is a result of the ancient poppler version. > In recent versions (I think from 0.12 on), the constructor of GlobalParams > takes as argument the location of the private poppler directory. Note, > however, that for this to be effective, you need to have a patched version > of poppler, which I guess is not what you (initially) want with Fink, unless > you have to. For more information, see src/TWApp.cpp (lines 148-152), as > well as the lib-patches/ directory. > > The easiest solution would be to comment out the line > QMAKE_CXXFLAGS += -DHAVE_POPPLER_XPDF_HEADERS > in TeXworks.pro, though. This way, you will not be able to use a > poppler-data/ directory alongside the TeXworks.app bundle, but poppler > should look for the default ones in some system dependent global directory. > In any case, you should check if this works properly (i.e., it picks up the > files installed by poppler-data). > > HTH > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From prernaatri at gmail.com Tue Apr 5 20:08:24 2011 From: prernaatri at gmail.com (Prerna Atri) Date: Tue, 5 Apr 2011 23:38:24 +0530 Subject: [texworks] Fink Package (for MAC OS X) TeXworks 0.3 - Build error In-Reply-To: <4D9B4EE7.9080901@gmail.com> References: <4D96FC2A.9030200@gmail.com> <4D9B4EE7.9080901@gmail.com> Message-ID: Hi, On Tue, Apr 5, 2011 at 10:48 PM, Stefan L?ffler wrote: > Hi, > > > On 2011-04-05 16:44, Prerna Atri wrote: > > Thanks for your valuable suggestions. We commented the compilation flag > used for enabling the poppler-xpdf headers and compiled TeXworks source. The > error reported earlier is no longer seen. > > > That's good news. In the long run, I still think this should be re-enabled > in the future, but for now every error that is gone is a good one ;). > > > However, we are currently facing the following failure on TeXworks > compilation. > * > * > * > /sw/src/fink.build/texworks-0.3-1/texworks-0.3/../../../../opt/kde4/mac/include/poppler/qt4/poppler-optcontent.cc:428:34: > error: poppler-optcontent.moc: No such file or directory > > The following build commands failed: > TeXworks: > CompileC > obj/TeXworks.build/Default/TeXworks.build/Objects-normal/i386/poppler-optcontent.o > /sw/src/fink.build/texworks-0.3-1/texworks-0.3/../../../../opt/kde4/mac/include/poppler/qt4/poppler-optcontent.cc > normal i386 c++ com.apple.compilers.gcc.4_2 > (1 failure) > * > > We searched for the .moc file but in vain. The poppler source folder for > 10.7 has only the poppler-optcontent.cc file, which makes a reference to the > poppler-optcontent.moc file, but we have not been able to locate the actual > file. > > > Again the old reminders: Tw is currently at 0.5, not 0.3, and you should > really use an up-to-date version of poppler! > > We are trying to port TeXworks as a package on Fink ( http://www.finkproject.org/). According to Fink packaging policy, for the installing the dependencies of the application we are trying to port, we must use packages already on Fink. The versions we mentioned for poppler and other dependencies are the latest ones currently available on Fink. Hence, moving to a newer version of poppler ( Hence, TW) is not feasible at the moment. > Anyway, I've looked at poppler 0.16.4, and the same file is still > mentioned. Makefile.am (in the same directory) lists it as BUILT_SOURCES, so > it's reasonable to assume it is an intermediate file produced on the fly. > Indeed, there are also the following three lines in the same file: > # This rule lets GNU make create any *.moc from the equivalent *.h > .h.moc: > $(AM_V_GEN) $(MOCQT4) -i $< -o $@ > > This suggests that you have to run Qt's moc to generate that file. Why this > is not done automatically, however, is still a mystery to me. > > Speaking of mysteries - why does this error occur during the Tw build? > Poppler is a dependency, but I'd expect it to be built/installed separately > before Tw is touched for the first time. Related to this: if poppler is > built as part of Tw (as opposed to separately), how is this done? For > example, if it's not done using the usual ./configure && make, implicit > rules like the .moc rule are easily missed. > As we mentioned above, poppler must be installed using the Fink package which has already been built according to Fink packaging policy. It could be possible that .moc files created in the process are for some reason not available after installation. We shall try to verify the same by installing poppler from source. > > HTH > Stefan > Thanks, Prerna. -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Wed Apr 6 11:02:08 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Wed, 06 Apr 2011 11:02:08 +0200 Subject: [texworks] New features and fixes to test In-Reply-To: <4D9A1442.9060707@gmail.com> References: <4D9A1442.9060707@gmail.com> Message-ID: <4D9C2C10.3030701@gmail.com> Hi, On 2011-04-04 20:56, Stefan L?ffler wrote: > - Test cases - PDF-related test cases have been added to svn (they are > *not* distributed with the source/binary packages, however, as they are > for testing purposes only) > they are accessible via > http://code.google.com/p/texworks/source/browse/trunk#trunk%2Ftestcases > and there's also a README explaining how to use them > Tw should pass all tests by default (on Windows and Ubuntu, where there > are prebuilt binaries) Addendum: These instructions may have been misleading (sorry for that, and thanks to Paul Norman for pointing it out). From the link posted above, you actually need to click each file in turn to get to GC's inline display of it (which will just give you a note that it can't display it for all but the README). There, you'll find a link labeled "View raw file" on the right hand side, which will finally give you access to the file itself. Saving the link from the file list I linked to will only give you the inline display HTML page, *not* the pdfs or pngs. The better way is to download the files directly from http://texworks.googlecode.com/svn/trunk/testcases HTH Stefan From st.loeffler at gmail.com Thu Apr 7 10:55:46 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 07 Apr 2011 10:55:46 +0200 Subject: [texworks] Large file issues? In-Reply-To: <4D9A204B.6040301@morningstar2.co.uk> References: <4D9A204B.6040301@morningstar2.co.uk> Message-ID: <4D9D7C12.5060400@gmail.com> Hi, On 2011-04-04 21:47, Joseph Wright wrote: > With large files (1000s of lines), I'm seeing two related issues: > 1) If the file gets modified externally, TeXworks hangs on trying to > reload. > 2) If I try to alter the highlighting, same thing > > To be able to load the file, I then have to delete it from the recent > files list (i.e. from the Registry on Windows or the plist on the Mac), > otherwise I get a hang when I try to open it. I wonder if other people > are seeing this issue. I can reproduce these issues. The problem seems to be in the syntax highlighter, which takes a long time to (re)highlight the whole document. Ideally, this should probably be done in some kind of on-demand fashion, but AFAIK this is not implemented in the QTextDocument class we use ATM. A few things to note: * changing the spell checking language also triggers a (complete) rehighlight * when loading a file with "!TEX ..." modlines, this can trigger one (or multiple) rehighlights. * in the recent files list, settings like spell checking language and syntax highlighting are also stored; therefore, when opening a file that has been open recently, one or more additional rehighlights take place. That said, r784 should alleviate this problem a bit, in that it catches the situation that a setting is overwritten by the same value and doesn't trigger a rehighlight in that case (e.g., spell checking is set to en_US, and the recent files handler "changes" it to en_US, no rehighlight takes place). Note, though, that while this should ensure that rehighlighting only takes place when necessary, it doesn't cut down on the time that takes by itself. I have experimented with some form of incremental update, but it seems prone to some hard-to-track errors (e.g., rehighlighting is scheduled for a paragraph, but that is deleted in the meantime). So, I guess this won't be solved completely until we do a complete overhaul of the editor. So, maybe it would be a good idea to open a bug report for this on GC. HTH Stefan From joseph.wright at morningstar2.co.uk Thu Apr 7 15:12:14 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Thu, 07 Apr 2011 14:12:14 +0100 Subject: [texworks] Large file issues? In-Reply-To: <4D9D7C12.5060400@gmail.com> References: <4D9A204B.6040301@morningstar2.co.uk> <4D9D7C12.5060400@gmail.com> Message-ID: <4D9DB82E.3030500@morningstar2.co.uk> On 07/04/2011 09:55, Stefan L?ffler wrote: > I can reproduce these issues. The problem seems to be in the syntax > highlighter, which takes a long time to (re)highlight the whole > document. Ideally, this should probably be done in some kind of > on-demand fashion, but AFAIK this is not implemented in the > QTextDocument class we use ATM. I guessed this was the case. Of course, what I need is files which are better divided up! (Not so simple, but probably desirable in the long term.) -- Joseph Wright From Daniela.Bose at Grenzebach.com Thu Apr 7 13:48:22 2011 From: Daniela.Bose at Grenzebach.com (Bose Daniela GA) Date: Thu, 7 Apr 2011 13:48:22 +0200 Subject: [texworks] Message from TeXworks user Message-ID: <1F951EF8FB2679498C987FF863D9941FD2A8F3@schreibnix.eggenstein.grenzebach.de> Hallo liebes TeXworksteam, ich habe ein Problem, ich bekomme den movie15 nicht installiert, wegen einer nicht autorisierten Berechtigung oder so. K?nnen Sie mir helfen, wie kann ich den movie 15 nachinstallieren. Ich denke das wird bei mir geblockt. Kann ich den movie15 auch anders nachinstallieren? Dear TeXworkteam, my english ist not so good , I have problems to install the movie15. MiKTeX Problem Report Message: HTTP/1.0 407 Proxy Authentication Required Data: FEHLER: Cache-Zugriff Verweigert

FEHLER

Cache-Zugriff Verweigert

Während des Versuches, die Seite
http://api.miktex.org/Repository.asmx
zu laden, trat der folgende Fehler auf:

  • Cache-Zugriff verweigert

Leider sind Sie zur Zeit nicht berechtigt 

    http://api.miktex.org/Repository.asmx
von diesem Cache zu beziehen, bis Sie sich authentifiziert haben.

Sie benötigen hierzu Netscape Version 2.0 (oder höher), Microsoft Internet Explorer 3.0 oder einen anderen HTTP/1.1 Browser. Bitte kontaktieren Sie den Cache-Administrator, wenn Sie Probleme haben, sich zu authentifizieren, oder ändern Sie Ihr Passwort.


Generated Thu, 07 Apr 2011 11:49:01 GMT by downloadnix.grenzebach.de (squid/2.6.STABLE5)
Source: Libraries\MiKTeX\PackageManager\PackageManager.cpp Line: 1507 MiKTeX: 2.9 OS: Microsoft Windows XP Professional Service Pack 3 (build 2600) Invokers: explorer/miktex-texworks/texify SystemAdmin: yes PowerUser: no Root0: C:\Dokumente und Einstellungen\boseda\Anwendungsdaten\MiKTeX\2.9 Root1: C:\Dokumente und Einstellungen\boseda\Lokale Einstellungen\Anwendungsdaten\MiKTeX\2.9 Root2: C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\MiKTeX\2.9 Root3: C:\Programme\MiKTeX 2.9 UserInstall: C:\Dokumente und Einstellungen\boseda\Anwendungsdaten\MiKTeX\2.9 UserConfig: C:\Dokumente und Einstellungen\boseda\Anwendungsdaten\MiKTeX\2.9 UserData: C:\Dokumente und Einstellungen\boseda\Lokale Einstellungen\Anwendungsdaten\MiKTeX\2.9 CommonInstall: C:\Programme\MiKTeX 2.9 CommonConfig: C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\MiKTeX\2.9 CommonData: C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\MiKTeX\2.9 Please can you help me? ----- configuration info ----- TeXworks version : 0.4.0r759 (MiKTeX 2.9) Install location : C:/Programme/MiKTeX 2.9/miktex/bin/miktex-texworks.exe Library path : C:/Dokumente und Einstellungen/boseda/Lokale Einstellungen/Anwendungsdaten/MiKTeX/2.9/TeXworks/0.4\ pdfTeX location : C:/Programme/MiKTeX 2.9/miktex/bin/pdftex.exe Operating system : Windows Microsoft Windows XP Professional Service Pack 3 (build 2600) Qt4 version : 4.7.2 (build) / 4.7.2 (runtime) ------------------------------ ___________________________________________ Grenzebach Automation GmbH, 76189 Karlsruhe, Germany, Registergericht Augsburg, HRB 20472, Gesch?ftsf?hrer: Roman Kaiser, Gesch?ftsf?hrer: Bernd Minning Hinweis auf elektronischen Datenschutz Diese elektronische Nachricht, einschlie?lich Anhang, ist eine vertrauliche Nachricht zwischen Grenzebach und den vorgesehenen Empf?nger/n, angegeben als Addressat/en. Sie beinhaltet private, rechtlich gesch?tzte Informationen. Falls Sie diese Nachricht in irgendeiner Form bekommen und Sie sind nicht der vorgesehene Empf?nger, bitten wir Sie, die Nachricht nicht zu lesen, verwenden, besprechen oder zu verbreiten. Wir w?ren Ihnen dankbar, wenn Sie den Sender dieser Nachricht nach Erhalt benachrichtigen. Bitte vernichten sie die Nachricht umgehend. Jegliche au?erbetriebliche Informationen, die nicht mit Grenzebach oder Partnern verbunden sind, werden weder von Grenzebach bef?rwortet, noch ist Grenzebach daf?r haftbar. INTERNET CONFIDENTIALITY STATEMENTS This electronic mail message, including attachments, is a confidential communication exclusively between GRENZEBACH and the intended recipient(s) indicated as the addressee(s). It contains information that is private and may be proprietary or may be covered by legal professional privilege. If you receive this message in any form and you are not the intended recipient you must not review, use, discuss or disseminate it. We would be grateful if you could contact the sender upon receipt and in any event you should destroy this message without delay. Anything contained in this message that is not connected with the business of GRENZEBACH or its affiliates is neither endorsed by nor is the liability of this company. -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Thu Apr 7 16:20:02 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 07 Apr 2011 16:20:02 +0200 Subject: [texworks] Message from TeXworks user In-Reply-To: <1F951EF8FB2679498C987FF863D9941FD2A8F3@schreibnix.eggenstein.grenzebach.de> References: <1F951EF8FB2679498C987FF863D9941FD2A8F3@schreibnix.eggenstein.grenzebach.de> Message-ID: <4D9DC812.2080205@gmail.com> Hi, On 2011-04-07 13:48, Bose Daniela GA wrote: > > my english ist not so good , I have problems to install the movie15. > What is movie15? / Was ist movie15? > ** > > *FEHLER: Cache-Zugriff Verweigert* > > [...] > > *

Leider sind Sie zur Zeit nicht berechtigt* > > *

    http://api.miktex.org/Repository.asmx
* > > *von diesem Cache zu beziehen, bis Sie sich authentifiziert haben.* > > *

* > > *

* > > *Sie benötigen hierzu Netscape Version 2.0 (oder höher), > Microsoft Internet* > > *Explorer 3.0 oder einen anderen HTTP/1.1 Browser. Bitte kontaktieren Sie* > > *den Cache-Administrator, wenn Sie > Probleme haben,* > > *sich zu authentifizieren, oder* > > * HREF="http://downloadnix.grenzebach.de/cgi-bin/chpasswd.cgi">ändern > Sie Ihr Passwort.* > > *[...]*** > > *Generated Thu, 07 Apr 2011 11:49:01 GMT by downloadnix.grenzebach.de > (squid/2.6.STABLE5)* > This sounds like a problem with your company's internet connection. As it says, you need to authenticate yourself somehow. Please contact your system administrator. This is not a TeXworks problem (TeXworks is only a front-end), and I doubt it is a MiKTeX problem, either. Das klingt mir sehr nach einem Problem mit der Internetverbindung in Ihrer Firma. In der Fehlermeldung steht ja, dass Sie sich authentifizieren m?ssen (mit Link zur Firmenwebsite). Wenden Sie sich daher bitte an Ihren Systemadministrator. Jedenfalls sieht mir das nicht nach einem Problem mit TeXworks aus (das ja nur ein Editor ist). Es ist eher noch ein Problem mit MiKTeX, aber auch das glaube ich nicht. HTH Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From bvoisin at me.com Thu Apr 7 16:26:06 2011 From: bvoisin at me.com (Bruno Voisin) Date: Thu, 07 Apr 2011 16:26:06 +0200 Subject: [texworks] Message from TeXworks user In-Reply-To: <4D9DC812.2080205@gmail.com> References: <1F951EF8FB2679498C987FF863D9941FD2A8F3@schreibnix.eggenstein.grenzebach.de> <4D9DC812.2080205@gmail.com> Message-ID: <6807E97C-971A-4FAD-A98C-EC93BC075EA9@me.com> Le 7 avr. 2011 ? 16:20, Stefan L?ffler a ?crit : > What is movie15? / Was ist movie15? It's a LaTeX package for movie inclusion (and sound, and 3D effects) in PDF output: http://www.ctan.org/tex-archive/macros/latex/contrib/movie15 That said, I heard of its existence but I've never used it myself. Bruno Voisin From esperanto at swing.be Thu Apr 7 17:10:27 2011 From: esperanto at swing.be (Alain Delmotte) Date: Thu, 07 Apr 2011 17:10:27 +0200 Subject: [texworks] auto completion In-Reply-To: <4D984D3F.5070609@gaponline.de> References: <4D96FC9A.1030901@gmail.com> <4D9826EC.6060508@gaponline.de> <4D982AD9.5050900@gmail.com> <4D9832E2.907@gaponline.de> <4D984451.1050704@gmail.com> <4D984D3F.5070609@gaponline.de> Message-ID: <4D9DD3E3.6020703@swing.be> Hi! One note: it is not useful to suppress the other completion definitions. Example: if you have the following completion short cuts bit bite bitemy if you type "bit", then you get the first completion definition (bit), but typing again switch to the second (bite), again gets the third (bitemy) and again brings you back to the first one. This allows to have, only typing bit: \begin{itemize} \item \end{itemize} and then typing \begin{itemize} \item[xyz] \end{itemize} and so on... Regards, Alain Le 3/04/2011 12:34, Andreas Hirsch a ?crit : > quoting Stefan L?ffler, [03.04.2011 11:56 +0100]: >> On 2011-04-03 10:42, Andreas Hirsch wrote: >>> now things work _nearly_ als expected, the expanded text is: >>> >>> \begin{itemize} >>> \item \end{itemize} >>> ? >>> >>> Could it be solved that: >>> >>> - \end{itemize} goes into the next line but >>> - no empty line is produced? >>> >>> I mean >>> >>> \begin{itemize} >>> \item >>> \end{itemize} >>> ? >>> >>> and the cursor is placed behind item? >> >> Sure. >> bit:=\begin{itemize}#RET#\item#INS##RET#\end{itemize}#RET#? >> Should do the trick. Note that #INS# only marks the cursor position, it >> doesn't insert anything (no spaces, newlines, etc.). > > works! great! > > Thank You! > > Andreas > From paul.a.norman at gmail.com Thu Apr 7 23:46:54 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Fri, 8 Apr 2011 09:46:54 +1200 Subject: [texworks] Message from TeXworks user In-Reply-To: <6807E97C-971A-4FAD-A98C-EC93BC075EA9@me.com> References: <1F951EF8FB2679498C987FF863D9941FD2A8F3@schreibnix.eggenstein.grenzebach.de> <4D9DC812.2080205@gmail.com> <6807E97C-971A-4FAD-A98C-EC93BC075EA9@me.com> Message-ID: Its a cool package. Liebe Daniela Bose GA, You may want to head over to the MiKTeX Forum, but try doing an update on your MiKTeX installation first perhaps. And then retry your document. http://sourceforge.net/projects/miktex/forums/forum/33790 Mein Deutsch ist schlecht! Sie m?ssen m?glicherweise auf MiKTeX Forum gehen, aber zuerst versuchen, ein Update auf Ihrem MiKTeX-Installation. Und dann versuchen, das Dokument zun?chst retypeset. Paul Data: FEHLER Cache-Zugriff Verweigert -------------------------------------------------------------------------------- W?hrend des Versuches, die Seite http://api.miktex.org/Repository.asmx zu laden, trat der folgende Fehler auf: Cache-Zugriff verweigert Leider sind Sie zur Zeit nicht berechtigt http://api.miktex.org/Repository.asmx von diesem Cache zu beziehen, bis Sie sich authentifiziert haben. Sie ben?tigen hierzu Netscape Version 2.0 (oder h?her), Microsoft Internet Explorer 3.0 oder einen anderen HTTP/1.1 Browser. Bitte kontaktieren Sie den Cache-Administrator, wenn Sie Probleme haben, sich zu authentifizieren, oder ?ndern Sie Ihr Passwort. Data: ERROR Cache Access Denied -------------------------------------------------- ------------------------------ During the experiment, the page http://api.miktex.org/Repository.asmx to invite the following error occurred: Cache Access Denied Unfortunately, you are not currently entitled http://api.miktex.org/Repository.asmx to purchase from this cache until you have authenticated yourself. You will need Netscape version 2.0 (or higher), Microsoft Internet Explorer 3.0 or an HTTP/1.1 compliant browser. Please contact the cache administrator if you have problems to log in, or change your password. On 8 April 2011 02:26, Bruno Voisin wrote: > Le 7 avr. 2011 ? 16:20, Stefan L?ffler a ?crit : > >> What is movie15? / Was ist movie15? > > It's a LaTeX package for movie inclusion (and sound, and 3D effects) in PDF output: > > http://www.ctan.org/tex-archive/macros/latex/contrib/movie15 > > That said, I heard of its existence but I've never used it myself. > > Bruno Voisin > > > From patrick at gundla.ch Thu Apr 7 16:21:00 2011 From: patrick at gundla.ch (Patrick Gundlach) Date: Thu, 7 Apr 2011 16:21:00 +0200 Subject: [texworks] Message from TeXworks user In-Reply-To: <1F951EF8FB2679498C987FF863D9941FD2A8F3@schreibnix.eggenstein.grenzebach.de> References: <1F951EF8FB2679498C987FF863D9941FD2A8F3@schreibnix.eggenstein.grenzebach.de> Message-ID: <7D05DCD7-8B63-45D6-875E-6B9AE5324792@gundla.ch> Hi, this sounds like a "local" problem to me. Do you have access to that page when you copy the following link into your web browser? Funktioniert diese URL, wenn du sie in den Browser kopierst? http://api.miktex.org/Repository.asmx Perhaps MikTeX doesn't honor some proxy settings? For me being no MikTeX expert, this does not sound like a problem that is directly related to TW, right? Patrick just for the non-german speaking user: > ich habe ein Problem, ich bekomme den movie15 nicht installiert, wegen einer nicht autorisierten Berechtigung oder so. > > K?nnen Sie mir helfen, wie kann ich den movie 15 nachinstallieren. Ich denke das wird bei mir geblockt. > > Kann ich den movie15 auch anders nachinstallieren? this is a longer version of the translation given: > I have problems to install the movie15. > FEHLER: Cache-Zugriff Verweigert error: cache access denied > > Während des Versuches, die Seite
while trying to access the page > > http://api.miktex.org/Repository.asmx
> > zu laden, trat der folgende Fehler auf: the following error occured: > Cache-Zugriff verweigert cache access denied. >

Leider sind Sie zur Zeit nicht berechtigt > > 

    http://api.miktex.org/Repository.asmx
> > von diesem Cache zu beziehen, bis Sie sich authentifiziert haben. you're not allowed to get [url] until you are authenticated. ... From M.Anyadike-Danes at erini.ac.uk Fri Apr 8 10:24:52 2011 From: M.Anyadike-Danes at erini.ac.uk (Michael Anyadike-Danes) Date: Fri, 8 Apr 2011 09:24:52 +0100 Subject: [texworks] message from TeXworks user(MiKTeX) Message-ID: Texworks user group I have loaded a new .bst file, updated the MiKTex database, but when I open (otherwise) exactly the same file in TeXworks it gives the message below, can anyone advise? Michael Anyadike-Danes ----------------------------------------------------- ! Extra }, or forgotten \endgroup. \par ...m \@noitemerr {\@@par }\fi \else {\@@par } \fi l.18 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lrudolph at meganet.net Fri Apr 8 18:27:37 2011 From: lrudolph at meganet.net (lrudolph at meganet.net) Date: Fri, 8 Apr 2011 12:27:37 -0400 (EDT) Subject: [texworks] how can I reset the editor that is called by typing "e" in the console bar? Message-ID: <60471.166.84.1.5.1302280057.squirrel@webmail.meganet.net> Good day, all. I have recently begun to use TeXWorks as a front end to MikTex (which I have been using for many years, after switching to it from emTeX), and I love it. I particularly love that I can easily switch from viewing a typeset chapter of the book I'm working on at the moment, to the TeX source file of that chapter, nicely opened for me at the right line in TeXWorks. HOWEVER, in some cases I would prefer to simply type "e" in the console bar, in direct reply to the TeX error message, and jump into the appropriate source file, as before opened for me in TeXWorks--but because of some setting, somewhere, what I jump into instead is notepad. (I am running all this under Windows 7.) This isn't the end of the world, but it is annoying. Is this setting something I can change (surely it is), and if so, how? It doesn't appear to be a TeXWorks setting (though I think it ought to be...); is it a MikTeX setting? a Windows setting? A Google search has not been informative. Lee Rudolph From reinhard.kotucha at web.de Sat Apr 9 19:42:35 2011 From: reinhard.kotucha at web.de (Reinhard Kotucha) Date: Sat, 9 Apr 2011 19:42:35 +0200 Subject: [texworks] how can I reset the editor that is called by typing "e" in the console bar? In-Reply-To: <60471.166.84.1.5.1302280057.squirrel@webmail.meganet.net> References: <60471.166.84.1.5.1302280057.squirrel@webmail.meganet.net> Message-ID: <19872.39563.497258.364005@zaphod.ms25.net> On 2011-04-08 at 12:27:37 -0400, lrudolph at meganet.net wrote: > Good day, all. I have recently begun to use TeXWorks as a front > end to MikTex (which I have been using for many years, after > switching to it from emTeX), and I love it. I particularly love > that I can easily switch from viewing a typeset chapter of the book > I'm working on at the moment, to the TeX source file of that > chapter, nicely opened for me at the right line in TeXWorks. > > HOWEVER, in some cases I would prefer to simply type "e" in the > console bar, in direct reply to the TeX error message, and jump > into the appropriate source file, as before opened for me in > TeXWorks--but because of some setting, somewhere, what I jump into > instead is notepad. (I am running all this under Windows 7.) This > isn't the end of the world, but it is annoying. > > Is this setting something I can change (surely it is), and if so, > how? It doesn't appear to be a TeXWorks setting (though I think it > ought to be...); is it a MikTeX setting? a Windows setting? A > Google search has not been informative. This is usually controlled by the environment variable TEXEDIT. The built-in default is notepad because it's assumed that that this exists on all Windows installations. You can set TEXEDIT=texworks -p=%d %s where %s is a placeholder for the filename and %d for the line number. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha at web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- From lrudolph at meganet.net Sat Apr 9 21:20:33 2011 From: lrudolph at meganet.net (lrudolph at meganet.net) Date: Sat, 09 Apr 2011 15:20:33 -0400 Subject: [texworks] how can I reset the editor that is called by typing "e" in the console bar? In-Reply-To: <19872.39563.497258.364005@zaphod.ms25.net> References: <60471.166.84.1.5.1302280057.squirrel@webmail.meganet.net>, <19872.39563.497258.364005@zaphod.ms25.net> Message-ID: <4DA07941.7662.1DC3B48@lrudolph.meganet.net> Richard Kotucha replied to my question (in the Subject: header) > This is usually controlled by the environment variable TEXEDIT. The > built-in default is notepad because it's assumed that that this exists > on all Windows installations. > > You can set > > TEXEDIT=texworks -p=%d %s > > where %s is a placeholder for the filename and %d for the line number. Thank you! In fact, this morning I got a bit cleverer with Google, and discovered that by TeXing something with the --src-special option, then opening the dvi file with YAP, I could set *YAP's* preferred editor, and that that would reset TexWork's (presumably by effecting the change to TEXEDIT as described above). I hadn't gotten around to writing to the list, but I'm very glad to have your explanation (which contains information that I still cannot locate in any of the help files supplied with MikTeX or TexWorks...though maybe a search on TEXEDIT might work; I'll try that). Regards, Lee Rudolph From st.loeffler at gmail.com Sun Apr 10 12:34:27 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 10 Apr 2011 12:34:27 +0200 Subject: [texworks] message from TeXworks user(MiKTeX) In-Reply-To: References: Message-ID: <4DA187B3.6000708@gmail.com> Hi, On 2011-04-08 10:24, Michael Anyadike-Danes wrote: > I have loaded a new .bst file, updated the MiKTex database, but when I > open (otherwise) exactly the same file in TeXworks it gives the > message below, can anyone advise? > > > > Michael Anyadike-Danes > > ----------------------------------------------------- > > ! Extra }, or forgotten \endgroup. > > \par ...m \@noitemerr {\@@par }\fi \else {\@@par } > > \fi > > l.18 > With the information you provided, I'm afraid no one can guess what's wrong. Some shot in the dark: did you try to remove all auxiliary files (e.g., via the "File" menu)? If this doesn't help, it would be helpful if you could provide the following information: * what .bst file do you use (is it a customized one, maybe?) * does this problem occur independently of which bibliography file you use? (sometimes, there is wrong data in the .bib file already) * a minimal example file; basically, an empty document with just one \cite command (and, of course, your .bst file) should suffice, if this is a fundamental problem. HTH Stefan PS: Which versions of Tw and MiKTeX do you use? On which operating system? -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Sun Apr 10 12:38:45 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 10 Apr 2011 12:38:45 +0200 Subject: [texworks] how can I reset the editor that is called by typing "e" in the console bar? In-Reply-To: <4DA07941.7662.1DC3B48@lrudolph.meganet.net> References: <60471.166.84.1.5.1302280057.squirrel@webmail.meganet.net>, <19872.39563.497258.364005@zaphod.ms25.net> <4DA07941.7662.1DC3B48@lrudolph.meganet.net> Message-ID: <4DA188B5.2000308@gmail.com> Hi, On 2011-04-09 21:20, lrudolph at meganet.net wrote: > Thank you! In fact, this morning I got a bit cleverer > with Google, and discovered that by TeXing something > with the --src-special option, then opening the dvi > file with YAP, I could set *YAP's* preferred editor, > and that that would reset TexWork's (presumably by > effecting the change to TEXEDIT as described above). > I hadn't gotten around to writing to the list, but > I'm very glad to have your explanation (which contains > information that I still cannot locate in any of the > help files supplied with MikTeX or TexWorks...though > maybe a search on TEXEDIT might work; I'll try that). In principle, Tw does set the TEXEDIT variable just before running the typeset command. However, there seems to have been an error in the way it did that, which should be fixed in r791. On a different matter, MiKTeX doesn't seem to respect that variable. Instead, one with the name MIKTEX_EDITOR is used. I didn't find any documentation of it (other than some forum posts), but it seems to work (at least on my MiKTeX 2.8 test system), so I added it to Tw as well (also in r791). HTH Stefan From st.loeffler at gmail.com Sun Apr 10 15:08:48 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 10 Apr 2011 15:08:48 +0200 Subject: [texworks] New features and fixes to test In-Reply-To: <4D9C2C10.3030701@gmail.com> References: <4D9A1442.9060707@gmail.com> <4D9C2C10.3030701@gmail.com> Message-ID: <4DA1ABE0.2010206@gmail.com> Hi, any progress on the testing of the new features? Do things work as expected? Do the test cases succeed? Also, what about the recent changes to the poppler patches for the Mac? Anyone? Regards, Stefan From gzjjgod at gmail.com Mon Apr 11 10:39:30 2011 From: gzjjgod at gmail.com (Jjgod Jiang) Date: Mon, 11 Apr 2011 10:39:30 +0200 Subject: [texworks] New features and fixes to test In-Reply-To: <4DA1ABE0.2010206@gmail.com> References: <4D9A1442.9060707@gmail.com> <4D9C2C10.3030701@gmail.com> <4DA1ABE0.2010206@gmail.com> Message-ID: On Sun, Apr 10, 2011 at 3:08 PM, Stefan L?ffler wrote: > any progress on the testing of the new features? Do things work as > expected? Do the test cases succeed? > Also, what about the recent changes to the poppler patches for the Mac? I can test the poppler patches once I get some time. Meanwhile, can you please update the TeXworks.pro to match the updated build instructions for Mac? Thanks. - Jiang From bpj at melroch.se Mon Apr 11 13:44:51 2011 From: bpj at melroch.se (BPJ) Date: Mon, 11 Apr 2011 13:44:51 +0200 Subject: [texworks] Are the smart quote strings configurable? Message-ID: <4DA2E9B3.7050709@melroch.se> The subject line says it all, really: Are the smart quote strings configurable? Ideally they should be configurable through the GUI since they are language dependent: what's appropriate for English isn't appropriate for Swedish, and other languages have other quoting styles again. I would like to have TW's smart quoting feature being able to turn " and ' into ? and ?, rather than ?? ?? while I type. Configuring the whole once and for all deep down in a config file won't do, as I work on English and Swedish documents about 50/50. P.S. I've always found the TeX ligatures rather annoying and prefer to use Unicode characters in my source, as you may have guessed. Interestingly I feel the other way around when it comes to -- and --- ! :-) /bpj From st.loeffler at gmail.com Mon Apr 11 14:07:42 2011 From: st.loeffler at gmail.com (=?windows-1252?Q?Stefan_L=F6ffler?=) Date: Mon, 11 Apr 2011 14:07:42 +0200 Subject: [texworks] Are the smart quote strings configurable? In-Reply-To: <4DA2E9B3.7050709@melroch.se> References: <4DA2E9B3.7050709@melroch.se> Message-ID: <4DA2EF0E.6030302@gmail.com> Hi, On 2011-04-11 13:44, BPJ wrote: > The subject line says it all, really: Are the smart quote strings > configurable? Ideally they should be configurable through the GUI > since they are language dependent: what's appropriate for English > isn't appropriate for Swedish, and other languages have other > quoting styles again. I would like to have TW's smart quoting > feature being able to turn " and ' into ? and ?, rather than > ?? ?? while I type. Configuring the whole once and for all > deep down in a config file won't do, as I work on English > and Swedish documents about 50/50. hm, despite the subject line and your text, I still don't know completely what you want ;). Anyway, I'll try to explain. Smart quotes are configurable in the file configuration/smart-quotes-modes.txt. Unfortunately, there is no UI dialog for this. However, you can add new settings there. So you could add something like "[Unicode Swedish]" and "[Unicode English]". Then both settings are available from the menu. HTH Stefan From st.loeffler at gmail.com Mon Apr 11 14:14:52 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Mon, 11 Apr 2011 14:14:52 +0200 Subject: [texworks] New features and fixes to test In-Reply-To: References: <4D9A1442.9060707@gmail.com> <4D9C2C10.3030701@gmail.com> <4DA1ABE0.2010206@gmail.com> Message-ID: <4DA2F0BC.6000807@gmail.com> Hi, On 2011-04-11 10:39, Jjgod Jiang wrote: > On Sun, Apr 10, 2011 at 3:08 PM, Stefan L?ffler wrote: >> any progress on the testing of the new features? Do things work as >> expected? Do the test cases succeed? >> Also, what about the recent changes to the poppler patches for the Mac? > I can test the poppler patches once I get some time. Great. > Meanwhile, can you please update the TeXworks.pro to match the updated build instructions for Mac? Thanks. I'm a bit reluctant to update TeXworks.pro, since that describes Jonathan's "official" build system. Especially as long as there is no one definite way of building Tw for the Mac (work has been reported on a Fink package, a homebrew package, as well as some custom/manual way). For now, the instructions on the mailing list are specific to some specific environments (e.g., 64 bit Intel processors on Mac 10.6), and while they are useful for individual testing, they are not good defaults for the official file. That said, the preferred way for accessing Tw is through a subversion checkout. With that, modifications to TeXworks.pro would have to be done only once (per computer). I'd very much would like to have a guide for this on the wiki, but no one has replied to my post of an initial draft some time ago. HTH Stefan From st.loeffler at gmail.com Tue Apr 12 10:33:03 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 12 Apr 2011 10:33:03 +0200 Subject: [texworks] New features and fixes to test In-Reply-To: <4D9A1442.9060707@gmail.com> References: <4D9A1442.9060707@gmail.com> Message-ID: <4DA40E3F.5060305@gmail.com> Hi, and another new (minor, long-requested) feature: an additional option to close the output panel after successful typesetting (regardless of whether is was open before or not). This was introduced in r793 and fixes issue 415 (http://code.google.com/p/texworks/issues/detail?id=415). Testing is (as always) welcome. Regards, Stefan From vext01 at gmail.com Wed Apr 13 13:05:32 2011 From: vext01 at gmail.com (Edd Barrett) Date: Wed, 13 Apr 2011 12:05:32 +0100 Subject: [texworks] TeXworks-0.4 on OpenBSD Message-ID: <20110413110532.GB28376@edd-i386.kent.ac.uk> Hi, I have almost finished porting 0.4 to OpenBSD, there was minor patching required. The patches are available here (bear in mind they are designed for use in the ports tree): https://github.com/vext01/ports-wip/tree/master/editors/texworks/patches I have a question regarding scripts. The default set of scripts, should they be picked up automatically from the qt resources, or do you copy them into a systemwide scripts dir? So far I have only had luck by copying the scripts into ~/.TeXworks/scripts/ Once I have done this, python, lua and QTscript scripts run just fine. Cheers -- Best Regards Edd Barrett http://www.theunixzoo.co.uk From vext01 at gmail.com Wed Apr 13 15:55:19 2011 From: vext01 at gmail.com (Edd Barrett) Date: Wed, 13 Apr 2011 14:55:19 +0100 Subject: [texworks] TeXworks-0.4 on OpenBSD In-Reply-To: <20110413110532.GB28376@edd-i386.kent.ac.uk> References: <20110413110532.GB28376@edd-i386.kent.ac.uk> Message-ID: <20110413135519.GC28376@edd-i386.kent.ac.uk> On Wed, Apr 13, 2011 at 12:05:32PM +0100, Edd Barrett wrote: > Hi, > > I have almost finished porting 0.4 to OpenBSD, there was minor patching > required. Doh, i spoke too soon. TeXworks locks up every 10 minutes of so and eventually crashes. Here is a backtrace, any ideas? I will leave this terminal open so that I can probe deeper if anyone know how to debug this, I don't even know which frame to begin with... (gdb) run Starting program: /usr/local/bin/texworks [New process 28077] pdfTeX 3.1415926-1.40.11-2.2 (TeX Live 2010-OpenBSD_Ports) kpathsea version 6.0.0 Copyright 2010 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). There is NO warranty. Redistribution of this software is covered by the terms of both the pdfTeX copyright and the Lesser GNU General Public License. For more information about these matters, see the file named COPYING and the pdfTeX source. Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX). Compiled with libpng 1.2.44; using libpng 1.2.44 Compiled with zlib 1.2.3; using zlib 1.2.3 Compiled with poppler version 0.14.5 Program received signal SIGSEGV, Segmentation fault. [Switching to process 28077, thread 0x20ca6d800] 0x00000002056e9bc5 in QPathSegments::addPath () from /usr/local/lib/libQtGui.so.10.0 (gdb) bt #0 0x00000002056e9bc5 in QPathSegments::addPath () from /usr/local/lib/libQtGui.so.10.0 #1 0x00000002056ed2c3 in QWingedEdge::QWingedEdge () from /usr/local/lib/libQtGui.so.10.0 #2 0x00000002056ed58f in QPathClipper::clip () from /usr/local/lib/libQtGui.so.10.0 #3 0x00000002056e0e8a in QPainterPath::simplified () from /usr/local/lib/libQtGui.so.10.0 #4 0x00000002056ed7dc in QPathClipper::clip () from /usr/local/lib/libQtGui.so.10.0 #5 0x00000002056e0f9b in QPainterPath::subtracted () from /usr/local/lib/libQtGui.so.10.0 #6 0x00000002056e1079 in QPainterPath::operator- () from /usr/local/lib/libQtGui.so.10.0 #7 0x00000002056e109f in QPainterPath::operator-= () from /usr/local/lib/libQtGui.so.10.0 #8 0x00000002057fa4ca in QTextLayout::draw () from /usr/local/lib/libQtGui.so.10.0 #9 0x000000020582fd81 in QTextDocumentLayoutPrivate::drawBlock () from /usr/local/lib/libQtGui.so.10.0 #10 0x0000000205833a50 in QTextDocumentLayoutPrivate::drawFlow () from /usr/local/lib/libQtGui.so.10.0 #11 0x0000000205832736 in QTextDocumentLayoutPrivate::drawFrame () from /usr/local/lib/libQtGui.so.10.0 #12 0x000000020583c9ee in QTextDocumentLayout::draw () from /usr/local/lib/libQtGui.so.10.0 #13 0x00000002057d8378 in QTextControl::drawContents () from /usr/local/lib/libQtGui.so.10.0 #14 0x0000000205a36e3c in QTextEditPrivate::paint () from /usr/local/lib/libQtGui.so.10.0 #15 0x0000000205a36f04 in QTextEdit::paintEvent () from /usr/local/lib/libQtGui.so.10.0 #16 0x00000002055caf90 in QWidget::event () from /usr/local/lib/libQtGui.so.10.0 #17 0x00000002059bc37b in QFrame::event () from /usr/local/lib/libQtGui.so.10.0 #18 0x0000000205a4d8e7 in QAbstractScrollArea::viewportEvent () from /usr/local/lib/libQtGui.so.10.0 #19 0x0000000205a4fae8 in QAbstractScrollAreaFilter::eventFilter () from /usr/local/lib/libQtGui.so.10.0 #20 0x0000000207b28b1f in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/local/lib/libQtCore.so.9.0 #21 0x0000000205569710 in QApplicationPrivate::notify_helper () from /usr/local/lib/libQtGui.so.10.0 #22 0x0000000205570df5 in QApplication::notify () from /usr/local/lib/libQtGui.so.10.0 #23 0x0000000207b28764 in QCoreApplication::notifyInternal () from /usr/local/lib/libQtCore.so.9.0 #24 0x00000002055c4cc2 in QWidgetPrivate::drawWidget () from /usr/local/lib/libQtGui.so.10.0 #25 0x00000002057a4201 in QWidgetBackingStore::sync () from /usr/local/lib/libQtGui.so.10.0 #26 0x00000002055bc556 in QWidgetPrivate::syncBackingStore () from /usr/local/lib/libQtGui.so.10.0 #27 0x00000002055cb648 in QWidget::event () from /usr/local/lib/libQtGui.so.10.0 #28 0x00000002059d9a01 in QMainWindow::event () from /usr/local/lib/libQtGui.so.10.0 #29 0x00000000004a3c34 in TeXDocument::event (this=0x20b50e800, event=0x20cf8fde0) at src/TeXDocument.cpp:717 #30 0x000000020556973f in QApplicationPrivate::notify_helper () from /usr/local/lib/libQtGui.so.10.0 #31 0x0000000205570df5 in QApplication::notify () from /usr/local/lib/libQtGui.so.10.0 #32 0x0000000207b28764 in QCoreApplication::notifyInternal () from /usr/local/lib/libQtCore.so.9.0 #33 0x0000000207b298ce in QCoreApplicationPrivate::sendPostedEvents () from /usr/local/lib/libQtCore.so.9.0 #34 0x0000000207b587b3 in QEventDispatcherGlib::registeredTimers () from /usr/local/lib/libQtCore.so.9.0 #35 0x00000002063264d3 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.2800.0 #36 0x000000020632a482 in g_main_context_prepare () from /usr/local/lib/libglib-2.0.so.2800.0 #37 0x000000020632aa9b in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.2800.0 #38 0x0000000207b58adc in QEventDispatcherGlib::processEvents () from /usr/local/lib/libQtCore.so.9.0 #39 0x000000020561f08f in QGuiEventDispatcherGlib::processEvents () from /usr/local/lib/libQtGui.so.10.0 #40 0x0000000207b27add in QEventLoop::processEvents () from /usr/local/lib/libQtCore.so.9.0 #41 0x0000000207b27d36 in QEventLoop::exec () from /usr/local/lib/libQtCore.so.9.0 #42 0x0000000207b29bce in QCoreApplication::exec () from /usr/local/lib/libQtCore.so.9.0 #43 0x0000000000467768 in main (argc=1, argv=Variable "argv" is not available. ) at src/main.cpp:163 -- Best Regards Edd Barrett http://www.theunixzoo.co.uk From st.loeffler at gmail.com Wed Apr 13 16:03:57 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Wed, 13 Apr 2011 16:03:57 +0200 Subject: [texworks] TeXworks-0.4 on OpenBSD In-Reply-To: <20110413110532.GB28376@edd-i386.kent.ac.uk> References: <20110413110532.GB28376@edd-i386.kent.ac.uk> Message-ID: <4DA5AD4D.50605@gmail.com> Hi, On 2011-04-13 13:05, Edd Barrett wrote: > I have almost finished porting 0.4 to OpenBSD, there was minor patching > required. The patches are available here (bear in mind they are designed > for use in the ports tree): > https://github.com/vext01/ports-wip/tree/master/editors/texworks/patches The patches are looking fine, nothing dramatic. > I have a question regarding scripts. The default set of scripts, should they be > picked up automatically from the qt resources, or do you copy them into a > systemwide scripts dir? > > So far I have only had luck by copying the scripts into ~/.TeXworks/scripts/ > > Once I have done this, python, lua and QTscript scripts run just fine. The scripts in res/resfiles/scripts should be compiled in by means of the Qt resource framework. They should be copied to the resource directory (~/.TeXworks/scripts) when you first run the application (provided that directory doesn't exist and contain files from an older version of Tw). There shouldn't be any need to copy any resource files manually. HTH Stefan From st.loeffler at gmail.com Wed Apr 13 16:13:44 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Wed, 13 Apr 2011 16:13:44 +0200 Subject: [texworks] TeXworks-0.4 on OpenBSD In-Reply-To: <20110413135519.GC28376@edd-i386.kent.ac.uk> References: <20110413110532.GB28376@edd-i386.kent.ac.uk> <20110413135519.GC28376@edd-i386.kent.ac.uk> Message-ID: <4DA5AF98.6070001@gmail.com> Hi, On 2011-04-13 15:55, Edd Barrett wrote: > On Wed, Apr 13, 2011 at 12:05:32PM +0100, Edd Barrett wrote: >> I have almost finished porting 0.4 to OpenBSD, there was minor patching >> required. > Doh, i spoke too soon. TeXworks locks up every 10 minutes of so and > eventually crashes. Here is a backtrace, any ideas? I will leave this > terminal open so that I can probe deeper if anyone know how to debug > this, I don't even know which frame to begin with... hm..., an error in QWingedEdge. Do you by any chance use highlighing of the current line, and a Qt < 4.2, and the memory usage of the Tw went sky-high? In that case, http://bugreports.qt.nokia.com/browse/QTBUG-15823 might affect you. A patch for Qt is provided in the lib-patches subdirectory (see the README there), or alternatively build the latest version of Qt. This is just a guess, though. HTH Stefan From vext01 at gmail.com Wed Apr 13 21:36:03 2011 From: vext01 at gmail.com (Edd Barrett) Date: Wed, 13 Apr 2011 20:36:03 +0100 Subject: [texworks] TeXworks-0.4 on OpenBSD In-Reply-To: <4DA5AD4D.50605@gmail.com> References: <20110413110532.GB28376@edd-i386.kent.ac.uk> <4DA5AD4D.50605@gmail.com> Message-ID: <20110413193603.GD28376@edd-i386.kent.ac.uk> On Wed, Apr 13, 2011 at 04:03:57PM +0200, Stefan L?ffler wrote: > The scripts in res/resfiles/scripts should be compiled in by means of > the Qt resource framework. They should be copied to the resource > directory (~/.TeXworks/scripts) when you first run the application > (provided that directory doesn't exist and contain files from an older > version of Tw). There shouldn't be any need to copy any resource files > manually. OK, I think I just removed the scripts from my home and not the dir. -- Best Regards Edd Barrett http://www.theunixzoo.co.uk From vext01 at gmail.com Wed Apr 13 21:38:19 2011 From: vext01 at gmail.com (Edd Barrett) Date: Wed, 13 Apr 2011 20:38:19 +0100 Subject: [texworks] TeXworks-0.4 on OpenBSD In-Reply-To: <4DA5AF98.6070001@gmail.com> References: <20110413110532.GB28376@edd-i386.kent.ac.uk> <20110413135519.GC28376@edd-i386.kent.ac.uk> <4DA5AF98.6070001@gmail.com> Message-ID: <20110413193819.GE28376@edd-i386.kent.ac.uk> On Wed, Apr 13, 2011 at 04:13:44PM +0200, Stefan L?ffler wrote: > Hi, > > On 2011-04-13 15:55, Edd Barrett wrote: > > On Wed, Apr 13, 2011 at 12:05:32PM +0100, Edd Barrett wrote: > >> I have almost finished porting 0.4 to OpenBSD, there was minor patching > >> required. > > Doh, i spoke too soon. TeXworks locks up every 10 minutes of so and > > eventually crashes. Here is a backtrace, any ideas? I will leave this > > terminal open so that I can probe deeper if anyone know how to debug > > this, I don't even know which frame to begin with... > > hm..., an error in QWingedEdge. Do you by any chance use highlighing of > the current line, and a Qt < 4.2, and the memory usage of the Tw went > sky-high? I am highlighting the current line, however with qt4-4.7.0. -- Best Regards Edd Barrett http://www.theunixzoo.co.uk From st.loeffler at gmail.com Wed Apr 13 21:51:19 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Wed, 13 Apr 2011 21:51:19 +0200 Subject: [texworks] TeXworks-0.4 on OpenBSD In-Reply-To: <20110413193819.GE28376@edd-i386.kent.ac.uk> References: <20110413110532.GB28376@edd-i386.kent.ac.uk> <20110413135519.GC28376@edd-i386.kent.ac.uk> <4DA5AF98.6070001@gmail.com> <20110413193819.GE28376@edd-i386.kent.ac.uk> Message-ID: <4DA5FEB7.8030106@gmail.com> On 2011-04-13 21:38, Edd Barrett wrote: > On Wed, Apr 13, 2011 at 04:13:44PM +0200, Stefan L?ffler wrote: >> Hi, >> >> On 2011-04-13 15:55, Edd Barrett wrote: >>> On Wed, Apr 13, 2011 at 12:05:32PM +0100, Edd Barrett wrote: >>>> I have almost finished porting 0.4 to OpenBSD, there was minor patching >>>> required. >>> Doh, i spoke too soon. TeXworks locks up every 10 minutes of so and >>> eventually crashes. Here is a backtrace, any ideas? I will leave this >>> terminal open so that I can probe deeper if anyone know how to debug >>> this, I don't even know which frame to begin with... >> hm..., an error in QWingedEdge. Do you by any chance use highlighing of >> the current line, and a Qt < 4.2, and the memory usage of the Tw went >> sky-high? > I am highlighting the current line, however with qt4-4.7.0. Sorry, my bad. The version should have read Qt < 4.7.2. So this clearly applies to your system (see the Qt bug link I posted, or the (now closed) Tw issue at http://code.google.com/p/texworks/issues/detail?id=438). HTH Stefan From vext01 at gmail.com Wed Apr 13 22:30:33 2011 From: vext01 at gmail.com (Edd Barrett) Date: Wed, 13 Apr 2011 21:30:33 +0100 Subject: [texworks] TeXworks-0.4 on OpenBSD In-Reply-To: <4DA5FEB7.8030106@gmail.com> References: <20110413110532.GB28376@edd-i386.kent.ac.uk> <20110413135519.GC28376@edd-i386.kent.ac.uk> <4DA5AF98.6070001@gmail.com> <20110413193819.GE28376@edd-i386.kent.ac.uk> <4DA5FEB7.8030106@gmail.com> Message-ID: <20110413203033.GF28376@edd-i386.kent.ac.uk> On Wed, Apr 13, 2011 at 09:51:19PM +0200, Stefan L?ffler wrote: > >> hm..., an error in QWingedEdge. Do you by any chance use highlighing of > >> the current line, and a Qt < 4.2, and the memory usage of the Tw went > >> sky-high? > > I am highlighting the current line, however with qt4-4.7.0. > > Sorry, my bad. The version should have read Qt < 4.7.2. So this clearly > applies to your system (see the Qt bug link I posted, or the (now > closed) Tw issue at http://code.google.com/p/texworks/issues/detail?id=438). Another developer comitted an update to qt-4.7.2 only yesterday, so I will try with this instead. Thanks for your help. -- Best Regards Edd Barrett http://www.theunixzoo.co.uk From suresh.amritapuri at gmail.com Fri Apr 15 00:15:59 2011 From: suresh.amritapuri at gmail.com (Suresh Kumar) Date: Thu, 14 Apr 2011 15:15:59 -0700 Subject: [texworks] basic editing commands Message-ID: Hi How can i get a list of basic text editing commands of texworks? thanks suresh -- R Suresh Kumar, http://www.m atrukripa.com Sarve bhavantu sukinaha (May everyone be happy) Sarve santu niramiyaha (May everyone be without affliction) Sarve bhadrani pashyantu (May everyone see only goodness) Ma kashchit dukha bhak bhavet (Let none be the victim of suffering) -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomr7 at verizon.net Fri Apr 15 11:10:12 2011 From: tomr7 at verizon.net (Tom Reinhardt) Date: Fri, 15 Apr 2011 05:10:12 -0400 Subject: [texworks] Latest LaTeX downloads break XY Pic on iMac Message-ID: Running on an iMac, software version 10.6.7, running the latest relevant updates from the TeX libraries, etc., I see that LaTeX no longer parses XY Pic diagrams that require under/over arrows correctly: For example -------------- next part -------------- A non-text attachment was scrubbed... Name: latex-image-1.pdf Type: application/pdf Size: 34193 bytes Desc: not available URL: -------------- next part -------------- should be produced by \xymatrix{A\ar@<0.5ex>[r]^{g}\ar@<-0.5ex>[r]_{h} & B\ar[r]^{f} &C}. This works in LaTeXIT, as the diagram above shows, but does not work in TexWorks or in TeXShop? Any suggestions? TomR From herbs at wideopenwest.com Fri Apr 15 23:52:34 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Fri, 15 Apr 2011 16:52:34 -0500 Subject: [texworks] Latest LaTeX downloads break XY Pic on iMac In-Reply-To: References: Message-ID: <44606200-6976-4C17-87DF-A2305FB6186D@wideopenwest.com> On Apr 15, 2011, at 4:10 AM, Tom Reinhardt wrote: > Running on an iMac, software version 10.6.7, running the latest relevant updates from the TeX libraries, etc., I see that LaTeX no longer parses XY Pic diagrams that require under/over > arrows correctly: > > For example > should be produced by > \xymatrix{A\ar@<0.5ex>[r]^{g}\ar@<-0.5ex>[r]_{h} & B\ar[r]^{f} &C}. > > This works in LaTeXIT, as the diagram above shows, but does not work in TexWorks or in TeXShop? > > Any suggestions? > > TomR Howdy, If it works in LaTeXiT and TeXshop, TeXworks and LaTeXit all are using the /usr/texbin binaries (i.e., the same TeX Distribution) it MUST work with the correct preamable in that latter two since all of these are just front ends to that TeX distribution. Could you give us a minimal but compilable sample tex file so we can test it on our systems? Good Luck, Herb Schulz (herbs at wideopenwest dot com) From st.loeffler at gmail.com Sat Apr 16 12:56:08 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sat, 16 Apr 2011 12:56:08 +0200 Subject: [texworks] Latest LaTeX downloads break XY Pic on iMac In-Reply-To: <44606200-6976-4C17-87DF-A2305FB6186D@wideopenwest.com> References: <44606200-6976-4C17-87DF-A2305FB6186D@wideopenwest.com> Message-ID: <4DA975C8.8090700@gmail.com> Hi, On 2011-04-15 23:52, Herbert Schulz wrote: > On Apr 15, 2011, at 4:10 AM, Tom Reinhardt wrote: > >> Running on an iMac, software version 10.6.7, running the latest relevant updates from the TeX libraries, etc., I see that LaTeX no longer parses XY Pic diagrams that require under/over >> arrows correctly: >> >> For example >> should be produced by >> \xymatrix{A\ar@<0.5ex>[r]^{g}\ar@<-0.5ex>[r]_{h} & B\ar[r]^{f} &C}. >> >> This works in LaTeXIT, as the diagram above shows, but does not work in TexWorks or in TeXShop? It works for me. Now, since this is not very helpful all by itself: I'm using Linux (Ubuntu), with TL'10. What TeX distro do you use? And what is the output you get? But as Herbert already pointed out, and as you wrote yourself ("I see that _LaTeX_ no longer parses XY Pic diagrams"), if anything this seems like a LaTeX issue, not a TeXworks or TeXShop issue, so it might be better to follow up on this with the mailing list of your distro. > Could you give us a minimal but compilable sample tex file so we can test it on our systems? FWIW, I used the following (it doesn't use the fonts, though): \documentclass{article} \usepackage{xypic} \begin{document} \xymatrix{A\ar@<0.5ex>[r]^{g}\ar@<-0.5ex>[r]_{h} & B\ar[r]^{f} &C} \end{document} HTH Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Sat Apr 16 12:58:25 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sat, 16 Apr 2011 12:58:25 +0200 Subject: [texworks] basic editing commands In-Reply-To: References: Message-ID: <4DA97651.8050109@gmail.com> Hi, On 2011-04-15 00:15, Suresh Kumar wrote: > How can i get a list of basic text editing commands of texworks? I'm not sure what you mean by "basic text editing commands". All the usual cut/copy/paste are available. (Un-)comment and (un-)indent are available via the menu (and shortcut keys). If it's this kind of information you're looking for, please take a look at the manual. HTH Stefan From herbs at wideopenwest.com Sat Apr 16 14:17:25 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Sat, 16 Apr 2011 07:17:25 -0500 Subject: [texworks] Latest LaTeX downloads break XY Pic on iMac In-Reply-To: <4DA975C8.8090700@gmail.com> References: <44606200-6976-4C17-87DF-A2305FB6186D@wideopenwest.com> <4DA975C8.8090700@gmail.com> Message-ID: <44CC2F5F-204C-4532-AF0A-A0BA6E2B60F3@wideopenwest.com> On Apr 16, 2011, at 5:56 AM, Stefan L?ffler wrote: > Hi, > > On 2011-04-15 23:52, Herbert Schulz wrote: >> On Apr 15, 2011, at 4:10 AM, Tom Reinhardt wrote: >> >>> Running on an iMac, software version 10.6.7, running the latest relevant updates from the TeX libraries, etc., I see that LaTeX no longer parses XY Pic diagrams that require under/over >>> arrows correctly: >>> >>> For example >>> should be produced by >>> \xymatrix{A\ar@<0.5ex>[r]^{g}\ar@<-0.5ex>[r]_{h} & B\ar[r]^{f} &C}. >>> >>> This works in LaTeXIT, as the diagram above shows, but does not work in TexWorks or in TeXShop? > > It works for me. > Now, since this is not very helpful all by itself: I'm using Linux > (Ubuntu), with TL'10. What TeX distro do you use? And what is the output > you get? > > But as Herbert already pointed out, and as you wrote yourself ("I see > that _LaTeX_ no longer parses XY Pic diagrams"), if anything this seems > like a LaTeX issue, not a TeXworks or TeXShop issue, so it might be > better to follow up on this with the mailing list of your distro. > >> Could you give us a minimal but compilable sample tex file so we can test it on our systems? > > FWIW, I used the following (it doesn't use the fonts, though): > > \documentclass{article} > > \usepackage{xypic} > > \begin{document} > > \xymatrix{A\ar@<0.5ex>[r]^{g}\ar@<-0.5ex>[r]_{h} & B\ar[r]^{f} &C} > > \end{document} > > > HTH > Stefan Howdy, Stefan's sample works fine for me. Both using latex->dvips->ps2pdf and pdflatex with a fully updated TeX Live 2010. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From suresh.amritapuri at gmail.com Sat Apr 16 22:50:28 2011 From: suresh.amritapuri at gmail.com (Suresh Kumar) Date: Sat, 16 Apr 2011 13:50:28 -0700 Subject: [texworks] basic editing commands In-Reply-To: <4DA97651.8050109@gmail.com> References: <4DA97651.8050109@gmail.com> Message-ID: I was trying to figure out how to delete a line, both after the cursor and the whole line and I could not find them..thats why i posted this.... On Sat, Apr 16, 2011 at 3:58 AM, Stefan L?ffler wrote: > Hi, > > On 2011-04-15 00:15, Suresh Kumar wrote: > > How can i get a list of basic text editing commands of texworks? > > I'm not sure what you mean by "basic text editing commands". All the > usual cut/copy/paste are available. (Un-)comment and (un-)indent are > available via the menu (and shortcut keys). If it's this kind of > information you're looking for, please take a look at the manual. > > HTH > Stefan > -- R Suresh Kumar, http://www.m atrukripa.com Sarve bhavantu sukinaha (May everyone be happy) Sarve santu niramiyaha (May everyone be without affliction) Sarve bhadrani pashyantu (May everyone see only goodness) Ma kashchit dukha bhak bhavet (Let none be the victim of suffering) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ranjbrans at yahoo.com Sat Apr 16 17:25:12 2011 From: ranjbrans at yahoo.com (Mehdi Ranjbaran) Date: Sat, 16 Apr 2011 08:25:12 -0700 (PDT) Subject: [texworks] technical problem involving \include, \includegraphics \graphicspath and grffile package Message-ID: <495679.18019.qm@web111510.mail.gq1.yahoo.com> Hello, I have a couple of difficulties with my Latex document which I hope you can resolve. I have a main file in which a chap2.tex is included: \include{chap2} In chap2.tex I include a graphic file fig1.pdf using \includegraphics within the figure environment. The graphic file is in a directory other than the current directory in which main.tex is. The path to the directory contains, however, space characters and that's the source of my problems. I use grffile package together with \graphicspath: \usepackage[space]{grffile} \graphicspath{../../My Graphic Files/} but get the error message:"! Package pdftex.def Error: File `fig1.pdf' not found. See the pdftex.def package documentation for explanation. Type H for immediate help. ... l.20 ...udegraphics{fig1.pdf} ?" However, when I don't use \graphicspath and include the full path of the graphic file in \includegraphics I have no difficulty and the final .pdf file is produced: \includegraphics{../../My Graphic Files/fig1.pdf} Do you know how I can get rid of this pesky error? I don't want to write the full path every time I use \includegraphics. Thank you. ----- configuration info ----- TeXworks version : 0.4.0r759 (MiKTeX 2.9) Install location : C:/Program Files (x86)/MiKTeX 2.9/miktex/bin/texworks.exe Library path???? : C:/Users/mehdi/AppData/Local/MiKTeX/2.9/TeXworks/0.4\ pdfTeX location? : C:/Program Files (x86)/MiKTeX 2.9/miktex/bin/pdftex.exe Operating system : Windows Microsoft Windows Vista Home Basic Edition, 64-bit Service Pack 2 (build 6002) Qt4 version????? : 4.7.2 (build) / 4.7.2 (runtime) ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthias.pospiech at gmx.de Sun Apr 17 00:40:59 2011 From: matthias.pospiech at gmx.de (Matthias Pospiech) Date: Sun, 17 Apr 2011 00:40:59 +0200 Subject: [texworks] basic editing commands In-Reply-To: References: <4DA97651.8050109@gmail.com> Message-ID: <4DAA1AFB.6010708@gmx.de> An HTML attachment was scrubbed... URL: From sigmundv at gmail.com Sun Apr 17 01:42:07 2011 From: sigmundv at gmail.com (sigmundv at gmail.com) Date: Sun, 17 Apr 2011 00:42:07 +0100 Subject: [texworks] basic editing commands In-Reply-To: <4DAA1AFB.6010708@gmx.de> References: <4DA97651.8050109@gmail.com> <4DAA1AFB.6010708@gmx.de> Message-ID: I think the OP was looking for some vim-style command. If this is the case I'd say that he should use vim with a LaTeX plugin instead... Sigmund On Sat, Apr 16, 2011 at 23:40, Matthias Pospiech wrote: > Am 16.04.2011 22:50, schrieb Suresh Kumar: > > I was trying to figure out how to delete a line, both after the cursor and > the whole line and I could not find them..thats why i posted this.... > > > It should work as in every 'standard' editor: > > Mark the whole line: [Pos1], [Shift]+[End] > Mark several lines: [Pos1], [Shift]+[End], [Shift] + [Up]/[Down] > Delete it : [Del] > > Matthias > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Sun Apr 17 07:47:11 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sun, 17 Apr 2011 17:47:11 +1200 Subject: [texworks] SCRIPTING: Windows Need - short file names Message-ID: Hi, A Windows Only Solution - short file names. There are times in LaTeX, operating under Windows, when it is useful to be able to just insert the short "no spaces" version of a file name or path. Dialogue box locates a file, and the windows short version of its name, is inserted in TeXworks document (no spaces in path). Requires System access - see: http://twscript.paulanorman.com/docs/html/files/TexWorksApplicationProgramingI.html http://code.google.com/p/texworks/issues/detail?id=261#c58 Note: (contains a CSRIPT call to activeX objects - see contained systemShortName.js) Script Download: http://twscript.paulanorman.com/downloads/?ShortName Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Sun Apr 17 07:55:25 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sun, 17 Apr 2011 17:55:25 +1200 Subject: [texworks] technical problem involving \include, \includegraphics \graphicspath and grffile package In-Reply-To: <495679.18019.qm@web111510.mail.gq1.yahoo.com> References: <495679.18019.qm@web111510.mail.gq1.yahoo.com> Message-ID: Dear Mehdi Ranjbaran, I have struck similar problems occasionally where for one reason or another no combination of LaTeX packages seem to help, or it is just faster to insert a short file + path name. You may be able to put a Windows "short file path" in your \graphicspath{ I have just posted a script that may help you do this in TeXworks. Use the script, selkect an appropriate file, and just take the filename.jpg off for use in \graphicspath{ See Tw issue http://code.google.com/p/texworks/issues/detail?id=261#c58 And http://twscript.paulanorman.com/downloads/?ShortName for the necessary two scripts. I hope that this helps, Paul On 17 April 2011 03:25, Mehdi Ranjbaran wrote: > Hello, > > > I have a couple of difficulties with my Latex document which I hope you can > resolve. I have a main file in which a chap2.tex is included: > > > \include{chap2} > > > In chap2.tex I include a graphic file fig1.pdf using \includegraphics > within the figure environment. The graphic file is in a directory other than > the current directory in which main.tex is. The path to the directory > contains, however, space characters and that's the source of my problems. I > use grffile package together with \graphicspath: > > > \usepackage[space]{grffile} > > \graphicspath{../../My Graphic Files/} > > > but get the error message: > > " > > ! Package pdftex.def Error: File `fig1.pdf' not found. > > See the pdftex.def package documentation for explanation. > > Type H for immediate help. > > ... > > l.20 ...udegraphics{fig1.pdf} > > ? > > " > > > However, when I don't use \graphicspath and include the full path of the > graphic file in \includegraphics I have no difficulty and the final .pdf > file is produced: > > > \includegraphics{../../My Graphic Files/fig1.pdf} > > Do you know how I can get rid of this pesky error? I don't want to write > the full path every time I use \includegraphics. > > Thank you. > > > ----- configuration info ----- > TeXworks version : 0.4.0r759 (MiKTeX 2.9) > Install location : C:/Program Files (x86)/MiKTeX > 2.9/miktex/bin/texworks.exe > Library path : C:/Users/mehdi/AppData/Local/MiKTeX/2.9/TeXworks/0.4\ > pdfTeX location : C:/Program Files (x86)/MiKTeX 2.9/miktex/bin/pdftex.exe > Operating system : Windows Microsoft Windows Vista Home Basic Edition, > 64-bit Service Pack 2 (build 6002) > Qt4 version : 4.7.2 (build) / 4.7.2 (runtime) > ------------------------------ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bvoisin at me.com Sun Apr 17 08:27:28 2011 From: bvoisin at me.com (Bruno Voisin) Date: Sun, 17 Apr 2011 08:27:28 +0200 Subject: [texworks] technical problem involving \include, \includegraphics \graphicspath and grffile package In-Reply-To: <495679.18019.qm@web111510.mail.gq1.yahoo.com> References: <495679.18019.qm@web111510.mail.gq1.yahoo.com> Message-ID: <600C287A-8ADE-4E37-A1A9-44D0E07112F2@me.com> Le 16 avr. 2011 ? 17:25, Mehdi Ranjbaran a ?crit : > The path to the directory contains, however, space characters and that's the source of my problems. I use grffile package together with \graphicspath: > > \usepackage[space]{grffile} > > \graphicspath{../../My Graphic Files/} > > but get the error message: > > " > ! Package pdftex.def Error: File `fig1.pdf' not found. > > [...] > > However, when I don't use \graphicspath and include the full path of the graphic file in \includegraphics I have no difficulty and the final .pdf file is produced: > > \includegraphics{../../My Graphic Files/fig1.pdf} > > Do you know how I can get rid of this pesky error? I don't want to write the full path every time I use \includegraphics. Did you try putting the path in \graphicspath between double braces, like \graphicspath{{../../My Graphic Files/}} According to its doc, \graphicspath is supposed to contain a list of directories, each within its own set of curly braces. Says grfguide.pdf: > The format is the same as for the LATEX2? primitive \input at path. A list of directories, each in a {} group (even if there is only one in the list). For example: > \graphicspath{{eps/}{tiff/}} Other than that, my suggestion would have been to include the path between double quotes "[...]". On the Mac this has been a way to include arbitrary file names for quite some time (XeTeX, OzTeX, ...), and I thought this was more-or-less a standard on any platform. But since you're using the grffile package, its doc seems to say it's not compatible with double quotes. Bruno Voisin From suresh.amritapuri at gmail.com Sun Apr 17 08:48:05 2011 From: suresh.amritapuri at gmail.com (Suresh Kumar) Date: Sat, 16 Apr 2011 23:48:05 -0700 Subject: [texworks] basic editing commands In-Reply-To: References: <4DA97651.8050109@gmail.com> <4DAA1AFB.6010708@gmx.de> Message-ID: yea, i was looking for emacs/eclipse like line killing command.... On Sat, Apr 16, 2011 at 4:42 PM, sigmundv at gmail.com wrote: > I think the OP was looking for some vim-style command. If this is the case > I'd say that he should use vim with a LaTeX plugin instead... > > > Sigmund > > > > On Sat, Apr 16, 2011 at 23:40, Matthias Pospiech > wrote: > >> Am 16.04.2011 22:50, schrieb Suresh Kumar: >> >> I was trying to figure out how to delete a line, both after the cursor and >> the whole line and I could not find them..thats why i posted this.... >> >> >> It should work as in every 'standard' editor: >> >> Mark the whole line: [Pos1], [Shift]+[End] >> Mark several lines: [Pos1], [Shift]+[End], [Shift] + [Up]/[Down] >> Delete it : [Del] >> >> Matthias >> >> > -- R Suresh Kumar, http://www.m atrukripa.com Sarve bhavantu sukinaha (May everyone be happy) Sarve santu niramiyaha (May everyone be without affliction) Sarve bhadrani pashyantu (May everyone see only goodness) Ma kashchit dukha bhak bhavet (Let none be the victim of suffering) -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Sun Apr 17 09:22:40 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 17 Apr 2011 09:22:40 +0200 Subject: [texworks] basic editing commands In-Reply-To: References: <4DA97651.8050109@gmail.com> <4DAA1AFB.6010708@gmx.de> Message-ID: <4DAA9540.6070500@gmail.com> Hi, On 2011-04-17 08:48, Suresh Kumar wrote: > yea, i was looking for emacs/eclipse like line killing command.... indeed, such a command is not provided by default. It should be fairly easy to provide with a script, though (in which case you could also assign an arbitrary shortcut to your liking to it). HTH Stefan From paul.a.norman at gmail.com Sun Apr 17 12:55:37 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sun, 17 Apr 2011 22:55:37 +1200 Subject: [texworks] SCRIPTING: Colour Dialogue Message-ID: Hi, I've uploaded a Script that displays some standard colours and offers some colour macro commands for insertion into Tw Document. This is a prototype which will be developed when time permits. Replaces deleted http://code.google.com/p/texworks/issues/detail?id=261#c25 with this current one: http://code.google.com/p/texworks/issues/detail?id=261#c59 xcolor_svgnames_X11names.js Version 0.4 - Sunday 17th, April, 2011 Needs File read and write see: http://twscript.paulanorman.com/docs/html/files/TexWorksApplicationProgramingI.html Script Download: http://twscript.paulanorman.com/downloads/?InsertColour Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Sun Apr 17 14:19:14 2011 From: st.loeffler at gmail.com (=?ISO-8859-15?Q?Stefan_L=F6ffler?=) Date: Sun, 17 Apr 2011 14:19:14 +0200 Subject: [texworks] Call for Help: Testing Message-ID: <4DAADAC2.1000104@gmail.com> Hi, over the past month, TeXworks has seen several bugfixes, enhancements, and also some minor new features, that warrant an 0.4.1 bugfix release. The preliminary schedule sees the end of April or early May as release date. Until then, I ask everyone who is willing to help to test the latest version (r801 at the time of writing) - in particular the parts that have changed (as reported previously here on the mailing list) and report any problems you might have. Thanks in advance, Stefan From lomov.vl at gmail.com Sun Apr 17 17:17:49 2011 From: lomov.vl at gmail.com (Vladimir Lomov) Date: Mon, 18 Apr 2011 00:17:49 +0900 Subject: [texworks] Russian translation update Message-ID: <20110417151749.GA3528@smoon> Hi list and Stefan esp. I updated translation of texworks on Russian (rev. 801). -- Patageometry, n.: The study of those mathematical properties that are invariant under brain transplants. -------------- next part -------------- A non-text attachment was scrubbed... Name: TeXworks_ru.ts.bz2 Type: application/octet-stream Size: 10877 bytes Desc: not available URL: From suresh.amritapuri at gmail.com Sun Apr 17 21:34:31 2011 From: suresh.amritapuri at gmail.com (Suresh Kumar) Date: Sun, 17 Apr 2011 12:34:31 -0700 Subject: [texworks] basic editing commands In-Reply-To: <4DAA9540.6070500@gmail.com> References: <4DA97651.8050109@gmail.com> <4DAA1AFB.6010708@gmx.de> <4DAA9540.6070500@gmail.com> Message-ID: i think it is time to learn scripting! On Sun, Apr 17, 2011 at 12:22 AM, Stefan L?ffler wrote: > Hi, > > On 2011-04-17 08:48, Suresh Kumar wrote: > > yea, i was looking for emacs/eclipse like line killing command.... > > indeed, such a command is not provided by default. It should be fairly > easy to provide with a script, though (in which case you could also > assign an arbitrary shortcut to your liking to it). > > HTH > Stefan > -- R Suresh Kumar, http://www.m atrukripa.com Sarve bhavantu sukinaha (May everyone be happy) Sarve santu niramiyaha (May everyone be without affliction) Sarve bhadrani pashyantu (May everyone see only goodness) Ma kashchit dukha bhak bhavet (Let none be the victim of suffering) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ovadia at pacbell.net Mon Apr 18 03:35:33 2011 From: ovadia at pacbell.net (Ovi Chitayat) Date: Sun, 17 Apr 2011 18:35:33 -0700 Subject: [texworks] question Message-ID: <97FF8E23F6AD4F808ED285DCADD35D7B@home390> Hi, Is there a way to reset an enumeration counter ? I am looking to for a way to do a dual digit or even a triple digit enumeration and have control over restarting any of the digit counters from the initial value. Example of resulting enumeration: 1.1.1 1.1.2 1.1.3 1.2.1 1.2.2 1.3.1 2.1.1 Notice: I need both LSB's to be able to reset to the initial value. Ovi -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Mon Apr 18 12:07:03 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 18 Apr 2011 22:07:03 +1200 Subject: [texworks] question In-Reply-To: <97FF8E23F6AD4F808ED285DCADD35D7B@home390> References: <97FF8E23F6AD4F808ED285DCADD35D7B@home390> Message-ID: Hi Ovi, Form among many very good ones these resources are very helpful: http://groups.google.com/group/latexusersgroup http://www.tug.org/interest.html http://theoval.cmp.uea.ac.uk/~nlct/latex/ Try searching on google with the phrase: LaTeX enumerate Also you can download a Tw scripting extension which can give you a bit of help on this from within your Tw editor window. http://twscript.paulanorman.com/downloads/?Latex2eHelp When you've followed the guidelines and installed it, start it from within the Editor with the Alt F1 + Alt 2 keys. Type: enumerate in the text box. And also try: counter You'll find your script directory when you need it for install, from your Help menu (on recent Tw releases) "Settings and Resources" and then the config link, the Scripts folder is in there. You can get a recent Tw release from here: http://code.google.com/p/texworks/downloads/list I think that version 801 is the most recent at the moment. Paul On 18 April 2011 13:35, Ovi Chitayat wrote: > Hi, > > Is there a way to reset an enumeration counter ? > > I am looking to for a way to do a dual digit or even a triple digit > enumeration > > and have control over restarting any of the digit counters from the initial > value. > > Example of resulting enumeration: > > 1.1.1 > > 1.1.2 > > 1.1.3 > > 1.2.1 > > 1.2.2 > > 1.3.1 > > 2.1.1 > > Notice: I need both LSB?s to be able to reset to the initial value. > > Ovi > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Mon Apr 18 13:35:04 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 18 Apr 2011 23:35:04 +1200 Subject: [texworks] Call for Help: Testing In-Reply-To: <4DAADAC2.1000104@gmail.com> References: <4DAADAC2.1000104@gmail.com> Message-ID: Dear Stefan, I think that your tweaking has got Tw starting more quickly, at least on Windows Xp, and that is great thank you! Help/"Settings and Resources" is working very smoothly, thanks for that. Its a great help for pointing people to. Windows toolbar tips are looking great now, issue 387 ver796 Pdf previeew issue 91 ver767, awesome - just a comment in Windows, one you double click and the other you left click - can both be made to operate on either approach, the same approach, or a single click? And in the Text editor the line number one be activated as well (I just discovered that the other two (CR-LF UTF-8) in the Text editor operate off a left click - very useful). I was looking through http://code.google.com/p/texworks/source/list trying to identify what else there was to check... Re-compression -- I noticed http://code.google.com/p/texworks/source/detail?r=763# Hasnlt helped us much yet, did another check on latest exe ... Ran UPX on the latest TeXworks.exe TeXworks.exe 21,162 Kb UPX -9 down to 8,199 Kb I believe it adds about one second to the start-up time. I think UPX is available for Linux as well(?) Awesome progress on many fronts :) Paul On 18 April 2011 00:19, Stefan L?ffler wrote: > Hi, > > over the past month, TeXworks has seen several bugfixes, enhancements, > and also some minor new features, that warrant an 0.4.1 bugfix release. > The preliminary schedule sees the end of April or early May as release > date. Until then, I ask everyone who is willing to help to test the > latest version (r801 at the time of writing) - in particular the parts > that have changed (as reported previously here on the mailing list) and > report any problems you might have. > > Thanks in advance, > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Mon Apr 18 17:23:14 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Mon, 18 Apr 2011 17:23:14 +0200 Subject: [texworks] Call for Help: Testing In-Reply-To: <4DAADAC2.1000104@gmail.com> References: <4DAADAC2.1000104@gmail.com> Message-ID: <4DAC5762.6050202@gmail.com> Hi, following up on issue 491 (http://code.google.com/p/texworks/issues/detail?id=491) about broken file path detection in the latexError.js script - maybe some people here can help by providing the results of some of the test cases mentioned there. Cheers, Stefan Original post: In order to resolve this satisfactorily across platforms, could someone post the error logs produced by MiKTeX & TeXLive on Windows as well as MacTeX on the Mac for the following situations: * Error in a file with a short name (e.g., 'test.tex') * Error in a file with a long name (too long for a single line) (e.g., 'a-very-very-long-file-name-to-ensure-latex-error-messages-are-broken-across-lines.tex') * Error in a file with spaces (e.g., 'test file.tex') * Error in a file with quotation marks (e.g., 'test "file".tex') * Error in a file with contained braces (e.g., 'test (file).tex') Minimal sample file: \documentclass{article} \begin{document} A\B \end{document} From st.loeffler at gmail.com Mon Apr 18 17:36:30 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Mon, 18 Apr 2011 17:36:30 +0200 Subject: [texworks] Call for Help: Testing In-Reply-To: References: <4DAADAC2.1000104@gmail.com> Message-ID: <4DAC5A7E.3090802@gmail.com> Hi, thanks for the positive feedback. On 2011-04-18 13:35, Paul A Norman wrote: > Pdf previeew issue 91 ver767, awesome - just a comment in Windows, one > you double click and the other you left click - can both be made to > operate on either approach, the same approach, or a single click? And > in the Text editor the line number one be activated as well (I just > discovered that the other two (CR-LF UTF-8) in the Text editor operate > off a left click - very useful). For me (Linux), it's right-clicking for all but the page. The reason for this is that they all open context menus (which are typically associated with a right-click). The page label, OTOH, initiates an action (namely opening the "Goto page" dialog), which would seem rather weird (to me, anyway) to be initiated by a right-click. Besides, I seem to remember that several applications have a double-click activation on that (granted, most applications have an edit box there, but AFAIK this produces significant problems on the Mac due to its size). Regarding the editor, I missed the line label. I'll try to remember it until I find time to fix it ;). > I was looking > through http://code.google.com/p/texworks/source/list trying to > identify what else there was to check... > > Re-compression -- > > I noticed http://code.google.com/p/texworks/source/detail?r=763# > Hasnlt helped us much yet, did another check on latest exe ... Yeah, it was just a first attempt, I didn't have time to look into this issue in detail yet. As far as (stable) releases are concerned, I'd prefer to go with uncompressed files, as they don't change that often (people don't have to download too much), hard disk space is not that limitted anymore these days (we're talking about 21MB) and speed is nice to have. For "daily" testing builds, OTOH, I agree that size matters, and speed does not so much. Still, I'd like to investigate this first. Cheers, Stefan From paul.a.norman at gmail.com Mon Apr 18 23:47:51 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 19 Apr 2011 09:47:51 +1200 Subject: [texworks] Call for Help: Testing In-Reply-To: <4DAC5A7E.3090802@gmail.com> References: <4DAADAC2.1000104@gmail.com> <4DAC5A7E.3090802@gmail.com> Message-ID: On 19 April 2011 03:36, Stefan L?ffler wrote: > Hi, > > thanks for the positive feedback. > > On 2011-04-18 13:35, Paul A Norman wrote: > > Pdf previeew issue 91 ver767, awesome - just a comment in Windows, one > > you double click and the other you left click - can both be made to > > operate on either approach, the same approach, or a single click? And > > in the Text editor the line number one be activated as well (I just > > discovered that the other two (CR-LF UTF-8) in the Text editor operate > > off a left click - very useful). > > For me (Linux), it's right-clicking for all but the page. Correct - right clicking. > The reason for > this is that they all open context menus (which are typically associated > with a right-click). The page label, OTOH, initiates an action (namely > opening the "Goto page" dialog), which would seem rather weird (to me, > anyway) to be initiated by a right-click. Besides, I seem to remember > that several applications have a double-click activation on that > (granted, most applications have an edit box there, but AFAIK this > produces significant problems on the Mac due to its size). > As I recall it the general best practice under Windows and Mac is to try and have similar looking components - especially when in proximity to each other - activated in similar ways to avoid interface confusion or even the possibility that a feature is left unknown to the user. Developers have provided more than one means of activating such things in the past to avoid missing people out. A single left click is the first course of action for many users according to labs in the past. Really relevant with these components being right beside eachother - in the editor set - three in a row that look to the eye like the same component - in the pdf preview two right beside each other. One you right click, the other you double left click - a tad counter-intuitive. Regarding the editor, I missed the line label. I'll try to remember it > until I find time to fix it ;). > A lot of people will tend to just single left click everything if they are not sure / trying things out. Best way to catch them. If it looks like a duck, walks like a duck, quacks like a duck, its probably a duck. On Windows at least, with their Qt shading, this component look more like a button than anything else. And a button you almost without exception left click. > > I was looking > > through http://code.google.com/p/texworks/source/list trying to > > identify what else there was to check... > > > > Re-compression -- > > > > I noticed http://code.google.com/p/texworks/source/detail?r=763# > > Hasnlt helped us much yet, did another check on latest exe ... > > Yeah, it was just a first attempt, I didn't have time to look into this > issue in detail yet. As far as (stable) releases are concerned, I'd > prefer to go with uncompressed files, as they don't change that often > (people don't have to download too much), hard disk space is not that > limitted anymore these days (we're talking about 21MB) and speed is nice > to have. For "daily" testing builds, OTOH, I agree that size matters, > and speed does not so much. Still, I'd like to investigate this first. > > Its worth it, there are still considerable numbers of people in developing countries who rely on speeds little better, or the same as dial up modems. I know one man in the Philipines who has been unable to guarantee a connection for ten minutes without it going down and requires reconnection, and have seen people in Fiji even near main nodes, have to wait over an hour to process a small raft of plain text emails. Paul Cheers, > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Wed Apr 20 07:51:25 2011 From: st.loeffler at gmail.com (=?ISO-8859-15?Q?Stefan_L=F6ffler?=) Date: Wed, 20 Apr 2011 07:51:25 +0200 Subject: [texworks] Russian translation update In-Reply-To: <20110417151749.GA3528@smoon> References: <20110417151749.GA3528@smoon> Message-ID: <4DAE745D.4090500@gmail.com> Hi, On 2011-04-17 17:17, Vladimir Lomov wrote: > I updated translation of texworks on Russian (rev. 801). Thanks a lot. I'll commit it with the other translations. Cheers, Stefan From vext01 at gmail.com Wed Apr 20 11:18:07 2011 From: vext01 at gmail.com (Edd Barrett) Date: Wed, 20 Apr 2011 10:18:07 +0100 Subject: [texworks] TeXworks-0.4 on OpenBSD In-Reply-To: <20110413203033.GF28376@edd-i386.kent.ac.uk> References: <20110413110532.GB28376@edd-i386.kent.ac.uk> <20110413135519.GC28376@edd-i386.kent.ac.uk> <4DA5AF98.6070001@gmail.com> <20110413193819.GE28376@edd-i386.kent.ac.uk> <4DA5FEB7.8030106@gmail.com> <20110413203033.GF28376@edd-i386.kent.ac.uk> Message-ID: <20110420091807.GA20460@edd-i386.kent.ac.uk> On Wed, Apr 13, 2011 at 09:30:33PM +0100, Edd Barrett wrote: > On Wed, Apr 13, 2011 at 09:51:19PM +0200, Stefan L?ffler wrote: > > >> hm..., an error in QWingedEdge. Do you by any chance use highlighing of > > >> the current line, and a Qt < 4.2, and the memory usage of the Tw went > > >> sky-high? > > > I am highlighting the current line, however with qt4-4.7.0. > > > > Sorry, my bad. The version should have read Qt < 4.7.2. So this clearly > > applies to your system (see the Qt bug link I posted, or the (now > > closed) Tw issue at http://code.google.com/p/texworks/issues/detail?id=438). > > Another developer comitted an update to qt-4.7.2 only yesterday, so I > will try with this instead. That fixed this btw. Cheers -- Best Regards Edd Barrett http://www.theunixzoo.co.uk From vext01 at gmail.com Wed Apr 20 11:21:29 2011 From: vext01 at gmail.com (Edd Barrett) Date: Wed, 20 Apr 2011 10:21:29 +0100 Subject: [texworks] texworks with tiling window managers Message-ID: <20110420092129.GB20460@edd-i386.kent.ac.uk> Hi, I notice that texworks is horrible to place in tiling window managers. I think this is because texworks is trying to place windows cleverly itself. Whilst that works well on a floating window manager, it sucks on window managers like awesome or scrotwm. Would anyone be opposed to a setting "don't manage window placement", which does exactly that and disables some of the placement schemes in the 'window' menu. Cheers -- Best Regards Edd Barrett http://www.theunixzoo.co.uk From st.loeffler at gmail.com Wed Apr 20 17:36:49 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Wed, 20 Apr 2011 17:36:49 +0200 Subject: [texworks] Call for Help: Testing In-Reply-To: References: <4DAADAC2.1000104@gmail.com> <4DAC5A7E.3090802@gmail.com> Message-ID: <4DAEFD91.3090201@gmail.com> On 2011-04-18 23:47, Paul A Norman wrote: > If it looks like a duck, walks like a duck, quacks like a duck, its > probably a duck. > On Windows at least, with their Qt shading, this component look more > like a button than anything else. OK, seeing them as buttons that open menus/dialogs is understandable. I'll see what I can do. > > > I was looking > > through http://code.google.com/p/texworks/source/list trying to > > identify what else there was to check... > > > > Re-compression -- > > > > I noticed http://code.google.com/p/texworks/source/detail?r=763# > > Hasnlt helped us much yet, did another check on latest exe ... > > Yeah, it was just a first attempt, I didn't have time to look into > this > issue in detail yet. As far as (stable) releases are concerned, I'd > prefer to go with uncompressed files, as they don't change that often > (people don't have to download too much), hard disk space is not that > limitted anymore these days (we're talking about 21MB) and speed > is nice > to have. > > For "daily" testing builds, OTOH, I agree that size matters, > and speed does not so much. Still, I'd like to investigate this first. > > > Its worth it, there are still considerable numbers of people in > developing countries who rely on speeds little better, or the same as > dial up modems. I know one man in the Philipines who has been unable > to guarantee a connection for ten minutes without it going down and > requires reconnection, and have seen people in Fiji even near main > nodes, have to wait over an hour to process a small raft of plain text > emails. Of course. OTOH, the installer already is quite a bit smaller than the archive, so it would be reasonable to download that if speed/capacity is an issue. Just to check, could you run UPX on the installer and see if it gets (significantly) smaller? (My guess is no, but if I'm wrong I'll look into using UPX on the installer; on the one hand, it's smaller to begin with, and on the other it is run only once, so any startup lag is no problem). In the meantime, I've looked a little bit into the issue with the main TeXworks.exe. It seems that Qt stores quite a lot of information on properties, methods, UI, ... as plain text in the .exe. This, naturally, can be compressed efficiently, yielding the much smaller size you reported. However, the files to download are compressed in a .zip archive. Therefore, I'd suspect that replacing the TeXworks.exe in the .zip file by an UPX'ed one would make only a minor difference. The .exe is smaller, but it won't be compressed anymore by the zip algorithm (right now, the compressed size is about 50% smaller than the uncompressed one). So, again, I would suspect the difference between an UPX'ed version and a non-UPX'ed one in a zip archive to be small (though non-zero, as I expect the UPX algorithm to give somewhat better results than zip). Regards, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Wed Apr 20 23:54:41 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 21 Apr 2011 09:54:41 +1200 Subject: [texworks] Call for Help: Testing In-Reply-To: <4DAEFD91.3090201@gmail.com> References: <4DAADAC2.1000104@gmail.com> <4DAC5A7E.3090802@gmail.com> <4DAEFD91.3090201@gmail.com> Message-ID: Yes, UPX actually has a go at the binary, where as standard zipping has traditionally only been able to handle text type stuff. Will attempt that at some point and get back on it. Keep in mind though its not just download, on a portable type setup, once installed, every saved Mb tends to end up being useful at some point :) Paul On 21 April 2011 03:36, Stefan L?ffler wrote: > On 2011-04-18 23:47, Paul A Norman wrote: > > If it looks like a duck, walks like a duck, quacks like a duck, its > probably a duck. > On Windows at least, with their Qt shading, this component look more like > a button than anything else. > > > OK, seeing them as buttons that open menus/dialogs is understandable. I'll > see what I can do. > > > > > I was looking >> > through http://code.google.com/p/texworks/source/list trying to >> > identify what else there was to check... >> > >> > Re-compression -- >> > >> > I noticed http://code.google.com/p/texworks/source/detail?r=763# >> > Hasnlt helped us much yet, did another check on latest exe ... >> >> Yeah, it was just a first attempt, I didn't have time to look into this >> issue in detail yet. As far as (stable) releases are concerned, I'd >> prefer to go with uncompressed files, as they don't change that often >> (people don't have to download too much), hard disk space is not that >> limitted anymore these days (we're talking about 21MB) and speed is nice >> to have. > > For "daily" testing builds, OTOH, I agree that size matters, >> and speed does not so much. Still, I'd like to investigate this first. >> >> > Its worth it, there are still considerable numbers of people in > developing countries who rely on speeds little better, or the same as dial > up modems. I know one man in the Philipines who has been unable to guarantee > a connection for ten minutes without it going down and requires > reconnection, and have seen people in Fiji even near main nodes, have to > wait over an hour to process a small raft of plain text emails. > > > Of course. OTOH, the installer already is quite a bit smaller than the > archive, so it would be reasonable to download that if speed/capacity is an > issue. Just to check, could you run UPX on the installer and see if it gets > (significantly) smaller? (My guess is no, but if I'm wrong I'll look into > using UPX on the installer; on the one hand, it's smaller to begin with, and > on the other it is run only once, so any startup lag is no problem). > > In the meantime, I've looked a little bit into the issue with the main > TeXworks.exe. It seems that Qt stores quite a lot of information on > properties, methods, UI, ... as plain text in the .exe. This, naturally, can > be compressed efficiently, yielding the much smaller size you reported. > However, the files to download are compressed in a .zip archive. Therefore, > I'd suspect that replacing the TeXworks.exe in the .zip file by an UPX'ed > one would make only a minor difference. The .exe is smaller, but it won't be > compressed anymore by the zip algorithm (right now, the compressed size is > about 50% smaller than the uncompressed one). So, again, I would suspect the > difference between an UPX'ed version and a non-UPX'ed one in a zip archive > to be small (though non-zero, as I expect the UPX algorithm to give somewhat > better results than zip). > > Regards, > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Thu Apr 21 02:40:49 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 21 Apr 2011 12:40:49 +1200 Subject: [texworks] Call for Help: Testing In-Reply-To: References: <4DAADAC2.1000104@gmail.com> <4DAC5A7E.3090802@gmail.com> <4DAEFD91.3090201@gmail.com> Message-ID: ok, Prob not really worth trying to UPX a properly constructed installer as you point out. It appears to possibly only try to UPX the stub depending on how the installer handles things anyway. Did an exhaustive set of tests that I'll keep for other things as well, as a benchmark as there is actually a useful mix of different types of stuff in each Tw update, the worst culprit on Xp standard NTFS on disk, is the popler data - some disk wastage reationg to sector sizes, with so many small files. Most of my tests involved extracting form the latest Tw zip and then re-compressing the deflated files with various techniques, UPXing and not UPXing the dll and exe. The conclusion appears to be that a LZMA 7Zip self extractor can be made (10.7 MB) that is about 6mb smaller than the standard curent Tw developer update zip. Or a straight forward 7Zip .7z archive can be made (10.6 Mb) that is also about six Mb smaller than the current development .zip (16.7 MB). Also if the dll and exe are UPXed then a SelfExtractor (SFX) can be made with 7Zip that is still only 12.4Mb Perhaps helpful for any one on slower connections and or using a thumb-drives from time to time, who is needing to keep up with the fixes. What ever else, it all gives us some idea of available compressions. File attached. Paul On 21 April 2011 09:54, Paul A Norman wrote: > Yes, UPX actually has a go at the binary, where as standard zipping has > traditionally only been able to handle text type stuff. > > Will attempt that at some point and get back on it. > > Keep in mind though its not just download, on a portable type setup, once > installed, every saved Mb tends to end up being useful at some point :) > > Paul > > > > On 21 April 2011 03:36, Stefan L?ffler wrote: > >> On 2011-04-18 23:47, Paul A Norman wrote: >> >> If it looks like a duck, walks like a duck, quacks like a duck, its >> probably a duck. >> On Windows at least, with their Qt shading, this component look more like >> a button than anything else. >> >> >> OK, seeing them as buttons that open menus/dialogs is understandable. I'll >> see what I can do. >> >> >> >> > I was looking >>> > through http://code.google.com/p/texworks/source/list trying to >>> > identify what else there was to check... >>> > >>> > Re-compression -- >>> > >>> > I noticed http://code.google.com/p/texworks/source/detail?r=763# >>> > Hasnlt helped us much yet, did another check on latest exe ... >>> >>> Yeah, it was just a first attempt, I didn't have time to look into this >>> issue in detail yet. As far as (stable) releases are concerned, I'd >>> prefer to go with uncompressed files, as they don't change that often >>> (people don't have to download too much), hard disk space is not that >>> limitted anymore these days (we're talking about 21MB) and speed is nice >>> to have. >> >> For "daily" testing builds, OTOH, I agree that size matters, >>> and speed does not so much. Still, I'd like to investigate this first. >>> >>> >> Its worth it, there are still considerable numbers of people in >> developing countries who rely on speeds little better, or the same as dial >> up modems. I know one man in the Philipines who has been unable to guarantee >> a connection for ten minutes without it going down and requires >> reconnection, and have seen people in Fiji even near main nodes, have to >> wait over an hour to process a small raft of plain text emails. >> >> >> Of course. OTOH, the installer already is quite a bit smaller than the >> archive, so it would be reasonable to download that if speed/capacity is an >> issue. Just to check, could you run UPX on the installer and see if it gets >> (significantly) smaller? (My guess is no, but if I'm wrong I'll look into >> using UPX on the installer; on the one hand, it's smaller to begin with, and >> on the other it is run only once, so any startup lag is no problem). >> >> In the meantime, I've looked a little bit into the issue with the main >> TeXworks.exe. It seems that Qt stores quite a lot of information on >> properties, methods, UI, ... as plain text in the .exe. This, naturally, can >> be compressed efficiently, yielding the much smaller size you reported. >> However, the files to download are compressed in a .zip archive. Therefore, >> I'd suspect that replacing the TeXworks.exe in the .zip file by an UPX'ed >> one would make only a minor difference. The .exe is smaller, but it won't be >> compressed anymore by the zip algorithm (right now, the compressed size is >> about 50% smaller than the uncompressed one). So, again, I would suspect the >> difference between an UPX'ed version and a non-UPX'ed one in a zip archive >> to be small (though non-zero, as I expect the UPX algorithm to give somewhat >> better results than zip). >> >> Regards, >> Stefan >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ?TeXworks-w32-0.5-r804.zip 16.7mb 16.7 mb on disk tW 0.5 VER804 Uncompressed to a folder 29.7 Mb 35.0 Mb on NTSF disk (out of box Xp settings) 7Z estimated the disk space uncompressed to be 37Mb re-compressed the extract of TeXworks-w32-0.5-r804.zip normal 7z compression as: tW 0.5 VER804.7z 11.0 MB and 11.0 MB on disk Then first UPXed the extracted binaries and again re-compressed the extract of TeXworks-w32-0.5-r804.zip as: tW 0.5 VER804(binaries UPXed) MAX 7z compression.7z 12.2 MB 12.2 MB Then with UPX-ed on extracted binaries (exe dll) and again re-compressed the extract of TeXworks-w32-0.5-r804.zip as: tW 0.5 VER804(binaries UPXed) MAX PPMD compression.7z 13.7 MB 13.7 MB re-compressed the extract of TeXworks-w32-0.5-r804.zip Ultra 7z compression as: tW 0.5 VER804(binaries NOT UPXed) MAX (Ultra) 7z compression LZMA.7z 10.6 MB and 10.7 MB Next making a self extracting archive, re-compressed the extract of TeXworks-w32-0.5-r804.zip (people don't have to have 7z installed): tW 0.5 VER804 SFX (binaries NOT UPXed) MAX (Ultra) 7z compression LZMA.exe 10.7 MB 10.7 MB FInally binaries UPXed and made into an Ultra 7z Self Extractor (TeXworks.exe 8.18 MB 8.18 MB - was 20.6 MB python27.dll 99 KB 99 KB - was 2.17 MB) tW 0.5 VER804 SFX (binaries UPXed) MAX (Ultra) 7z compression LZMA.exe 12.4 MB 12.4 MB From byelozyorov at cs.uni-saarland.de Thu Apr 21 11:38:43 2011 From: byelozyorov at cs.uni-saarland.de (Sergiy Byelozyorov) Date: Thu, 21 Apr 2011 11:38:43 +0200 Subject: [texworks] How to make preview and main window minimize together? Message-ID: Dear developers, I like the design of you application, however it would be nice if I could minimize both windows together at the same time with one mouse click. Alternatively you can also make both preview and code editor to be panes with a movable splitter within a single window. This doesn't have to be default, but it's nice to have such an option. Thank you for the great application. Sergiy Byelozyorov Computer Graphics Chair Universitat des Saarlandes Tel.: +49 (681) 302-3837 Web: http://graphics.cs.uni-saarland.de/sbyelozyorov/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Thu Apr 21 12:50:27 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 21 Apr 2011 22:50:27 +1200 Subject: [texworks] How to make preview and main window minimize together? In-Reply-To: References: Message-ID: Thank you Sergiy, Your suggestions have been entered against the following 'issue' (if you would like to track progress): http://code.google.com/p/texworks/issues/detail?id=285#c4 The possibility of splitting the screen has been mentioned before, earlier on that page. Your contribution is appreciated, Paul On 21 April 2011 21:38, Sergiy Byelozyorov wrote: > Dear developers, > > I like the design of you application, however it would be nice if I could > minimize both windows together at the same time with one mouse click. > Alternatively you can also make both preview and code editor to be panes > with a movable splitter within a single window. This doesn't have to be > default, but it's nice to have such an option. Thank you for the great > application. > > Sergiy Byelozyorov > Computer Graphics Chair > Universitat des Saarlandes > Tel.: +49 (681) 302-3837 > Web: http://graphics.cs.uni-saarland.de/sbyelozyorov/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vafa018 at gmail.com Fri Apr 22 05:26:02 2011 From: vafa018 at gmail.com (Vafa Khalighi) Date: Fri, 22 Apr 2011 13:26:02 +1000 Subject: [texworks] Two problems with TeXworks 0.4.0 on Mac OSX 10.6.7 Message-ID: I downloaded the latest version from https://www.dropbox.com/s/vs9qutjgtwised7/TeXworks.zip but I have two problems: 1. In "Preferences=>Scripts" I can not activate "Enable plug-in scripting languages". 2. Although this version allows typing RTL in textworks but when you type ZWNJ between two words, then it makes it LTR, for example if I type ?????? then in the editor I see ?????? but this does not happen on Linux (ubuntu 10.10) with the same version of texworks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Sat Apr 23 04:56:33 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sat, 23 Apr 2011 14:56:33 +1200 Subject: [texworks] Two problems with TeXworks 0.4.0 on Mac OSX 10.6.7 In-Reply-To: References: Message-ID: Dear Vafa Khalighi, Thanks for the heads up on those issues. I am afraid that that is not looking like an "official" project build, you can read the full notes at: http://tug.org/pipermail/texworks/2011q1/003963.html "I called it "quick" because I don't want to mess up with all the different SDKs and universal binaries stuff, but this build should fix most Mac users' needs." The history behind it, is that there have been some problems in getting the MacOs builds to work, and Jiang, has quite well managed to side step the more troublesome problems for now, just to get something out that will give general functionality for "*most* Mac user's needs". So we might expect that there will be some features missing from that "unoffical" build just now. Any more gifted Mac developers, with time, out there ..?.. :) Paul Full Quote from Jiang: "Hi, "I just did a quick Mac OS X 10.6 x86_64 build with: - TeXworks svn trunk (should be close to 0.4.0, right?) - Qt 4.7.2 (with other 4.7.x changes since I'm a Qt developer personally) - poppler 0.16.3 - hunspell-1.2.14 - Other libraries are shipped with Mac OS X "It's available here for people who wants to try:https://www.dropbox.com/s/vs9qutjgtwised7/TeXworks.zip I called it "quick" because I don't want to mess up with all the different SDKs and universal binaries stuff, but this build should fix most Mac users'needs. Cheers, Jiang On 22 April 2011 15:26, Vafa Khalighi wrote: > I downloaded the latest version from > https://www.dropbox.com/s/vs9qutjgtwised7/TeXworks.zip but I have two > problems: > > 1. In "Preferences=>Scripts" I can not activate "Enable plug-in > scripting languages". > 2. Although this version allows typing RTL in textworks but when you > type ZWNJ between two words, then it makes it LTR, for example if I type > ?????? then in the editor I see ?????? but this does not happen on Linux > (ubuntu 10.10) with the same version of texworks. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gzjjgod at gmail.com Mon Apr 25 16:12:44 2011 From: gzjjgod at gmail.com (Jjgod Jiang) Date: Mon, 25 Apr 2011 16:12:44 +0200 Subject: [texworks] Two problems with TeXworks 0.4.0 on Mac OSX 10.6.7 In-Reply-To: References: Message-ID: On Fri, Apr 22, 2011 at 5:26 AM, Vafa Khalighi wrote: > In "Preferences=>Scripts" I can not activate "Enable plug-in scripting > languages". I've no idea about this. > Although this version allows typing RTL in textworks but when you type ZWNJ > between two words, then it makes it LTR, for example if I type ?????? then > in the editor I see ?????? but this does not happen on Linux (ubuntu 10.10) > with the same version of texworks. I vaguely remember that there was a Qt bug about ZWNJ handling. Please submit a bug to: http://bugreports.qt.nokia.com/ if you can reproduce it in a Qt only test case (textedit demo from Qt SDK for instance), thanks. - Jiang From vafa018 at gmail.com Tue Apr 26 11:19:58 2011 From: vafa018 at gmail.com (Vafa Khalighi) Date: Tue, 26 Apr 2011 19:19:58 +1000 Subject: [texworks] Two problems with TeXworks 0.4.0 on Mac OSX 10.6.7 In-Reply-To: References: Message-ID: > I vaguely remember that there was a Qt bug about ZWNJ handling. Please > submit a bug to: http://bugreports.qt.nokia.com/ if you can reproduce it > in > a Qt only test case (textedit demo from Qt SDK for instance), thanks. > > Only if the Ubuntu and Mac versions are build with different versions of Qt! -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Wed Apr 27 19:16:29 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Wed, 27 Apr 2011 19:16:29 +0200 Subject: [texworks] Two problems with TeXworks 0.4.0 on Mac OSX 10.6.7 In-Reply-To: References: Message-ID: <4DB84F6D.8010003@gmail.com> Hi, On 2011-04-22 05:26, Vafa Khalighi wrote: > I downloaded the latest version from > https://www.dropbox.com/s/vs9qutjgtwised7/TeXworks.zip but I have two > problems: > > 1. In "Preferences=>Scripts" I can not activate "Enable plug-in > scripting languages". > By "can not activate", do you mean: 1) you can't click the checkbox (e.g., it is disabled, gray, ...) 2) you can click the checkbox, but no checkmark appears 3) you can check the box, but settings are not retained after closing the preferences dialog / the application 4) everything of the above works as expected, but the setting doesn't seem to have any effect 5) something else. I would expect nr. 4, in which case I would go on speculating that the build you use doesn't have scripting plugins compiled in / doesn't provide them. If that is the case, the setting you mention naturally has no visible effect. Also note that you need to have lua and/or python scripts installed or use "Scripts > Scripting TeXworks > About Scripts..." to see any effect. HTH Stefan PS: "Only if the Ubuntu and Mac versions are build with different versions of Qt!" Oh, but they are. Ubuntu uses the Linux version, and on the Mac the Mac version is used. Most of the code is identical, of course, but some parts depend on platform-specific features/code/libraries, so in effect they are different (even with the same version number). -------------- next part -------------- An HTML attachment was scrubbed... URL: From herbs at wideopenwest.com Wed Apr 27 19:23:47 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Wed, 27 Apr 2011 12:23:47 -0500 Subject: [texworks] Two problems with TeXworks 0.4.0 on Mac OSX 10.6.7 In-Reply-To: <4DB84F6D.8010003@gmail.com> References: <4DB84F6D.8010003@gmail.com> Message-ID: On Apr 27, 2011, at 12:16 PM, Stefan L?ffler wrote: > Hi, > > On 2011-04-22 05:26, Vafa Khalighi wrote: >> I downloaded the latest version from >> https://www.dropbox.com/s/vs9qutjgtwised7/TeXworks.zip but I have two >> problems: >> >> 1. In "Preferences=>Scripts" I can not activate "Enable plug-in >> scripting languages". >> > > By "can not activate", do you mean: > 1) you can't click the checkbox (e.g., it is disabled, gray, ...) > 2) you can click the checkbox, but no checkmark appears > 3) you can check the box, but settings are not retained after closing > the preferences dialog / the application > 4) everything of the above works as expected, but the setting doesn't > seem to have any effect > 5) something else. > > I would expect nr. 4, in which case I would go on speculating that the > build you use doesn't have scripting plugins compiled in / doesn't > provide them. If that is the case, the setting you mention naturally has > no visible effect. Also note that you need to have lua and/or python > scripts installed or use "Scripts > Scripting TeXworks > About > Scripts..." to see any effect. > > HTH > Stefan > > PS: "Only if the Ubuntu and Mac versions are build with different > versions of Qt!" > Oh, but they are. Ubuntu uses the Linux version, and on the Mac the Mac > version is used. Most of the code is identical, of course, but some > parts depend on platform-specific features/code/libraries, so in effect > they are different (even with the same version number). Howdy, Sorry, it's (1) with ``Version 0.5 r.756 (personal)'' that I downloaded a while ago. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From st.loeffler at gmail.com Wed Apr 27 19:32:08 2011 From: st.loeffler at gmail.com (=?ISO-8859-15?Q?Stefan_L=F6ffler?=) Date: Wed, 27 Apr 2011 19:32:08 +0200 Subject: [texworks] Call for Help: Translations Message-ID: <4DB85318.7080201@gmail.com> Hi, as mentioned before, we heading for a bugfix release (0.4.1) of TeXworks, which should appear in early May. To that end, I've asked the translators of previous versions to update their contributions, and thankfully most have indeed done so very fast. There are, however, a few languages for which I haven't got any feedback yet. These are: French, Japanese, Polish, Portuguese (pt_BR), and Simplified Chinese. At least for French, I'm pretty sure (from past private communications) that Alain will not be able to update the translations this time. Therefore, I ask anyone who knows one of these languages and is willing to help to update the translations we have (since this is a bugfix release, changes are not extensive). To get you started, there is a guide at http://code.google.com/p/texworks/wiki/Translating (you can skip the lupdate if you use r801 or later). In addition to the normal translation files, there are a few more strings in supplementary files that I want to ask you to check and (if necessary) translate. These are the strings "Open the following file types with TeXworks by default:" (from win32/texworks-setup-script.iss), "(La)TeX Editor" (from texworks.desktop), and "A simple environment for editing, typesetting, and previewing TeX documents" (adapted from texworks.desktop). These are used in the Windows installer and for program shortcuts on Linux. To ensure the strings are formated correctly, please use the attached template file to send the translations back (instead of copying them into the mail). Note: if the translation is already provided and correct, simply leave the corresponding line in the template file empty. Thanks in advance, Stefan -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: tw-additional-translations-template.txt URL: From st.loeffler at gmail.com Wed Apr 27 20:00:43 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Wed, 27 Apr 2011 20:00:43 +0200 Subject: [texworks] Two problems with TeXworks 0.4.0 on Mac OSX 10.6.7 In-Reply-To: References: <4DB84F6D.8010003@gmail.com> Message-ID: <4DB859CB.9000606@gmail.com> Hi, On 2011-04-27 19:23, Herbert Schulz wrote: > On Apr 27, 2011, at 12:16 PM, Stefan L?ffler wrote >> On 2011-04-22 05:26, Vafa Khalighi wrote: >>> I downloaded the latest version from >>> https://www.dropbox.com/s/vs9qutjgtwised7/TeXworks.zip but I have two >>> problems: >>> >>> 1. In "Preferences=>Scripts" I can not activate "Enable plug-in >>> scripting languages". >>> >> By "can not activate", do you mean: >> 1) you can't click the checkbox (e.g., it is disabled, gray, ...) >> 2) you can click the checkbox, but no checkmark appears >> 3) you can check the box, but settings are not retained after closing >> the preferences dialog / the application >> 4) everything of the above works as expected, but the setting doesn't >> seem to have any effect >> 5) something else. >> >> I would expect nr. 4, in which case I would go on speculating that the >> build you use doesn't have scripting plugins compiled in / doesn't >> provide them. If that is the case, the setting you mention naturally has >> no visible effect. Also note that you need to have lua and/or python >> scripts installed or use "Scripts > Scripting TeXworks > About >> Scripts..." to see any effect. > Howdy, > > Sorry, it's (1) with ``Version 0.5 r.756 (personal)'' that I downloaded a while ago. OK. I just checked the source code again - it's (a little) more sophisticated than I remembered. Indeed, if you have only the built-in QtScript support, but no other plugins (lua, python), then this setting is disabled, as it makes no sense. Besides, it could be potentially dangerous if the user could change the setting without having any means of checking the result (and, as a result, possibly forgetting over time about the changes). Anyway, I'm pretty sure now that the above-mentioned build simply doesn't provide the lua and python plugins, and that that is the reason the option is disabled. HTH Stefan From gzjjgod at gmail.com Wed Apr 27 20:03:11 2011 From: gzjjgod at gmail.com (Jjgod Jiang) Date: Wed, 27 Apr 2011 20:03:11 +0200 Subject: [texworks] Two problems with TeXworks 0.4.0 on Mac OSX 10.6.7 In-Reply-To: <4DB859CB.9000606@gmail.com> References: <4DB84F6D.8010003@gmail.com> <4DB859CB.9000606@gmail.com> Message-ID: On Wed, Apr 27, 2011 at 8:00 PM, Stefan L?ffler wrote: > Hi, > > On 2011-04-27 19:23, Herbert Schulz wrote: >> On Apr 27, 2011, at 12:16 PM, Stefan L?ffler wrote >>> On 2011-04-22 05:26, Vafa Khalighi wrote: >>>> I downloaded the latest version from >>>> https://www.dropbox.com/s/vs9qutjgtwised7/TeXworks.zip but I have two >>>> problems: >>>> >>>> ? 1. In "Preferences=>Scripts" I can not activate "Enable plug-in >>>> ? ? ?scripting languages". >>>> >>> By "can not activate", do you mean: >>> 1) you can't click the checkbox (e.g., it is disabled, gray, ...) >>> 2) you can click the checkbox, but no checkmark appears >>> 3) you can check the box, but settings are not retained after closing >>> the preferences dialog / the application >>> 4) everything of the above works as expected, but the setting doesn't >>> seem to have any effect >>> 5) something else. >>> >>> I would expect nr. 4, in which case I would go on speculating that the >>> build you use doesn't have scripting plugins compiled in / doesn't >>> provide them. If that is the case, the setting you mention naturally has >>> no visible effect. Also note that you need to have lua and/or python >>> scripts installed or use "Scripts > Scripting TeXworks > About >>> Scripts..." to see any effect. >> Howdy, >> >> Sorry, it's (1) with ``Version 0.5 r.756 (personal)'' that I downloaded a while ago. > > OK. I just checked the source code again - it's (a little) more > sophisticated than I remembered. Indeed, if you have only the built-in > QtScript support, but no other plugins (lua, python), then this setting > is disabled, as it makes no sense. Besides, it could be potentially > dangerous if the user could change the setting without having any means > of checking the result (and, as a result, possibly forgetting over time > about the changes). > Anyway, I'm pretty sure now that the above-mentioned build simply > doesn't provide the lua and python plugins, and that that is the reason > the option is disabled. Exactly, I will compile the plugins and provide a new package soon. - Jiang From paul.a.norman at gmail.com Thu Apr 28 10:49:33 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 28 Apr 2011 20:49:33 +1200 Subject: [texworks] OFF-TOPIC: Ever wanted to know more about your pdf file? Message-ID: Just in case you do need/want to ... "As we develop the GNU PDF Library we are generating free documentation about many parts of the PDF specification, the several existing PDF standards, PDF implementation issues, etc. That documentation is available in this webpage and organized into the PDF Knowledge Database. http://www.gnupdf.org/Category:PDF Paul From uncommonnonsense at gmail.com Thu Apr 28 15:52:21 2011 From: uncommonnonsense at gmail.com (Edoardo Vacchi) Date: Thu, 28 Apr 2011 15:52:21 +0200 Subject: [texworks] About the native PDF viewer (feature request and a question) Message-ID: The native viewer feels odd to me sometimes. I wish that holding the down arrow would make the viewer not block to the end of the current page; also I'd expect page down to scroll the view not to change to a new page. Is it possible to add "continuous" scrolling to the viewer? that is, when a page ends, being able to see the top of the one which follows (like in a word processor)? As a workaround, can TeXworks be configured to work with SumatraPDF (SyncTeX enabled build) ? I don't seem to be able to find anything related. Thanks a lot and keep it up, I like TeXworks, it's simple but it does what I need. e.v. From crickzhang1 at gmail.com Sat Apr 30 16:39:57 2011 From: crickzhang1 at gmail.com (Yinhe Zhang) Date: Sat, 30 Apr 2011 22:39:57 +0800 Subject: [texworks] Call for Help: Translations In-Reply-To: <4DB85318.7080201@gmail.com> References: <4DB85318.7080201@gmail.com> Message-ID: Stefan, The translation files for Simplified Chinese are attached. Sorry for late. Also attached translated strings for Simplified Chinese for "* tw-additional-translations-template.txt".* Regards, Yinhe Zhang On Thu, Apr 28, 2011 at 1:32 AM, Stefan L?ffler wrote: > Hi, > > as mentioned before, we heading for a bugfix release (0.4.1) of > TeXworks, which should appear in early May. To that end, I've asked the > translators of previous versions to update their contributions, and > thankfully most have indeed done so very fast. > > There are, however, a few languages for which I haven't got any feedback > yet. These are: French, Japanese, Polish, Portuguese (pt_BR), and > Simplified Chinese. > > At least for French, I'm pretty sure (from past private communications) > that Alain will not be able to update the translations this time. > Therefore, I ask anyone who knows one of these languages and is willing > to help to update the translations we have (since this is a bugfix > release, changes are not extensive). > > To get you started, there is a guide at > http://code.google.com/p/texworks/wiki/Translating (you can skip the > lupdate if you use r801 or later). > In addition to the normal translation files, there are a few more > strings in supplementary files that I want to ask you to check and (if > necessary) translate. These are the strings "Open the following file > types with TeXworks by default:" (from win32/texworks-setup-script.iss), > "(La)TeX Editor" (from texworks.desktop), and "A simple environment for > editing, typesetting, and previewing TeX documents" (adapted from > texworks.desktop). These are used in the Windows installer and for > program shortcuts on Linux. To ensure the strings are formated > correctly, please use the attached template file to send the > translations back (instead of copying them into the mail). Note: if the > translation is already provided and correct, simply leave the > corresponding line in the template file empty. > > Thanks in advance, > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ???? TeXworks ????????? (La)TeX ??? ???????????? TeX ????????? -------------- next part -------------- A non-text attachment was scrubbed... Name: TeXworks_zh_CN.ts Type: text/vnd.trolltech.linguist Size: 68478 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TeXworks_zh_CN.qm Type: application/octet-stream Size: 38333 bytes Desc: not available URL: From st.loeffler at gmail.com Sun May 1 19:14:58 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Sun, 01 May 2011 19:14:58 +0200 Subject: [texworks] Call for Help: Translations In-Reply-To: References: <4DB85318.7080201@gmail.com> Message-ID: <4DBD9512.3000907@gmail.com> Hi, On 2011-04-30 16:39, Yinhe Zhang wrote: > The translation files for Simplified Chinese are attached. Sorry for > late. Also attached translated strings for Simplified Chinese for > "*tw-additional-translations-template.txt".* Thanks a lot. I've committed them in r806. Regards, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Mon May 2 04:35:28 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 2 May 2011 14:35:28 +1200 Subject: [texworks] About the native PDF viewer (feature request and a question) In-Reply-To: References: Message-ID: Hi Edoardo, > As a workaround, can TeXworks be configured to work with SumatraPDF > (SyncTeX enabled build) ? I don't seem to be able to find anything > related. Going in one direction ... TeXworks (even scripting) can tell you the line number the editor is in when a script is activated. It may be possible to use a system call to use syncable version of Sumatra to open a pdf at a certain line. (Sumatra is a standalone executable with no dependacies afaik). .. Then going in the other direction, are you looking for information on a command line switch for what happens when you doubleclick in SumatraPDF? I.e what options to set inside Sumatra (or any other syncinable pdf viewer for that matter ) to call TeXworks..? I'm not sure that TeXworks is yet set to receive such switches (file name and line number) when being called or opened... ? afaik Sumatra is Windows only - and somewhat under Wine in Linux, so broadening this out to cope more generally ... Can we make TeXworks monitor a port we could safely address in a running copy of TeXworks - would be ideal and have a certain list of accepted registered commands like open this .tex document (if not already open) at this line number, and bring the appropriate editor window into focus? Perhaps also a 'port' command in the acceptable list that says insert this text at cursor position/line number? So other applications (platform independent) can generally "talk" to TeXworks. (Perhaps even the reverse as well? Tw able to talk to another application's port?) Tw polling a user defined port (- with an established 'factory set' default number) for - "command", "text1", "text2", ... , "end" Instead, perhaps tying in with planned developments for being able to call scripts that Stefan has mentioned, the only acceptable 'port' received command could even just be strings "", "varaibleOne", "VariableTwo", ..., "end". And already registered/user approved scripts are the only thing a port command can run? Would there be an actual security risk? Or Edoardo, are you just looking for a means to yourself in C++ more directly integrate Sumatra into TeXworks itself (replacing poppler)? I'd really like the general solution for wider possibilities :) But then I wouldn't be doing all the hard C++ ... Paul On 29 April 2011 01:52, Edoardo Vacchi wrote: > The native viewer feels odd to me sometimes. > > I wish that holding the down arrow would make the viewer not block to > the end of the current page; also I'd expect page down to scroll the > view not to change to a new page. > > Is it possible to add "continuous" scrolling to the viewer? that is, > when a page ends, being able to see the top of the one which follows > (like in a word processor)? > > As a workaround, can TeXworks be configured to work with SumatraPDF > (SyncTeX enabled build) ? I don't seem to be able to find anything > related. > > Thanks a lot and keep it up, I like TeXworks, it's simple but it does > what I need. > > e.v. > From ovadia at pacbell.net Sun May 1 22:21:52 2011 From: ovadia at pacbell.net (Ovi Chitayat) Date: Sun, 1 May 2011 13:21:52 -0700 Subject: [texworks] gnuplot does not generate .table files Message-ID: Hi, I have a simple gnuplot 'plot' command within a tikzpicture block as follows \begin{tikzpicture}[domain=-5:5] \draw[arrows={-latex}] (-5,0) -- (6,0) node[below] {$x$}; \draw[arrows={-latex}] (0,-1.2) -- (0,2.5) node[above] {$f(x)$}; \draw[thick, color=blue, samples=100] plot[id=2] function{x} node[above] {$f(x) = x$}; \end{tikzpicture} This segment *IS* able to generate the .2.gnuplot so I know gnuplot does execute (not a \write18 issue). When I use the gnuplot interactive program (windows xp, gnuplot V 4.2 patch 4) and 'load' the .2.gnuplot file, the corresponding .2.table *IS* created in the same directory that would have contained the file generated by my code. The set of packages used is \usepackage{verbatim} \usepackage{amsmath} \usepackage{amssymb} \usepackage[pdftex]{graphicx} \usepackage{tikz} \usepackage[americaninductor]{circuitikz} I have searched long and wide and could not find a clue. Please help. Ovi -------------- next part -------------- An HTML attachment was scrubbed... URL: From uncommonnonsense at gmail.com Mon May 2 16:01:19 2011 From: uncommonnonsense at gmail.com (Edoardo Vacchi) Date: Mon, 2 May 2011 16:01:19 +0200 Subject: [texworks] About the native PDF viewer (feature request and a question) In-Reply-To: References: Message-ID: > Hi Edoardo, Hi Paul > .. Then going in the other direction, are you looking for information > on a command line switch for what happens when you doubleclick in > SumatraPDF? there is a synctex-enabled build of sumatra available here http://william.famille-blum.org/software/sumatra/index.html the command line for the tex editor can either be set via switch or via an option in Sumatra's config dialog. > Can we make TeXworks monitor a port we could safely address in a > running copy of TeXworks - would be ideal and have a certain list of > accepted registered commands like open this .tex document (if not > already open) at this line number, and bring the appropriate editor > window into focus? Perhaps also a 'port' command in the acceptable > list that says insert this text at cursor position/line number? many applications (such as texniccenter or texmaker) accomplish this by allowing only one instance and looking at command line switches > Or Edoardo, are you just looking for a means to yourself in C++ more > directly integrate Sumatra into TeXworks itself (replacing poppler)? As you are saying yourself, Sumatra is Windows-specific, so no. I'd rather use an external editor or have poppler refined in its 'rough edges' -- e.v. From sigmundv at gmail.com Mon May 2 16:59:08 2011 From: sigmundv at gmail.com (sigmundv at gmail.com) Date: Mon, 2 May 2011 15:59:08 +0100 Subject: [texworks] gnuplot does not generate .table files In-Reply-To: References: Message-ID: It IS a \write18 issue, so you need to call pdflatex with --shell-escape. Sigmund On Sun, May 1, 2011 at 21:21, Ovi Chitayat wrote: > Hi, > > I have a simple gnuplot ?plot? command within a tikzpicture block as > follows > > > > \begin{tikzpicture}[domain=-5:5] > > \draw[arrows={-latex}] (-5,0) -- (6,0) node[below] {$x$}; > > \draw[arrows={-latex}] (0,-1.2) -- (0,2.5) node[above] {$f(x)$}; > > \draw[thick, color=blue, samples=100] plot[id=2] function{x} node[above] > {$f(x) = x$}; > > \end{tikzpicture} > > > > This segment **IS** able to generate the .2.gnuplot so I know gnuplot > does execute (not a \write18 issue). > > When I use the gnuplot interactive program (windows xp, gnuplot V 4.2 patch > 4) and ?load? the > > .2.gnuplot file, the corresponding .2.table **IS** created in > the same directory that would have contained the file generated by my code. > > > > The set of packages used is > > > > \usepackage{verbatim} > > \usepackage{amsmath} > > \usepackage{amssymb} > > \usepackage[pdftex]{graphicx} > > \usepackage{tikz} > > \usepackage[americaninductor]{circuitikz} > > > > I have searched long and wide and could not find a clue. > > Please help. > > Ovi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Mon May 2 23:55:24 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 3 May 2011 09:55:24 +1200 Subject: [texworks] About the native PDF viewer (feature request and a question) In-Reply-To: References: Message-ID: On 3 May 2011 02:01, Edoardo Vacchi wrote: >> Hi Edoardo, > > Hi Paul > >> .. Then going in the other direction, are you looking for information >> on a command line switch for what happens when you doubleclick in >> SumatraPDF? > > there is a synctex-enabled build of sumatra available here > http://william.famille-blum.org/software/sumatra/index.html > the command line for the tex editor can either be set via > switch or via an option in Sumatra's config dialog. > >> Can we make TeXworks monitor a ?port we could safely address in ?a >> running copy of TeXworks - would be ideal and have a certain list of >> accepted registered commands like open this .tex document (if not >> already open) at this line number, and bring the appropriate editor >> window into focus? Perhaps also a 'port' command in the acceptable >> list that says insert this text at cursor position/line number? > > many applications (such as texniccenter or texmaker) accomplish this > by allowing only one instance and looking at command line switches > Yes that is the straightforward solution here, I was starting to think further ahead. >> Or Edoardo, are you just looking for a means to yourself in C++ more >> directly integrate Sumatra into TeXworks itself (replacing poppler)? > > As you are saying yourself, Sumatra is Windows-specific, so no. I'd > rather use an external editor or have poppler refined in its 'rough > edges' > There may be some things that this (or any) project may not be able to easily actually change about poppler, and some things that would be customisable. May be if you can spot features that you want poppler in TeXworks to achieve, already operating well in another C++ OpenSource project, and make recommendations to the developers here, based on those, so that the research is substantially done already for them? Paul > -- > e.v. > From uncommonnonsense at gmail.com Tue May 3 00:26:43 2011 From: uncommonnonsense at gmail.com (Edoardo Vacchi) Date: Tue, 3 May 2011 00:26:43 +0200 Subject: [texworks] About the native PDF viewer (feature request and a question) In-Reply-To: References: Message-ID: On Mon, May 2, 2011 at 11:55 PM, Paul A Norman wrote: > May be if you can spot features ?that you want poppler ?in TeXworks to > achieve, already operating well in another C++ OpenSource project, and > make recommendations to the developers here, based on those, so that > the research is substantially done already for them? well AFAIR evince is quite good at displaying PDFs, it has a less awkward UI and it is poppler-based, so you may want to have a look there. Also, Okular is Qt-based see: http://en.wikipedia.org/wiki/Poppler_(software)#PDF_readers_using_Poppler They both can have page facing, and continuous page scrolling; also I'd rather have mouse mode (hand vs. zoom tool) in the right-click menu; also, I'd expect the zoom tool to actually zoom the page instead of acting as a magnifying glass just my impressions, though e. From paul.a.norman at gmail.com Tue May 3 04:18:10 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 3 May 2011 14:18:10 +1200 Subject: [texworks] gnuplot does not generate .table files In-Reply-To: References: Message-ID: That's great Ovi, Thanks for sharing it - I've put this back in the thread for others to use... >> Paul, I just figured it out. The thing to do is to get texify to pass the switch to pdflatex. This is done as : --tex-option=--shell-escape not just simplely --shell-scape. << Paul On 3 May 2011 02:59, sigmundv at gmail.com wrote: > It IS a \write18 issue, so you need to call pdflatex with --shell-escape. > > > Sigmund > > > On Sun, May 1, 2011 at 21:21, Ovi Chitayat wrote: >> >> Hi, >> >> I have a simple gnuplot ?plot? command within a tikzpicture block as >> follows >> >> >> >> \begin{tikzpicture}[domain=-5:5] >> >> \draw[arrows={-latex}] (-5,0) -- (6,0) node[below] {$x$}; >> >> \draw[arrows={-latex}] (0,-1.2) -- (0,2.5) node[above] {$f(x)$}; >> >> \draw[thick, color=blue, samples=100] plot[id=2] function{x} node[above] >> {$f(x) = x$}; >> >> \end{tikzpicture} >> >> >> >> This segment *IS* able to generate the .2.gnuplot so I know gnuplot >> does execute (not a \write18 issue). >> >> When I use the gnuplot interactive program (windows xp, gnuplot V 4.2 >> patch 4) and ?load? the >> >> .2.gnuplot file, the corresponding .2.table *IS* created in the >> same directory that would have contained the file generated by my code. >> >> >> >> The set of packages used is >> >> >> >> \usepackage{verbatim} >> >> \usepackage{amsmath} >> >> \usepackage{amssymb} >> >> \usepackage[pdftex]{graphicx} >> >> \usepackage{tikz} >> >> \usepackage[americaninductor]{circuitikz} >> >> >> >> I have searched long and wide and could not find a clue. >> >> Please help. >> >> Ovi > From ovadia at pacbell.net Tue May 3 20:54:43 2011 From: ovadia at pacbell.net (Ovi Chitayat) Date: Tue, 3 May 2011 11:54:43 -0700 (PDT) Subject: [texworks] matlab from pdflatex/latex Message-ID: <337973.41621.qm@web81006.mail.mud.yahoo.com> Hi, Does anyone have sample code to have matlab called from *tex, generate plot data and have *tex plot this data? No need to explain write18 issues... Ovi -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Wed May 4 18:55:02 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Wed, 04 May 2011 18:55:02 +0200 Subject: [texworks] About the native PDF viewer (feature request and a question) In-Reply-To: References: Message-ID: <4DC184E6.2090301@gmail.com> Hi, On 2011-05-02 16:01, Edoardo Vacchi wrote: >> Can we make TeXworks monitor a port we could safely address in a >> running copy of TeXworks - would be ideal and have a certain list of >> accepted registered commands like open this .tex document (if not >> already open) at this line number, and bring the appropriate editor >> window into focus? Perhaps also a 'port' command in the acceptable >> list that says insert this text at cursor position/line number? > many applications (such as texniccenter or texmaker) accomplish this > by allowing only one instance and looking at command line switches This actually applies to TeXworks as well. It is a single-instance, and it supports the --position=... switch (or the short form -p ...), which currently can be used to jump to a specific line (for .tex files) or page (for .pdf files). HTH Stefan From st.loeffler at gmail.com Wed May 4 19:20:11 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Wed, 04 May 2011 19:20:11 +0200 Subject: [texworks] About the native PDF viewer (feature request and a question) In-Reply-To: References: Message-ID: <4DC18ACB.9000700@gmail.com> Hi, On 2011-05-03 00:26, Edoardo Vacchi wrote: > On Mon, May 2, 2011 at 11:55 PM, Paul A Norman wrote: > >> May be if you can spot features that you want poppler in TeXworks to >> achieve, already operating well in another C++ OpenSource project, and >> make recommendations to the developers here, based on those, so that >> the research is substantially done already for them? > well AFAIR evince is quite good at displaying PDFs, it has a less > awkward UI and it is poppler-based, so you may want to have a look > there. Yes, evince is poppler-based, but not on Qt, so unfortunately there are many things that are different in the poppler binding used by evince. > Also, Okular is Qt-based > see: http://en.wikipedia.org/wiki/Poppler_(software)#PDF_readers_using_Poppler Actually, Okular looks a lot more powerful than I had thought. I'll definitely have to check out their sources and maybe use something for Tw. > They both can have page facing, and continuous page scrolling; This already is on the wish list (http://code.google.com/p/texworks/issues/detail?id=296). I hope this gets implemented in the 0.5 series. > also I'd rather have mouse mode (hand vs. zoom tool) in the right-click > menu; This sounds like an interesting idea. Could you add it to the issue tracker at http://code.google.com/p/texworks/issues/, please? > also, I'd expect the zoom tool to actually zoom the page instead > of acting as a magnifying glass Well, I'd rather not abandon the current magnifying glass version, as I find it quite useful, in particular when you want to quickly check something rather small. But I agree that the toolbar icon (a magnifying glass with a +) can be misleading, so could you please file a bug for that? > just my impressions, though Thanks for sharing them! Cheers, Stefan From paul.a.norman at gmail.com Thu May 5 02:11:59 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 5 May 2011 12:11:59 +1200 Subject: [texworks] About the native PDF viewer (feature request and a question) In-Reply-To: <4DC184E6.2090301@gmail.com> References: <4DC184E6.2090301@gmail.com> Message-ID: On 5 May 2011 04:55, Stefan L?ffler wrote: > Hi, > > On 2011-05-02 16:01, Edoardo Vacchi wrote: >>> Can we make TeXworks monitor a ?port we could safely address in ?a >>> running copy of TeXworks - would be ideal and have a certain list of >>> accepted registered commands like open this .tex document (if not >>> already open) at this line number, and bring the appropriate editor >>> window into focus? Perhaps also a 'port' command in the acceptable >>> list that says insert this text at cursor position/line number? >> many applications (such as texniccenter or texmaker) accomplish this >> by allowing only one instance and looking at command line switches > > This actually applies to TeXworks as well. It is a single-instance, and > it supports the --position=... switch (or the short form -p ...), which > currently can be used to jump to a specific line (for .tex files) or > page (for .pdf files). > That got me hunting - sounded really useful :) I couldn't find it in the manual - searched over the files - did I miss it or is it yet to go in the manual? At - http://www.google.com/codesearch/p?hl=en#TCAOwTxChU8/trunk/man/texworks.1&q=position%3D%20package:http://texworks%5C.googlecode%5C.com&sa=N&cd=2&ct=rc -- Found this reference in the source code - are these all of the command line switches? .SH OPTIONS Form the cmd shell on Xp only one set of these worked ... ".TP .B --help, -? Display a short overview over all command line options" texworks --help texworks -h Nothing happens at all TeXworks does not appear as a running process as far as I can tell, however if Tw is open already, but not in focus, it is brought to the front of the desktop. No message on the command line. .TP .B --position=, -p Open the next specified file at the given position (line or page) texworks -p=1000 "/some/path/myTex.tex" texworks -p=10 "/some/path/myTex.pdf" Very nice. The switch MUST appear BEFORE the file name. ".TP .B --version, -v Display version information" texworks --version texworks -v Nothing happens at all, however if Tw is open already, but not in focus, it is brought to the front of the desktop. No message on the command line. With texworks -p=10 "/some/path/myTex.pdf" The source is not opened with it (just a note not a complaint) And with texworks -p=1000 "/some/path/myTex.tex" I have object modules (PhpJs ($P), twConst, msgBox, twPan ($tw) as in FileTracker.js ) loaded when Tw starts and there is no problem with them at all. // Script-Type: hook // Hook: TeXworksLaunched All is fine there. But I have a hookscript that works on ... // Hook: LoadFile That gets interfered with. That script monitors and records all files opened by TeXworks to give me an exhaustive list of unique filenames for when I need to look back beyond the Recent Files list. The .tex opens, and then it does not jump to line 1000 until I clear my hookscript error message in the Debugger. Once the debugger is cleared, the editor jumps correctly to line 1000 as indicated above. The error is that my script wants to open its monitoring file, but it can't find it - when I am using -p=someIntegerLineNumber while opening a .tex file As might be expected, this does not happen when opening a .pdf to a page number -p=12 My script ( FileTracker.js) fails when something like this is used on the command line: texworks -p=1000 "/some/path/myTex.tex" FileTracker.js is below - as I say it always manages to find its record file (in same directory as script itself) undedr normal circumstances (i.e. when not using -p=someLineNumber switch). Any advice appreciated please. Paul > HTH > Stefan > Sample of filelist.txt =============== D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/scripts/Graphics/GraphicInsertColWidth.js D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/scripts/text/autocomplete.js D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/scripts/FileTracker/fileList.txt D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/syntax/javascript.php D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/scripts/Scripting - Experiments/tw_OBJECT.js C:/Hold/MyFile.txt D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/configuration/texworks-config.txt FileTracker.js ========== // TeXworksScript // Title: File Tracker // Description: Keeps track of first opening of a file // Author: Paul Norman // Version: 0.3 // Script-Type: hook // Hook: LoadFile eval(TW.app.getGlobal("helper_twPan")); // Comment if NOT Needed - This includes PhpJs ($P), twConst, msgBox, twPan ($tw) function writeFileList(thisPath) { twPan.file_put_contents("fileList.txt" , fileList + thisPath + PhpJs.chr(13) + PhpJs.chr(10) ); } var currentFile = TW.target.fileName; var fileList = twPan.file_get_contents("fileList.txt"); if (fileList == undefined)// first usage { fileList = ""; writeFileList(currentFile); } else { if (fileList.indexOf(currentFile) == -1) { writeFileList(currentFile); } } null From paul.a.norman at gmail.com Thu May 5 03:46:45 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 5 May 2011 13:46:45 +1200 Subject: [texworks] About the native PDF viewer (feature request and a question) In-Reply-To: References: <4DC184E6.2090301@gmail.com> Message-ID: P.S. if a copy of TeXworks is already open even just on a new blank file, my previously reported probl;em with the hook script does not happen, it seems to only happen when Tw is being started from the command line from scratch. Also, as hinted at in the source code, it looks possible to gang-up the files to be opened, each with a preceding line/page number switch e.g. >texworks -p=1500 "/SomePath/MyFile01.tex" -p=2500 "/SomePath/MyFile02.tex" -p=25 "/SomePath/MyFile03.pdf" Paul On 5 May 2011 12:11, Paul A Norman wrote: > On 5 May 2011 04:55, Stefan L?ffler wrote: >> Hi, >> >> On 2011-05-02 16:01, Edoardo Vacchi wrote: >>>> Can we make TeXworks monitor a ?port we could safely address in ?a >>>> running copy of TeXworks - would be ideal and have a certain list of >>>> accepted registered commands like open this .tex document (if not >>>> already open) at this line number, and bring the appropriate editor >>>> window into focus? Perhaps also a 'port' command in the acceptable >>>> list that says insert this text at cursor position/line number? >>> many applications (such as texniccenter or texmaker) accomplish this >>> by allowing only one instance and looking at command line switches >> >> This actually applies to TeXworks as well. It is a single-instance, and >> it supports the --position=... switch (or the short form -p ...), which >> currently can be used to jump to a specific line (for .tex files) or >> page (for .pdf files). >> > > That got me hunting - sounded really useful :) > > I couldn't find it in the manual - searched over the files - did I > miss it or is it yet to go in the manual? > > At - > ?http://www.google.com/codesearch/p?hl=en#TCAOwTxChU8/trunk/man/texworks.1&q=position%3D%20package:http://texworks%5C.googlecode%5C.com&sa=N&cd=2&ct=rc > > -- Found this reference in the source code - are these all of the > command line switches? > > .SH OPTIONS > > Form the cmd shell on Xp only one set of these worked ... > > ".TP > .B --help, -? > Display a short overview over all command line options" > > texworks --help > texworks -h > > Nothing happens at all TeXworks does not appear as a running process > as far as I can tell, however if Tw is open already, but not in focus, > it is brought to the front of the desktop. > > No message on the command line. > > .TP > .B --position=, -p > Open the next specified file at the given position (line or page) > > texworks -p=1000 "/some/path/myTex.tex" > texworks -p=10 "/some/path/myTex.pdf" > > Very nice. > > The switch MUST appear BEFORE the file name. > > ".TP > .B --version, -v > Display version information" > > texworks --version > texworks -v > > Nothing happens at all, however if Tw is open already, but not in > focus, it is brought to the front of the desktop. > > No message on the command line. > > With > > texworks -p=10 "/some/path/myTex.pdf" > > The source is not opened with it (just a note not a complaint) > > And with > > texworks -p=1000 "/some/path/myTex.tex" > > I have object modules (PhpJs ($P), twConst, msgBox, twPan ($tw) as in > FileTracker.js ) loaded when Tw starts and there is no problem with > them at all. > > // Script-Type: hook > // Hook: TeXworksLaunched > > All is fine there. > > But I have a hookscript that works on ... > > // Hook: LoadFile > > That gets interfered with. That script monitors and records all files > opened by TeXworks to give me an exhaustive list of unique filenames > for when I need to look back beyond the Recent Files list. > > The .tex opens, and then it does not jump to line 1000 until I clear > my hookscript error message in the Debugger. Once the debugger is > cleared, the editor jumps correctly to line 1000 as indicated above. > > The error is that my script wants to open its monitoring file, but it > can't find it - when I am using -p=someIntegerLineNumber while opening > a .tex file > > As might be expected, this does not happen when opening a .pdf to a > page number -p=12 > > My script ( FileTracker.js) ?fails when something like this is used on > the command line: > > texworks -p=1000 "/some/path/myTex.tex" > > ?FileTracker.js is below - as I say it always manages to find its > record file (in same directory as script itself) undedr normal > circumstances (i.e. when not using -p=someLineNumber switch). > > Any advice appreciated please. > > Paul > >> HTH >> Stefan >> > > Sample of filelist.txt > =============== > > D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/scripts/Graphics/GraphicInsertColWidth.js > D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/scripts/text/autocomplete.js > D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/scripts/FileTracker/fileList.txt > D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/syntax/javascript.php > D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/scripts/Scripting > - Experiments/tw_OBJECT.js > C:/Hold/MyFile.txt > D:/LaTeXPortable/LatexUtils/TeXworks/TeXworks/config/configuration/texworks-config.txt > > FileTracker.js > ========== > > // TeXworksScript > // Title: ?File Tracker > // Description: Keeps track of first opening of a file > // Author: ?Paul Norman > // Version: 0.3 > // Script-Type: hook > // Hook: LoadFile > > > ?eval(TW.app.getGlobal("helper_twPan")); // ?Comment if NOT Needed - > This includes PhpJs ($P), twConst, msgBox, twPan ($tw) > > ? ?function writeFileList(thisPath) > ? ? ? ? ?{ > ? ? ? ? ? twPan.file_put_contents("fileList.txt" > ? ? ? ? ? , fileList > ? ? ? ? ? + thisPath > ? ? ? ? ? + PhpJs.chr(13) + PhpJs.chr(10) > ? ? ? ? ? ); > ? ? ? ? ?} > > > ?var ?currentFile ?= TW.target.fileName; > > > ?var ?fileList = twPan.file_get_contents("fileList.txt"); > > > ? if (fileList == undefined)// first usage > ? ? { > ? ? ? fileList = ""; > ? ? ? writeFileList(currentFile); > ? ? ? ? ? ?} > ? ? ?else > ? ? ?{ > ? ? ? ?if (fileList.indexOf(currentFile) == -1) > ? ? ? ? { > ? ? ? ? ?writeFileList(currentFile); > ? ? ? ? } > > ? ? ?} > > ? null > From kohda at pm.tokushima-u.ac.jp Thu May 5 10:03:19 2011 From: kohda at pm.tokushima-u.ac.jp (Atsuhito Kohda) Date: Thu, 05 May 2011 17:03:19 +0900 (JST) Subject: [texworks] fails to start without dbus running due to logic error In-Reply-To: <20110504095153.GA25819@email.mathematik.uni-freiburg.de> Message-ID: <20110505.170319.193725827.kohda@pm.tokushima-u.ac.jp> Hi all, I, a maintainer of TeXworks of Debian, got the following bug report recently (Bug#625543). > The following patch fixes a bug in the control flow that causes > texworks to not start without a running dbus daemon. > > --- texworks-0.4.0.orig/src/main.cpp > +++ texworks-0.4.0/src/main.cpp > @@ -141,8 +141,8 @@ > continue; > interface.call("openFile", fi.absoluteFilePath(), fileToOpen.position); > } > + return 0; > } > - return 0; > } > > new TWAdaptor(&app); If this is a real problem, I prefer to be fixed in an upstream than to be fixed in locally Debian so I forward this to the list. I'm sorry if this is an already known problem or if this is not an appropriate list to ask a bug. Best regards, 2011-5-5(Thu) -- Debian Developer - much more I18N of Debian Atsuhito Kohda Department of Math., Univ. of Tokushima From st.loeffler at gmail.com Thu May 5 21:02:34 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 05 May 2011 21:02:34 +0200 Subject: [texworks] fails to start without dbus running due to logic error In-Reply-To: <20110505.170319.193725827.kohda@pm.tokushima-u.ac.jp> References: <20110505.170319.193725827.kohda@pm.tokushima-u.ac.jp> Message-ID: <4DC2F44A.3030405@gmail.com> Hi, On 2011-05-05 10:03, Atsuhito Kohda wrote: > I, a maintainer of TeXworks of Debian, got the following > bug report recently (Bug#625543). > If this is a real problem, I prefer to be fixed in an upstream > than to be fixed in locally Debian so I forward this to the list. > > I'm sorry if this is an already known problem or if this is > not an appropriate list to ask a bug. These are the bug reports I like: the ones with (simple) patches ;). Thanks for letting us know - I committed the patch as r808. Reporting bugs here is fine, though the dedicated bug tracker is at http://code.google.com/p/texworks/issues/list (primarily to keep lengthy technical discussions off this list for all users, and to keep track of older issues that can't/aren't solved immediately). Cheers, Stefan From st.loeffler at gmail.com Thu May 5 21:31:33 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 05 May 2011 21:31:33 +0200 Subject: [texworks] About the native PDF viewer (feature request and a question) In-Reply-To: References: <4DC184E6.2090301@gmail.com> Message-ID: <4DC2FB15.60206@gmail.com> Hi, On 2011-05-05 02:11, Paul A Norman wrote: > On 5 May 2011 04:55, Stefan L?ffler wrote: >> On 2011-05-02 16:01, Edoardo Vacchi wrote: >>>> Can we make TeXworks monitor a port we could safely address in a >>>> running copy of TeXworks - would be ideal and have a certain list of >>>> accepted registered commands like open this .tex document (if not >>>> already open) at this line number, and bring the appropriate editor >>>> window into focus? Perhaps also a 'port' command in the acceptable >>>> list that says insert this text at cursor position/line number? >>> many applications (such as texniccenter or texmaker) accomplish this >>> by allowing only one instance and looking at command line switches >> This actually applies to TeXworks as well. It is a single-instance, and >> it supports the --position=... switch (or the short form -p ...), which >> currently can be used to jump to a specific line (for .tex files) or >> page (for .pdf files). >> > That got me hunting - sounded really useful :) > > I couldn't find it in the manual - searched over the files - did I > miss it or is it yet to go in the manual? I can't remember off-hand, but chances are high that it isn't in the manual yet. Actually I don't really know where best to put it. Any suggestions? > At - > http://www.google.com/codesearch/p?hl=en#TCAOwTxChU8/trunk/man/texworks.1&q=position%3D%20package:http://texworks%5C.googlecode%5C.com&sa=N&cd=2&ct=rc > > -- Found this reference in the source code - are these all of the > command line switches? > > .SH OPTIONS Yes, all these (3) are command line options. The file you found (man/texworks.1) is actually a man-page that is used on *nix (and Mac, I think) as a brief documentation on the command line. The actual place in the code where this is handed is in src/main.cpp (lines 52-95). > Form the cmd shell on Xp only one set of these worked ... Yes, only "position" works. This is a known problem (http://code.google.com/p/texworks/issues/detail?id=475), but the workaround I noted down there doesn't seem to work. In fact, after some searching the internet, there doesn't seem to be any (simple) possibility by design. Anyway, "version" and "help" are not crucial and provided primarily for GNU compliance on Linux. > ".TP > .B --help, -? > Display a short overview over all command line options" > > texworks --help > texworks -h > > Nothing happens at all TeXworks does not appear as a running process > as far as I can tell, however if Tw is open already, but not in focus, > it is brought to the front of the desktop. See above. The effect is the same as when trying to launch TeXworks multiple times. > .TP > .B --position=, -p > Open the next specified file at the given position (line or page) > > texworks -p=1000 "/some/path/myTex.tex" > texworks -p=10 "/some/path/myTex.pdf" > > Very nice. > > The switch MUST appear BEFORE the file name. Precisely. It modifies the behavior for the next filename it finds only. I.e., if you want to open to files at line 100 each, you'd need to say "texworks -p=100 a.tex -p=100 b.tex". > With > > texworks -p=10 "/some/path/myTex.pdf" > > The source is not opened with it (just a note not a complaint) This is always the case when opening pdf files. > I have object modules (PhpJs ($P), twConst, msgBox, twPan ($tw) as in > FileTracker.js ) loaded when Tw starts and there is no problem with > them at all. > > // Script-Type: hook > // Hook: TeXworksLaunched > > All is fine there. > > But I have a hookscript that works on ... > > // Hook: LoadFile > > That gets interfered with. That script monitors and records all files > opened by TeXworks to give me an exhaustive list of unique filenames > for when I need to look back beyond the Recent Files list. > > The .tex opens, and then it does not jump to line 1000 until I clear > my hookscript error message in the Debugger. Once the debugger is > cleared, the editor jumps correctly to line 1000 as indicated above. > > The error is that my script wants to open its monitoring file, but it > can't find it - when I am using -p=someIntegerLineNumber while opening > a .tex file On 2011-05-05 03:46, Paul A Norman wrote: > P.S. if a copy of TeXworks is already open even just on a new blank > file, my previously reported probl;em with the hook script does not > happen, it seems to only happen when Tw is being started from the > command line from scratch. I think I can explain this. When starting Tw, the sequence of events is as follows: 1) Parse command line 2) Load each file given on the command line (I omit the case when none are given). For each file: 2a) Load the file contents from disk 2b) Run LoadFile hook 2c) deal with presentation on screen (including moving the cursor around) After all files are processed 3) Once the rest of the application is fully initialized, run the TeXworksLaunched hook Consequently, when you set up your frameworks/functions/etc. in TeXworksLaunched, it will not be available in the first LoadFile executions. If there is an error in LoadFile, the presentation stuff is not dealt with, so the cursor only moves after that error is dismissed. As a workaround for your case, you could set a global in TeXworksLaunched once all your code is initialized. In LoadFile, you can then check for that flag, and if it is not present defer logging to a TeXworksLaunched handler. HTH Stefan From murray at math.umass.edu Fri May 6 17:12:30 2011 From: murray at math.umass.edu (Murray Eisenberg) Date: Fri, 06 May 2011 11:12:30 -0400 Subject: [texworks] \begin...\end environment completion? Message-ID: <4DC40FDE.4070804@math.umass.edu> I'm using current texworks in Mac TeXShop. Is there some way to cause the texworks editor to supply automatically the \end{env} part of a \begin{env}...\end{env} environment delimiters after I type the "\begin{env}" part? This is something I'm accustomed to doing in WinEdt under Windows (with any TeX engine). There, for example, if I type \begin{enumerate} and press Alt-Enter, the editor automatically inserts a blank line after what I typed, automatically types \end{enumerate}, and positions the cursor back at the start of the blank line, so what I have is: \begin{enumerate} * \end{enumerate} A great time-saver. I'm told that the Mac is a more user-friendly place to work than a PC with Windows, but I cannot even find documentation about such a feature for texworks (or TeXShop). -- Murray Eisenberg murray at math.umass.edu Mathematics & Statistics Dept. Lederle Graduate Research Tower phone 413 549-1020 (H) University of Massachusetts 413 545-2859 (W) 710 North Pleasant Street fax 413 545-1801 Amherst, MA 01003-9305 From herbs at wideopenwest.com Fri May 6 21:29:24 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Fri, 6 May 2011 14:29:24 -0500 Subject: [texworks] \begin...\end environment completion? In-Reply-To: <4DC40FDE.4070804@math.umass.edu> References: <4DC40FDE.4070804@math.umass.edu> Message-ID: <7A7C82EC-5E13-494C-96D6-626D94A7C8F7@wideopenwest.com> On May 6, 2011, at 10:12 AM, Murray Eisenberg wrote: > I'm using current texworks in Mac TeXShop. Is there some way to cause the texworks editor to supply automatically the \end{env} part of a \begin{env}...\end{env} environment delimiters after I type the "\begin{env}" part? > > This is something I'm accustomed to doing in WinEdt under Windows (with any TeX engine). There, for example, if I type > > \begin{enumerate} > > and press Alt-Enter, the editor automatically inserts a blank line after what I typed, automatically types \end{enumerate}, and positions the cursor back at the start of the blank line, so what I have is: > > \begin{enumerate} > * > \end{enumerate} > > A great time-saver. > > I'm told that the Mac is a more user-friendly place to work than a PC with Windows, but I cannot even find documentation about such a feature for texworks (or TeXShop). Howdy, Ummmm... Are you using TeXworks or TeXShop? If you are using TeXShop there are several ways of getting that completion with the latest version: (1)If you have \begin{myenvironment} with the cursor just after the closing brace simply press Esc and the corresponding \end{myenvironment} will be placed on the next line and the cursor will remain where it started. (2)If you are using TeXShop 2.41 you can complete an environment (i.e., balance \begin...\end) by using the Source->Close Current Environment (Ctl-Cmd-C) which will give you the \end{myenvironment} with the cursor at the end of the statement. (3)If you are using any of the usual environments you can use Command Completion (TeXworks has a similar feature as TeXShop in this instance). E.g., to get a skeleton for an enumerate environment simply write \benu at the start of a line and press Esc (with TeXworks you press Tab --- TeXShop lets you make the ``trigger'' key Tab too in TeXshop->Preferences->Source->Command Completion Triggered By:) and you'll get (a little bit different in TeXworks) \begin{enumerate} \item |?| \end{enumerate}? where |?| is a selected ? (called a Mark for Command Completion). You can move from Mark to Mark, etc. For TeXShop take a look at ~/Library/TeXShop/CommandCompletion/Quick Start Guide... or the full documentation for a list of all completions/abbreviations supplied by default with TeXShop (~/Library/ is the Library folder in your HOME folder). Good Luck, Herb Schulz (herbs at wideopenwest dot com) From murrayeisenberg at gmail.com Fri May 6 21:57:03 2011 From: murrayeisenberg at gmail.com (Murray Eisenberg) Date: Fri, 06 May 2011 15:57:03 -0400 Subject: [texworks] \begin...\end environment completion? In-Reply-To: <7A7C82EC-5E13-494C-96D6-626D94A7C8F7@wideopenwest.com> References: <4DC40FDE.4070804@math.umass.edu> <7A7C82EC-5E13-494C-96D6-626D94A7C8F7@wideopenwest.com> Message-ID: <4DC4528F.3000307@gmail.com> Sorry, I was indeed using texworks whereas I had intended to use TeXShop: I hadn't noticed that when I double-clicked the source tex file it opened in texworks instead of TeXShop. And then I confused the names of the front ends. No wonder I couldn't find what I wanted in the Help, which was for texworks instead of TeXShop. What you say works, and I thank you. On 5/6/2011 3:29 PM, Herbert Schulz wrote: > > On May 6, 2011, at 10:12 AM, Murray Eisenberg wrote: > >> I'm using current texworks in Mac TeXShop. Is there some way to cause the texworks editor to supply automatically the \end{env} part of a \begin{env}...\end{env} environment delimiters after I type the "\begin{env}" part? >> >> This is something I'm accustomed to doing in WinEdt under Windows (with any TeX engine). There, for example, if I type >> >> \begin{enumerate} >> >> and press Alt-Enter, the editor automatically inserts a blank line after what I typed, automatically types \end{enumerate}, and positions the cursor back at the start of the blank line, so what I have is: >> >> \begin{enumerate} >> * >> \end{enumerate} >>... > > Howdy, > > Ummmm... Are you using TeXworks or TeXShop? > > If you are using TeXShop there are several ways of getting that completion with the latest version: > > (1)If you have > > \begin{myenvironment} > > with the cursor just after the closing brace simply press Esc and the corresponding > > \end{myenvironment} > > will be placed on the next line and the cursor will remain where it started. > > (2)If you are using TeXShop 2.41 you can complete an environment (i.e., balance \begin...\end) by using the Source->Close Current Environment (Ctl-Cmd-C) which will give you the \end{myenvironment} with the cursor at the end of the statement. > > (3)If you are using any of the usual environments you can use Command Completion (TeXworks has a similar feature as TeXShop in this instance). E.g., to get a skeleton for an enumerate environment simply write > > \benu > > at the start of a line and press Esc (with TeXworks you press Tab --- TeXShop lets you make the ``trigger'' key Tab too in TeXshop->Preferences->Source->Command Completion Triggered By:) and you'll get (a little bit different in TeXworks) > > \begin{enumerate} > \item > |?| > \end{enumerate}? > > where |?| is a selected ? (called a Mark for Command Completion). You can move from Mark to Mark, etc. For TeXShop take a look at ~/Library/TeXShop/CommandCompletion/Quick Start Guide... or the full documentation for a list of all completions/abbreviations supplied by default with TeXShop (~/Library/ is the Library folder in your HOME folder). -- Murray Eisenberg murray at math.umass.edu Mathematics & Statistics Dept. Lederle Graduate Research Tower phone 413 549-1020 (H) University of Massachusetts 413 545-2859 (W) 710 North Pleasant Street fax 413 545-1801 Amherst, MA 01003-9305 From agbqc at juno.com Sun May 8 21:05:46 2011 From: agbqc at juno.com (agbqc at juno.com) Date: Sun, 8 May 2011 22:05:46 +0300 Subject: [texworks] input files Message-ID: <20110508.120629.946.474057@mailpop07.vgs.untd.com> I just downloaded MikTex to my new computer. Where do my input files need to be so that when I TeX a file, the program will know where to find them? Thanks. Arthur Goodman ____________________________________________________________ Groupon™ Official Site 1 ridiculously huge coupon a day. Get 50-90% off your city's best! http://thirdpartyoffers.juno.com/TGL3141/4dc6e9d1e471d2e57f5st04vuc From sigmundv at gmail.com Mon May 9 12:31:45 2011 From: sigmundv at gmail.com (sigmundv at gmail.com) Date: Mon, 9 May 2011 12:31:45 +0200 Subject: [texworks] input files In-Reply-To: <20110508.120629.946.474057@mailpop07.vgs.untd.com> References: <20110508.120629.946.474057@mailpop07.vgs.untd.com> Message-ID: Any directory will do, as long as LaTeX is on the path. The MikTeX installer should set this up for you, so after installing MikTeX you should be ready to go. Sigmund On Sun, May 8, 2011 at 21:05, wrote: > I just downloaded MikTex to my new computer. > Where do my input files need to be so that when I TeX a file, the program > will > know where to find them? > > Thanks. > Arthur Goodman > ____________________________________________________________ > Groupon™ Official Site > 1 ridiculously huge coupon a day. Get 50-90% off your city's best! > http://thirdpartyoffers.juno.com/TGL3141/4dc6e9d1e471d2e57f5st04vuc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joerg.kleinman at gmx.de Tue May 10 14:28:04 2011 From: joerg.kleinman at gmx.de (Joerg Klein) Date: Tue, 10 May 2011 14:28:04 +0200 Subject: [texworks] Message from TeXworks user Message-ID: <4DC92F54.8030305@gmx.de> Hello, I trey to work with MikTeX. I got this errormessage. What ist wrong? This is pdfTeX, Version 3.1415926-1.40.11 (MiKTeX 2.9) entering extended mode (C:/Users/klein/Downloads/Hallo/test.tex that is all. Thank you for the help Joerg ----- configuration info ----- TeXworks version : 0.4.0r759 (MiKTeX 2.9) Install location : C:/Program Files/MiKTeX 2.9/miktex/bin/miktex-texworks.exe Library path : C:/Users/klein/AppData/Local/MiKTeX/2.9/TeXworks/0.4\ pdfTeX location : C:/Program Files/MiKTeX 2.9/miktex/bin/pdftex.exe Operating system : Windows Microsoft Windows 7 Business Edition, 32-bit (build 7600) Qt4 version : 4.7.2 (build) / 4.7.2 (runtime) ------------------------------ From sigmundv at gmail.com Tue May 10 15:45:13 2011 From: sigmundv at gmail.com (sigmundv at gmail.com) Date: Tue, 10 May 2011 15:45:13 +0200 Subject: [texworks] Message from TeXworks user In-Reply-To: <4DC92F54.8030305@gmx.de> References: <4DC92F54.8030305@gmx.de> Message-ID: What does your test.tex look like? Sigmund On Tue, May 10, 2011 at 14:28, Joerg Klein wrote: > Hello, > > I trey to work with MikTeX. I got this errormessage. What ist wrong? > > This is pdfTeX, Version 3.1415926-1.40.11 (MiKTeX 2.9) > > entering extended mode > > (C:/Users/klein/Downloads/Hallo/test.tex > > > that is all. > > Thank you for the help > > Joerg > > ----- configuration info ----- > TeXworks version : 0.4.0r759 (MiKTeX 2.9) > Install location : C:/Program Files/MiKTeX > 2.9/miktex/bin/miktex-texworks.exe > Library path : C:/Users/klein/AppData/Local/MiKTeX/2.9/TeXworks/0.4\ > pdfTeX location : C:/Program Files/MiKTeX 2.9/miktex/bin/pdftex.exe > Operating system : Windows Microsoft Windows 7 Business Edition, 32-bit > (build 7600) > Qt4 version : 4.7.2 (build) / 4.7.2 (runtime) > ------------------------------ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From source at sharpsteen.net Thu May 12 07:23:42 2011 From: source at sharpsteen.net (Charlie Sharpsteen) Date: Wed, 11 May 2011 22:23:42 -0700 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) Message-ID: Hey everyone, I just finished a CMake-based build of TeXworks that is capable of producing stand-alone apps. At least, the resulting binary build on OS X 10.6.7 appears to be running fine on a clean install of OS X 10.6.4. A Drag N' Drop installer is available at: https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-813-8c754c5.dmg Currently the build is Snow Leopard only and there is no support for Qt plugins such as Lua and Python scripting. If someone wants to play with the build system, the code is available at: https://github.com/downloads/Sharpie/TeXworks Direct git access: git://github.com/Sharpie/TeXworks.git If anyone has any improvements/corrections, feel free to fork the repo and send a pull request. If the core developers are interested in bringing this new build system into the SVN repository, the following patch should apply cleanly against revision 813: https://github.com/Sharpie/TeXworks/compare/texworks-svn...cmake-only There is only one teenie-tiny change to src/TWApp.h to guard against D-Bus that affects the existing code code. Hope this is useful to someone! -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Thu May 12 21:24:01 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 12 May 2011 21:24:01 +0200 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: References: Message-ID: <4DCC33D1.2080408@gmail.com> Hi, this is looking awesome, thanks! If you agree, I'd like to write something up (well, actually, copy from you ;)) for the Tw wiki. WARNING (for non-developers): The rest of this message is very technical. A few questions: 1) is it possible to use the upstream svn repo instead of cloning a git version of it? That would have the benefit that people don't have to rely/wait on you pulling changes, as long as nothing dramatic changes. 2) Can you add support for stable releases? They are in /tags in the svn repo (if the answer to 1) is yes, this is trivial) 3) I noticed you mention homebrew; can your cmake system be incorporated into homebrew? On 2011-05-12 07:23, Charlie Sharpsteen wrote: > If someone wants to play with the build system, the code is available at: > > https://github.com/downloads/Sharpie/TeXworks This didn't work for me. > Direct git access: > > git://github.com/Sharpie/TeXworks.git > > > If anyone has any improvements/corrections, feel free to fork the repo > and send a pull request. Done. I wanted to send separate pull requests for different sets of changes, but didn't succeed (is it possible at all? I have practically no experience with git/github). > If the core developers are interested in bringing this new build > system into the SVN repository, the following patch should apply > cleanly against revision 813: > > https://github.com/Sharpie/TeXworks/compare/texworks-svn...cmake-only > > There is only one teenie-tiny change to src/TWApp.h to guard against > D-Bus that affects the existing code code. Bringing the whole CMake system in will need some thinking and discussion, so please be patient. Regarding the patch: it seems trivial, but the way I read the Qt docs, Q_WS_X11 and Q_WS_MAC should be mutually exclusive. See, e.g., main.cpp, which also uses dbus, but only guards against Q_WS_X11 - why doesn't that cause problems for you? The only thing I can think of is that your workaround "ADD_DEFINITIONS( -DQ_WS_MAC )" is not really resolving the issue (note that there is TwApp.h, but no main.h, to be processed by moc). I could imagine that QT4_WRAP_CPP actually mistakes the system and defines Q_WS_X11 _instead of_ DQ_WS_MAC. Can this be overridden by "REMOVE_DEFINITIONS( -DQ_WS_X11 )"? All in all, I'd rather have a proper solution if possible rather than hacking the svn code... > Hope this is useful to someone! I think it will be tremendously useful! Thanks very much again! -Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From source at sharpsteen.net Thu May 12 22:33:27 2011 From: source at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 12 May 2011 13:33:27 -0700 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: <4DCC33D1.2080408@gmail.com> References: <4DCC33D1.2080408@gmail.com> Message-ID: On Thu, May 12, 2011 at 12:24 PM, Stefan L?ffler wrote: > Hi, > > this is looking awesome, thanks! If you agree, I'd like to write something > up (well, actually, copy from you ;)) for the Tw wiki. > > WARNING (for non-developers): The rest of this message is very technical. > > > A few questions: > 1) is it possible to use the upstream svn repo instead of cloning a git > version of it? That would have the benefit that people don't have to > rely/wait on you pulling changes, as long as nothing dramatic changes. > My Git repo was cloned from the offical TeXworks SVN repository, the texworks-svn branch is currently tracking your trunk. If I disappear and someone wants to use my CMake patches on top of the newest version of the SVN repo, the following workflow should do the trick: # Clone the Git repository: git clone git://github.com/Sharpie/TeXworks.git cd TeXworks # Add the TeXworks svn repository, remove the `trunk` part and add --stdlayout if you want to bring in branches and tags from SVN. git svn init http://texworks.googlecode.com/svn/trunk/ # Bring in SVN history (this will take a while) git svn fetch # Checkout the SVN trunk as a git branch git checkout -b texworks-upstream remotes/git-svn # Checkout the CMake branch git checkout cmake-only # Forward-port all changes in cmake-only onto the the SVN trunk: git rebase texworks-upstream # If new changes occur in SVN: git checkout texworks-upstream git svn rebase git checkout cmake-only git rebase texworks-upstream 2) Can you add support for stable releases? They are in /tags in the svn > repo (if the answer to 1) is yes, this is trivial) > Sure, I'll just have to import the tags directory into the Git repository. > 3) I noticed you mention homebrew; can your cmake system be incorporated > into homebrew? > Yes, Homebrew builds quite a few projects that use CMake. However, it does have a policy that frowns on including Applications unless they have a lot of dependencies or are otherwise difficult to obtain. > > On 2011-05-12 07:23, Charlie Sharpsteen wrote: > > If someone wants to play with the build system, the code is available at: > > https://github.com/downloads/Sharpie/TeXworks > > > This didn't work for me. > Gah. Bad copy and paste job, the correct url is: https://github.com/Sharpie/TeXworks > > Direct git access: > > git://github.com/Sharpie/TeXworks.git > > If anyone has any improvements/corrections, feel free to fork the repo > and send a pull request. > > > Done. I wanted to send separate pull requests for different sets of > changes, but didn't succeed (is it possible at all? I have practically no > experience with git/github). > Looks great! I'll pull your changes over, when I get the chance. One thing you may be interested in is that CPack can be set to build Debian packages and RPMs on Linux. To generate separate pull requests, you have to adopt the "branching mindset" that git is famous (infamous?) for. Basically, it works like this: # If there is another upstream repo you want to get updates from get remote add upstream git://github.com/Sharpie/TeXworks.git # Check out the master branch and sync it with "upstream" git checkout master git pull upstream master # If any conflicts happen: git mergetool # Create a new branch for a feature that will start out as a copy of the master branch: git branch feature-x master # Switch to the feature-x branch git checkout feature-x # Hack Hack Hack # Push some feature brances to GitHub git push origin feature-x feature-y Now to open a pull request, go to your project page on GitHub.com, select the desired branch from the "Switch Branches" menu and then hit the "Pull Request" button. The resulting request will only contain commits from the branch you selected. Or, to do it the ol' fashioned way: # Create patchfiles containing all the commits that happened on the feature-x branch relative to your master branch git format-patch master...feature-x # Or a given remote master branch git fetch upstream # Make sure git has an up-to-date picture of the upstream repo git format-patch upstream/master...feature-x Quick 'n dirty Git Reference: http://gitref.org More in-depth: http://progit.org http://gitready.com If the core developers are interested in bringing this new build system > into the SVN repository, the following patch should apply cleanly against > revision 813: > > https://github.com/Sharpie/TeXworks/compare/texworks-svn...cmake-only > > There is only one teenie-tiny change to src/TWApp.h to guard against > D-Bus that affects the existing code code. > > > Bringing the whole CMake system in will need some thinking and discussion, > so please be patient. > No problem, I will try to keep the cmake-only branch limited to changes that concern the build system--i.e. by excluding things like the README swap I did for the GitHub project page. That way a GitHub comparison between texworks-svn and cmake-only should always generate a nice patch if you decide to bring it into the main repo. > Regarding the patch: it seems trivial, but the way I read the Qt docs, > Q_WS_X11 and Q_WS_MAC should be mutually exclusive. See, e.g., main.cpp, > which also uses dbus, but only guards against Q_WS_X11 - why doesn't that > cause problems for you? The only thing I can think of is that your > workaround "ADD_DEFINITIONS( -DQ_WS_MAC )" is not really resolving the issue > (note that there is TwApp.h, but no main.h, to be processed by moc). I could > imagine that QT4_WRAP_CPP actually mistakes the system and defines Q_WS_X11 > _instead of_ DQ_WS_MAC. Can this be overridden by "REMOVE_DEFINITIONS( > -DQ_WS_X11 )"? > All in all, I'd rather have a proper solution if possible rather than > hacking the svn code... > The problem that is occurring for me is that when QT4_WRAP_CPP processes TWApp.h to generate moc_TWApp.cxx, it runs the following command: cd /Users/sharpie/code/TeX/texworks/build/src && /usr/local/Cellar/qt/4.7.3/bin/moc -I/usr/local/Cellar/qt/4.7.3/include -F/usr/local/Cellar/qt/4.7.3/lib -I/usr/local/Cellar/qt/4.7.3/lib/QtScript.framework/Headers -I/usr/local/Cellar/qt/4.7.3/include/QtUiTools -I/usr/local/Cellar/qt/4.7.3/lib/QtScriptTools.framework/Headers -I/usr/local/Cellar/qt/4.7.3/lib/QtGui.framework/Headers -I/usr/local/Cellar/qt/4.7.3/lib/QtXml.framework/Headers -I/usr/local/Cellar/qt/4.7.3/lib/QtCore.framework/Headers -I/Users/sharpie/code/TeX/texworks/src -I/Users/sharpie/code/TeX/texworks/build/src -I/usr/local/include/hunspell -I/usr/local/include/poppler -I/usr/local/Cellar/poppler/0.16.5/include/poppler/qt4 -I/usr/X11R6/include -I/usr/include -DQT_SCRIPT_LIB -DQT_UITOOLS_LIB -DQT_SCRIPTTOOLS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -o /Users/sharpie/code/TeX/texworks/build/src/moc_TWApp.cxx /Users/sharpie/code/TeX/texworks/src/TWApp.h Somehow, that command apparently processes TWApp with Q_WS_X11 defined which causes the D-Bus dependencies to show up. I don't think REMOVE_DEFINITIONS( -DQ_WS_X11 ) would be a solution because CMake is not passing -DQ_WS_X11. It seems likely that one of the Qt header files is setting the definition. I'm by no means an expert on Qt, but it seems likely that Q_WS_X11 could be defined for Mac since X11 is present on my machine. One thing that I may try is running QT4_AUTOMOC on the `*.cpp` files instead of QT4_WRAP_CPP on the headers to see if it makes a difference. Hope this is useful to someone! > > > I think it will be tremendously useful! Thanks very much again! > > -Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Fri May 13 00:00:19 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 12 May 2011 15:00:19 -0700 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: References: <4DCC33D1.2080408@gmail.com> Message-ID: On Thu, May 12, 2011 at 1:33 PM, Charlie Sharpsteen wrote: > No problem, I will try to keep the cmake-only branch limited to changes > that concern the build system--i.e. by excluding things like the README swap > I did for the GitHub project page. That way a GitHub comparison between > texworks-svn and cmake-only should always generate a nice patch if you > decide to bring it into the main repo. > > > >> Regarding the patch: it seems trivial, but the way I read the Qt docs, >> Q_WS_X11 and Q_WS_MAC should be mutually exclusive. See, e.g., main.cpp, >> which also uses dbus, but only guards against Q_WS_X11 - why doesn't that >> cause problems for you? The only thing I can think of is that your >> workaround "ADD_DEFINITIONS( -DQ_WS_MAC )" is not really resolving the issue >> (note that there is TwApp.h, but no main.h, to be processed by moc). I could >> imagine that QT4_WRAP_CPP actually mistakes the system and defines Q_WS_X11 >> _instead of_ DQ_WS_MAC. Can this be overridden by "REMOVE_DEFINITIONS( >> -DQ_WS_X11 )"? >> All in all, I'd rather have a proper solution if possible rather than >> hacking the svn code... >> > > The problem that is occurring for me is that when QT4_WRAP_CPP processes > TWApp.h to generate moc_TWApp.cxx, it runs the following command: > > cd /Users/sharpie/code/TeX/texworks/build/src && > /usr/local/Cellar/qt/4.7.3/bin/moc -I/usr/local/Cellar/qt/4.7.3/include > -F/usr/local/Cellar/qt/4.7.3/lib > -I/usr/local/Cellar/qt/4.7.3/lib/QtScript.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/include/QtUiTools > -I/usr/local/Cellar/qt/4.7.3/lib/QtScriptTools.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/lib/QtGui.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/lib/QtXml.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/lib/QtCore.framework/Headers > -I/Users/sharpie/code/TeX/texworks/src > -I/Users/sharpie/code/TeX/texworks/build/src -I/usr/local/include/hunspell > -I/usr/local/include/poppler > -I/usr/local/Cellar/poppler/0.16.5/include/poppler/qt4 -I/usr/X11R6/include > -I/usr/include -DQT_SCRIPT_LIB -DQT_UITOOLS_LIB -DQT_SCRIPTTOOLS_LIB > -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -o > /Users/sharpie/code/TeX/texworks/build/src/moc_TWApp.cxx > /Users/sharpie/code/TeX/texworks/src/TWApp.h > > Somehow, that command apparently processes TWApp with Q_WS_X11 defined > which causes the D-Bus dependencies to show up. I don't > think REMOVE_DEFINITIONS( -DQ_WS_X11 ) would be a solution because CMake is > not passing -DQ_WS_X11. It seems likely that one of the Qt header files is > setting the definition. I'm by no means an expert on Qt, but it seems > likely that Q_WS_X11 could be defined for Mac since X11 is present on my > machine. > > One thing that I may try is running QT4_AUTOMOC on the `*.cpp` files > instead of QT4_WRAP_CPP on the headers to see if it makes a difference. > Something that just occurred to me after looking at the -D switches CMake passes to moc is that substituting: #ifdef Q_WS_X11 For: #ifdef QT_DBUS_LIB In TWApp.h may work if it doesn't break the qmake build. -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Fri May 13 00:06:55 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 12 May 2011 15:06:55 -0700 Subject: [texworks] matlab from pdflatex/latex Message-ID: > Hi, > Does anyone have sample code to have matlab called from *tex, generate plot data > and have *tex plot this data? > No need to explain write18 issues... > Ovi You might try asking this question on the TeX Stackexchange: http://tex.stachexchange.net I'll bet you'll get a beautifully illustrated answer. -Charlie From chuck at sharpsteen.net Fri May 13 06:35:50 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 12 May 2011 21:35:50 -0700 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: References: Message-ID: Allright, I've managed to make a build of TeXworks.app that passes the poppler-data.pdf test when moved to another system. This requires applying `lib-patches/poppler-qt4-globalparams.patch` to the Poppler source before building it. Homebrew has a neat feature that allows it to install using arbitrary files on the local filesystem. That means I could add a file to the TeXworks source that apackager could use to install Poppler thusly: brew install --with-qt4 --enable-xpdf-headers cmake/packaging/mac/poppler.rb And the patches in `lib-patches` would be applied automatically. However, there is a choice to be made. Applying `poppler-qt4-globalparams.patch` makes pretty minimal changes which means that the custom poppler.rb file is barely different than the poppler.rb shipped with Homebrew. This means that it would be easy to keep a custom version of poppler.rb up to date without much knowledge of the inner working of Homebrew. However, applying `poppler-mac-font-handling.patch` is much more involved. This requires making poppler.rb re-run autoconf, which requires `gettext` to be installed for some m4 macros and some changes to be made to the configure args. This involves some major changes to poppler.rb which increases the maintenance burden involved in keeping it easy to install a custom version of Poppler for build Mac packages. The size difference between TeXworks.app with libfonconfig.dylib and without fontconfig was 1MB. I saw mention that including fontconfig causes unwanted files to show up in user Fonts directories, but I didn't notice any changes to /Library/Fonts or ~/Library/Fonts on my test machine---perhaps this is a side effect of using a fontconfig library other than the one provided by Apple in /usr/X11/lib. So, I guess the question is---how badly do we want to get rid of Fontconfig? Leaving it in is starting to look like the easiest course of action on OS X. -Charlie From paul.a.norman at gmail.com Sat May 14 05:44:12 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sat, 14 May 2011 15:44:12 +1200 Subject: [texworks] SCRIPTING: Designing and Using Form/ Dialogues for Script - Some Notes Message-ID: Hi, I have tried to make some introductory notes for designing and using form/ dialogues for Script - probably only QtScript - JavaScript and not Pyhton and Lua just now(?). "Qt provides a free WYSIWYG User Interface editor called Qt Creator http://qt.nokia.com/products/developer-tools/ that can be used to design forms / dialogues (saved as an xml file with .ui extension) that can be linked to your Qt .js scripts at Script run time. ... " I recommend using the .chm found here - http://twscript.paulanorman.com/docs/index.html After downloading look in menu tree at left for: (red askerisks) Script Authoring / UI Dialogue/Form Scripts. On-line web version - http://twscript.paulanorman.com/docs/html/files/DialogueScripts.html Hopefully help kick start anyone wanting to make useful dialogues to help people! Paul From chuck at sharpsteen.net Sun May 15 03:01:26 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sat, 14 May 2011 18:01:26 -0700 Subject: [texworks] Updated builds of TeXworks for OS X Message-ID: I just rolled up two new TeXworks binaries for Mac OS X: https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-813-33d0430-SLeopard.dmg https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-813-33d0430-Leopard.dmg (**NOTE that none of these links should be considered permanent, I may have to delete builds to conserve disk space on GitHub. Generally I will try to keep the last two builds available.**) The first binary is for OS X 10.6.x and is x86_64 only. The second binary is for OS X 10.5.x -- 10.6.x and contains both ppc and i386 architectures. I don't actually have a PPC-based machine to test on, so if someone who does could try out the Leopard build and let me know if it works that would be awesome! Compared to the first build I did, there are three improvements: - The first build does not contain a proper Info.plist file which means OS X will not recognize it as an editor for `.tex` files. - The new builds contain Poppler font data which helps the PDF viewer to display content such as CJK fonts. - The new builds have full scripting support by including Lua 5.1.4 and linking against the standard OS X Python frameworks (Python 2.6.1 on 10.6.x and Python 2.5.1 on 10.5.x). Current issues with the builds: - If anyone is feeling artistic, it would be nice to come up with a snazzy background image for the Drag N' Drop installer. - I am taking the path of least resistance by including Apple's Fontconfig from /usr/X11/lib. It only adds a MB or so to the distribution---do we really want/need to get rid of it? The process of removing Fontconfig makes it much more difficult to set up an environment for building redistributable packages. This would reduce the number of people who could help with packaging OS X builds. - I noticed that the last official Mac build includes the following Qt plugins: * accessible * codecs * graphicssystems * imageformats * script Currently, my builds don't contain any of these plugins and seem to run fine (given extremely limited testing). Are any of these plugins necessary? Once some of these issues are resolved, we could look into packing up a build of the 0.4.0 stable release. -Charlie From st.loeffler at gmail.com Sun May 15 10:17:23 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 15 May 2011 10:17:23 +0200 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: References: <4DCC33D1.2080408@gmail.com> Message-ID: <4DCF8C13.3090205@gmail.com> Hi, On 2011-05-12 22:33, Charlie Sharpsteen wrote: > On Thu, May 12, 2011 at 12:24 PM, Stefan L?ffler > > wrote: > > > A few questions: > 1) is it possible to use the upstream svn repo instead of cloning > a git version of it? That would have the benefit that people don't > have to rely/wait on you pulling changes, as long as nothing > dramatic changes. > > > My Git repo was cloned from the offical TeXworks SVN repository, the > texworks-svn branch is currently tracking your trunk. If I disappear > and someone wants to use my CMake patches on top of the newest version > of the SVN repo, the following workflow should do the trick: [snip] Thanks for the guide. > 2) Can you add support for stable releases? They are in /tags in the > svn repo (if the answer to 1) is yes, this is trivial) > > Sure, I'll just have to import the tags directory into the Git repository. Great! Maybe you could even do that before all the packaging-related questions are resolved, so people can build their own 0.4 stable release? But then again, there is a new one (0.4.1) coming up soon (hopefully), so maybe there isn't too much sense into building oneselve an 0.4.0 now... > > 3) I noticed you mention homebrew; can your cmake system be > incorporated into homebrew? > > > Yes, Homebrew builds quite a few projects that use CMake. However, it > does have a policy that frowns on including Applications unless they > have a lot of dependencies or are otherwise difficult to obtain. OK, no problem. The build instructions as they are seem simple enough (for a programmers eye, anyway ;)), and they wouldn't get that much easier with a homebrew formula. >> Direct git access: >> >> git://github.com/Sharpie/TeXworks.git >> >> >> If anyone has any improvements/corrections, feel free to fork the >> repo and send a pull request. > > Done. I wanted to send separate pull requests for different sets > of changes, but didn't succeed (is it possible at all? I have > practically no experience with git/github). > > > Looks great! I'll pull your changes over, when I get the chance. One > thing you may be interested in is that CPack can be set to build > Debian packages and RPMs on Linux. Yeah, so I heard. Anyway, for the time, the script I wrote for producing Debian packages is working well, and actually only has to prepare source packages as the binaries are built online at Launchpad. But maybe others like to have a stab at this. BTW: I tested your CMake build environment, and it seems to work without problems on Ubuntu (I'm not sure what the exact dependencies are, as I already had them installed, but I'd assume those posted on GC + cmake, git should pretty much do the trick). In case you want to update that warning message. > To generate separate pull requests, you have to adopt the "branching > mindset" that git is famous (infamous?) for. Basically, it works like > this: Yeah, I've heard about that branching policy. Personally, I don't like creating dozens of branches with one or two lines changed in each, but then again I haven't been doing much with git thus far. > Regarding the patch: it seems trivial, but the way I read the Qt > docs, Q_WS_X11 and Q_WS_MAC should be mutually exclusive. See, > e.g., main.cpp, which also uses dbus, but only guards against > Q_WS_X11 - why doesn't that cause problems for you? The only thing > I can think of is that your workaround "ADD_DEFINITIONS( > -DQ_WS_MAC )" is not really resolving the issue (note that there > is TwApp.h, but no main.h, to be processed by moc). I could > imagine that QT4_WRAP_CPP actually mistakes the system and defines > Q_WS_X11 _instead of_ DQ_WS_MAC. Can this be overridden by > "REMOVE_DEFINITIONS( -DQ_WS_X11 )"? > All in all, I'd rather have a proper solution if possible rather > than hacking the svn code... > > > The problem that is occurring for me is that when QT4_WRAP_CPP > processes TWApp.h to generate moc_TWApp.cxx, it runs the following > command: > > cd /Users/sharpie/code/TeX/texworks/build/src && > /usr/local/Cellar/qt/4.7.3/bin/moc > -I/usr/local/Cellar/qt/4.7.3/include -F/usr/local/Cellar/qt/4.7.3/lib > -I/usr/local/Cellar/qt/4.7.3/lib/QtScript.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/include/QtUiTools > -I/usr/local/Cellar/qt/4.7.3/lib/QtScriptTools.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/lib/QtGui.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/lib/QtXml.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/lib/QtCore.framework/Headers > -I/Users/sharpie/code/TeX/texworks/src > -I/Users/sharpie/code/TeX/texworks/build/src > -I/usr/local/include/hunspell -I/usr/local/include/poppler > -I/usr/local/Cellar/poppler/0.16.5/include/poppler/qt4 > -I/usr/X11R6/include -I/usr/include -DQT_SCRIPT_LIB -DQT_UITOOLS_LIB > -DQT_SCRIPTTOOLS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -o > /Users/sharpie/code/TeX/texworks/build/src/moc_TWApp.cxx > /Users/sharpie/code/TeX/texworks/src/TWApp.h > > Somehow, that command apparently processes TWApp with Q_WS_X11 defined > which causes the D-Bus dependencies to show up. I don't > think REMOVE_DEFINITIONS( -DQ_WS_X11 ) would be a solution because > CMake is not passing -DQ_WS_X11. It seems likely that one of the Qt > header files is setting the definition. I'm by no means an expert on > Qt, but it seems likely that Q_WS_X11 could be defined for Mac since > X11 is present on my machine. I just noticed that during the initial configuration (`cmake ..` in a clean directory), CMake prints out which of those Q_WS_* are defined. What does that say for you? In addition, does the file build/src/moc_TWApp.cxx contain any reference to dbus? For me on Linux (with dbus), it contains no #include's or anything, only some type names and function calls related to TWAdaptor. And finally, you can easily check the compile-time settings by simply adding some lines like #ifdef Q_WS_X11 #warning Q_WS_X11 #endif #ifdef Q_WS_MAC #warning Q_WS_MAC #endif in some prominent location (e.g., the TWApp.h) and recompile. On 2011-05-13 00:00, Charlie Sharpsteen wrote: > > Something that just occurred to me after looking at the -D switches > CMake passes to moc is that substituting: > > #ifdef Q_WS_X11 > > For: > > #ifdef QT_DBUS_LIB > > In TWApp.h may work if it doesn't break the qmake build. Excellent point. I did just that in r817. I didn't find any mentioning of QT_DBUS_LIB in the documentation, yet, but it appears to be set on Linux and to not be set on Windows. From Qt 4.4 upwards, anyway (for 4.3, it's not set, but then again I don't think many people use that anymore; besides, it's easy to #def when invoking qmake). Cheers, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From joseph.wright at morningstar2.co.uk Sun May 15 11:01:35 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Sun, 15 May 2011 10:01:35 +0100 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: References: Message-ID: <4DCF966F.70509@morningstar2.co.uk> On 15/05/2011 02:01, Charlie Sharpsteen wrote: > I just rolled up two new TeXworks binaries for Mac OS X: > > https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-813-33d0430-SLeopard.dmg > https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-813-33d0430-Leopard.dmg I've grabbed the Snow Leopard build, and in the main it looks good so far. One oddity. On the TeXworks menu, in place of 'About TeXworks' I have 'Settings and Resources'. There seems to be one of these for each open file, which could get a bit messy! -- Joseph Wright From henrikmidtiby at gmail.com Sun May 15 11:26:09 2011 From: henrikmidtiby at gmail.com (Henrik Skov Midtiby) Date: Sun, 15 May 2011 11:26:09 +0200 Subject: [texworks] SCRIPTING: Get content of specified directory Message-ID: Hi >From at script would I like to get access to the contents of the current directory. This information should be used for autocompleting filenames for includegraphics and input macros in latex. I know it is possible to access the commandline and issue an 'ls -all' or something similar, but is this information also available directly in QtScript? Best regards, Henrik Skov Midtiby From joseph.wright at morningstar2.co.uk Sun May 15 12:01:07 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Sun, 15 May 2011 11:01:07 +0100 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: References: Message-ID: <4DCFA463.9040608@morningstar2.co.uk> On 15/05/2011 02:01, Charlie Sharpsteen wrote: > - The first build does not contain a proper Info.plist file which > means OS X will not recognize it as an editor for `.tex` files. Would it be sensible to add at least some of the other file types to the list? For example, .ltx is used by some people for LaTeX files, and for developers like me .dtx would be nice :-) (I guess this can be done 'by hand', but I know that on Windows TeXworks will be associated with a number of file types, for example .cls) -- Joseph Wright From paul.a.norman at gmail.com Sun May 15 12:22:00 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sun, 15 May 2011 22:22:00 +1200 Subject: [texworks] SCRIPTING: Get content of specified directory In-Reply-To: References: Message-ID: Dear Henrik, Not so far as far as I know. As you have, I've been using system calls to things like "cmd /c mkdir \""+ documentPath +"images\"" Can switch case on http://twscript.paulanorman.com/docs/html/files/platform.html and prepare differnt statements for the TW.system call. http://twscript.paulanorman.com/docs/html/files/systemQString.html (see subheadngs in and under main headings "User 'Library' Modules and helper objects" at http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm for some explanation on twPan - recomend downloading from http://twscript.paulanorman.com/docs/index.html and the .chm there.) and have been using things like ... function chooseFromDirectoryListing(Description, pathDir, fileExtension) { // pathDir (no trailing slash), fileExtension with . E.g. .txt // TW.app.clipboard = "cmd /c dir /b \"" + pathDir + "\\*" + fileExtension + "\""; var fileList = twPan.osCmd("cmd /c dir /b \"" + pathDir + "\\*" + fileExtension + "\"" , true) removeExtnsn = new RegExp(fileExtension,"ig"); fileList = fileList.replace(removeExtnsn,"").split(lineBreak); // var chosenAnswer = // twPan.select(Description, fileList); var chosenAnswer = TW.getItem(null, Description, Description, fileList); if (twPan.emptyString(chosenAnswer) == false) { chosenAnswer = chosenAnswer + fileExtension; } return chosenAnswer; } You can use http://twscript.paulanorman.com/docs/html/files/getOpenFileNames.html See also notes in http://twscript.paulanorman.com/docs/html/files/getOpenFileNameQString.html Can get one or multi-select more file names though returns an array in that case, requires User interaction though. Paul On 15 May 2011 21:26, Henrik Skov Midtiby wrote: > Hi > > >From at script would I like to get access to the contents of the > current directory. > This information should be used for autocompleting filenames for > includegraphics and input macros in latex. > > I know it is possible to access the commandline and issue an 'ls -all' > or something similar, but is this information also available directly > in QtScript? > > Best regards, > Henrik Skov Midtiby > From st.loeffler at gmail.com Sun May 15 14:10:24 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 15 May 2011 14:10:24 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig (was: Another TeXworks mac build (with a buildsystem!)) In-Reply-To: References: Message-ID: <4DCFC2B0.4020905@gmail.com> Hi, On 2011-05-13 06:35, Charlie Sharpsteen wrote: > I could add a file to the TeXworks source that apackager could use to > install Poppler thusly: > > brew install --with-qt4 --enable-xpdf-headers cmake/packaging/mac/poppler.rb > > And the patches in `lib-patches` would be applied automatically. Sounds good to me. It's really just the poppler-qt4-globalparams.patch, as poppler-win32-font-handling.patch only applies to Windows-specific files. > So, I guess the question is---how badly do we want to get rid of > Fontconfig? Leaving it in is starting to look like the easiest course > of action on OS X. This is up to Jonathan Kew to decide (I explicitly CC'ed him to this mail, hopefully he'll reply), as he set up the original "no-fontconfig" policy. Not being a Mac developer or user myself, I can only abide by the judgment of those who must live with the consequences (whatever they may be). Regards, Stefan From st.loeffler at gmail.com Sun May 15 14:22:51 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 15 May 2011 14:22:51 +0200 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: References: Message-ID: <4DCFC59B.6090501@gmail.com> On 2011-05-15 03:01, Charlie Sharpsteen wrote: > I just rolled up two new TeXworks binaries for Mac OS X: > > The first binary is for OS X 10.6.x and is x86_64 only. The second > binary is for OS X 10.5.x -- 10.6.x and contains both ppc and i386 > architectures. I don't actually have a PPC-based machine to test on, > so if someone who does could try out the Leopard build and let me know > if it works that would be awesome! Wow, this is awesome, thanks! How did you manage universal builds (I'm asking primarily out of curiosity, as this has been a topic of some discussion in the past, and not being a Mac user myself I couldn't make heads or tails of (some of) the posts. > Compared to the first build I did, there are three improvements: > > - The first build does not contain a proper Info.plist file which > means OS X will not recognize it as an editor for `.tex` files. Can you (or someone else) check if this also resolved the problem reported in comment #3 at http://code.google.com/p/texworks/issues/detail?id=494#c3, please (i.e., the menu entry "About TeXworks..." in the Apple menu read only "About...")? I think it might, but it would be nice to have some confirmation. > Current issues with the builds: > > - If anyone is feeling artistic, it would be nice to come up with a > snazzy background image for the Drag N' Drop installer. I'm not feeling particularly artistic, but what kind of image are we talking about? Is there a webpage with some screenshots, maybe? > - I noticed that the last official Mac build includes the following > Qt plugins: > > * accessible > * codecs > * graphicssystems > * imageformats > * script > > Currently, my builds don't contain any of these plugins and seem > to run fine (given extremely limited testing). Are any of these > plugins necessary? This may have been related to the Qt version, the flags used to build it, and/or deployment system used. From the looks of it, I would suggest the following methods of testing: 1) Do scripts (in particular QtScript scripts, e.g. the normal .js files) work? If so, the "script" plugin is probably included already. 2) Do you have an exhaustive list of codecs when you click on the second status bar widget from the right in the editor window? If so, "codecs" are probably taken care of. 2) Do pdfs with embedded .png or .jpg files display correctly? 3) Can you drag&drop image files (e.g., .png or .jpg) into the editor and they get converted to \includegraphics{...} commands automatically? If 2 and 3 work, then "imageformats" (and perhaps "graphicssystems") are taken care of. HTH Stefan From st.loeffler at gmail.com Sun May 15 14:33:07 2011 From: st.loeffler at gmail.com (=?ISO-8859-15?Q?Stefan_L=F6ffler?=) Date: Sun, 15 May 2011 14:33:07 +0200 Subject: [texworks] Building TeXworks for the Mac yourself Message-ID: <4DCFC803.9000401@gmail.com> Hi, thanks to Charlie Sharpsteen, there are some Mac builds of the latest version of TeXworks ready for download (see his posts to this list). In addition, he kindly shared his build system. While using ready-made builds is convenient for many "normal" users, it has a few drawbacks. First, you have to download and install a complete new package every time some minor things in TeXworks are changed. And second, you can't help develop and improve TeXworks' code, not as much as you could when compiling it yourself, anyway ;). (Of course, providing bug reports, feature requests, etc. is always very welcome; without anyone testing possible changes, however, even before they are committed, leaves developers like me without a Mac searching for the proverbial needle in a haystack). Anyway, with Charlie's build system for the Mac in place, you almost good to go for building TeXworks yourself - if you want. I've uploaded a guide derived from the original readme file at http://code.google.com/p/texworks/wiki/BuildingOnMacOSXHomebrew. AFAIK, however, it was not tested on a clean (meaning: no development files installed) system, yet. So, if you're willing to try, please take a look at it, and report anything (be at a successful compilation, a problem, a suggestion, or whatever else) you experience here so we can improve this guide and others can follow in your footsteps in the future. Regards, Stefan From joseph.wright at morningstar2.co.uk Sun May 15 14:46:56 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Sun, 15 May 2011 13:46:56 +0100 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: <4DCFC59B.6090501@gmail.com> References: <4DCFC59B.6090501@gmail.com> Message-ID: <4DCFCB40.4080003@morningstar2.co.uk> On 15/05/2011 13:22, Stefan L?ffler wrote: >> - The first build does not contain a proper Info.plist file which >> means OS X will not recognize it as an editor for `.tex` files. > > Can you (or someone else) check if this also resolved the problem > reported in comment #3 at > http://code.google.com/p/texworks/issues/detail?id=494#c3, please (i.e., > the menu entry "About TeXworks..." in the Apple menu read only > "About...")? I think it might, but it would be nice to have some > confirmation. I do see 'About', but as I said in another mail also get one 'Settings and Resources ..' after it per file opened: see the attached. -- Joseph Wright -------------- next part -------------- A non-text attachment was scrubbed... Name: About.png Type: image/png Size: 105963 bytes Desc: not available URL: From schuster.wolfgang at googlemail.com Sun May 15 14:48:05 2011 From: schuster.wolfgang at googlemail.com (Wolfgang Schuster) Date: Sun, 15 May 2011 14:48:05 +0200 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: <4DCFC59B.6090501@gmail.com> References: <4DCFC59B.6090501@gmail.com> Message-ID: <7727C01B-3F5D-470E-8987-A23A7AD2ED56@googlemail.com> Am 15.05.2011 um 14:22 schrieb Stefan L?ffler: >> Current issues with the builds: >> >> - If anyone is feeling artistic, it would be nice to come up with a >> snazzy background image for the Drag N' Drop installer. > > I'm not feeling particularly artistic, but what kind of image are we > talking about? Is there a webpage with some screenshots, maybe? The first image shows how TeXworks currently looks and from the second image from Firefox installer you can see what he wants. TeXworks : http://d.pr/TL6l Firefox : http://d.pr/Oz5A Wolfgang From joseph.wright at morningstar2.co.uk Sun May 15 14:48:40 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Sun, 15 May 2011 13:48:40 +0100 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DCFC2B0.4020905@gmail.com> References: <4DCFC2B0.4020905@gmail.com> Message-ID: <4DCFCBA8.2070506@morningstar2.co.uk> On 15/05/2011 13:10, Stefan L?ffler wrote: >> So, I guess the question is---how badly do we want to get rid of >> Fontconfig? Leaving it in is starting to look like the easiest course >> of action on OS X. > > This is up to Jonathan Kew to decide (I explicitly CC'ed him to this > mail, hopefully he'll reply), as he set up the original "no-fontconfig" > policy. Not being a Mac developer or user myself, I can only abide by > the judgment of those who must live with the consequences (whatever they > may be). Wassn't the point here that TeXworks is a 'native' application, both on Windows and on the Mac, and they both have their own font systems. (BTW, I don't see JK on the CC list.) -- Joseph Wright From joseph.wright at morningstar2.co.uk Sun May 15 14:56:18 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Sun, 15 May 2011 13:56:18 +0100 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: <4DCFCB40.4080003@morningstar2.co.uk> References: <4DCFC59B.6090501@gmail.com> <4DCFCB40.4080003@morningstar2.co.uk> Message-ID: <4DCFCD72.6080407@morningstar2.co.uk> On 15/05/2011 13:46, Joseph Wright wrote: > On 15/05/2011 13:22, Stefan L?ffler wrote: >>> - The first build does not contain a proper Info.plist file which >>> means OS X will not recognize it as an editor for `.tex` files. >> >> Can you (or someone else) check if this also resolved the problem >> reported in comment #3 at >> http://code.google.com/p/texworks/issues/detail?id=494#c3, please (i.e., >> the menu entry "About TeXworks..." in the Apple menu read only >> "About...")? I think it might, but it would be nice to have some >> confirmation. > > I do see 'About', but as I said in another mail also get one 'Settings > and Resources ..' after it per file opened: see the attached. Then again, if I close all of my documents and then reopen some, the 'About' entry vanishes, and I get an extra 'Settings and Resources ...' in its place. -- Joseph Wright From st.loeffler at gmail.com Sun May 15 16:04:22 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 15 May 2011 16:04:22 +0200 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: <4DCFCD72.6080407@morningstar2.co.uk> References: <4DCFC59B.6090501@gmail.com> <4DCFCB40.4080003@morningstar2.co.uk> <4DCFCD72.6080407@morningstar2.co.uk> Message-ID: <4DCFDD66.9050505@gmail.com> Hi, On 2011-05-15 14:56, Joseph Wright wrote: > On 15/05/2011 13:46, Joseph Wright wrote: >> On 15/05/2011 13:22, Stefan L?ffler wrote: >>>> - The first build does not contain a proper Info.plist file which >>>> means OS X will not recognize it as an editor for `.tex` files. >>> Can you (or someone else) check if this also resolved the problem >>> reported in comment #3 at >>> http://code.google.com/p/texworks/issues/detail?id=494#c3, please (i.e., >>> the menu entry "About TeXworks..." in the Apple menu read only >>> "About...")? I think it might, but it would be nice to have some >>> confirmation. >> I do see 'About', but as I said in another mail also get one 'Settings >> and Resources ..' after it per file opened: see the attached. > Then again, if I close all of my documents and then reopen some, the > 'About' entry vanishes, and I get an extra 'Settings and Resources ...' > in its place. The "Settings and Resources..." problem is hopefully fixed with r818. Re. the vanishing of "About", this has been reported at http://code.google.com/p/texworks/issues/detail?id=494, and I believe it is actually a Qt issue (see http://bugreports.qt.nokia.com/browse/QTBUG-17941). We'll see if it will be fixed soon (probably not) or if one of the workaround is applicable to the Tw code. HTH Stefan From chuck at sharpsteen.net Mon May 16 01:10:36 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sun, 15 May 2011 16:10:36 -0700 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: <4DCF8C13.3090205@gmail.com> References: <4DCC33D1.2080408@gmail.com> <4DCF8C13.3090205@gmail.com> Message-ID: On Sun, May 15, 2011 at 1:17 AM, Stefan L?ffler wrote: > Hi, > > On 2011-05-12 22:33, Charlie Sharpsteen wrote: > > On Thu, May 12, 2011 at 12:24 PM, Stefan L?ffler > wrote: >> >> A few questions: >> 1) is it possible to use the upstream svn repo instead of cloning a git >> version of it? That would have the benefit that people don't have to >> rely/wait on you pulling changes, as long as nothing dramatic changes. > > My Git repo was cloned from the offical TeXworks SVN repository, the > texworks-svn branch is currently tracking your trunk. ?If I disappear and > someone wants to use my CMake patches on top of the newest version of the > SVN repo, the following workflow should do the trick: > > [snip] > > Thanks for the guide. > > 2) Can you add support for stable releases? They are in /tags in the svn > repo (if the answer to 1) is yes, this is trivial) > > Sure, I'll just have to import the tags directory into the Git repository. > > Great! Maybe you could even do that before all the packaging-related > questions are resolved, so people can build their own 0.4 stable release? > But then again, there is a new one (0.4.1) coming up soon (hopefully), so > maybe there isn't too much sense into building oneselve an 0.4.0 now... There is one dilemma that I did not forsee as this is the first time I have published a repository that was cloned using git-svn. The problem is that when I started this project, I was only interested in the TeXworks trunk, so I only cloned the trunk: git svn clone http://texworks.googlecode.com/svn/trunk/ If I now clone the rest of the SVN tree from: http://texworks.googlecode.com/svn Git sees it as a completely separate repository since there is a different "root path". So, what I have published on GitHub is not a suitable mirror of the SVN repository for someone who is interested in working with branches or tags. There are two choices: 1. Use `git rebase` to graft the release-0.4.0 tag onto my clone of the trunk. This will create a Git branch that people can pull and build from, but the result will still be unsatisfactory for anyone looking for a true mirror of the SVN repo. 2. Re-clone the SVN repo using `svn` as the root path instead of `svn/trunk`---this will create a full mirror. Then I would move my master branch over to this new clone. The problem with this choice is that anyone who has already cloned my git repository would have to deal with an "upstream rebase" (this means the history of a repository you pulled from got re-written). This means that they have to stash any changes that I haven't accepted in a pull request and then re-synch with my master branch: # Save a copy of your current master branch git checkout master git branch old-master # Re-synch your master branch with the rebased remote branch git remote add sharpie://github.com/Sharpie/TeXworks.git # If you don't already have my repository as a remote git fetch sharpie git reset --hard sharpie/master # Pull over any commits you made that weren't in my branch git log --oneline old-master # To browse the change log for commits git cherry-pick # Repeat for each commit that needs to be copied git branch -D old-master # Remove old master branch Which is a bit of an ugly operation, but one that will only have to be done once. >> Regarding the patch: it seems trivial, but the way I read the Qt docs, >> Q_WS_X11 and Q_WS_MAC should be mutually exclusive. See, e.g., main.cpp, >> which also uses dbus, but only guards against Q_WS_X11 - why doesn't that >> cause problems for you? The only thing I can think of is that your >> workaround "ADD_DEFINITIONS( -DQ_WS_MAC )" is not really resolving the issue >> (note that there is TwApp.h, but no main.h, to be processed by moc). I could >> imagine that QT4_WRAP_CPP actually mistakes the system and defines Q_WS_X11 >> _instead of_ DQ_WS_MAC. Can this be overridden by "REMOVE_DEFINITIONS( >> -DQ_WS_X11 )"? >> All in all, I'd rather have a proper solution if possible rather than >> hacking the svn code... > > The problem that is?occurring?for me is that when QT4_WRAP_CPP processes > TWApp.h to generate?moc_TWApp.cxx, it runs the following command: > cd /Users/sharpie/code/TeX/texworks/build/src && > /usr/local/Cellar/qt/4.7.3/bin/moc -I/usr/local/Cellar/qt/4.7.3/include > -F/usr/local/Cellar/qt/4.7.3/lib > -I/usr/local/Cellar/qt/4.7.3/lib/QtScript.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/include/QtUiTools > -I/usr/local/Cellar/qt/4.7.3/lib/QtScriptTools.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/lib/QtGui.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/lib/QtXml.framework/Headers > -I/usr/local/Cellar/qt/4.7.3/lib/QtCore.framework/Headers > -I/Users/sharpie/code/TeX/texworks/src > -I/Users/sharpie/code/TeX/texworks/build/src -I/usr/local/include/hunspell > -I/usr/local/include/poppler > -I/usr/local/Cellar/poppler/0.16.5/include/poppler/qt4 -I/usr/X11R6/include > -I/usr/include -DQT_SCRIPT_LIB -DQT_UITOOLS_LIB -DQT_SCRIPTTOOLS_LIB > -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB?-o > /Users/sharpie/code/TeX/texworks/build/src/moc_TWApp.cxx > /Users/sharpie/code/TeX/texworks/src/TWApp.h > > Somehow, that command?apparently?processes TWApp with Q_WS_X11 defined which > causes the D-Bus dependencies to show up. ?I don't think?REMOVE_DEFINITIONS( > -DQ_WS_X11 ) would be a solution because CMake is not passing -DQ_WS_X11. It > seems likely that one of the Qt header files is setting the definition. ?I'm > by no means an expert on Qt, but it seems likely that Q_WS_X11 could be > defined for Mac since X11 is present on my machine. > > I just noticed that during the initial configuration (`cmake ..` in a clean > directory), CMake prints out which of those Q_WS_* are defined. What does > that say for you? CMake says that Q_WS_X11 is not found. But still, moc processes TWApp.h in such a way that moc_TWApp.cxx contains the section protected by Q_WS_X11. When the app is compiled, Q_WS_X11 is not defined and so the compiler throws an error. Very strange behavior. > In addition, does the file build/src/moc_TWApp.cxx contain any reference to > dbus? For me on Linux (with dbus), it contains no #include's or anything, > only some type names and function calls related to TWAdaptor. > And finally, you can easily check the compile-time settings by simply adding > some lines like > #ifdef Q_WS_X11 > ??? #warning Q_WS_X11 > #endif > #ifdef Q_WS_MAC > ??? #warning Q_WS_MAC > #endif > > in some prominent location (e.g., the TWApp.h) and recompile. > > > On 2011-05-13 00:00, Charlie Sharpsteen wrote: > > Something that just?occurred?to me after looking at the -D switches CMake > passes to moc is that substituting: > ? ? #ifdef Q_WS_X11 > For: > ? ? #ifdef QT_DBUS_LIB > In TWApp.h may work if it doesn't break the qmake build. > > Excellent point. I did just that in r817. I didn't find any mentioning of > QT_DBUS_LIB in the documentation, yet, but it appears to be set on Linux and > to not be set on Windows. From Qt 4.4 upwards, anyway (for 4.3, it's not > set, but then again I don't think many people use that anymore; besides, > it's easy to #def when invoking qmake). This works with CMake as well and seems to be the cleanest resolution to the problem---I removed my change to TWApp.h. The total patch against TeXworks SVN trunk: https://github.com/Sharpie/TeXworks/compare/texworks-svn...cmake-only No longer affects any existing TeXworks code. > Cheers, > Stefan > -Charlie From chuck at sharpsteen.net Mon May 16 01:30:53 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sun, 15 May 2011 16:30:53 -0700 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: <4DCFA463.9040608@morningstar2.co.uk> References: <4DCFA463.9040608@morningstar2.co.uk> Message-ID: On Sun, May 15, 2011 at 3:01 AM, Joseph Wright wrote: > On 15/05/2011 02:01, Charlie Sharpsteen wrote: >> ? - The first build does not contain a proper Info.plist file which >> means OS X will not recognize it as an editor for `.tex` files. > > Would it be sensible to add at least some of the other file types to the > list? For example, .ltx is used by some people for LaTeX files, and for > developers like me .dtx would be nice :-) > > (I guess this can be done 'by hand', but I know that on Windows TeXworks > will be associated with a number of file types, for example .cls) Currently it looks like TeXworks only associates its self with .tex, .ltx and .pdf on OS X. The relevant file in the TeXworks source is TeXworks.plist.in, under the XML section starting with "CFBundleDocumentTypes". I agree that this list should be expanded. However I am reluctant to modify this file myself as I am trying to keep changes to existing files in my fork to a minimum. This policy ensures an easy merge of my work back into SVN if/when the time comes. Perhaps it would be more appropriate to address this issue by submitting a patch directly to the main TeXworks repo? The changes would propagate downstream into my builds. -Charlie > -- > Joseph Wright > From chuck at sharpsteen.net Mon May 16 02:12:03 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sun, 15 May 2011 17:12:03 -0700 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: <4DCFC59B.6090501@gmail.com> References: <4DCFC59B.6090501@gmail.com> Message-ID: On Sun, May 15, 2011 at 5:22 AM, Stefan L?ffler wrote: > On 2011-05-15 03:01, Charlie Sharpsteen wrote: >> I just rolled up two new TeXworks binaries for Mac OS X: >> >> The first binary is for OS X 10.6.x and is x86_64 only. The second >> binary is for OS X 10.5.x -- 10.6.x and contains both ppc and i386 >> architectures. ?I don't actually have a PPC-based machine to test on, >> so if someone who does could try out the Leopard build and let me know >> if it works that would be awesome! > > Wow, this is awesome, thanks! How did you manage universal builds (I'm > asking primarily out of curiosity, as this has been a topic of some > discussion in the past, and not being a Mac user myself I couldn't make > heads or tails of (some of) the posts. The easy part is that CMake takes care of creating universal builds of TeXworks as you can define the variable CMAKE_OSX_ARCHITECTURES as a semicolon-delimited list at configure-time. For example, to set up a build that would produce a three-way universal binary: cmake .. -DCMAKE_OSX_ARCHITECTURES="ppc;i386;x86_64" The hard part is ensuring that the TeXworks dependencies (Qt, Hunspell and Poppler) are available as universal binaries for each architecture you desire. There are basically two ways to achieve this: 1. The easy way: Configure the dependencies with CFLAGS set to include multiple `-arch` flags. i.e: `CFLAGS="-arch ppc -arch i386 -arch x86_64"`. Also, if building a project that configures using GNU autotools, pass `--disable-dependency-tracking` to `configure` so that GCC isn't set up to compile with `-E`, `-S`, `-M`or `-save-temps` flags which are incompatible with using multiple arch flags. You will need to build using the GCC compilers provided by Apple in XCode as GNU GCC does not understand how to handle multiple arch flags. 2. The hard way (some configure scripts just can't be convinced to set method 1 up right): Configure the dependency for one architecture---then build and istall it to a temporary location. Repeat for each architecture you need. Combine the resulting single-architecture binaries into a universal binary using the `lipo` tool. This is tedious and messy, but from what I understand this is what Apple's GCC does "under the hood" when it gets passed multiple arch flags. Luckily, the TeXworks dependencies build into universal binaries just fine using method #1. Qt has special configure flags that handle universal binary creation. Thank yourselves for having such a short dependency list as it makes this whole operation much easier. I may look into adding custom Homebrew formulae for `qt.rb` and `hunspell.rb` alongside `poppler.rb` that take care of building universal binaries. >> Compared to the first build I did, there are three improvements: >> >> ? - The first build does not contain a proper Info.plist file which >> means OS X will not recognize it as an editor for `.tex` files. > > Can you (or someone else) check if this also resolved the problem > reported in comment #3 at > http://code.google.com/p/texworks/issues/detail?id=494#c3, please (i.e., > the menu entry "About TeXworks..." in the Apple menu read only > "About...")? I think it might, but it would be nice to have some > confirmation. It looks like creating a proper Info.plist solved the problem with having "About" instead of "About TeXworks" in the Apple menu. Revision 818 seems to solve the problem with multiple "Settings and Resources" entries. The "About TeXworks" entry is still disappearing if all windows are closed. >> Current issues with the builds: >> >> ? - If anyone is feeling artistic, it would be nice to come up with a >> snazzy background image for the Drag N' Drop installer. > > I'm not feeling particularly artistic, but what kind of image are we > talking about? Is there a webpage with some screenshots, maybe? Wolfgang Schuster provided an excellent example of the desired effect. It looks like we will need: 1. A PNG file that contains the background image. 2. A DS_Store file that tells OS X how to position the directory contents and points to the PNG file as a background image. If someone comes up with a nice background, I could probably create the DS_Store file. >> ? - I noticed that the last official Mac build includes the following >> Qt plugins: >> >> ? ? * accessible >> ? ? * codecs >> ? ? * graphicssystems >> ? ? * imageformats >> ? ? * script >> >> ? ? Currently, my builds don't contain any of these plugins and seem >> to run fine (given extremely limited testing). Are any of these >> plugins necessary? > > This may have been related to the Qt version, the flags used to build > it, and/or deployment system used. From the looks of it, I would suggest > the following methods of testing: > 1) Do scripts (in particular QtScript scripts, e.g. the normal .js > files) work? If so, the "script" plugin is probably included already. QtScript scripts look like they are working. If anyone notices that they aren't, let me know! > 2) Do you have an exhaustive list of codecs when you click on the second > status bar widget from the right in the editor window? If so, "codecs" > are probably taken care of. I get a pretty long list, so this may "work on my machine" at least. I do need to spend some time validating that the codecs can actually be used. > 2) Do pdfs with embedded .png or .jpg files display correctly? > 3) Can you drag&drop image files (e.g., .png or .jpg) into the editor > and they get converted to \includegraphics{...} commands automatically? > > If 2 and 3 work, then "imageformats" (and perhaps "graphicssystems") are > taken care of. All images seem to display correctly. Drag and drop of PNG files works. However, JPEG drag and drop causes TeXworks to open the JPEG file for editing instead of inserting \includgraphics{...}. So it looks like I may need to add some of the graphics plugins. -Charlie > HTH > Stefan > From lomov.vl at gmail.com Mon May 16 04:33:01 2011 From: lomov.vl at gmail.com (Vladimir Lomov) Date: Mon, 16 May 2011 11:33:01 +0900 Subject: [texworks] Updated Russian translation Message-ID: <20110516023301.GB9245@smoon> Good day. I checked last rev. from svn and found that some strings were untranslated. I send updated TS file. (I generated TS file using lupdate and work with it in linguist so now I'm sure that all strings are translated). --- WBR, Vladimir Lomov -- To avoid criticism, do nothing, say nothing, be nothing. -- Elbert Hubbard -------------- next part -------------- A non-text attachment was scrubbed... Name: TeXworks_ru.ts.bz2 Type: application/octet-stream Size: 10864 bytes Desc: not available URL: From joseph.wright at morningstar2.co.uk Mon May 16 08:06:13 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Mon, 16 May 2011 07:06:13 +0100 Subject: [texworks] Building TeXworks for the Mac yourself In-Reply-To: <4DCFC803.9000401@gmail.com> References: <4DCFC803.9000401@gmail.com> Message-ID: <4DD0BED5.2080902@morningstar2.co.uk> On 15/05/2011 13:33, Stefan L?ffler wrote: > Anyway, with Charlie's build system for the Mac in place, you almost > good to go for building TeXworks yourself - if you want. I've uploaded a > guide derived from the original readme file at > http://code.google.com/p/texworks/wiki/BuildingOnMacOSXHomebrew. AFAIK, > however, it was not tested on a clean (meaning: no development files > installed) system, yet. So, if you're willing to try, please take a look > at it, and report anything (be at a successful compilation, a problem, a > suggestion, or whatever else) you experience here so we can improve this > guide and others can follow in your footsteps in the future. After a few false starts to strip out some material from earlier attempts, I seem to have got this working. The only notes I'd add are that (1) Xcode 3 is on the second DVD that came with my Mac, so I avoided downloading it. (Install the 'Developer Tools' or something like that.) (2) Building Qt tool over 2 hours even after it was downloaded, and the download was also pretty long. So pick a time when you can leave that particular step running. (P.S. The extra menu item does seem to have gone - thanks) -- Joseph Wright From joseph.wright at morningstar2.co.uk Mon May 16 08:11:09 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Mon, 16 May 2011 07:11:09 +0100 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: References: <4DCFA463.9040608@morningstar2.co.uk> Message-ID: <4DD0BFFD.8090402@morningstar2.co.uk> On 16/05/2011 00:30, Charlie Sharpsteen wrote: > Currently it looks like TeXworks only associates its self with .tex, > .ltx and .pdf on OS X. The relevant file in the TeXworks source is > TeXworks.plist.in, under the XML section starting with > "CFBundleDocumentTypes". > > I agree that this list should be expanded. However I am reluctant to > modify this file myself as I am trying to keep changes to existing > files in my fork to a minimum. This policy ensures an easy merge of my > work back into SVN if/when the time comes. > > Perhaps it would be more appropriate to address this issue by > submitting a patch directly to the main TeXworks repo? The changes > would propagate downstream into my builds. Of course, I was thinking about the main TeXworks codebase. I will take a look at this if I get a chance: I'd hope that there is not too much 'code' involved here. -- Joseph Wright From joseph.wright at morningstar2.co.uk Mon May 16 09:30:42 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Mon, 16 May 2011 08:30:42 +0100 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: <4DD0BFFD.8090402@morningstar2.co.uk> References: <4DCFA463.9040608@morningstar2.co.uk> <4DD0BFFD.8090402@morningstar2.co.uk> Message-ID: <4DD0D2A2.6010504@morningstar2.co.uk> On 16/05/2011 07:11, Joseph Wright wrote: > On 16/05/2011 00:30, Charlie Sharpsteen wrote: >> Currently it looks like TeXworks only associates its self with .tex, >> .ltx and .pdf on OS X. The relevant file in the TeXworks source is >> TeXworks.plist.in, under the XML section starting with >> "CFBundleDocumentTypes". >> >> I agree that this list should be expanded. However I am reluctant to >> modify this file myself as I am trying to keep changes to existing >> files in my fork to a minimum. This policy ensures an easy merge of my >> work back into SVN if/when the time comes. >> >> Perhaps it would be more appropriate to address this issue by >> submitting a patch directly to the main TeXworks repo? The changes >> would propagate downstream into my builds. > > Of course, I was thinking about the main TeXworks codebase. I will take > a look at this if I get a chance: I'd hope that there is not too much > 'code' involved here. Looking at this again, I realise that the official version only associates .tex and .pdf with TeXworks on Windows, so the Mac version is already going further! It's the TeX Live version of TeXworks that is associated with .cls and .sty files on my system, and nothing at all picks up .dtx 'out of the box'. Now, I'm not sure what is 'correct' here. At the very least I suspect that Windows and Mac OS X should be consistent. I'm not 100% sure that TeXworks should be associating itself with .pdf (this is handy if you have no other viewer installed, but that seems like an edge case to me). Would a consistent list of: - .tex - .ltx - .sty - .cls - .dtx be reasonable? (I've left out .bib as there are a number of dedicated editors for BibTeX files.) -- Joseph Wright From jfkthame at googlemail.com Mon May 16 13:34:31 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Mon, 16 May 2011 12:34:31 +0100 Subject: [texworks] Mac OS TeXworks + fontconfig (was: Another TeXworks mac build (with a buildsystem!)) In-Reply-To: <4DCFC2B0.4020905@gmail.com> References: <4DCFC2B0.4020905@gmail.com> Message-ID: <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> On 15 May 2011, at 13:10, Stefan L?ffler wrote: > Hi, > > On 2011-05-13 06:35, Charlie Sharpsteen wrote: >> I could add a file to the TeXworks source that apackager could use to >> install Poppler thusly: >> >> brew install --with-qt4 --enable-xpdf-headers cmake/packaging/mac/poppler.rb >> >> And the patches in `lib-patches` would be applied automatically. > > Sounds good to me. It's really just the poppler-qt4-globalparams.patch, > as poppler-win32-font-handling.patch only applies to Windows-specific files. > >> So, I guess the question is---how badly do we want to get rid of >> Fontconfig? Leaving it in is starting to look like the easiest course >> of action on OS X. > > This is up to Jonathan Kew to decide (I explicitly CC'ed him to this > mail, hopefully he'll reply), as he set up the original "no-fontconfig" > policy. Not being a Mac developer or user myself, I can only abide by > the judgment of those who must live with the consequences (whatever they > may be). There are a few questions that I think need answering before making a definite statement here. Does the fontconfig-based build recognize the correct collection of installed fonts (so that PDFs that use any of those fonts, and don't have them embedded, will display as expected on the user's system)? On my laptop here, I notice that the list of fonts shown by fc-list in the Terminal does *not* seem to match the list displayed by Apple's ftxinstalledfonts (from the Apple Font Tool suite), so I'm a bit suspicious that the two "worlds" are not necessarily kept in sync properly. Does this version of fontconfig work without adding cache files to each font directory that it scans? It used to do that, but perhaps Apple has customized it so as to avoid this, or at least make the cache files invisible? (I didn't see font cache files on my laptop, so I think this issue may have been solved.) What happens if the TeXworks user doesn't have the X11 package installed? At least on older OS versions, it was a non-default optional install, so IMO an application like TW that aims to be a Mac OS app (rather than an X11 app) should not depend on it. JK From kakuto at fuk.kindai.ac.jp Mon May 16 14:12:48 2011 From: kakuto at fuk.kindai.ac.jp (Akira Kakuto) Date: Mon, 16 May 2011 21:12:48 +0900 Subject: [texworks] Mac OS TeXworks + fontconfig (was: Another TeXworks mac build (with a buildsystem!)) In-Reply-To: <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> References: <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> Message-ID: <13055479684949030000105d@sniffer> Dear Jonathan, > There are a few questions that I think need answering before > making a definite statement here. Slightly related issue: I'm considering to rename my fontconfig utilities (fc-cache.exe, fc-cat.exe, fc-list.exe, fc-match.exe, fc-query.exe, fc-scan.exe) like (xfc-cache.exe, xfc-cat.exe, xfc-list.exe, xfc-match.exe, xfc-query.exe, xfc-scan.exe) because people may install other fontconfig, and my statically linked one to XeTeX is dependent on Kpse and is not for generic use. WDYT? Thanks, Akira From henrikmidtiby at gmail.com Mon May 16 17:53:17 2011 From: henrikmidtiby at gmail.com (Henrik Skov Midtiby) Date: Mon, 16 May 2011 17:53:17 +0200 Subject: [texworks] SCRIPTING: Get content of specified directory In-Reply-To: References: Message-ID: Hi Paul Thanks for your input. I now have autocompletion working for the macros \includegraphics, \input and \include based on the files present in the directory of the file open for editing. This part works on systems where the "ls" command is available and where the file path does not contain any spaces. The code have only been tested on linux at the moment. The result is uploaded at http://code.google.com/p/texworks/issues/detail?id=261#c60 With the description ==================== Context based autocompleter for completing words used in the open document, arguments to label and ref and as a new feature filename autocompletion for include, input and includegraphics commands. Guide to use. 1. start typing the long word that should be autocompleted 2. press " + m" and the autocompleter will complete the word or at least make a suggestion for a completion. 3. if not satisfied with the suggestion press " + m" until the correct word is found. ==================== Best regards, Henrik Skov Midtiby On 15 May 2011 12:22, Paul A Norman wrote: > Dear Henrik, > > Not so far as far as I know. > > As you have, I've been using system calls to things like ?"cmd /c > mkdir \""+ documentPath +"images\"" > Can switch case on > http://twscript.paulanorman.com/docs/html/files/platform.html and > prepare differnt statements for the TW.system call. > http://twscript.paulanorman.com/docs/html/files/systemQString.html > > (see subheadngs in and under main headings "User 'Library' Modules and > helper objects" ?at > http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm for > some explanation on twPan - recomend downloading from > http://twscript.paulanorman.com/docs/index.html and the .chm there.) > > and ?have been using things like ... > > ?function ?chooseFromDirectoryListing(Description, pathDir, fileExtension) > ?{ > ?// pathDir (no trailing slash), fileExtension with . E.g. ?.txt > > ? // ? ? TW.app.clipboard = "cmd /c dir /b ?\"" > ? ? ? ? ? ? ? ? ? ? ? ? ?+ ?pathDir + "\\*" + fileExtension + "\""; > > ? ? ?var fileList = twPan.osCmd("cmd /c dir /b ?\"" > ? ? ? ? ? ? ? ? ? ? ? ? ?+ ?pathDir + "\\*" + fileExtension + "\"" > ? ? ? ? ? ? ? ? ? ? ? ? ? ? , true) > > ? ? ? ? ?removeExtnsn = new RegExp(fileExtension,"ig"); > > ? ? ? ?fileList = fileList.replace(removeExtnsn,"").split(lineBreak); > > ?// ? ?var chosenAnswer = > ? ? ? ? ? ?// ? twPan.select(Description, fileList); > > ?var chosenAnswer = ? ?TW.getItem(null, Description, Description, fileList); > > ? ? ? ?if (twPan.emptyString(chosenAnswer) == false) > ? ? ? ? ?{ > ? ? ? ? ?chosenAnswer = chosenAnswer + fileExtension; > ? ? ? ? ? } > > ? ? ?return chosenAnswer; > ? ?} > > You can use > > http://twscript.paulanorman.com/docs/html/files/getOpenFileNames.html > > See also notes in > http://twscript.paulanorman.com/docs/html/files/getOpenFileNameQString.html > > Can get one or multi-select more file names though returns an array in > that case, requires User interaction though. > > Paul > > > > On 15 May 2011 21:26, Henrik Skov Midtiby wrote: >> Hi >> >> >From at script would I like to get access to the contents of the >> current directory. >> This information should be used for autocompleting filenames for >> includegraphics and input macros in latex. >> >> I know it is possible to access the commandline and issue an 'ls -all' >> or something similar, but is this information also available directly >> in QtScript? >> >> Best regards, >> Henrik Skov Midtiby >> > From paul.a.norman at gmail.com Tue May 17 02:12:25 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 17 May 2011 12:12:25 +1200 Subject: [texworks] SCRIPTING: Get content of specified directory In-Reply-To: References: Message-ID: Looking really awesome Henrik! Haven't tried all scenarios yet, but really like the precision of operation, and the clarity of coding - made it really easy for me to try and get it running under Windows for your new feature - input of filenames. Often people have asked here whether there could be an automatic completion of environments \begin{something} sa a s a sad sad fd f \begin{ofsomething} sa a s a sad sad fd f \end{ofsomething} Is that something that you would see possibly logically fitting in with your code at all? With your new code, under Windows - I've tried these alterations, I don't think they'd break the Linux version (?) Quotes for possible spaces in file path (platform tested), and I've found that for *some* Dos commands and utilities we need to absolutely reverse the path delimiter to a backslash - fickle problem, and safer to actually sample the output to determine whether \n or \r\n is doing the line breaks and not assume it on platform. Regards, Paul line 304(?) function getListOfFilesInDir(directory) { if (TW.platform() == 'Windows') { var retVal = TW.system("cmd /c dir /b \"" + directory.replace(/\//g,"\\") +"\"", true); } else { var retVal = TW.system("ls " + directory, true); } return retVal.output; } function typeOfLineBreak(sample) // Win OS with utilities called can return either { if (sample.indexOf("\r\n") > -1) { return "\r\n"; } return "\n"; } function getMatchingFilenames(filenamesInDirectory, localPath, inputWord, words) { while(filenamesInDirectory.indexOf(typeOfLineBreak(filenamesInDirectory)) > -1) { ... On 17 May 2011 03:53, Henrik Skov Midtiby wrote: > Hi Paul > > Thanks for your input. > > I now have autocompletion working for the macros \includegraphics, > \input and \include based on the files present in the directory of the > file open for editing. > This part works on systems where the "ls" command is available and > where the file path does not contain any spaces. The code have only > been tested on linux at the moment. > > The result is uploaded at > http://code.google.com/p/texworks/issues/detail?id=261#c60 > With the description > ==================== > Context based autocompleter for completing words used in the open > document, arguments to label and ref and as a new feature filename > autocompletion for include, input and includegraphics commands. > > Guide to use. > 1. start typing the long word that should be autocompleted > 2. press " + m" and the autocompleter will complete the word or > at least make a suggestion for a completion. > 3. if not satisfied with the suggestion press " + m" until the > correct word is found. > ==================== > > Best regards, > Henrik Skov Midtiby > > > On 15 May 2011 12:22, Paul A Norman wrote: >> Dear Henrik, >> >> Not so far as far as I know. >> >> As you have, I've been using system calls to things like ?"cmd /c >> mkdir \""+ documentPath +"images\"" >> Can switch case on >> http://twscript.paulanorman.com/docs/html/files/platform.html and >> prepare differnt statements for the TW.system call. >> http://twscript.paulanorman.com/docs/html/files/systemQString.html >> >> (see subheadngs in and under main headings "User 'Library' Modules and >> helper objects" ?at >> http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm for >> some explanation on twPan - recomend downloading from >> http://twscript.paulanorman.com/docs/index.html and the .chm there.) >> >> and ?have been using things like ... >> >> ?function ?chooseFromDirectoryListing(Description, pathDir, fileExtension) >> ?{ >> ?// pathDir (no trailing slash), fileExtension with . E.g. ?.txt >> >> ? // ? ? TW.app.clipboard = "cmd /c dir /b ?\"" >> ? ? ? ? ? ? ? ? ? ? ? ? ?+ ?pathDir + "\\*" + fileExtension + "\""; >> >> ? ? ?var fileList = twPan.osCmd("cmd /c dir /b ?\"" >> ? ? ? ? ? ? ? ? ? ? ? ? ?+ ?pathDir + "\\*" + fileExtension + "\"" >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? , true) >> >> ? ? ? ? ?removeExtnsn = new RegExp(fileExtension,"ig"); >> >> ? ? ? ?fileList = fileList.replace(removeExtnsn,"").split(lineBreak); >> >> ?// ? ?var chosenAnswer = >> ? ? ? ? ? ?// ? twPan.select(Description, fileList); >> >> ?var chosenAnswer = ? ?TW.getItem(null, Description, Description, fileList); >> >> ? ? ? ?if (twPan.emptyString(chosenAnswer) == false) >> ? ? ? ? ?{ >> ? ? ? ? ?chosenAnswer = chosenAnswer + fileExtension; >> ? ? ? ? ? } >> >> ? ? ?return chosenAnswer; >> ? ?} >> >> You can use >> >> http://twscript.paulanorman.com/docs/html/files/getOpenFileNames.html >> >> See also notes in >> http://twscript.paulanorman.com/docs/html/files/getOpenFileNameQString.html >> >> Can get one or multi-select more file names though returns an array in >> that case, requires User interaction though. >> >> Paul >> >> >> >> On 15 May 2011 21:26, Henrik Skov Midtiby wrote: >>> Hi >>> >>> >From at script would I like to get access to the contents of the >>> current directory. >>> This information should be used for autocompleting filenames for >>> includegraphics and input macros in latex. >>> >>> I know it is possible to access the commandline and issue an 'ls -all' >>> or something similar, but is this information also available directly >>> in QtScript? >>> >>> Best regards, >>> Henrik Skov Midtiby >>> >> > > From herbs at wideopenwest.com Tue May 17 02:55:18 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Mon, 16 May 2011 19:55:18 -0500 Subject: [texworks] SCRIPTING: Get content of specified directory In-Reply-To: References: Message-ID: <8E069DF3-583C-46D2-AB74-6AF6286186E1@wideopenwest.com> On May 16, 2011, at 7:12 PM, Paul A Norman wrote: > Looking really awesome Henrik! > > Haven't tried all scenarios yet, but really like the precision of > operation, and the clarity of coding - made it really easy for me to > try and get it running under Windows for your new feature - input of > filenames. > > Often people have asked here whether there could be an automatic > completion of environments > > \begin{something} sa a s a sad sad fd f > > > \begin{ofsomething} sa a s a sad sad fd f > \end{ofsomething} > > Is that something that you would see possibly logically fitting in > with your code at all? > > With your new code, under Windows - I've tried these alterations, I > don't think they'd break the Linux version (?) > > Quotes for possible spaces in file path (platform tested), and I've > found that for *some* Dos commands and utilities we need to absolutely > reverse the path delimiter to a backslash - fickle problem, and safer > to actually sample the output to determine whether \n or \r\n is doing > the line breaks and not assume it on platform. > > Regards, > Paul Howdy, I'm not sure why that is preferable to simply using Command Completion and creating a full skeleton before yous tart to fill things in. In addition typing Ctl-M (isn't that simply a carriage return) if you are NOT in an environment would create \end{document} since that it the penultimate environment. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From paul.a.norman at gmail.com Tue May 17 03:36:18 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 17 May 2011 13:36:18 +1200 Subject: [texworks] SCRIPTING: Get content of specified directory In-Reply-To: <8E069DF3-583C-46D2-AB74-6AF6286186E1@wideopenwest.com> References: <8E069DF3-583C-46D2-AB74-6AF6286186E1@wideopenwest.com> Message-ID: Thanks Herb, Command Completion is really good for environments already registered, and I use it. I can understand for people who are using other packages that Command Completion is not set up for (and who maybe understand LaTeX well enough to have written their own), and yet who appear to not feel comfortable with trying to alter Tw configuration files to set it up themselves, why a simple completion macro would be helpful. You can use conditionals in Script and decide not to automatically put \end{document} in. Paul On 17 May 2011 12:55, Herbert Schulz wrote: > > On May 16, 2011, at 7:12 PM, Paul A Norman wrote: > >> Looking really awesome Henrik! >> >> Haven't tried all scenarios yet, but really like the precision of >> operation, and the clarity of coding - made it really easy for me to >> try and get it running under Windows for your new feature - input of >> filenames. >> >> Often people have asked here whether there could be an automatic >> completion of environments >> >> \begin{something} ? sa a s a sad sad ?fd f >> >> >> \begin{ofsomething} ? sa a s a sad sad ?fd f >> \end{ofsomething} >> >> Is that something that you would see possibly logically fitting in >> with your code at all? >> >> With your new code, under Windows - I've tried these alterations, I >> don't think they'd break the Linux version (?) >> >> Quotes for possible spaces in file path (platform tested), and I've >> found that for *some* Dos commands and utilities we need to absolutely >> reverse the path delimiter to a backslash - fickle problem, and safer >> to actually sample the output to determine whether \n or \r\n is doing >> the line breaks and not assume it on platform. >> >> Regards, >> Paul > > Howdy, > > I'm not sure why that is preferable to simply using Command Completion and creating a full skeleton before yous tart to fill things in. In addition typing Ctl-M (isn't that simply a carriage return) if you are NOT in an environment would create \end{document} since that it the penultimate environment. > > Good Luck, > > Herb Schulz > (herbs at wideopenwest dot com) > > > > > From st.loeffler at gmail.com Tue May 17 07:36:32 2011 From: st.loeffler at gmail.com (=?ISO-8859-15?Q?Stefan_L=F6ffler?=) Date: Tue, 17 May 2011 07:36:32 +0200 Subject: [texworks] Updated Russian translation In-Reply-To: <20110516023301.GB9245@smoon> References: <20110516023301.GB9245@smoon> Message-ID: <4DD20960.8010906@gmail.com> Hi, On 2011-05-16 04:33, Vladimir Lomov wrote: > I checked last rev. from svn and found that some strings were > untranslated. I send updated TS file. Thanks, committed as r819. Cheers, Stefan From st.loeffler at gmail.com Tue May 17 07:42:13 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 17 May 2011 07:42:13 +0200 Subject: [texworks] Building TeXworks for the Mac yourself In-Reply-To: <4DD0BED5.2080902@morningstar2.co.uk> References: <4DCFC803.9000401@gmail.com> <4DD0BED5.2080902@morningstar2.co.uk> Message-ID: <4DD20AB5.9070401@gmail.com> Hi, On 2011-05-16 08:06, Joseph Wright wrote: > On 15/05/2011 13:33, Stefan L?ffler wrote: >> Anyway, with Charlie's build system for the Mac in place, you almost >> good to go for building TeXworks yourself - if you want. I've uploaded a >> guide derived from the original readme file at >> http://code.google.com/p/texworks/wiki/BuildingOnMacOSXHomebrew. AFAIK, >> however, it was not tested on a clean (meaning: no development files >> installed) system, yet. So, if you're willing to try, please take a look >> at it, and report anything (be at a successful compilation, a problem, a >> suggestion, or whatever else) you experience here so we can improve this >> guide and others can follow in your footsteps in the future. > After a few false starts to strip out some material from earlier > attempts, I seem to have got this working. The only notes I'd add are > that (1) Xcode 3 is on the second DVD that came with my Mac, so I > avoided downloading it. (Install the 'Developer Tools' or something like > that.) (2) Building Qt tool over 2 hours even after it was downloaded, > and the download was also pretty long. So pick a time when you can leave > that particular step running. Thanks for testing and providing feedback! Re. 1): If you (or someone else) could check the correct term (without the "or something like that" ;)) I'll add it to the guide. BTW: Is having a second DVD with developer tools common, or is this specific to your version/configuration (sorry, I've lived in the Windows world for quite a while, where most operating systems come in a wide variety of variants ranging from "basic" to "ultimate" with different features and support). Re. 2): Right now it says "/Warning: Some of these will take a long time to finish. Especially Qt is quite large (several 100s of MB), so make sure you have a good internet connection and (up to) a couple of hours. The good thing is that each installation should run without requiring any input from you." /just below the "brew install" commands. If this is unclear (or too easy to overlook), I happily accept improvements. Cheers, Stefan // -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Tue May 17 08:07:18 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 17 May 2011 08:07:18 +0200 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: References: <4DCFC59B.6090501@gmail.com> Message-ID: <4DD21096.1090907@gmail.com> Hi, thanks for your description of building universal binaries. I think, things are beginning to add up in my head ;). On 2011-05-16 02:12, Charlie Sharpsteen wrote: > [snip] > Luckily, the TeXworks dependencies build into universal binaries just > fine using method #1. Qt has special configure flags that handle > universal binary creation. Thank yourselves for having such a short > dependency list as it makes this whole operation much easier. I may > look into adding custom Homebrew formulae for `qt.rb` and > `hunspell.rb` alongside `poppler.rb` that take care of building > universal binaries. Doesn't qt.rb have a "universal" flag? From its formula: ['--universal', "Build both x86_64 and x86 architectures."] It doesn't seem to build ppc binaries, though. Anyway, I could imagine that patches for this might also be of interest to the upstream repo... >>> Current issues with the builds: >>> >>> - If anyone is feeling artistic, it would be nice to come up with a >>> snazzy background image for the Drag N' Drop installer. >> I'm not feeling particularly artistic, but what kind of image are we >> talking about? Is there a webpage with some screenshots, maybe? > Wolfgang Schuster provided an excellent example of the desired effect. > It looks like we will need: > > 1. A PNG file that contains the background image. > > 2. A DS_Store file that tells OS X how to position the directory > contents and points to the PNG file as a background image. > > If someone comes up with a nice background, I could probably create > the DS_Store file. Thanks. I'll see if I can wrap something up, but I'm not going to have much time in the foreseeable future. So if someone else has a go at it I wouldn't mind ;). >>> - I noticed that the last official Mac build includes the following >>> Qt plugins: >>> >>> * accessible >>> * codecs >>> * graphicssystems >>> * imageformats >>> * script >>> >>> Currently, my builds don't contain any of these plugins and seem >>> to run fine (given extremely limited testing). Are any of these >>> plugins necessary? > >> 2) Do pdfs with embedded .png or .jpg files display correctly? >> 3) Can you drag&drop image files (e.g., .png or .jpg) into the editor >> and they get converted to \includegraphics{...} commands automatically? >> >> If 2 and 3 work, then "imageformats" (and perhaps "graphicssystems") are >> taken care of. > All images seem to display correctly. Drag and drop of PNG files > works. However, JPEG drag and drop causes TeXworks to open the JPEG > file for editing instead of inserting \includgraphics{...}. So it > looks like I may need to add some of the graphics plugins. Hm... You could try to see what QImageReader::supportedImageFormats() gives (you'll also need to add "#include "; see http://doc.trolltech.com/4.7/qimagereader.html#supportedImageFormats) at run time. Other than that, I found http://doc.trolltech.com/4.7/deployment-mac.html#the-mac-deployment-tool, which states (among other things) that Qt's default deployment tool follows the "Image format plugins are always deployed" policy. If CMake is not using said macdeployqt, I guess you have to convince it to deploy those image format plugins itself... HTH Stefan From st.loeffler at gmail.com Tue May 17 08:23:55 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 17 May 2011 08:23:55 +0200 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: References: <4DCC33D1.2080408@gmail.com> <4DCF8C13.3090205@gmail.com> Message-ID: <4DD2147B.4090208@gmail.com> Hi, On 2011-05-16 01:10, Charlie Sharpsteen wrote: > On Sun, May 15, 2011 at 1:17 AM, Stefan L?ffler wrote: >> Great! Maybe you could even do that before all the packaging-related >> questions are resolved, so people can build their own 0.4 stable release? >> But then again, there is a new one (0.4.1) coming up soon (hopefully), so >> maybe there isn't too much sense into building oneselve an 0.4.0 now... > There is one dilemma that I did not forsee as this is the first time I > have published a repository that was cloned using git-svn. The > problem is that when I started this project, I was only interested in > the TeXworks trunk, so I only cloned the trunk: > > git svn clone http://texworks.googlecode.com/svn/trunk/ > > If I now clone the rest of the SVN tree from: > > http://texworks.googlecode.com/svn > > Git sees it as a completely separate repository since there is a > different "root path". So, what I have published on GitHub is not a > suitable mirror of the SVN repository for someone who is interested in > working with branches or tags. > > There are two choices: > > 1. Use `git rebase` to graft the release-0.4.0 tag onto my clone > of the trunk. This will create a Git branch that people can pull and > build from, but the result will still be unsatisfactory for anyone > looking for a true mirror of the SVN repo. > > 2. Re-clone the SVN repo using `svn` as the root path instead of > `svn/trunk`---this will create a full mirror. Then I would move my > master branch over to this new clone. The problem with this choice is > that anyone who has already cloned my git repository would have to > deal with an "upstream rebase" (this means the history of a repository > you pulled from got re-written). This means that they have to stash > any changes that I haven't accepted in a pull request and then > re-synch with my master branch: First, a few observations from my side: * Pulling in 0.4.0 strikes me as a short-term solution. 0.4.1 is in the making, and hopefully many more releases will follow. Of course, the CMake files might be pulled into the upstream repo, but for now this has not been decided, so it's probably safer to draft a solution that doesn't depend on that. * There are several directories in the root path that are probably not needed, like manual/, website/, or wiki/ (note that the manual is included in the releases). branches/ right now only contains copies of the 0.2 and 0.4 stable series and is used primarily for cherry-picking, but of course might be used for testing "release candidates" in the future (other than that, branches would probably be only of interest to some few developers who could merge your cmake-only changes). So cloning the whole repo seems like overkill to me. From my POV, all that's needed right now is really trunk/ and tags/ (but, according to the observation above, with the possibility to expand this list). So, it would seem to me that making a cut now is probably the best option. I don't know how many people (apart from me) actually have changes to the code they need to rebase - please speak up now ;) - but I guess the number is small. HTH Stefan From paul.a.norman at gmail.com Tue May 17 09:02:08 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 17 May 2011 19:02:08 +1200 Subject: [texworks] SCRIPTING: Get content of specified directory In-Reply-To: References: <8E069DF3-583C-46D2-AB74-6AF6286186E1@wideopenwest.com> Message-ID: Ok, here is a small script for completing an environment like \begin{something} http://code.google.com/p/texworks/issues/detail?id=261#c61 If there are alterations later, I'll put them at http://twscript.paulanorman.com/downloads/ I think it is multi nesting safe - place cursor on a new line, where you want \end{something} and just activate with Alt E keys. It works from top down to where your cursor is, so it won't know if the environment is already ended past the cursor. After some discussion on the list, I realised that I had always wanted this for myself when ever someone had mentioned it, and finally felt to have a real go at it! And it looked too different to fit with the Crtl M work Henrik had done. Please let me know what breaks it. Paul On 17 May 2011 13:36, Paul A Norman wrote: > Thanks Herb, > > Command Completion is really good for environments already registered, > and I use it. > > I can understand for people who are using other packages that Command > Completion is not set up for (and who maybe understand LaTeX well > enough to have written their own), and yet who appear to not feel > comfortable with trying to alter Tw configuration files to set it up > themselves, why a simple completion macro would be helpful. > > You can use conditionals in Script and decide not to automatically put > ?\end{document} in. > > Paul > > On 17 May 2011 12:55, Herbert Schulz wrote: >> >> On May 16, 2011, at 7:12 PM, Paul A Norman wrote: >> >>> Looking really awesome Henrik! >>> >>> Haven't tried all scenarios yet, but really like the precision of >>> operation, and the clarity of coding - made it really easy for me to >>> try and get it running under Windows for your new feature - input of >>> filenames. >>> >>> Often people have asked here whether there could be an automatic >>> completion of environments >>> >>> \begin{something} ? sa a s a sad sad ?fd f >>> >>> >>> \begin{ofsomething} ? sa a s a sad sad ?fd f >>> \end{ofsomething} >>> >>> Is that something that you would see possibly logically fitting in >>> with your code at all? >>> >>> With your new code, under Windows - I've tried these alterations, I >>> don't think they'd break the Linux version (?) >>> >>> Quotes for possible spaces in file path (platform tested), and I've >>> found that for *some* Dos commands and utilities we need to absolutely >>> reverse the path delimiter to a backslash - fickle problem, and safer >>> to actually sample the output to determine whether \n or \r\n is doing >>> the line breaks and not assume it on platform. >>> >>> Regards, >>> Paul >> >> Howdy, >> >> I'm not sure why that is preferable to simply using Command Completion and creating a full skeleton before yous tart to fill things in. In addition typing Ctl-M (isn't that simply a carriage return) if you are NOT in an environment would create \end{document} since that it the penultimate environment. >> >> Good Luck, >> >> Herb Schulz >> (herbs at wideopenwest dot com) >> >> >> >> >> > From chuck at sharpsteen.net Tue May 17 23:57:58 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 17 May 2011 14:57:58 -0700 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: <4DD21096.1090907@gmail.com> References: <4DCFC59B.6090501@gmail.com> <4DD21096.1090907@gmail.com> Message-ID: On Mon, May 16, 2011 at 11:07 PM, Stefan L?ffler wrote: > Hi, > > thanks for your description of building universal binaries. I think, > things are beginning to add up in my head ;). > > On 2011-05-16 02:12, Charlie Sharpsteen wrote: >> [snip] >> Luckily, the TeXworks dependencies build into universal binaries just >> fine using method #1. Qt has special configure flags that handle >> universal binary creation. Thank yourselves for having such a short >> dependency list as it makes this whole operation much easier. ?I may >> look into adding custom Homebrew formulae for `qt.rb` and >> `hunspell.rb` alongside `poppler.rb` that take care of building >> universal binaries. > > Doesn't qt.rb have a "universal" flag? From its formula: > ['--universal', "Build both x86_64 and x86 architectures."] > > It doesn't seem to build ppc binaries, though. Anyway, I could imagine > that patches for this might also be of interest to the upstream repo... Homebrew's formula for Qt does have a `--universal` flag, but this is just a trigger that causes qt.rb to pass the appropriate flags for building `i386` and `x86_64` to the Qt configure script. Unfortunately, PPC additions aren't welcome in the main Homebrew repository. This is because the project was started well after Apple switched to Intel hardware and there are only 4 people with commit access to the central repository---not supporting PPC is a line that had to be drawn in order to keep the workload manageable. The Homebrew philosophy is that if someone doesn't like the Homebrew philosophy it should be trivial for them to fork the project and do whatever they please. There is a fork that maintains PPC support: https://github.com/sceaga/homebrew/commits/powerpc But I don't know how active it is. >>>> Current issues with the builds: >>>> >>>> ? - If anyone is feeling artistic, it would be nice to come up with a >>>> snazzy background image for the Drag N' Drop installer. >>> I'm not feeling particularly artistic, but what kind of image are we >>> talking about? Is there a webpage with some screenshots, maybe? >> Wolfgang Schuster provided an excellent example of the desired effect. >> It looks like we will need: >> >> ? 1. A PNG file that contains the background image. >> >> ? 2. A DS_Store file that tells OS X how to position the directory >> contents and points to the PNG file as a background image. >> >> If someone comes up with a nice background, I could probably create >> the DS_Store file. > > Thanks. I'll see if I can wrap something up, but I'm not going to have > much time in the foreseeable future. So if someone else has a go at it I > wouldn't mind ;). > >>>> ? - I noticed that the last official Mac build includes the following >>>> Qt plugins: >>>> >>>> ? ? * accessible >>>> ? ? * codecs >>>> ? ? * graphicssystems >>>> ? ? * imageformats >>>> ? ? * script >>>> >>>> ? ? Currently, my builds don't contain any of these plugins and seem >>>> to run fine (given extremely limited testing). Are any of these >>>> plugins necessary? >> >>> 2) Do pdfs with embedded .png or .jpg files display correctly? >>> 3) Can you drag&drop image files (e.g., .png or .jpg) into the editor >>> and they get converted to \includegraphics{...} commands automatically? >>> >>> If 2 and 3 work, then "imageformats" (and perhaps "graphicssystems") are >>> taken care of. >> All images seem to display correctly. Drag and drop of PNG files >> works. However, JPEG drag and drop causes TeXworks to open the JPEG >> file for editing instead of inserting \includgraphics{...}. So it >> looks like I may need to add some of the graphics plugins. > > Hm... > You could try to see what QImageReader::supportedImageFormats() gives > (you'll also need to add "#include "; see > http://doc.trolltech.com/4.7/qimagereader.html#supportedImageFormats) at > run time. > > Other than that, I found > http://doc.trolltech.com/4.7/deployment-mac.html#the-mac-deployment-tool, which > states (among other things) that Qt's default deployment tool follows > the "Image format plugins are always deployed" policy. If CMake is not > using said macdeployqt, I guess you have to convince it to deploy those > image format plugins itself... > > HTH > Stefan I think I may address the plugin situation by importing this CMake module into the project: https://github.com/KDAB/Charm/blob/master/CMake/DeployQt4.cmake It provides a wrapper on top of the `fixup_bundle` function that takes care of importing plugins from the main Qt libraries. -Charlie From chuck at sharpsteen.net Wed May 18 00:09:35 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 17 May 2011 15:09:35 -0700 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: <4DD2147B.4090208@gmail.com> References: <4DCC33D1.2080408@gmail.com> <4DCF8C13.3090205@gmail.com> <4DD2147B.4090208@gmail.com> Message-ID: On Mon, May 16, 2011 at 11:23 PM, Stefan L?ffler wrote: > Hi, snip >> ? ? 2. Re-clone the SVN repo using `svn` as the root path instead of >> `svn/trunk`---this will create a full mirror. Then I would move my >> master branch over to this new clone. The problem with this choice is >> that anyone who has already cloned my git repository would have to >> deal with an "upstream rebase" (this means the history of a repository >> you pulled from got re-written). This means that they have to stash >> any changes that I haven't accepted in a pull request and then >> re-synch with my master branch: snip > So, it would seem to me that making a cut now is probably the best > option. I don't know how many people (apart from me) actually have > changes to the code they need to rebase - please speak up now ;) - but I > guess the number is small. > > HTH > Stefan That is my feeling too. I hate to re-write published history, but the result will be a proper clone of the SVN history with the ability to import future tags and branches. The sooner it happens, the less painful it will be. So, I will rebase my master branch onto a full clone of the SVN history this weekend---if anyone out there has cloned my repository and made changes either submit a pull request to get them into my master before the rebase or make a note of your commit numbers so you can cherry-pick them afterwards. -Charlie From paul.a.norman at gmail.com Wed May 18 04:28:20 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 18 May 2011 14:28:20 +1200 Subject: [texworks] SCRIPTING: Get content of specified directory In-Reply-To: References: <8E069DF3-583C-46D2-AB74-6AF6286186E1@wideopenwest.com> Message-ID: Ok, found a few things that would break script mentioned in comment 61. Here is a link to a new download. Also script now enhanced to indicate which open Environments have not yet been closed in a document. Activates with Alt E twice, Paul, http://twscript.paulanorman.com/downloads/?endEnvironment On 17 May 2011 19:02, Paul A Norman wrote: > Ok, here is a small script for completing an environment like \begin{something} > > http://code.google.com/p/texworks/issues/detail?id=261#c61 > > If there are alterations later, I'll put them at > http://twscript.paulanorman.com/downloads/ > > I think it is multi nesting safe - place cursor on a new line, where > you want \end{something} and just activate with Alt E keys. It works > from top down to where your cursor is, so it won't know if the > environment is already ended past the cursor. > > After some discussion on the list, I realised that I had always wanted > this for myself when ever someone had mentioned it, and finally felt > to have a real go at it! > > And it looked too different to fit with the Crtl M work Henrik had done. > > Please let me know what breaks it. > > Paul > > On 17 May 2011 13:36, Paul A Norman wrote: >> Thanks Herb, >> >> Command Completion is really good for environments already registered, >> and I use it. >> >> I can understand for people who are using other packages that Command >> Completion is not set up for (and who maybe understand LaTeX well >> enough to have written their own), and yet who appear to not feel >> comfortable with trying to alter Tw configuration files to set it up >> themselves, why a simple completion macro would be helpful. >> >> You can use conditionals in Script and decide not to automatically put >> ?\end{document} in. >> >> Paul >> >> On 17 May 2011 12:55, Herbert Schulz wrote: >>> >>> On May 16, 2011, at 7:12 PM, Paul A Norman wrote: >>> >>>> Looking really awesome Henrik! >>>> >>>> Haven't tried all scenarios yet, but really like the precision of >>>> operation, and the clarity of coding - made it really easy for me to >>>> try and get it running under Windows for your new feature - input of >>>> filenames. >>>> >>>> Often people have asked here whether there could be an automatic >>>> completion of environments >>>> >>>> \begin{something} ? sa a s a sad sad ?fd f >>>> >>>> >>>> \begin{ofsomething} ? sa a s a sad sad ?fd f >>>> \end{ofsomething} >>>> >>>> Is that something that you would see possibly logically fitting in >>>> with your code at all? >>>> >>>> With your new code, under Windows - I've tried these alterations, I >>>> don't think they'd break the Linux version (?) >>>> >>>> Quotes for possible spaces in file path (platform tested), and I've >>>> found that for *some* Dos commands and utilities we need to absolutely >>>> reverse the path delimiter to a backslash - fickle problem, and safer >>>> to actually sample the output to determine whether \n or \r\n is doing >>>> the line breaks and not assume it on platform. >>>> >>>> Regards, >>>> Paul >>> >>> Howdy, >>> >>> I'm not sure why that is preferable to simply using Command Completion and creating a full skeleton before yous tart to fill things in. In addition typing Ctl-M (isn't that simply a carriage return) if you are NOT in an environment would create \end{document} since that it the penultimate environment. >>> >>> Good Luck, >>> >>> Herb Schulz >>> (herbs at wideopenwest dot com) >>> >>> >>> >>> >>> >> > From L.Santiago at warwick.ac.uk Tue May 17 22:48:04 2011 From: L.Santiago at warwick.ac.uk (Santiago, Lualhati) Date: Tue, 17 May 2011 21:48:04 +0100 Subject: [texworks] Message from TeXworks user Message-ID: Hello and thank you for your help, I would like to request help and guidance for installing the dictionary of British EN, if you could please help me on this. I do not see how to do it, where to install the OO dictionary. And I am also not sure as to how to properly install it. I cannot find a TexWorks folder in my computer, but only a MikTex, so I suppose that is where my dictionaries should go. But I also cannot find anywhere any folder under the name of /dictionary, or any place where the default dictionaries I currently have (US, FR,GER) are installed. Thank you. I would really appreciate it if you could help me on this, as I need to write in British English. Best regards, Lualhati ----- configuration info ----- TeXworks version : 0.3r670 (MiKTeX 2.9) Install location : C:/Program Files (x86)/MiKTeX 2.9/miktex/bin/miktex-texworks.exe Library path : C:\Users\Lulu\AppData\Local\MiKTeX\2.9\TeXworks\ pdfTeX location : C:/Program Files (x86)/MiKTeX 2.9/miktex/bin/pdftex.exe Operating system : Windows Microsoft Windows 7 Business Edition, 64-bit (build 7600) Qt4 version : 4.7.0 (build) / 4.7.0 (runtime) ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin at texberatung.com Wed May 18 12:13:57 2011 From: martin at texberatung.com (Martin Sievers) Date: Wed, 18 May 2011 12:13:57 +0200 Subject: [texworks] Message from TeXworks user In-Reply-To: References: Message-ID: <4DD39BE5.4000305@texberatung.com> Am 17.05.2011 22:48, schrieb Santiago, Lualhati: > Hello and thank you for your help, > > I would like to request help and guidance for installing the dictionary > of British EN, if you could please help me on this. > > I do not see how to do it, where to install the OO dictionary. And I am > also not sure as to how to properly install it. I cannot find a TexWorks > folder in my computer, but only a MikTex, so I suppose that is where my > dictionaries should go. But I also cannot find anywhere any folder under > the name of /dictionary, or any place where the default dictionaries I > currently have (US, FR,GER) are installed. > > Thank you. I would really appreciate it if you could help me on this, as > I need to write in British English. > > Best regards, > > Lualhati > > ----- configuration info ----- > TeXworks version : 0.3r670 (MiKTeX 2.9) > Install location : C:/Program Files (x86)/MiKTeX > 2.9/miktex/bin/miktex-texworks.exe > Library path : C:\Users\Lulu\AppData\Local\MiKTeX\2.9\TeXworks\ > pdfTeX location : C:/Program Files (x86)/MiKTeX 2.9/miktex/bin/pdftex.exe > Operating system : Windows Microsoft Windows 7 Business Edition, 64-bit > (build 7600) > Qt4 version : 4.7.0 (build) / 4.7.0 (runtime) > ------------------------------ > Hello, have you read http://code.google.com/p/texworks/wiki/SpellingDictionaries ? The folder is usually somewhere under "application data\miktex\texworks" and is called "dictionaries". Best regards Martin From paul.a.norman at gmail.com Thu May 19 04:03:25 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 19 May 2011 14:03:25 +1200 Subject: [texworks] SCRIPTING: 1. __FILE__ not quite true and 2. TW.system not handling - or _ in path structure(?) Message-ID: Hi, Some unexpected results ... TW.information(null, "", __FILE__); Shows the path and file name - but the first segment between the first delimeter / / set is set to lowercase and I have some capitals there. E.g. Real path is: G:/LaTeXPortable/LaTexUtils/TeXWorks/texworks/config/scripts/Image Handling/convertImage.js But __FILE__ copies to clipboard in Script as: G:/latexportable/LaTexUtils/TeXWorks/texworks/config/scripts/Image Handling/convertImage.js All the other capitals are ok. Also, If I change this part of the path /Image Handling/ to either of /Image-Handling/ /Image_Handling/ I get strange results when I try to pass this through TW.system even just for: cmd /c dir /b \" + scriptPath + "\\*.txt\"" "Parameter format not correct - "latexportable"." The above works fine when it is /Image Handling/ in the path (with the space). And copying cmd /c dir /b \" + scriptPath + "\\*.txt\"" in expanded form to the clipboard in script and then pasting it into a dos prompt works fine for all three path versions of /Image Handling/ /Image-Handling/ /Image_Handling/ Any thoughts appreciated please, Paul From st.loeffler at gmail.com Thu May 19 10:16:31 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 19 May 2011 10:16:31 +0200 Subject: [texworks] Updated builds of TeXworks for OS X In-Reply-To: <4DD0D2A2.6010504@morningstar2.co.uk> References: <4DCFA463.9040608@morningstar2.co.uk> <4DD0BFFD.8090402@morningstar2.co.uk> <4DD0D2A2.6010504@morningstar2.co.uk> Message-ID: <4DD4D1DF.7020702@gmail.com> Hi, On 2011-05-16 09:30, Joseph Wright wrote: > Looking at this again, I realise that the official version only > associates .tex and .pdf with TeXworks on Windows, so the Mac version is > already going further! It's the TeX Live version of TeXworks that is > associated with .cls and .sty files on my system, and nothing at all > picks up .dtx 'out of the box'. > > Now, I'm not sure what is 'correct' here. At the very least I suspect > that Windows and Mac OS X should be consistent. I'm not 100% sure that > TeXworks should be associating itself with .pdf (this is handy if you > have no other viewer installed, but that seems like an edge case to me). > Would a consistent list of: > - .tex > - .ltx > - .sty > - .cls > - .dtx > be reasonable? Thanks for the suggestion, I've added it in r820. Hopefully it works as I expect. A few remarks: * Originally, I had reservations regarding adding "package authoring" files to the Windows installer because the could confuse "newbie" users. But on the other hand, it's better if those files are opened in Tw automatically should the user stumble across them rather than Windows presenting a list to open the "unknown file type". Expert users can disable the creation of those file associations, but they are set by default. * On Windows, pdf files are not associated with Tw by default, but there is the option to do so in the installer. * On the Mac, Tw registers itself as a pdf viewer, but does not set LSIsAppleDefaultForType to true (as it does for .tex etc.). If this works as I expect from its name, this should not override the default viewer app for pdfs, but merely register as an alternative. * The settings for Windows and the Mac don't necessarily have to be the same. The _supported_ file types should, of course (and this should hopefully be fixed in r820), but how they are handled, whether they are default, etc. strongly depends on the system (and the questions how defaults are handled and how easily they are changed). > (I've left out .bib as there are a number of dedicated editors for > BibTeX files.) Yes, BiBTeX is a completely different story, and while any text file (including .bib) can be edited by Tw, of course, I think we should only assign it to files with a TeX syntax. Cheers, Stefan From st.loeffler at gmail.com Thu May 19 12:38:09 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 19 May 2011 12:38:09 +0200 Subject: [texworks] SCRIPTING: 1. __FILE__ not quite true and 2. TW.system not handling - or _ in path structure(?) In-Reply-To: References: Message-ID: <4DD4F311.50108@gmail.com> Hi, On 2011-05-19 04:03, Paul A Norman wrote: > TW.information(null, "", __FILE__); > > Shows the path and file name - but the first segment between the first > delimeter / / set is set to lowercase and I have some capitals there. > > E.g. > > Real path is: > > G:/LaTeXPortable/LaTexUtils/TeXWorks/texworks/config/scripts/Image > Handling/convertImage.js > > But __FILE__ copies to clipboard in Script as: > > G:/latexportable/LaTexUtils/TeXWorks/texworks/config/scripts/Image > Handling/convertImage.js Hm, this is weird. __FILE__ is provided directly by the QtScript API, though, AFAIK. Tw doesn't do anything with it (nor does it exist in, e.g., lua). So this might be a Qt bug (but then again, I'm not sure if this feature is documented at all - probably that should be checked first). > Also, If I change this part of the path /Image Handling/ to either > of /Image-Handling/ /Image_Handling/ > > I get strange results when I try to pass this through TW.system even > just for: cmd /c dir /b \" + scriptPath + "\\*.txt\"" > > "Parameter format not correct - "latexportable"." > > The above works fine when it is /Image Handling/ in the path (with the space). > > And copying cmd /c dir /b \" + scriptPath + "\\*.txt\"" in expanded > form to the clipboard in script and then pasting it into a dos prompt > works fine for all three path versions of /Image Handling/ > /Image-Handling/ /Image_Handling/ This is strange, too. Again, Tw doesn't do anything with the command line, it passes is straight to http://doc.trolltech.com/4.7/qprocess.html#start-2. So, two suggestons: * Does it work (for a path without spaces) if you remove the quotes? * Does it work if you escape the quotes (http://doc.trolltech.com/4.7/qprocess.html#start-2 actually has an example on `dir`). HTH Stefan From paul.a.norman at gmail.com Thu May 19 13:06:18 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 19 May 2011 23:06:18 +1200 Subject: [texworks] SCRIPTING: 1. __FILE__ not quite true and 2. TW.system not handling - or _ in path structure(?) In-Reply-To: <4DD4F311.50108@gmail.com> References: <4DD4F311.50108@gmail.com> Message-ID: Thanks Stefan, I'll see if I can identify what is happening better. 2. is strange, as it is the paths with out the spaces, using - or _ instead of spaces that is giving me grief. process.start("dir \"\"\"My Documents\"\"\"" woah! I've been getting away with "dir \"dah dah dah\" " no worries. Paul On 19 May 2011 22:38, Stefan L?ffler wrote: > Hi, > > On 2011-05-19 04:03, Paul A Norman wrote: >> ?TW.information(null, "", __FILE__); >> >> Shows the path and file name - but the first segment between the first >> delimeter / / set ?is set to lowercase and I have some capitals there. >> >> E.g. >> >> Real path is: >> >> G:/LaTeXPortable/LaTexUtils/TeXWorks/texworks/config/scripts/Image >> Handling/convertImage.js >> >> But __FILE__ copies to clipboard in Script as: >> >> G:/latexportable/LaTexUtils/TeXWorks/texworks/config/scripts/Image >> Handling/convertImage.js > > Hm, this is weird. __FILE__ is provided directly by the QtScript API, > though, AFAIK. Tw doesn't do anything with it (nor does it exist in, > e.g., lua). So this might be a Qt bug (but then again, I'm not sure if > this feature is documented at all - probably that should be checked first). > >> Also, If I change this part of the path ?/Image Handling/ ?to either >> of ? /Image-Handling/ ?/Image_Handling/ >> >> I get strange results when I try to pass this through TW.system even >> just for: ?cmd /c dir /b \" + scriptPath + "\\*.txt\"" >> >> "Parameter format not correct - "latexportable"." >> >> The above works fine when it is /Image Handling/ in the path (with the space). >> >> And copying cmd /c dir /b \" + scriptPath + "\\*.txt\"" in expanded >> form to the clipboard in script and then pasting it into a dos prompt >> works fine for all three path versions of ? /Image Handling/ >> /Image-Handling/ ?/Image_Handling/ > > This is strange, too. Again, Tw doesn't do anything with the command > line, it passes is straight to > http://doc.trolltech.com/4.7/qprocess.html#start-2. So, two suggestons: > ?* Does it work (for a path without spaces) if you remove the quotes? > ?* Does it work if you escape the quotes > (http://doc.trolltech.com/4.7/qprocess.html#start-2 actually has an > example on `dir`). > > HTH > Stefan > From n.ashrafinia at gmail.com Fri May 20 15:27:31 2011 From: n.ashrafinia at gmail.com (narges ashrafinia) Date: Fri, 20 May 2011 17:57:31 +0430 Subject: [texworks] Message from TeXworks user Message-ID: <4dd66c49.41cad80a.1b43.ffffcbff@mx.google.com> ----- configuration info ----- TeXworks version : 0.4.0r759 (MiKTeX 2.9) Install location : C:/Program Files/MiKTeX 2.9/miktex/bin/miktex-texworks.exe Library path : C:/Users/Doctor/AppData/Local/MiKTeX/2.9/TeXworks/0.4\ pdfTeX location : C:/Program Files/MiKTeX 2.9/miktex/bin/pdftex.exe Operating system : Windows Microsoft Windows 7 Business Edition, 32-bit (build 7600) Qt4 version : 4.7.2 (build) / 4.7.2 (runtime) ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From henrikmidtiby at gmail.com Fri May 20 15:40:04 2011 From: henrikmidtiby at gmail.com (Henrik Skov Midtiby) Date: Fri, 20 May 2011 15:40:04 +0200 Subject: [texworks] SCRIPTING: Get content of specified directory In-Reply-To: References: Message-ID: Hi Paul and others I have tried to use your code for filename completion for windows. It it still not tested ... In addition the script can now complete open environments (which is determined by looking at the current file from the beginning and to the cursor location). The script can be downloaded from https://github.com/henrikmidtiby/autocompleteForTexworks/blob/master/scripts/autocomplete.js Any comments and ideas for improvements are appreciated. Best regards, Henrik On 17 May 2011 02:12, Paul A Norman wrote: > Looking really awesome Henrik! > > Haven't tried all scenarios yet, but really like the precision of > operation, and the clarity of coding - made it really easy for me to > try and get it running under Windows for your new feature - input of > filenames. > > Often people have asked here whether there could be an automatic > completion of environments > > \begin{something} ? sa a s a sad sad ?fd f > > > \begin{ofsomething} ? sa a s a sad sad ?fd f > \end{ofsomething} > > Is that something that you would see possibly logically fitting in > with your code at all? > > With your new code, under Windows - I've tried these alterations, I > don't think they'd break the Linux version (?) > > Quotes for possible spaces in file path (platform tested), and I've > found that for *some* Dos commands and utilities we need to absolutely > reverse the path delimiter to a backslash - fickle problem, and safer > to actually sample the output to determine whether \n or \r\n is doing > the line breaks and not assume it on platform. > > Regards, > Paul > line 304(?) > function getListOfFilesInDir(directory) > { > > ?if (TW.platform() == 'Windows') > ? { > ? var retVal = TW.system("cmd /c dir /b \"" + > directory.replace(/\//g,"\\") +"\"", true); > ? } > ? else > ? ? ? ?{ > ? ? ? ?var retVal = TW.system("ls " + directory, true); > ? ? ? ?} > > ? ? ? ?return retVal.output; > } > > function typeOfLineBreak(sample) // Win OS with utilities called can > return either > ?{ > ? if (sample.indexOf("\r\n") > -1) > ? ? { > ? ? ? return "\r\n"; > ? ? ? } > > ? ? ?return "\n"; > > ?} > > > function getMatchingFilenames(filenamesInDirectory, localPath, inputWord, words) > { > ? ? ? ?while(filenamesInDirectory.indexOf(typeOfLineBreak(filenamesInDirectory)) > -1) > ? ? ? ?{ > ... > > On 17 May 2011 03:53, Henrik Skov Midtiby wrote: >> Hi Paul >> >> Thanks for your input. >> >> I now have autocompletion working for the macros \includegraphics, >> \input and \include based on the files present in the directory of the >> file open for editing. >> This part works on systems where the "ls" command is available and >> where the file path does not contain any spaces. The code have only >> been tested on linux at the moment. >> >> The result is uploaded at >> http://code.google.com/p/texworks/issues/detail?id=261#c60 >> With the description >> ==================== >> Context based autocompleter for completing words used in the open >> document, arguments to label and ref and as a new feature filename >> autocompletion for include, input and includegraphics commands. >> >> Guide to use. >> 1. start typing the long word that should be autocompleted >> 2. press " + m" and the autocompleter will complete the word or >> at least make a suggestion for a completion. >> 3. if not satisfied with the suggestion press " + m" until the >> correct word is found. >> ==================== >> >> Best regards, >> Henrik Skov Midtiby >> >> >> On 15 May 2011 12:22, Paul A Norman wrote: >>> Dear Henrik, >>> >>> Not so far as far as I know. >>> >>> As you have, I've been using system calls to things like ?"cmd /c >>> mkdir \""+ documentPath +"images\"" >>> Can switch case on >>> http://twscript.paulanorman.com/docs/html/files/platform.html and >>> prepare differnt statements for the TW.system call. >>> http://twscript.paulanorman.com/docs/html/files/systemQString.html >>> >>> (see subheadngs in and under main headings "User 'Library' Modules and >>> helper objects" ?at >>> http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm for >>> some explanation on twPan - recomend downloading from >>> http://twscript.paulanorman.com/docs/index.html and the .chm there.) >>> >>> and ?have been using things like ... >>> >>> ?function ?chooseFromDirectoryListing(Description, pathDir, fileExtension) >>> ?{ >>> ?// pathDir (no trailing slash), fileExtension with . E.g. ?.txt >>> >>> ? // ? ? TW.app.clipboard = "cmd /c dir /b ?\"" >>> ? ? ? ? ? ? ? ? ? ? ? ? ?+ ?pathDir + "\\*" + fileExtension + "\""; >>> >>> ? ? ?var fileList = twPan.osCmd("cmd /c dir /b ?\"" >>> ? ? ? ? ? ? ? ? ? ? ? ? ?+ ?pathDir + "\\*" + fileExtension + "\"" >>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? , true) >>> >>> ? ? ? ? ?removeExtnsn = new RegExp(fileExtension,"ig"); >>> >>> ? ? ? ?fileList = fileList.replace(removeExtnsn,"").split(lineBreak); >>> >>> ?// ? ?var chosenAnswer = >>> ? ? ? ? ? ?// ? twPan.select(Description, fileList); >>> >>> ?var chosenAnswer = ? ?TW.getItem(null, Description, Description, fileList); >>> >>> ? ? ? ?if (twPan.emptyString(chosenAnswer) == false) >>> ? ? ? ? ?{ >>> ? ? ? ? ?chosenAnswer = chosenAnswer + fileExtension; >>> ? ? ? ? ? } >>> >>> ? ? ?return chosenAnswer; >>> ? ?} >>> >>> You can use >>> >>> http://twscript.paulanorman.com/docs/html/files/getOpenFileNames.html >>> >>> See also notes in >>> http://twscript.paulanorman.com/docs/html/files/getOpenFileNameQString.html >>> >>> Can get one or multi-select more file names though returns an array in >>> that case, requires User interaction though. >>> >>> Paul >>> >>> >>> >>> On 15 May 2011 21:26, Henrik Skov Midtiby wrote: >>>> Hi >>>> >>>> >From at script would I like to get access to the contents of the >>>> current directory. >>>> This information should be used for autocompleting filenames for >>>> includegraphics and input macros in latex. >>>> >>>> I know it is possible to access the commandline and issue an 'ls -all' >>>> or something similar, but is this information also available directly >>>> in QtScript? >>>> >>>> Best regards, >>>> Henrik Skov Midtiby >>>> >>> >> >> > > From daleif at imf.au.dk Fri May 20 16:20:30 2011 From: daleif at imf.au.dk (Lars Madsen) Date: Fri, 20 May 2011 16:20:30 +0200 Subject: [texworks] texworks and encodings Message-ID: <4DD678AE.20005@imf.au.dk> Hi where I work some departments have computer labs where they have windows computers with miktex and of course texworks. yesterday a student came to me with a problem. TeXWorks can easily handle writing in UTF8 or say latin1. But if TeXWorks is configured to save in latin1, and one attempts to open a file written in UTF8, then TeXWorks jumbles the special characters and cannot show them correctly. Wouldn't it be possible for TW to detect the encoding and switch to that encoding when working with this file. We solved the problem by reconfiguring TW, but for a novice user, this is not something they know about (most users do not understand the concept of encodings) /daleif From herbs at wideopenwest.com Fri May 20 21:07:09 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Fri, 20 May 2011 14:07:09 -0500 Subject: [texworks] texworks and encodings In-Reply-To: <4DD678AE.20005@imf.au.dk> References: <4DD678AE.20005@imf.au.dk> Message-ID: <5D19C454-73D6-47FE-B488-01C3B4D23E43@wideopenwest.com> On May 20, 2011, at 9:20 AM, Lars Madsen wrote: > Hi > > where I work some departments have computer labs where they have windows computers with miktex and of course texworks. > > yesterday a student came to me with a problem. > > TeXWorks can easily handle writing in UTF8 or say latin1. But if TeXWorks is configured to save in latin1, and one attempts to open a file written in UTF8, then TeXWorks jumbles the special characters and cannot show them correctly. > > Wouldn't it be possible for TW to detect the encoding and switch to that encoding when working with this file. > > We solved the problem by reconfiguring TW, but for a novice user, this is not something they know about (most users do not understand the concept of encodings) > > /daleif Howdy, I believe that programs that determine the input encoding when they open them are using heuristics and too often ``guess'' wrong. I've experienced that with BBEdit and have had to Re-Open with the proper encoding. The easiest way to have TeXworks (and TeXShop on the Mac too) open any given file with the correct encoding is to place the line % !TEX encoding = UTF-8 Unicode or % !TEX encoding = IsoLatin near the top of the file. (That is what I use for TeXshop and I'm pretty sure it works for TeXworks too.) For files coming from ``somewhere else'' you need to be informed what the encoding is (if it's from windows I'd assume latin1 (IsoLatin above) or be very careful when you open the file NOT to change it and save it and re-open with the proper encoding. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From chuck at sharpsteen.net Fri May 20 22:46:35 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Fri, 20 May 2011 13:46:35 -0700 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: References: <4DCC33D1.2080408@gmail.com> <4DCF8C13.3090205@gmail.com> <4DD2147B.4090208@gmail.com> Message-ID: On Tue, May 17, 2011 at 3:09 PM, Charlie Sharpsteen wrote: > So, I will rebase my master branch onto a full clone of the SVN > history this weekend---if anyone out there has cloned my repository > and made changes either submit a pull request to get them into my > master before the rebase or make a note of your commit numbers so you > can cherry-pick them afterwards. > > -Charlie I just pushed three new branches that were cloned from the root of the SVN repository: texworks-trunk texworks-0.2 texworks-0.4 The cmake-only branch has been rebased onto the tip of texworks-trunk. The URL for reviewing changes compared to the SVN trunk is now: https://github.com/Sharpie/TeXworks/compare/texworks-trunk...cmake-only A patch can be obtained by adding `.patch` to that URL: https://github.com/Sharpie/TeXworks/compare/texworks-trunk...cmake-only.patch Tomorrow evening I plan to rebase my master branch onto texworks-trunk and delete the old texworks-svn branch. -Charlie From josiahmanson at gmail.com Sat May 21 00:48:13 2011 From: josiahmanson at gmail.com (Josiah Manson) Date: Fri, 20 May 2011 17:48:13 -0500 Subject: [texworks] Font setting forgotten Message-ID: Hi, I just wanted to report a problem with version 0.40 r.759. If I set the font size and type, it works just fine for the current instance, but is not preserved if I close and then reopen the program. From chuck at sharpsteen.net Sat May 21 01:07:11 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Fri, 20 May 2011 16:07:11 -0700 Subject: [texworks] Font setting forgotten In-Reply-To: References: Message-ID: Which OS are you using? On Fri, May 20, 2011 at 3:48 PM, Josiah Manson wrote: > Hi, I just wanted to report a problem with version 0.40 r.759. If I > set the font size and type, it works just fine for the current > instance, but is not preserved if I close and then reopen the program. > From paul.a.norman at gmail.com Sat May 21 02:46:25 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sat, 21 May 2011 12:46:25 +1200 Subject: [texworks] Message from TeXworks user In-Reply-To: <4dd66c49.41cad80a.1b43.ffffcbff@mx.google.com> References: <4dd66c49.41cad80a.1b43.ffffcbff@mx.google.com> Message-ID: HI Narges, Got any more information for us? Your last message was a bit blank or was it an accident? Paul On 21 May 2011 01:27, narges ashrafinia wrote: > > > ----- configuration info ----- > TeXworks version : 0.4.0r759 (MiKTeX 2.9) > Install location : C:/Program Files/MiKTeX > 2.9/miktex/bin/miktex-texworks.exe > Library path???? : C:/Users/Doctor/AppData/Local/MiKTeX/2.9/TeXworks/0.4\ > pdfTeX location? : C:/Program Files/MiKTeX 2.9/miktex/bin/pdftex.exe > Operating system : Windows Microsoft Windows 7 Business Edition, 32-bit > (build 7600) > Qt4 version????? : 4.7.2 (build) / 4.7.2 (runtime) > ------------------------------ From sigmundv at gmail.com Sat May 21 03:24:28 2011 From: sigmundv at gmail.com (sigmundv at gmail.com) Date: Sat, 21 May 2011 03:24:28 +0200 Subject: [texworks] Message from TeXworks user In-Reply-To: References: <4dd66c49.41cad80a.1b43.ffffcbff@mx.google.com> Message-ID: Must have been an accident. Looks like the signature of a user on some geeky forum... Sigmund On Sat, May 21, 2011 at 02:46, Paul A Norman wrote: > HI Narges, > > Got any more information for us? > Your last message was a bit blank or was it an accident? > > Paul > > On 21 May 2011 01:27, narges ashrafinia wrote: > > > > > > ----- configuration info ----- > > TeXworks version : 0.4.0r759 (MiKTeX 2.9) > > Install location : C:/Program Files/MiKTeX > > 2.9/miktex/bin/miktex-texworks.exe > > Library path : C:/Users/Doctor/AppData/Local/MiKTeX/2.9/TeXworks/0.4\ > > pdfTeX location : C:/Program Files/MiKTeX 2.9/miktex/bin/pdftex.exe > > Operating system : Windows Microsoft Windows 7 Business Edition, 32-bit > > (build 7600) > > Qt4 version : 4.7.2 (build) / 4.7.2 (runtime) > > ------------------------------ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Sat May 21 09:41:47 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sat, 21 May 2011 09:41:47 +0200 Subject: [texworks] Font setting forgotten In-Reply-To: References: Message-ID: <4DD76CBB.2070606@gmail.com> Hi, On 2011-05-21 00:48, Josiah Manson wrote: > Hi, I just wanted to report a problem with version 0.40 r.759. If I > set the font size and type, it works just fine for the current > instance, but is not preserved if I close and then reopen the program. I assume you change the font settings in "Format > Font..."? This is intended to apply only to the current window. To set the default for all (new) windows, please use "Edit > Preferences... > Editor". HTH Stefan From st.loeffler at gmail.com Sat May 21 09:44:05 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Sat, 21 May 2011 09:44:05 +0200 Subject: [texworks] Message from TeXworks user In-Reply-To: References: <4dd66c49.41cad80a.1b43.ffffcbff@mx.google.com> Message-ID: <4DD76D45.7080502@gmail.com> On 2011-05-21 03:24, sigmundv at gmail.com wrote: > Must have been an accident. Looks like the signature of a user on some > geeky forum... > > On 21 May 2011 01:27, narges ashrafinia > wrote: > > > > ----- configuration info ----- > > TeXworks version : 0.4.0r759 (MiKTeX 2.9) > > Install location : C:/Program Files/MiKTeX > > 2.9/miktex/bin/miktex-texworks.exe > > Library path : > C:/Users/Doctor/AppData/Local/MiKTeX/2.9/TeXworks/0.4\ > > pdfTeX location : C:/Program Files/MiKTeX 2.9/miktex/bin/pdftex.exe > > Operating system : Windows Microsoft Windows 7 Business Edition, > 32-bit > > (build 7600) > > Qt4 version : 4.7.2 (build) / 4.7.2 (runtime) > > ------------------------------ > In fact, to me this looks like the data that is added when using "Help > Email to mailing list" to help debugging problems. Of course, people can also use it as signature, but in general I'd doubt that ;). Cheers, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Sat May 21 10:09:21 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sat, 21 May 2011 10:09:21 +0200 Subject: [texworks] texworks and encodings In-Reply-To: <4DD678AE.20005@imf.au.dk> References: <4DD678AE.20005@imf.au.dk> Message-ID: <4DD77331.9070105@gmail.com> Hi, On 2011-05-20 16:20, Lars Madsen wrote: > Wouldn't it be possible for TW to detect the encoding and switch to > that encoding when working with this file. The answer to this question is manifold. As Herbert already pointed out, encoding detection is essentially guessing (and often requires language-detection as well). Of course I agree that ideally, Tw should "just work", no matter what file is thrown at it, but... In many (simple) situations I don't expect this to be a problem. As long as you only deal with your own documents, e.g., you can either use the default utf-8 (preferred) or - especially in cases that you want to work with other files created by a different program - change the default accordingly. If you use non-ASCII characters, you need the inputenc package, AFAIK. So you should at least be aware that a thing like encoding exists and can possibly cause problems. Only when dealing with files with using different encodings this causes problems, but in that case it's certainly the safest to add information about the encoding near the top of the file, which Tw picks up similar to TeXShop. Moreover, others who may want to work with the file can also quickly see what encoding was used and take the necessary steps without having to contact the original author to figure out what encoding to use. So far for the practical aspects. In addition, there are a few technical issues involved: Qt doesn't support encoding-detection. Using additional libraries creates additional dependencies (which possibly complicate building the program, at least on some OSs). And they increase the size of Tw. The unicode ICU library for example has 18.7 MB on my Linux system! So, the bottom line is: it would be great to have it, but the cost is rather high, and (I hope) the encoding issue only affects a minority of Tw users. FWIW, I recently added the possibility to "reload a file using a selected encoding" to avoid having to go to a different editor to add the "%!TEX encoding" modline. This was also added to the manual, and should be included in the upcoming 0.4.1 release. HTH Stefan From daleif at imf.au.dk Sat May 21 10:40:55 2011 From: daleif at imf.au.dk (Lars Madsen) Date: Sat, 21 May 2011 10:40:55 +0200 Subject: [texworks] texworks and encodings In-Reply-To: <4DD77331.9070105@gmail.com> References: <4DD678AE.20005@imf.au.dk> <4DD77331.9070105@gmail.com> Message-ID: <4DD77A97.30001@imf.au.dk> On 05/21/2011 10:09 AM, Stefan L?ffler wrote: > Hi, > > On 2011-05-20 16:20, Lars Madsen wrote: >> Wouldn't it be possible for TW to detect the encoding and switch to >> that encoding when working with this file. > > The answer to this question is manifold. > As Herbert already pointed out, encoding detection is essentially > guessing (and often requires language-detection as well). Of course I > agree that ideally, Tw should "just work", no matter what file is thrown > at it, but... > > In many (simple) situations I don't expect this to be a problem. As long > as you only deal with your own documents, e.g., you can either use the > default utf-8 (preferred) or - especially in cases that you want to work > with other files created by a different program - change the default > accordingly. > > If you use non-ASCII characters, you need the inputenc package, AFAIK. > So you should at least be aware that a thing like encoding exists and > can possibly cause problems. > > Only when dealing with files with using different encodings this causes > problems, but in that case it's certainly the safest to add information > about the encoding near the top of the file, which Tw picks up similar > to TeXShop. Moreover, others who may want to work with the file can also > quickly see what encoding was used and take the necessary steps without > having to contact the original author to figure out what encoding to use. > > So far for the practical aspects. In addition, there are a few technical > issues involved: > > Qt doesn't support encoding-detection. > > Using additional libraries creates additional dependencies (which > possibly complicate building the program, at least on some OSs). And > they increase the size of Tw. The unicode ICU library for example has > 18.7 MB on my Linux system! > > So, the bottom line is: it would be great to have it, but the cost is > rather high, and (I hope) the encoding issue only affects a minority of > Tw users. FWIW, I recently added the possibility to "reload a file using > a selected encoding" to avoid having to go to a different editor to add > the "%!TEX encoding" modline. This was also added to the manual, and > should be included in the upcoming 0.4.1 release. > > HTH > Stefan That sounds like a good compromise I'll add something about the %!TEX modline in my LaTeX book Of course it is not a problem when users use their own computers. But it will come when users either use Lab computers or when they exchange files among them self. /daleif From gzjjgod at gmail.com Sat May 21 10:52:39 2011 From: gzjjgod at gmail.com (Jjgod Jiang) Date: Sat, 21 May 2011 10:52:39 +0200 Subject: [texworks] texworks and encodings In-Reply-To: <4DD77331.9070105@gmail.com> References: <4DD678AE.20005@imf.au.dk> <4DD77331.9070105@gmail.com> Message-ID: On Sat, May 21, 2011 at 10:09 AM, Stefan L?ffler wrote: > Using additional libraries creates additional dependencies (which > possibly complicate building the program, at least on some OSs). And > they increase the size of Tw. The unicode ICU library for example has > 18.7 MB on my Linux system! Who said you must use ICU to do encoding detection? The Mozilla charset detector [1] builds as a 500kb static library on my machine. [1] http://www.mozilla.org/projects/intl/chardet.html From josiahmanson at gmail.com Sat May 21 00:55:07 2011 From: josiahmanson at gmail.com (Josiah Manson) Date: Fri, 20 May 2011 17:55:07 -0500 Subject: [texworks] Font setting forgotten In-Reply-To: References: Message-ID: Sorry. I forgot to mention that my OS is Windows 7, 64-bit. On Fri, May 20, 2011 at 5:48 PM, Josiah Manson wrote: > Hi, I just wanted to report a problem with version 0.40 r.759. If I > set the font size and type, it works just fine for the current > instance, but is not preserved if I close and then reopen the program. > From josiahmanson at gmail.com Sat May 21 01:09:44 2011 From: josiahmanson at gmail.com (Josiah Manson) Date: Fri, 20 May 2011 18:09:44 -0500 Subject: [texworks] Font setting forgotten In-Reply-To: References: Message-ID: Sorry. I forgot to mention that my OS is Windows 7, 64-bit. On Fri, May 20, 2011 at 6:07 PM, Charlie Sharpsteen wrote: > Which OS are you using? > > On Fri, May 20, 2011 at 3:48 PM, Josiah Manson wrote: >> Hi, I just wanted to report a problem with version 0.40 r.759. If I >> set the font size and type, it works just fine for the current >> instance, but is not preserved if I close and then reopen the program. >> > From josiahmanson at gmail.com Sat May 21 12:54:41 2011 From: josiahmanson at gmail.com (Josiah Manson) Date: Sat, 21 May 2011 05:54:41 -0500 Subject: [texworks] Font setting forgotten In-Reply-To: <4DD76CBB.2070606@gmail.com> References: <4DD76CBB.2070606@gmail.com> Message-ID: That was it. Thank you for your help. You may consider adding some warning message or doing something else to let users know that the chance is not permanent and point them in the right direction. It did not occur to me that I had simply gone to the wrong menu, because everything seemed to work as expected until I restarted the editor. This is especially true because I can't think of a reason to temporarily change fonts. On Sat, May 21, 2011 at 2:41 AM, Stefan L?ffler wrote: > Hi, > > On 2011-05-21 00:48, Josiah Manson wrote: >> Hi, I just wanted to report a problem with version 0.40 r.759. If I >> set the font size and type, it works just fine for the current >> instance, but is not preserved if I close and then reopen the program. > > I assume you change the font settings in "Format > Font..."? This is > intended to apply only to the current window. To set the default for all > (new) windows, please use "Edit > Preferences... > Editor". > > HTH > Stefan > From reinhard.kotucha at web.de Sat May 21 23:07:27 2011 From: reinhard.kotucha at web.de (Reinhard Kotucha) Date: Sat, 21 May 2011 23:07:27 +0200 Subject: [texworks] Font setting forgotten In-Reply-To: References: <4DD76CBB.2070606@gmail.com> Message-ID: <19928.10639.550179.146521@zaphod.ms25.net> On 2011-05-21 at 05:54:41 -0500, Josiah Manson wrote: > That was it. Thank you for your help. > > You may consider adding some warning message or doing something > else to let users know that the chance is not permanent and point > them in the right direction. It did not occur to me that I had > simply gone to the wrong menu, because everything seemed to work as > expected until I restarted the editor. This is especially true > because I can't think of a reason to temporarily change fonts. Such a warning message is certainly nice for beginners, but annoying for everybody else. Generally, if something doesn't work as expected, it should be sufficient to look into the manual. On the other hand, I don't object if a warning message pops up by default which contains a button "Don't show this message again". Of course, it's extra work for the programmers. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha at web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- From texworld at laposte.net Sun May 22 17:15:27 2011 From: texworld at laposte.net (TeXWorld) Date: Sun, 22 May 2011 17:15:27 +0200 Subject: [texworks] Feature request : switching on/off layers Message-ID: <4DD9288F.5070403@laposte.net> Hello, I often make pdf with layers. The problem is that the texworks viewer doesn't enable users to switch on or off layers as acrobat or foxit reader does. Thanks. Jack From paul.a.norman at gmail.com Mon May 23 02:57:31 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 23 May 2011 12:57:31 +1200 Subject: [texworks] Feature request : switching on/off layers In-Reply-To: <4DD9288F.5070403@laposte.net> References: <4DD9288F.5070403@laposte.net> Message-ID: Hi Jack, Are you wanting to analyse Obama's birth certificate ? :):):) http://wireupdate.com/video/2011/04/president-obamas-birth-certificate-pdf-has-layers/ On a more serious note... I do not know how much work is involved and there appeared previously to be questions here ( http://www.kdedevelopers.org/node/3328 ) on functionality: "The only limitation is that there is no easy way to know which pages are affected by toggling a layer, and that is the only problem that keeps me from adding the layer support in Okular" ... "Layer supports: Poppler now supports the layers in PDF documents, and the Qt4 frontend exposes an item model ( http://doc.trolltech.com/4.1/qabstractitemmodel.html ) for reading and manipulating the layers (enable and disable them). The only limitation is that there is no easy way to know which pages are affected by toggling a layer, and that is the only problem that keeps me from adding the layer support in Okular (a basically working patch without immediate page refreshing lies on my HD)." Haven't yet seen anything more recent yet but it might be out there somewhere... Paul On 23 May 2011 03:15, TeXWorld wrote: > Hello, > > I often make pdf with layers. The problem is that the texworks viewer > doesn't enable users to switch on or off layers as acrobat or foxit reader > does. > Thanks. > > Jack > > From paul.a.norman at gmail.com Mon May 23 23:41:06 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 24 May 2011 09:41:06 +1200 Subject: [texworks] Qt - POPPLER - and font rendering / rasterising generally Message-ID: HI, Some people may be interested in these notes on font presentation, background, history and info. Some specifc notes on Qt and Cairo and fontspec etc regarding fontrendering with poppler and Qt projects as per TeXworks.. "A Treatise on Font Rasterisation With an Emphasis on Free Software", Freddie Witherden, https://freddie.witherden.org/pages/font-rasterisation/ Paul From paul.a.norman at gmail.com Tue May 24 03:01:40 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 24 May 2011 13:01:40 +1200 Subject: [texworks] SCRIPTING: on linux say Ubuntu - script write priveledges Message-ID: Hi, Appreciate any info please from Linux user(s) on some basic questions. For reference I'm looking at Ubuntu 11.04. After setting the ppa required https://launchpad.net/~texworks/+archive/ppa, Using sudo apt-get install stuff to setup TeXworks 0.5 ver813 (works really nicely), when a user runs a Tw script from TeXworks, can the script automatically (if Tw's preferences permissions are already set) write/read to subdirectories of the Tw script's own directory? Also I have found that when logged in under the user name established during Ubuntu install, running TeXworks form a console produces a version that shows the TeXworks menu items in the new Unity top frame, however if I start TeXworks as sudo TeXworks I get a more classical looking (similar to Windows) appearance of TeXworks layout with the Tw menus in the program's own frame. What should I make of that please? Paul From paul.a.norman at gmail.com Tue May 24 03:03:33 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 24 May 2011 13:03:33 +1200 Subject: [texworks] SCRIPTING: on linux say Ubuntu - script write priveledges In-Reply-To: References: Message-ID: opps, I should have written ... " if I start TeXworks as sudo teworks" (no capitals) Paul On 24 May 2011 13:01, Paul A Norman wrote: > Hi, > > Appreciate any info please from Linux user(s) on some basic questions. > > For reference I'm looking at Ubuntu 11.04. > > After setting the ppa required > https://launchpad.net/~texworks/+archive/ppa, Using sudo apt-get > install stuff to setup TeXworks 0.5 ver813 (works really nicely), when > a user runs a Tw script from TeXworks, can the script automatically > (if Tw's preferences permissions are already set) write/read to > subdirectories of the Tw script's own directory? > > Also I have found that when logged in under the user name established > during Ubuntu install, running TeXworks form a console produces a > version that shows the TeXworks menu items in the new Unity top frame, > however if I start TeXworks as sudo TeXworks I get a more classical > looking (similar to Windows) appearance of TeXworks layout with the Tw > menus in the program's own frame. What should I make of that please? > > Paul > From gzjjgod at gmail.com Tue May 24 06:30:02 2011 From: gzjjgod at gmail.com (Jjgod Jiang) Date: Tue, 24 May 2011 06:30:02 +0200 Subject: [texworks] Qt - POPPLER - and font rendering / rasterising generally In-Reply-To: References: Message-ID: On Mon, May 23, 2011 at 11:41 PM, Paul A Norman wrote: > Some people ?may be interested in these notes on font presentation, > background, history and info. > > Some specifc notes on Qt and Cairo and fontspec etc regarding > fontrendering with poppler and Qt projects as per TeXworks.. > > "A Treatise on Font Rasterisation With an Emphasis on Free Software", > Freddie Witherden, > https://freddie.witherden.org/pages/font-rasterisation/ This article was published a while ago so some of information are not entirely accurate, for instance, since Qt 4.8 (not released yet unfortunately, but you can get the source from qt.gitorious.org), you can set the hintingPreference of a QFont to get subpixel positioned text, with NoHinting or VerticalHinting you can get the same layout result in X11, Mac OS X and Windows. See [1] for details. - Jiang [1] http://labs.qt.nokia.com/2011/03/14/hint-hint-nudge-nudge-say-no-more/ From st.loeffler at gmail.com Tue May 24 08:04:57 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Tue, 24 May 2011 08:04:57 +0200 Subject: [texworks] Feature request : switching on/off layers In-Reply-To: <4DD9288F.5070403@laposte.net> References: <4DD9288F.5070403@laposte.net> Message-ID: <4DDB4A89.5020406@gmail.com> Hi, On 2011-05-22 17:15, TeXWorld wrote: > I often make pdf with layers. The problem is that the texworks viewer > doesn't enable users to switch on or off layers as acrobat or foxit > reader does. Thanks for the suggestion - please add it to the issue list at http://code.google.com/p/texworks/issues/list. If poppler supports it (as Paul suggested), it probably can be implemented (please add Paul's links to the issue description). Note, though, that other changes to the previewer will most likely have to be implemented first... Cheers, Stefan From paul.a.norman at gmail.com Tue May 24 08:14:46 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 24 May 2011 18:14:46 +1200 Subject: [texworks] Qt - POPPLER - and font rendering / rasterising generally In-Reply-To: References: Message-ID: Thanks Jiang, That sounds very worthwhile to know in advance. Paul On 24 May 2011 16:30, Jjgod Jiang wrote: > On Mon, May 23, 2011 at 11:41 PM, Paul A Norman wrote: >> Some people ?may be interested in these notes on font presentation, >> background, history and info. >> >> Some specifc notes on Qt and Cairo and fontspec etc regarding >> fontrendering with poppler and Qt projects as per TeXworks.. >> >> "A Treatise on Font Rasterisation With an Emphasis on Free Software", >> Freddie Witherden, >> https://freddie.witherden.org/pages/font-rasterisation/ > > This article was published a while ago so some of information are not > entirely accurate, for instance, since Qt 4.8 (not released yet > unfortunately, but you can get the source from qt.gitorious.org), > you can set the hintingPreference of a QFont to get subpixel positioned > text, with NoHinting or VerticalHinting you can get the same layout > result in X11, Mac OS X and Windows. See [1] for details. > > - Jiang > > [1] http://labs.qt.nokia.com/2011/03/14/hint-hint-nudge-nudge-say-no-more/ > > From st.loeffler at gmail.com Tue May 24 08:15:32 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 24 May 2011 08:15:32 +0200 Subject: [texworks] SCRIPTING: on linux say Ubuntu - script write priveledges In-Reply-To: References: Message-ID: <4DDB4D04.6090800@gmail.com> Hi, On 2011-05-24 03:01, Paul A Norman wrote: > Appreciate any info please from Linux user(s) on some basic questions. > > For reference I'm looking at Ubuntu 11.04. Welcome to the Linux world :). > After setting the ppa required > https://launchpad.net/~texworks/+archive/ppa, Using sudo apt-get > install stuff to setup TeXworks 0.5 ver813 (works really nicely), when > a user runs a Tw script from TeXworks, can the script automatically > (if Tw's preferences permissions are already set) write/read to > subdirectories of the Tw script's own directory? Yes, that should be possible in the same way as on the other OSs by default. Of course, the user must have read/write permissions to the files and directories in question. This is required by Linux independent of Tw. Since, by default, the resources are put under the user's home directory, this shouldn't be a problem. Note, though, that resources provided by Tw typically are installed read-only (on my machine, anyway). I haven't investigated this yet, as it is not a problem for me (any noone else has complained yet ;)) - you wouldn't want to overwrite "official" files, anyway, would you? > Also I have found that when logged in under the user name established > during Ubuntu install, running TeXworks form a console produces a > version that shows the TeXworks menu items in the new Unity top frame, > however if I start TeXworks as sudo TeXworks I get a more classical > looking (similar to Windows) appearance of TeXworks layout with the Tw > menus in the program's own frame. What should I make of that please? Interesting, I haven't noticed this before, but I can confirm it. Is there a special reason to run Tw with sudo (normally, one wouldn't; btw, GUI applications should be run with gksudo, but this doesn't change the effect)? I tried with other Qt/KDE applications as well (kcalc, kdenlive), and they exhibit the same problem. So I'd say this is a problem with the interaction Qt-unity as the root user. Did you try creating a new user (different from the one created during installation) and running Tw or other Qt/KDE apps there? Cheers, Stefan From paul.a.norman at gmail.com Tue May 24 09:08:52 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 24 May 2011 19:08:52 +1200 Subject: [texworks] SCRIPTING: on linux say Ubuntu - script write priveledges In-Reply-To: <4DDB4D04.6090800@gmail.com> References: <4DDB4D04.6090800@gmail.com> Message-ID: On 24 May 2011 18:15, Stefan L?ffler wrote: > Hi, > > On 2011-05-24 03:01, Paul A Norman wrote: >> Appreciate any info please from Linux user(s) on some basic questions. >> >> For reference I'm looking at Ubuntu 11.04. > > Welcome to the Linux world :). Thnx :) Been in and out of it for years - had always wanted to be in a position to just use it only, used to use a little Kylix, then Lazarus now, but as to being able to be based on Linux only ... alas not yet ... We do have one dedicated box for visitors here to use, rest is dual boot or VMs regrettably. Remember when everyone was just trying to get X Windows servers to work ~~ oops ... then RedHat was it for a while ... Now various Linux distributions will give any OS a run for their money! -- I mean license ... I really like Ubuntu family K- and X- .. as well. Been able to setup old machines and get more life out of them .... Would look to putting current Xp systems into sandboxed VBoxes under say Ubuntu when the time for Xp expires... > >> After setting the ppa required >> https://launchpad.net/~texworks/+archive/ppa, Using sudo apt-get >> install stuff to setup TeXworks 0.5 ver813 (works really nicely), when >> a user runs a Tw script from TeXworks, can the script automatically >> (if Tw's preferences permissions are already set) write/read to >> subdirectories of the Tw script's own directory? > > Yes, that should be possible in the same way as on the other OSs by default. > > Of course, the user must have read/write permissions to the files and > directories in question. This is required by Linux independent of Tw. > Since, by default, the resources are put under the user's home > directory, this shouldn't be a problem. Ok, please see point below. This is leading to what I am thinking about. > Note, though, that resources > provided by Tw typically are installed read-only (on my machine, > anyway). I haven't investigated this yet, as it is not a problem for me > (any noone else has complained yet ;)) - you wouldn't want to overwrite > "official" files, anyway, would you? > > >> Also I have found that when logged in under the user name established >> during Ubuntu install, running TeXworks form a console produces a >> version that shows the TeXworks menu items in the new Unity top frame, >> however if I start TeXworks as sudo TeXworks I get a more classical >> looking (similar to Windows) appearance of TeXworks layout with the Tw >> menus in the program's own frame. What should I make of that please? > > Interesting, I haven't noticed this before, but I can confirm it. Is > there a special reason to run Tw with sudo (normally, one wouldn't; btw, > GUI applications should be run with gksudo, but this doesn't change the > effect)? > I tried with other Qt/KDE applications as well (kcalc, kdenlive), and > they exhibit the same problem. So I'd say this is a problem with the > interaction Qt-unity as the root user. Did you try creating a new user > (different from the one created during installation) and running Tw or > other Qt/KDE apps there? Well this is where I am at... Using a new user, would require that the scripts were copied to their (new) home directory? Or what happens to Linux file permissions, or does TeXworks install as it's own group with linux file permissions to everyone or as its in HOME/USER obviously then scripts are limited to that User? That's when/why I started looking at sudo - thanks for note on gksudo, it floats back into memory dimmly :) (I like Jamie's comment when talking about gksudo , "...Man pages are extremely useful for this kind of thing, a lot of the time they seem to contain gibberish or language that only experienced unix/linux sysadmins can understand, but this really just depends on the author. ... https://lists.ubuntu.com/archives/ubuntu-studio-users/2007-September/000472.html) In some educational situations say, and in other shared circumstances, does each User maintain their own Script folder (yes), or/and can an administrator set up a central Tw script repository on each PC, or preferably even for a whole local network? Thanks, paul > > Cheers, > Stefan > From marco.canini at gmail.com Tue May 24 16:22:09 2011 From: marco.canini at gmail.com (Marco Canini) Date: Tue, 24 May 2011 16:22:09 +0200 Subject: [texworks] do scripts support context menus? Message-ID: Hello, I would like to make a script that when I right click on a \input{...} command it shows an 'Open file' in the context menu. Is that doable with the current API (0.4 r759)? I reckon implementing the same functionality triggered by CTRL + left click or double click on the \input{...} command would be more complex and the API doesn't support that. Am I right? Thanks -- Marco Canini From paul.a.norman at gmail.com Wed May 25 01:25:04 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 25 May 2011 11:25:04 +1200 Subject: [texworks] do scripts support context menus? In-Reply-To: References: Message-ID: Hi Marco, AFAIK at present there is no way to directly use an altered context menu with scripting, but it has been sort of potentially flagged as a possibility. You may be able to connect mouse clicks to an editor window using hooks, but I do not know how stable that would be, and Stefan provided notes in November 2010, that suggested that meanwhile those parts of the Tw scripting api should be left alone - you can look through http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm and the chm download version http://twscript.paulanorman.com/docs/ for "TeXworks Script Api functions and properties" There was a detailed discussion back in April last year including this... > > 5) Introduce a new script type ("multi", "mixed", ... ideas welcome) > that defines only functions. There is one special function (e.g. > init()) > that gets called when the TWScript object is created. Its purpose > is to > register menu items, toolbar items, hooks, ... (whatever comes to > mind). > Each of them gets connected to a function provided by the script. > > http://tug.org/mailman/htdig/texworks/2010q2/002685.html And another discussion involving me where adding the whole script menu to the rightcontext menu was mooted. Perhaps there could be new part of script header (or just altering the current // Context: operatoin) that indicates which menus a script should appear in? Then using the same kind of business logic as presntly, it and its directory folder only appear in menus indicated as is currently done? (Even if you have a directory under scripts it is not added to the Script menu unless it has a valid Tw .qt or .js .py .lua in it.) Possibly something like altering // Context: current options to have the current settings to continue to refer to their current main menu locations (supports legacy scripts), and instead of C++ looking for a single option here currently PDFDocument or TeXDocument It could look for one or more collection members instead and apply all choices present, perhaps two additional memebers of such a collection - PDFDocument-ContextMenu and TeXDocument-ContextMenu So the script header portion could sometimes look like this for some reason ... // Context: TeXDocument TeXDocument-ContextMenu PDFDocument-ContextMenu And so on. You may find from what Stefan and Jonathan have already flagged in older threads, that there are better plans - much more wide sweeping as well (positioned menu subtrees buttons toolbars etc ...). Paul On 25 May 2011 02:22, Marco Canini wrote: > Hello, > > I would like to make a script that when I right click on a \input{...} > command it shows an 'Open file' in the context menu. Is that doable > with the current API (0.4 r759)? > I reckon implementing the same functionality triggered by CTRL + left > click or double click on the \input{...} command would be more complex > and the API doesn't support that. Am I right? > > Thanks > > -- > Marco Canini > From marco.canini at gmail.com Wed May 25 13:25:27 2011 From: marco.canini at gmail.com (Marco Canini) Date: Wed, 25 May 2011 13:25:27 +0200 Subject: [texworks] do scripts support context menus? In-Reply-To: References: Message-ID: Paul, thanks for the info. Perhaps something that would still satisfy me is the ability to associate a shortcut to a script. Can that be done? Cheers On Wed, May 25, 2011 at 1:25 AM, Paul A Norman wrote: > Hi Marco, > > AFAIK at present there is no way to directly use an altered context > menu with scripting, but it has been sort of potentially flagged as a > possibility. > > You may be able to connect mouse clicks to an editor window using > hooks, but I do not know how stable that would be, and Stefan provided > notes in November 2010, that suggested that meanwhile those parts of > the Tw scripting api should be left alone - you can look through > http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm and > the chm download version http://twscript.paulanorman.com/docs/ ?for > "TeXworks Script Api functions and properties" > > There was a detailed discussion back in April last year including this... > >> >> ? ? 5) Introduce a new script type ("multi", "mixed", ... ideas welcome) >> ? ? that defines only functions. There is one special function (e.g. >> ? ? init()) >> ? ? that gets called when the TWScript object is created. Its purpose >> ? ? is to >> ? ? register menu items, toolbar items, hooks, ... (whatever comes to >> ? ? mind). >> ? ? Each of them gets connected to a function provided by the script. >> >> > > http://tug.org/mailman/htdig/texworks/2010q2/002685.html > > And another discussion involving me where adding the whole script menu > to the rightcontext menu was mooted. > > > > Perhaps there could be new part of script header (or just altering the > current // Context: operatoin) that indicates which menus a script > should appear in? > > Then using the same kind of business logic as presntly, it and its > directory folder only appear in menus indicated as is currently done? > (Even if you have a directory under scripts it is not added to the > Script menu unless it has a valid Tw .qt or .js .py .lua in it.) > > Possibly something like altering // Context: ?current options to have > the current settings to continue to refer to their current main menu > locations (supports legacy scripts), and instead of C++ looking for a > single option here currently > > PDFDocument or TeXDocument > > It could look for one or more collection members instead and apply all > choices present, perhaps two additional memebers of such a collection > - PDFDocument-ContextMenu ?and TeXDocument-ContextMenu > > So the script header portion could sometimes look like this for some reason ... > > // Context: TeXDocument ?TeXDocument-ContextMenu ?PDFDocument-ContextMenu > > And so on. > > > > You may find from what Stefan and Jonathan have already flagged in > older threads, that there are better plans - much more wide sweeping > as well (positioned menu subtrees buttons toolbars etc ...). > > Paul > > > On 25 May 2011 02:22, Marco Canini wrote: >> Hello, >> >> I would like to make a script that when I right click on a \input{...} >> command it shows an 'Open file' in the context menu. Is that doable >> with the current API (0.4 r759)? >> I reckon implementing the same functionality triggered by CTRL + left >> click or double click on the \input{...} command would be more complex >> and the API doesn't support that. Am I right? >> >> Thanks >> >> -- >> Marco Canini >> > -- Marco Canini From henrikmidtiby at gmail.com Wed May 25 13:29:07 2011 From: henrikmidtiby at gmail.com (Henrik Skov Midtiby) Date: Wed, 25 May 2011 13:29:07 +0200 Subject: [texworks] do scripts support context menus? In-Reply-To: References: Message-ID: Hi Marco, To insert a shortcut to a script is very easy. Simply insert a line like // Shortcut: Ctrl+M in one of the first lines in the script file. Then the script can be activated with the shortcut Crtl + M Henrik On 25 May 2011 13:25, Marco Canini wrote: > Paul, > > thanks for the info. Perhaps something that would still satisfy me is > the ability to associate a shortcut to a script. Can that be done? > Cheers > > On Wed, May 25, 2011 at 1:25 AM, Paul A Norman wrote: >> Hi Marco, >> >> AFAIK at present there is no way to directly use an altered context >> menu with scripting, but it has been sort of potentially flagged as a >> possibility. >> >> You may be able to connect mouse clicks to an editor window using >> hooks, but I do not know how stable that would be, and Stefan provided >> notes in November 2010, that suggested that meanwhile those parts of >> the Tw scripting api should be left alone - you can look through >> http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm and >> the chm download version http://twscript.paulanorman.com/docs/ ?for >> "TeXworks Script Api functions and properties" >> >> There was a detailed discussion back in April last year including this... >> >>> >>> ? ? 5) Introduce a new script type ("multi", "mixed", ... ideas welcome) >>> ? ? that defines only functions. There is one special function (e.g. >>> ? ? init()) >>> ? ? that gets called when the TWScript object is created. Its purpose >>> ? ? is to >>> ? ? register menu items, toolbar items, hooks, ... (whatever comes to >>> ? ? mind). >>> ? ? Each of them gets connected to a function provided by the script. >>> >>> >> >> http://tug.org/mailman/htdig/texworks/2010q2/002685.html >> >> And another discussion involving me where adding the whole script menu >> to the rightcontext menu was mooted. >> >> >> >> Perhaps there could be new part of script header (or just altering the >> current // Context: operatoin) that indicates which menus a script >> should appear in? >> >> Then using the same kind of business logic as presntly, it and its >> directory folder only appear in menus indicated as is currently done? >> (Even if you have a directory under scripts it is not added to the >> Script menu unless it has a valid Tw .qt or .js .py .lua in it.) >> >> Possibly something like altering // Context: ?current options to have >> the current settings to continue to refer to their current main menu >> locations (supports legacy scripts), and instead of C++ looking for a >> single option here currently >> >> PDFDocument or TeXDocument >> >> It could look for one or more collection members instead and apply all >> choices present, perhaps two additional memebers of such a collection >> - PDFDocument-ContextMenu ?and TeXDocument-ContextMenu >> >> So the script header portion could sometimes look like this for some reason ... >> >> // Context: TeXDocument ?TeXDocument-ContextMenu ?PDFDocument-ContextMenu >> >> And so on. >> >> >> >> You may find from what Stefan and Jonathan have already flagged in >> older threads, that there are better plans - much more wide sweeping >> as well (positioned menu subtrees buttons toolbars etc ...). >> >> Paul >> >> >> On 25 May 2011 02:22, Marco Canini wrote: >>> Hello, >>> >>> I would like to make a script that when I right click on a \input{...} >>> command it shows an 'Open file' in the context menu. Is that doable >>> with the current API (0.4 r759)? >>> I reckon implementing the same functionality triggered by CTRL + left >>> click or double click on the \input{...} command would be more complex >>> and the API doesn't support that. Am I right? >>> >>> Thanks >>> >>> -- >>> Marco Canini >>> >> > > > > -- > Marco Canini > > From paul.a.norman at gmail.com Wed May 25 13:40:06 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 25 May 2011 23:40:06 +1200 Subject: [texworks] do scripts support context menus? In-Reply-To: References: Message-ID: Paul You can also have a look at http://code.google.com/p/texworks/issues/detail?id=261#c41 helps correctly generate a new script correctly. You can alter the script to put things on the clipboard instead of inserting into a Tw document, And also perhaps at the top headings: Getting Started, Scripts Basics, TeXworks as a QtScript editor, Script Authoring on http://twscript.paulanorman.info/docs/html/TexWorksQtScripting.htm Paul On 25 May 2011 23:29, Henrik Skov Midtiby wrote: > Hi Marco, > > To insert a shortcut to a script is very easy. Simply insert a line like > > // Shortcut: Ctrl+M > > in one of the first lines in the script file. > Then the script can be activated with the shortcut Crtl + M > > Henrik > > On 25 May 2011 13:25, Marco Canini wrote: >> Paul, >> >> thanks for the info. Perhaps something that would still satisfy me is >> the ability to associate a shortcut to a script. Can that be done? >> Cheers >> >> On Wed, May 25, 2011 at 1:25 AM, Paul A Norman wrote: >>> Hi Marco, >>> >>> AFAIK at present there is no way to directly use an altered context >>> menu with scripting, but it has been sort of potentially flagged as a >>> possibility. >>> >>> You may be able to connect mouse clicks to an editor window using >>> hooks, but I do not know how stable that would be, and Stefan provided >>> notes in November 2010, that suggested that meanwhile those parts of >>> the Tw scripting api should be left alone - you can look through >>> http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm and >>> the chm download version http://twscript.paulanorman.com/docs/ ?for >>> "TeXworks Script Api functions and properties" >>> >>> There was a detailed discussion back in April last year including this... >>> >>>> >>>> ? ? 5) Introduce a new script type ("multi", "mixed", ... ideas welcome) >>>> ? ? that defines only functions. There is one special function (e.g. >>>> ? ? init()) >>>> ? ? that gets called when the TWScript object is created. Its purpose >>>> ? ? is to >>>> ? ? register menu items, toolbar items, hooks, ... (whatever comes to >>>> ? ? mind). >>>> ? ? Each of them gets connected to a function provided by the script. >>>> >>>> >>> >>> http://tug.org/mailman/htdig/texworks/2010q2/002685.html >>> >>> And another discussion involving me where adding the whole script menu >>> to the rightcontext menu was mooted. >>> >>> >>> >>> Perhaps there could be new part of script header (or just altering the >>> current // Context: operatoin) that indicates which menus a script >>> should appear in? >>> >>> Then using the same kind of business logic as presntly, it and its >>> directory folder only appear in menus indicated as is currently done? >>> (Even if you have a directory under scripts it is not added to the >>> Script menu unless it has a valid Tw .qt or .js .py .lua in it.) >>> >>> Possibly something like altering // Context: ?current options to have >>> the current settings to continue to refer to their current main menu >>> locations (supports legacy scripts), and instead of C++ looking for a >>> single option here currently >>> >>> PDFDocument or TeXDocument >>> >>> It could look for one or more collection members instead and apply all >>> choices present, perhaps two additional memebers of such a collection >>> - PDFDocument-ContextMenu ?and TeXDocument-ContextMenu >>> >>> So the script header portion could sometimes look like this for some reason ... >>> >>> // Context: TeXDocument ?TeXDocument-ContextMenu ?PDFDocument-ContextMenu >>> >>> And so on. >>> >>> >>> >>> You may find from what Stefan and Jonathan have already flagged in >>> older threads, that there are better plans - much more wide sweeping >>> as well (positioned menu subtrees buttons toolbars etc ...). >>> >>> Paul >>> >>> >>> On 25 May 2011 02:22, Marco Canini wrote: >>>> Hello, >>>> >>>> I would like to make a script that when I right click on a \input{...} >>>> command it shows an 'Open file' in the context menu. Is that doable >>>> with the current API (0.4 r759)? >>>> I reckon implementing the same functionality triggered by CTRL + left >>>> click or double click on the \input{...} command would be more complex >>>> and the API doesn't support that. Am I right? >>>> >>>> Thanks >>>> >>>> -- >>>> Marco Canini >>>> >>> >> >> >> >> -- >> Marco Canini >> >> > > From texworld at laposte.net Wed May 25 18:15:18 2011 From: texworld at laposte.net (TeXWorld) Date: Wed, 25 May 2011 18:15:18 +0200 Subject: [texworks] Feature request : switching on/off layers In-Reply-To: <4DDB4A89.5020406@gmail.com> References: <4DD9288F.5070403@laposte.net> <4DDB4A89.5020406@gmail.com> Message-ID: <4DDD2B16.5040204@laposte.net> Ok, it's done. Jack Le 24/05/2011 08:04, Stefan L?ffler a ?crit : > Hi, > > On 2011-05-22 17:15, TeXWorld wrote: >> I often make pdf with layers. The problem is that the texworks viewer >> doesn't enable users to switch on or off layers as acrobat or foxit >> reader does. > Thanks for the suggestion - please add it to the issue list at > http://code.google.com/p/texworks/issues/list. If poppler supports it > (as Paul suggested), it probably can be implemented (please add Paul's > links to the issue description). Note, though, that other changes to the > previewer will most likely have to be implemented first... > > Cheers, > Stefan > > From st.loeffler at gmail.com Wed May 25 20:47:15 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Wed, 25 May 2011 20:47:15 +0200 Subject: [texworks] SCRIPTING: on linux say Ubuntu - script write priveledges In-Reply-To: References: <4DDB4D04.6090800@gmail.com> Message-ID: <4DDD4EB3.8030709@gmail.com> Hi, On 2011-05-24 09:08, Paul A Norman wrote: > > > > Would look to putting current Xp systems into sandboxed VBoxes under > say Ubuntu when the time for Xp expires... The time for XP has expired, hasn't it? (mainstream support ended in 2009, anyway) FWIW, running XP under VirtualBox on Ubuntu works. Whether it works well depends on your system, processor, and its ability for virtualization. On my PC at work, things slow down horribly when running VBox, on my laptop at home it works quite well (though I still wouldn't try to play games on it ;)). > > >>> After setting the ppa required >>> https://launchpad.net/~texworks/+archive/ppa, Using sudo apt-get >>> install stuff to setup TeXworks 0.5 ver813 (works really nicely), when >>> a user runs a Tw script from TeXworks, can the script automatically >>> (if Tw's preferences permissions are already set) write/read to >>> subdirectories of the Tw script's own directory? >> Yes, that should be possible in the same way as on the other OSs by default. >> >> Of course, the user must have read/write permissions to the files and >> directories in question. This is required by Linux independent of Tw. >> Since, by default, the resources are put under the user's home >> directory, this shouldn't be a problem. > Ok, please see point below. This is leading to what I am thinking about. > >> Note, though, that resources >> provided by Tw typically are installed read-only (on my machine, >> anyway). I haven't investigated this yet, as it is not a problem for me >> (any noone else has complained yet ;)) - you wouldn't want to overwrite >> "official" files, anyway, would you? >> >> >>> Also I have found that when logged in under the user name established >>> during Ubuntu install, running TeXworks form a console produces a >>> version that shows the TeXworks menu items in the new Unity top frame, >>> however if I start TeXworks as sudo TeXworks I get a more classical >>> looking (similar to Windows) appearance of TeXworks layout with the Tw >>> menus in the program's own frame. What should I make of that please? >> Interesting, I haven't noticed this before, but I can confirm it. Is >> there a special reason to run Tw with sudo (normally, one wouldn't; btw, >> GUI applications should be run with gksudo, but this doesn't change the >> effect)? >> I tried with other Qt/KDE applications as well (kcalc, kdenlive), and >> they exhibit the same problem. So I'd say this is a problem with the >> interaction Qt-unity as the root user. Did you try creating a new user >> (different from the one created during installation) and running Tw or >> other Qt/KDE apps there? I tried the new user thing myself, it seems the behavior is exactly the same as with the "default" (i.e., created during installation) user. So, this indeed seems to be a Qt/unity bug. Since you found it, I leave it to you to report it (try `ubuntu-bug unity` on the command line) if you want to. > Well this is where I am at... > > Using a new user, would require that the scripts were copied to their > (new) home directory? Yes. The bundled scripts (and other resources) are installed automatically when the user runs Tw for the first time. But other scripts would need to be copied/linked manually. > Or what happens to Linux file permissions, or does TeXworks install as > it's own group with linux file permissions to everyone or as its in > HOME/USER obviously then scripts are limited to that User? Tw should install scripts with the permissions of the user it was run by (i.e., either the current user or root). It seems files are created with read permission for everyone, write and execute permissions for no one. User and group are set to the ones of the user that ran Tw. > That's when/why I started looking at sudo - thanks for note on gksudo, > it floats back into memory dimmly :) There's really no need for that, as everyone gets the same permissions. In fact, it will probably create the files with user and group root, which means that it's harder to change permissions (e.g., if you want to change a script). > (I like Jamie's comment when talking about gksudo , "...Man pages are > extremely useful for this kind of thing, a lot of the time > they seem to contain gibberish or language that only experienced > unix/linux sysadmins can understand, but this really just depends on > the author. ... > https://lists.ubuntu.com/archives/ubuntu-studio-users/2007-September/000472.html) How true... In fact, I don't understand the differences myself, I just read about it somewhere and thought that there probably is a (good?) reason for it ;). > In some educational situations say, and in other shared > circumstances, does each User maintain their own Script folder (yes), > or/and can an administrator set up a central Tw script repository on > each PC, or preferably even for a whole local network? Partly global setups are not supported at the moment. Basically, this is because there's no waterproof concept yet how to "merge" global and local settings. For instance, how to distinguish (easily) between a sys-admin wanting to override user settings (e.g., for security reasons) and one wanting to provide sensible defaults for the user to customize? That said, the texworks-setup.ini approach still works (you can put it alongside the texworks binary; in the ppa install, this would be in /usr/bin/). This way, all users could use the same resources (preferably not in /usr/bin, but instead maybe in /etc/texworks or /var/texworks or something of the sort). HTH Stefan From paul.a.norman at gmail.com Thu May 26 02:52:30 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 26 May 2011 12:52:30 +1200 Subject: [texworks] SCRIPTING: on linux say Ubuntu - script write priveledges In-Reply-To: <4DDD4EB3.8030709@gmail.com> References: <4DDB4D04.6090800@gmail.com> <4DDD4EB3.8030709@gmail.com> Message-ID: Dear Stefan, Thanks for that comprehensive answer. On 26 May 2011 06:47, Stefan L?ffler wrote: > Hi, > > On 2011-05-24 09:08, Paul A Norman wrote: >> >> >> >> Would look to putting current Xp systems into sandboxed VBoxes under >> say Ubuntu when the time for Xp expires... > > The time for XP has expired, hasn't it? (mainstream support ended in > 2009, anyway) Its the security updates that are yet to finish (thats what is the decider in a sense) and that may have been flagged by the announcement by Balmer of Windows 8 in the last coupls of days http://www.techspot.com/news/43917-microsoft-ceo-finally-talks-windows-8-slates-it-for-2012.html which got me thinking again. > FWIW, running XP under VirtualBox on Ubuntu works. Whether it works well > depends on your system, processor, and its ability for virtualization. > On my PC at work, things slow down horribly when running VBox, on my > laptop at home it works quite well (though I still wouldn't try to play > games on it ;)). Good to know. Strangely (to some) I've never got into games !) > >> >> >>>> After setting the ppa required >>>> https://launchpad.net/~texworks/+archive/ppa, Using sudo apt-get >>>> install stuff to setup TeXworks 0.5 ver813 (works really nicely), when >>>> a user runs a Tw script from TeXworks, can the script automatically >>>> (if Tw's preferences permissions are already set) write/read to >>>> subdirectories of the Tw script's own directory? >>> Yes, that should be possible in the same way as on the other OSs by default. >>> >>> Of course, the user must have read/write permissions to the files and >>> directories in question. This is required by Linux independent of Tw. >>> Since, by default, the resources are put under the user's home >>> directory, this shouldn't be a problem. >> Ok, please see point below. This is leading to what I am thinking about. >> >>> ?Note, though, that resources >>> provided by Tw typically are installed read-only (on my machine, >>> anyway). I haven't investigated this yet, as it is not a problem for me >>> (any noone else has complained yet ;)) - you wouldn't want to overwrite >>> "official" files, anyway, would you? >>> >>> >>>> Also I have found that when logged in under the user name established >>>> during Ubuntu install, running TeXworks form a console produces a >>>> version that shows the TeXworks menu items in the new Unity top frame, >>>> however if I start TeXworks as sudo TeXworks I get a more classical >>>> looking (similar to Windows) appearance of TeXworks layout with the Tw >>>> menus in the program's own frame. What should I make of that please? >>> Interesting, I haven't noticed this before, but I can confirm it. Is >>> there a special reason to run Tw with sudo (normally, one wouldn't; btw, >>> GUI applications should be run with gksudo, but this doesn't change the >>> effect)? >>> I tried with other Qt/KDE applications as well (kcalc, kdenlive), and >>> they exhibit the same problem. So I'd say this is a problem with the >>> interaction Qt-unity as the root user. Did you try creating a new user >>> (different from the one created during installation) and running Tw or >>> other Qt/KDE apps there? > > I tried the new user thing myself, it seems the behavior is exactly the > same as with the "default" (i.e., created during installation) user. So, > this indeed seems to be a Qt/unity bug. Since you found it, I leave it > to you to report it (try `ubuntu-bug unity` on the command line) if you > want to. Done - hadn't logged in there since 2009 it seems! >> Well this is where I am at... >> >> Using a new user, would require that the scripts were copied to their >> (new) home directory? > > Yes. The bundled scripts (and other resources) are installed > automatically when the user runs Tw for the first time. But other > scripts would need to be copied/linked manually. > >> Or what happens to Linux file permissions, or does TeXworks install as >> it's own group with linux file permissions to everyone or as its in >> HOME/USER obviously then scripts are limited to that User? > > Tw should install scripts with the permissions of the user it was run by > (i.e., either the current user or root). It seems files are created with > read permission for everyone, write and execute permissions for no one. > User and group are set to the ones of the user that ran Tw. > >> That's when/why I started looking at sudo - thanks for note on gksudo, >> it floats back into memory dimmly :) > > There's really no need for that, as everyone gets the same permissions. > In fact, it will probably create the files with user and group root, > which means that it's harder to change permissions (e.g., if you want to > change a script). > >> (I like Jamie's comment when talking about gksudo , "...Man pages are >> extremely useful for this kind of thing, a lot of the time >> they seem to contain gibberish or language that only experienced >> unix/linux sysadmins can understand, but this really just depends on >> the author. ... >> https://lists.ubuntu.com/archives/ubuntu-studio-users/2007-September/000472.html) > > How true... > In fact, I don't understand the differences myself, I just read about it > somewhere and thought that there probably is a (good?) reason for it ;). > >> In some educational situations say, and ?in other shared >> circumstances, does each User maintain their own Script folder (yes), >> or/and can an administrator set up a central Tw script repository on >> each PC, or preferably even for a whole local network? > > Partly global setups are not supported at the moment. Basically, this is > because there's no waterproof concept yet how to "merge" global and > local settings. For instance, how to distinguish (easily) between a > sys-admin wanting to override user settings (e.g., for security reasons) > and one wanting to provide sensible defaults for the user to customize? > I understand the maze of thought. Perhaps the sword (or razor) of simplicity here ... May need two concurrent branches of Tw for the futurre? (Perhaps achieved by whether a .so .dll plugin is present or not on the main server?) A full bodied personal version of Tw, and an Administrator's roll out version - with special features for administration etc..? > That said, the texworks-setup.ini approach still works (you can put it > alongside the texworks binary; in the ppa install, this would be in > /usr/bin/). This way, all users could use the same resources (preferably > not in /usr/bin, but instead maybe in /etc/texworks or /var/texworks or > something of the sort). Ok. This overall, at present, this all sorts of rules out doing ppa packages for bundles of scripts in a way? Wouldn't be sure where to place them. So would Tw (over long term development) respect a network UNC type path for scripts' location? (local network centralised repository), would I run into a nightmare of permissions issues even trying to get such a networked located script to operate on a User's home directory? Have been wondering to myself over the last year and a bit (trying to balance Windows and Linux etc usage) if a simple script reposirtories/down loader/installer/maintainer is needed in Tw itself? Where by a user can nominate sites they want to download and maintain scripts from, perhaps as a set format in zip modules contained in set directory structures on script sites (which could be a local network repository). Sort of raises itself a bit again with this discussion. Paul > > HTH > Stefan > From chuck at sharpsteen.net Thu May 26 07:54:56 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Wed, 25 May 2011 22:54:56 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig (was: Another TeXworks mac build (with a buildsystem!)) In-Reply-To: <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> Message-ID: On Mon, May 16, 2011 at 4:34 AM, Jonathan Kew wrote: > > On 15 May 2011, at 13:10, Stefan L?ffler wrote: > >> Hi, >> >> On 2011-05-13 06:35, Charlie Sharpsteen wrote: >>> I could add a file to the TeXworks source that apackager could use to >>> install Poppler thusly: >>> >>> ? ?brew install --with-qt4 --enable-xpdf-headers cmake/packaging/mac/poppler.rb >>> >>> And the patches in `lib-patches` would be applied automatically. >> >> Sounds good to me. It's really just the poppler-qt4-globalparams.patch, >> as poppler-win32-font-handling.patch only applies to Windows-specific files. >> >>> So, I guess the question is---how badly do we want to get rid of >>> Fontconfig? Leaving it in is starting to look like the easiest course >>> of action on OS X. >> >> This is up to Jonathan Kew to decide (I explicitly CC'ed him to this >> mail, hopefully he'll reply), as he set up the original "no-fontconfig" >> policy. Not being a Mac developer or user myself, I can only abide by >> the judgment of those who must live with the consequences (whatever they >> may be). > > There are a few questions that I think need answering before making a definite statement here. > > Does the fontconfig-based build recognize the correct collection of installed fonts (so that PDFs that use any of those fonts, and don't have them embedded, will display as expected on the user's system)? On my laptop here, I notice that the list of fonts shown by fc-list in the Terminal does *not* seem to match the list displayed by Apple's ftxinstalledfonts (from the Apple Font Tool suite), so I'm a bit suspicious that the two "worlds" are not necessarily kept in sync properly. > > Does this version of fontconfig work without adding cache files to each font directory that it scans? It used to do that, but perhaps Apple has customized it so as to avoid this, or at least make the cache files invisible? (I didn't see font cache files on my laptop, so I think this issue may have been solved.) > > What happens if the TeXworks user doesn't have the X11 package installed? At least on older OS versions, it was a non-default optional install, so IMO an application like TW that aims to be a Mac OS app (rather than an X11 app) should not depend on it. > > JK I have been tinkering with this for a while and here is what I've been able to learn: - As of OS X 10.5.0, X11 is installed by default. A user has to go out of their way to disable X11 during installation. - CMake copies all dynamic libraries that are external dependencies of TeXworks into the .app bundle during packaging. An external dependency is defined as any library discovered by `otool -L` that is not in `/usr/lib` or part of a framework in `/System/Library/Frameworks`. As far as I can tell, this version of Fontconfig does not leave any "droppings" in ~/Library/Fonts or /System/Library/Fonts or /Library/Fonts. - If I do install OS X without X11, my builds of TeXworks will still run but the viewer fails to display `base-14-fonts.pdf` correctly. If I copy the contents of `/usr/X11/lib/X11/fonts` and `/usr/X11/lib/X11/fontconfig` over to the new machine, then things work better but there are still some failures in the Symbol and ZapfDingbats fonts. So, Poppler does indeed depend on more than fontconfig.dylib if PDF files without embedded fonts are to be displayed correctly. Here is what `base-14-fonts.pdf` looks like on a machine with X11 fonts: http://i.imgur.com/DW1yG.png Here is what it looks like on a machine without X11 fonts: http://i.imgur.com/Atlmj.png Re-building Poppler to use Quartz font handling took some doing, but here are the results on a machine without X11 fonts: http://i.imgur.com/SV6WG.png Applying the patches to Poppler and re-running autoconf is a bit of a maintenance burden. If we do decide to drop fontconfig from the mac build, I would suggest re-submitting the patches to the Poppler project as having Quartz font support in the official source would dramatically cut down the amount of maintenance we would have to do. -Charlie From jfkthame at googlemail.com Thu May 26 12:03:01 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Thu, 26 May 2011 11:03:01 +0100 Subject: [texworks] Mac OS TeXworks + fontconfig (was: Another TeXworks mac build (with a buildsystem!)) In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> Message-ID: On 26 May 2011, at 06:54, Charlie Sharpsteen wrote: > > Here is what `base-14-fonts.pdf` looks like on a machine with X11 fonts: > > http://i.imgur.com/DW1yG.png > Re-building Poppler to use Quartz font handling took some doing, but > here are the results on a machine without X11 fonts: > > http://i.imgur.com/SV6WG.png Interesting.... neither of these is entirely successful. (Thanks VERY much for your building and testing efforts!) The fontconfig/X11-fonts version fails to handle Helvetica Bold [Oblique], it just renders the non-bold faces. (And it's got a .notdef glyph in place of the "mu" in the middle of the Symbol line. That's probably an encoding mismatch related the "micro" symbol and the Greek letter "mu".) Meanwhile, the Quartz one gets Helvetica right, but doesn't find either Symbol or ZapfDingbats, and just falls back to Helvetica glyphs for both of those lines. I don't recall the details of the patch for finding Quartz fonts, but maybe this could be fixed? JK From chuck at sharpsteen.net Thu May 26 22:32:29 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 26 May 2011 13:32:29 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig (was: Another TeXworks mac build (with a buildsystem!)) In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> Message-ID: On Thu, May 26, 2011 at 3:03 AM, Jonathan Kew wrote: > On 26 May 2011, at 06:54, Charlie Sharpsteen wrote: > >> >> Here is what `base-14-fonts.pdf` looks like on a machine with X11 fonts: >> >> ? ?http://i.imgur.com/DW1yG.png > >> Re-building Poppler to use Quartz font handling took some doing, but >> here are the results on a machine without X11 fonts: >> >> ? ?http://i.imgur.com/SV6WG.png > > Interesting.... neither of these is entirely successful. (Thanks VERY much for your building and testing efforts!) The fontconfig/X11-fonts version fails to handle Helvetica Bold [Oblique], it just renders the non-bold faces. (And it's got a .notdef glyph in place of the "mu" in the middle of the Symbol line. That's probably an encoding mismatch related the "micro" symbol and the Greek letter "mu".) > > Meanwhile, the Quartz one gets Helvetica right, but doesn't find either Symbol or ZapfDingbats, and just falls back to Helvetica glyphs for both of those lines. I don't recall the details of the patch for finding Quartz fonts, but maybe this could be fixed? > > JK I could take a look at the font patch to see what needs to be fixed, but I have never really dug into the guts of any font handling system so it would probably take a while. One interesting thing I noted is that Poppler needs to be build with the "splash" backend enabled in order to get any font output at all. -Charlie From st.loeffler at gmail.com Fri May 27 08:01:19 2011 From: st.loeffler at gmail.com (=?ISO-8859-15?Q?Stefan_L=F6ffler?=) Date: Fri, 27 May 2011 08:01:19 +0200 Subject: [texworks] 0.4.1 released Message-ID: <4DDF3E2F.7000806@gmail.com> Hi, I only want to spread the word that 0.4.1 is released. As a bugfix release, it is not a milestone, but it should smooth some rough edges, fix some bugs, and even introduce a few minor new features. The primary intention of this release was to wrap up all the improvements of the last couple of weeks, and to give the TeXLive team a good basis for their upcoming pre-release testing. If you've kept up to date with the development branch (0.5), there is no need to switch to 0.4.1, as it is based entirely on 0.5. Thanks for all the great support! -Stefan L?ffler From chuck at sharpsteen.net Fri May 27 23:57:00 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Fri, 27 May 2011 14:57:00 -0700 Subject: [texworks] 0.4.1 released In-Reply-To: <4DDF3E2F.7000806@gmail.com> References: <4DDF3E2F.7000806@gmail.com> Message-ID: On Thu, May 26, 2011 at 11:01 PM, Stefan L?ffler wrote: > Hi, > > I only want to spread the word that 0.4.1 is released. As a bugfix > release, it is not a milestone, but it should smooth some rough edges, > fix some bugs, and even introduce a few minor new features. > > The primary intention of this release was to wrap up all the > improvements of the last couple of weeks, and to give the TeXLive team a > good basis for their upcoming pre-release testing. If you've kept up to > date with the development branch (0.5), there is no need to switch to > 0.4.1, as it is based entirely on 0.5. > > Thanks for all the great support! > > -Stefan L?ffler I just uploaded two new Mac binaries based on 0.4.1: For Leopard (ppc and i386 architectures): https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.4.1-829-aa010eb-Leopard.dmg For Snow Leopard (x86_64 architecture): https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.4.1-829-aa010eb-SLeopard.dmg ** Note that these links are semi-permanent. If I produce new builds in the future, I may delete old ones to conserve disk space. ** The only major change in the build process used to produce these binaries is that some core Qt plugins are copied into TeXworks.app. This means that things like drag-and-drop of image files and text codecs should now be fully supported. The binaries still include a version of Poppler that is dependent on the Fontconfig library included in Apple's X11 package. This means the PDF viewer may not work properly on systems that don't have X11 fonts and configuration info. Howeve, the X11 package is installed by default since OS X 10.5.0---a user would have to go out of their way to set up a system that does not include it. There is work underway to revise patches to Poppler that let it use the native Quartz font system instead of Fontconfig. If anyone wishes to submit patches that improve the CMake build system or the packaging of TeXworks on OS X, pull requests are welcomed at: https://github.com/Sharpie/TeXworks -Charlie From st.loeffler at gmail.com Sat May 28 10:11:07 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sat, 28 May 2011 10:11:07 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> Message-ID: <4DE0AE1B.8040705@gmail.com> Hi, first of all: I don't have much experience with the guts of font handling, either, but maybe some of my comments can still help. On 2011-05-26 22:32, Charlie Sharpsteen wrote: > On Thu, May 26, 2011 at 3:03 AM, Jonathan Kew wrote: >> Interesting.... neither of these is entirely successful. (Thanks VERY much for your building and testing efforts!) The fontconfig/X11-fonts version fails to handle Helvetica Bold [Oblique], it just renders the non-bold faces. (And it's got a .notdef glyph in place of the "mu" in the middle of the Symbol line. That's probably an encoding mismatch related the "micro" symbol and the Greek letter "mu".) Just to collect some basic information: - Which version of poppler are you using (0.16.5 is the current one, AFAIK) - What Helvetica* fonts do you have in /System/Library/Fonts? @Jonathan: Any idea how one could work around the "mu" problem? Hack poppler-data, maybe? >> Meanwhile, the Quartz one gets Helvetica right, but doesn't find either Symbol or ZapfDingbats, and just falls back to Helvetica glyphs for both of those lines. I don't recall the details of the patch for finding Quartz fonts, but maybe this could be fixed? Hopefully. The way I see it ATM, the patch works as follows (all of this applies to loadPlatformFont(), font substitution if no suitable candidate is found is performed elsewhere, but shouldn't matter here as we expect all fonts can be found): Call ATSFontFindFromPostScriptName**to look for the font. If it's not found, strip parts after "," and after "-" and try again. Next, do what the following comments says: // Currently support only TrueType fonts: check for presence of 'glyf' table // if the font comes from a .ttf file, we can use that directly // for .dfont or suitcase files, FoFiTrueType can't handle them, so we extract // the required font to a temporary .ttf file and then use that > I could take a look at the font patch to see what needs to be fixed, > but I have never really dug into the guts of any font handling system > so it would probably take a while. I took a look at the font patch. I can't claim I understood all the Mac-specific stuff, but from your screenshot, all fonts come from /tmp. This suggests we're in the section started by the comment // for .dfont or suitcase files, FoFiTrueType can't handle them, so we extract // the required font to a temporary .ttf file and then use that So, I see 3 possibilities: 1) The Symbol and ZapfDingbats fonts are not found by ATSFontFindFromPostScriptName 2) They are only available in OpenType/CFF or other non-ttf formats and are thus not handled 3) Some other problem I've attached a symbol/zapf only version of the testcase so it's easier for you to debug (not so many other fonts that are loaded). I'd suggest adding some debug output lines to poppler (poppler/GlobalParamsMac.cc, the file the patch modifies) to check if possibilities 1 or 2 above apply. > One interesting thing I noted is > that Poppler needs to be build with the "splash" backend enabled in > order to get any font output at all. That I can explain. Tw explicitly sets the render backend to splash (src/PDFDocument.cpp at 1420). Maybe this is outdated (cairo might give good results?) but the arthur backend (which apparently was the default at least in earlier versions) was crap, so that's why this is there. HTH Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: base14-fonts-symbols-only.pdf Type: video/x-flv Size: 973 bytes Desc: not available URL: From chuck at sharpsteen.net Sat May 28 10:44:35 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sat, 28 May 2011 01:44:35 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DE0AE1B.8040705@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> Message-ID: On Sat, May 28, 2011 at 1:11 AM, Stefan L?ffler wrote: > Hi, > > first of all: I don't have much experience with the guts of font handling, > either, but maybe some of my comments can still help. > > On 2011-05-26 22:32, Charlie Sharpsteen wrote: > > On Thu, May 26, 2011 at 3:03 AM, Jonathan Kew > wrote: > > Interesting.... neither of these is entirely successful. (Thanks VERY much > for your building and testing efforts!) The fontconfig/X11-fonts version > fails to handle Helvetica Bold [Oblique], it just renders the non-bold > faces. (And it's got a .notdef glyph in place of the "mu" in the middle of > the Symbol line. That's probably an encoding mismatch related the "micro" > symbol and the Greek letter "mu".) > > Just to collect some basic information: > - Which version of poppler are you using (0.16.5 is the current one, AFAIK) Both builds were produced using Poppler 0.16.5. The Fontconfig-based build was created using a Homebrew formula in my master branch: https://github.com/Sharpie/TeXworks/blob/master/cmake/packaging/mac/poppler.rb A Homebrew Formula is just a Ruby class that contains information how to download, patch, build and install a piece of software. That poppler.rb file is derived from the standard Hombrew Formula for Poppler with some additions to apply the patch `poppler-qt4-globalparams.patch` which enables us to bundle poppler-data into the TeXworks app. It also disables some unneeded Poppler features to reduce the number of dynamic dependencies in the Poppler library. The Quartz-based build was created using this formula in my poppler-font-handling branch: https://github.com/Sharpie/TeXworks/blob/poppler-font-handling/cmake/packaging/mac/poppler.rb This build applies `poppler-mac-font-handling.patch` to get rid of the dependencies on Fontconfig. This requires re-running the Autotools in order to generate a new Configure script. A new patch, `poppler-mac-remove-iconv.patch`, is also applied to remove references to libiconv in `configure.ac`---otherwise GNU gettext would need to be installed in order to provide M4 macros required by Autotools. This build is also more aggressive in the number of extraneous backends and other features that are disabled. > - What Helvetica* fonts do you have in /System/Library/Fonts? Here's what I have on my test systems (OS X 10.6.7 and 10.5.0): Charlie-Sharpsteens-Mac-Pro:~ sharpie$ ls /System/Library/Fonts/Helve* /System/Library/Fonts/HelveLTMM /System/Library/Fonts/Helvetica LT MM /System/Library/Fonts/Helvetica.dfont /System/Library/Fonts/HelveticaNeue.dfont > @Jonathan: Any idea how one could work around the "mu" problem? Hack > poppler-data, maybe? > > Meanwhile, the Quartz one gets Helvetica right, but doesn't find either > Symbol or ZapfDingbats, and just falls back to Helvetica glyphs for both of > those lines. I don't recall the details of the patch for finding Quartz > fonts, but maybe this could be fixed? > > Hopefully. The way I see it ATM, the patch works as follows (all of this > applies to loadPlatformFont(), font substitution if no suitable candidate is > found is performed elsewhere, but shouldn't matter here as we expect all > fonts can be found): > Call ATSFontFindFromPostScriptName to look for the font. If it's not found, > strip parts after "," and after "-" and try again. > > Next, do what the following comments says: > // Currently support only TrueType fonts: check for presence of 'glyf' table > > // if the font comes from a .ttf file, we can use that directly > > // for .dfont or suitcase files, FoFiTrueType can't handle them, so we > extract > // the required font to a temporary .ttf file and then use that > > I could take a look at the font patch to see what needs to be fixed, > but I have never really dug into the guts of any font handling system > so it would probably take a while. > > I took a look at the font patch. I can't claim I understood all the > Mac-specific stuff, but from your screenshot, all fonts come from /tmp. This > suggests we're in the section started by the comment > // for .dfont or suitcase files, FoFiTrueType can't handle them, so we > extract > // the required font to a temporary .ttf file and then use that > > So, I see 3 possibilities: > 1) The Symbol and ZapfDingbats fonts are not found by > ATSFontFindFromPostScriptName > 2) They are only available in OpenType/CFF or other non-ttf formats and are > thus not handled > 3) Some other problem > > I've attached a symbol/zapf only version of the testcase so it's easier for > you to debug (not so many other fonts that are loaded). I'd suggest adding > some debug output lines to poppler (poppler/GlobalParamsMac.cc, the file the > patch modifies) to check if possibilities 1 or 2 above apply. I will look into this when I get a chance. > One interesting thing I noted is > that Poppler needs to be build with the "splash" backend enabled in > order to get any font output at all. > > That I can explain. Tw explicitly sets the render backend to splash > (src/PDFDocument.cpp at 1420). Maybe this is outdated (cairo might give good > results?) but the arthur backend (which apparently was the default at least > in earlier versions) was crap, so that's why this is there. Thanks for pointing this out---it makes a lot of sense now. did a quick grep for "backend" in the qt subdirectory of the Poppler source and the only results referred to Splash or Arthur---so it looks like those are our choices. It is too bad that the Qt backend is not more tightly integrated with the Qt drawing system. -Charlie > HTH > Stefan From chuck at sharpsteen.net Sat May 28 10:53:13 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sat, 28 May 2011 01:53:13 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> Message-ID: On Sat, May 28, 2011 at 1:44 AM, Charlie Sharpsteen wrote: > Thanks for pointing this out---it makes a lot of sense now. did a > quick grep for "backend" in the qt subdirectory of the Poppler source > and the only results referred to Splash or Arthur---so it looks like > those are our choices. It is too bad that the Qt backend is not more > tightly integrated with the Qt drawing system. > > -Charlie Bah, just saw that Arthur *is* a Qt drawing system. Kindly disregard the babbling person in this corner of the mailing list---he is going to bed now. From gzjjgod at gmail.com Sat May 28 11:11:27 2011 From: gzjjgod at gmail.com (Jjgod Jiang) Date: Sat, 28 May 2011 11:11:27 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> Message-ID: On Sat, May 28, 2011 at 10:53 AM, Charlie Sharpsteen wrote: > Bah, just saw that Arthur *is* a Qt drawing system. ?Kindly disregard > the babbling person in this corner of the mailing list---he is going > to bed now. Yep, Arthur is the code name for Qt raster paint engine rewritten from Qt 4. - Jiang From jfkthame at googlemail.com Sat May 28 11:14:19 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Sat, 28 May 2011 10:14:19 +0100 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> Message-ID: <73744B54-37AE-4927-9C04-7AA5020578E4@gmail.com> On 28 May 2011, at 09:53, Charlie Sharpsteen wrote: > On Sat, May 28, 2011 at 1:44 AM, Charlie Sharpsteen > wrote: >> Thanks for pointing this out---it makes a lot of sense now. did a >> quick grep for "backend" in the qt subdirectory of the Poppler source >> and the only results referred to Splash or Arthur---so it looks like >> those are our choices. It is too bad that the Qt backend is not more >> tightly integrated with the Qt drawing system. >> >> -Charlie > > Bah, just saw that Arthur *is* a Qt drawing system. Indeed - it might be interesting to try setting up TW to use Arthur and see if it's better/worse than Splash at this point. Back when I started TW, Arthur was in a fairly broken state and definitely not usable, but there's been work on it since then. Using Cairo would be another direction to explore; AFAIK there's no "official" support for integrating Poppler+Cairo+Qt, but I believe it's possible and can give good results. The main downside is that it brings in an additional dependency. It might be worth it for Cairo's printing support, though. JK From st.loeffler at gmail.com Sat May 28 17:49:11 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sat, 28 May 2011 17:49:11 +0200 Subject: [texworks] Background image Drag N' Drop installer (was: Updated builds of TeXworks for OS X) In-Reply-To: References: Message-ID: <4DE11977.9090408@gmail.com> Hi, On 2011-05-15 03:01, Charlie Sharpsteen wrote: > - If anyone is feeling artistic, it would be nice to come up with a > snazzy background image for the Drag N' Drop installer. I was not feeling particularly artistic, but since nobody else had a go at it, I wrapped something up. It's really just a rip-off of the Firefox image Wolfgang posted, but maybe it's helpful. I'm attaching two variants with version numbers (0.4.1 & 0.5) and one without. Please tell me which one you prefer. HTH Stefan PS: I've created the image as vector graphic (.svg). If you want, I can send you that as well, but in any case it's easy to change things and to make .pngs at arbitrary sizes. -------------- next part -------------- A non-text attachment was scrubbed... Name: mac-installer-background-0.4.1.png Type: image/png Size: 73830 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mac-installer-background-0.5.png Type: image/png Size: 73768 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mac-installer-background-no-version.png Type: image/png Size: 72801 bytes Desc: not available URL: From chuck at sharpsteen.net Sat May 28 18:12:02 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sat, 28 May 2011 09:12:02 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DE0AE1B.8040705@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> Message-ID: On Sat, May 28, 2011 at 1:11 AM, Stefan L?ffler wrote: > So, I see 3 possibilities: > 1) The Symbol and ZapfDingbats fonts are not found by > ATSFontFindFromPostScriptName > 2) They are only available in OpenType/CFF or other non-ttf formats and are > thus not handled > 3) Some other problem > > I've attached a symbol/zapf only version of the testcase so it's easier for > you to debug (not so many other fonts that are loaded). I'd suggest adding > some debug output lines to poppler (poppler/GlobalParamsMac.cc, the file the > patch modifies) to check if possibilities 1 or 2 above apply. Allright, I patched some debugging output int GlobalParamsMac.cc: https://github.com/Sharpie/TeXworks/blob/poppler-font-handling/lib-patches/poppler-debug.patch The patch prints out the value of `fontName` which is sent into the font loading function and the value of `fontPath` which is the font file that will be loaded. This is the resulting output when `loading base-14-fonts.pdf`: grendel:build sharpie$ ./TeXworks.app/Contents/MacOS/TeXworks QFileSystemWatcher::removePaths: list is empty Lookup font: Times-Roman found in file: /System/Library/Fonts/Times.dfont Lookup font: Times-Bold found in file: /System/Library/Fonts/Times.dfont Lookup font: Times-Italic found in file: /System/Library/Fonts/Times.dfont Lookup font: Times-BoldItalic found in file: /System/Library/Fonts/Times.dfont Lookup font: Helvetica found in file: /System/Library/Fonts/Helvetica.dfont Lookup font: Helvetica-Bold found in file: /System/Library/Fonts/Helvetica.dfont Lookup font: Helvetica-Oblique found in file: /System/Library/Fonts/Helvetica.dfont Lookup font: Helvetica-BoldOblique found in file: /System/Library/Fonts/Helvetica.dfont Lookup font: Courier found in file: /System/Library/Fonts/Courier.dfont Lookup font: Courier-Bold found in file: /System/Library/Fonts/Courier.dfont Lookup font: Courier-Oblique found in file: /System/Library/Fonts/Courier.dfont Lookup font: Courier-BoldOblique found in file: /System/Library/Fonts/Courier.dfont Lookup font: Symbol found in file: /System/Library/Fonts/Symbol.ttf "Error: Couldn't find a font for 'ZapfDingbats', subst is 'Helvetica'" "Error: Couldn't find a font for 'ZapfDingbats', subst is 'Helvetica'" This test was done on 10.6.7, while the other tests were done on 10.5.0. However the output is the same: http://i.imgur.com/yhp6s.png The only difference is that Snow Leopard has a .ttf for the Symbol font while Leopard has a .dfont file. So, the problem appears to be that ZapfDingbats is not being recognized. However, the font files do exist On 10.6.7: /System/Library/Fonts/ZapfDingbats.ttf On 10.5.0: /System/Library/Fonts/ZapfDingbats.dfont Perhaps there is something exceptional about the dingbat font that keeps the logic in `GlobalParams::loadPlatformFont` from recognizing it as valid? -Charlie From chuck at sharpsteen.net Sat May 28 18:25:11 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sat, 28 May 2011 09:25:11 -0700 Subject: [texworks] Background image Drag N' Drop installer (was: Updated builds of TeXworks for OS X) In-Reply-To: <4DE11977.9090408@gmail.com> References: <4DE11977.9090408@gmail.com> Message-ID: On Sat, May 28, 2011 at 8:49 AM, Stefan L?ffler wrote: > Hi, > > On 2011-05-15 03:01, Charlie Sharpsteen wrote: >> ? - If anyone is feeling artistic, it would be nice to come up with a >> snazzy background image for the Drag N' Drop installer. > > I was not feeling particularly artistic, but since nobody else had a go > at it, I wrapped something up. It's really just a rip-off of the Firefox > image Wolfgang posted, but maybe it's helpful. I'm attaching two > variants with version numbers (0.4.1 & 0.5) and one without. Please tell > me which one you prefer. > > HTH > Stefan > > PS: I've created the image as vector graphic (.svg). If you want, I can > send you that as well, but in any case it's easy to change things and to > make .pngs at arbitrary sizes. This looks great! Although I think we need to remove the icon images as they will be provided by the icons of the actual app and folder. For example, here is the actual background image used by the firefox DMG: http://i.imgur.com/pmb1B.png Having the SVG file would be interesting as we could possibly insert a variable for the version number that gets filled in during configuration. Then something like ImageMagick could be used to render the SVG to a PNG. -Charlie From st.loeffler at gmail.com Sun May 29 09:27:03 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 29 May 2011 09:27:03 +0200 Subject: [texworks] Background image Drag N' Drop installer In-Reply-To: References: <4DE11977.9090408@gmail.com> Message-ID: <4DE1F547.7070201@gmail.com> Hi, On 2011-05-28 18:25, Charlie Sharpsteen wrote: > This looks great! Although I think we need to remove the icon images > as they will be provided by the icons of the actual app and folder. Sure, no problem. In fact, without the icons the svg becomes smaller and more portable (not to mention less prone to license violations connected to the apps folder icon ;)). > Having the SVG file would be interesting as we could possibly insert a > variable for the version number that gets filled in during > configuration. Then something like ImageMagick could be used to render > the SVG to a PNG. Yeah, that was the (ultimate) idea. If it works, one could even add the revision number - but if it doesn't, sticking with just the version is fine as well, and with only a few releases per year (at most) easy to keep track of manually. Anyway, I attached the (somewhat cleaned) svg file, plus the same pngs in case the conversion doesn't work out of the box. Note that I created the image in Inkscape, and used some rather fancy clipping boxes etc. of which I don't know how portable they are. Cheers, Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: mac-installer-background.svg Type: image/svg+xml Size: 9726 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mac-installer-background-0.4.1.png Type: image/png Size: 33518 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mac-installer-background-0.5.png Type: image/png Size: 33464 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mac-installer-background-no-version.png Type: image/png Size: 32308 bytes Desc: not available URL: From st.loeffler at gmail.com Sun May 29 10:40:17 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 29 May 2011 10:40:17 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> Message-ID: <4DE20671.7090102@gmail.com> Hi, On 2011-05-28 18:12, Charlie Sharpsteen wrote: > Allright, I patched some debugging output int GlobalParamsMac.cc: > > https://github.com/Sharpie/TeXworks/blob/poppler-font-handling/lib-patches/poppler-debug.patch > > The patch prints out the value of `fontName` which is sent into the > font loading function and the value of `fontPath` which is the font > file that will be loaded. This is the resulting output when `loading > base-14-fonts.pdf`: Thanks for testing. > [snip] > > So, the problem appears to be that ZapfDingbats is not being > recognized. However, the font files do exist > > On 10.6.7: > > /System/Library/Fonts/ZapfDingbats.ttf > > On 10.5.0: > > /System/Library/Fonts/ZapfDingbats.dfont > > Perhaps there is something exceptional about the dingbat font that > keeps the logic in `GlobalParams::loadPlatformFont` from recognizing > it as valid? Maybe. I sent you a pull request that adds more debug output (basically, around every point in the function where something can go wrong). Hopefully this will give a better indication where things fail. -Stefan PS: phew, branching remote branches, cherry-picking commits, I'm learning a lot about git here :). From chuck at sharpsteen.net Sun May 29 12:08:40 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sun, 29 May 2011 03:08:40 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DE20671.7090102@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> Message-ID: On Sun, May 29, 2011 at 1:40 AM, Stefan L?ffler wrote: > Hi, > > On 2011-05-28 18:12, Charlie Sharpsteen wrote: >> Allright, I patched some debugging output int GlobalParamsMac.cc: >> >> ? ? https://github.com/Sharpie/TeXworks/blob/poppler-font-handling/lib-patches/poppler-debug.patch >> >> The patch prints out the value of `fontName` which is sent into the >> font loading function and the value of `fontPath` which is the font >> file that will be loaded. ?This is the resulting output when `loading >> base-14-fonts.pdf`: > > Thanks for testing. > >> [snip] >> >> So, the problem appears to be that ZapfDingbats is not being >> recognized. ?However, the font files do exist >> >> On 10.6.7: >> >> ? ? /System/Library/Fonts/ZapfDingbats.ttf >> >> On 10.5.0: >> >> ? ? /System/Library/Fonts/ZapfDingbats.dfont >> >> Perhaps there is something exceptional about the dingbat font that >> keeps the logic in `GlobalParams::loadPlatformFont` from recognizing >> it as valid? > > Maybe. I sent you a pull request that adds more debug output (basically, > around every point in the function where something can go wrong). > Hopefully this will give a better indication where things fail. > > -Stefan Allright, I applied the pull request and added one more log statement. Here's the results of loading base-14-fonts.pdf: QFileSystemWatcher::removePaths: list is empty Lookup font: Times-Roman ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/UNgvGH1x.ttf Lookup font: Times-Bold ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/ArQD2Yg2.ttf Lookup font: Times-Italic ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/rMHRifPr.ttf Lookup font: Times-BoldItalic ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/fPrbPf68.ttf Lookup font: Helvetica ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/K7MBFFu0.ttf Lookup font: Helvetica-Bold ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/cqyjMmsP.ttf Lookup font: Helvetica-Oblique ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/X6n6fEMm.ttf Lookup font: Helvetica-BoldOblique ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/SZ9wIxwW.ttf Lookup font: Courier ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/y1BE8igp.ttf Lookup font: Courier-Bold ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/KqJlPdog.ttf Lookup font: Courier-Oblique ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/bulPJZj8.ttf Lookup font: Courier-BoldOblique ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/iDDzPKQP.ttf Lookup font: Symbol ATSFontFindFromPostScriptName found fontRef found 'glyf' table found in file: /System/Library/Fonts/Symbol.ttf Lookup font: ZapfDingbats ATSFontFindFromPostScriptName failed! Bailing out! "Error: Couldn't find a font for 'ZapfDingbats', subst is 'Helvetica'" Lookup font: ZapfDingbats ATSFontFindFromPostScriptName failed! Bailing out! "Error: Couldn't find a font for 'ZapfDingbats', subst is 'Helvetica'" So, looks like the problem with ZapfDingbats is that ATSFontFindFromPostScriptName can't locate it using that name for some reason. > PS: phew, branching remote branches, cherry-picking commits, I'm > learning a lot about git here :). From st.loeffler at gmail.com Sun May 29 12:38:10 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 29 May 2011 12:38:10 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> Message-ID: <4DE22212.4070602@gmail.com> On 2011-05-29 12:08, Charlie Sharpsteen wrote: > Lookup font: ZapfDingbats > ATSFontFindFromPostScriptName failed! Bailing out! > "Error: Couldn't find a font for 'ZapfDingbats', subst is 'Helvetica'" > > So, looks like the problem with ZapfDingbats is that > ATSFontFindFromPostScriptName can't locate it using that name for some > reason. Well, that's that, then. Unfortunately, I didn't find any documentation regarding ATSFontFindFromPostScriptName on the web. But maybe the PostScript name is simply slightly different ("Zap-Dingbats" or "Dingbats" would come to mind). Is there any way to check that? http://fontforge.sourceforge.net/ might help (if you don't have it and don't want to build it, you can also send me the font off-list and I have a look at it), but I really don't know enough about fonts and the Mac to know what's going on beneath the hood. -Stefan From jfkthame at googlemail.com Sun May 29 13:25:23 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Sun, 29 May 2011 12:25:23 +0100 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DE22212.4070602@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> Message-ID: On my Mac (running OS X 10.6), at least, the font's PS name is ZapfDingbatsITC. Maybe we could enhance the code to try both ZapfDingbats and ZapfDingbatsITC? JK On 29 May 2011, at 11:38, Stefan L?ffler wrote: > On 2011-05-29 12:08, Charlie Sharpsteen wrote: >> Lookup font: ZapfDingbats >> ATSFontFindFromPostScriptName failed! Bailing out! >> "Error: Couldn't find a font for 'ZapfDingbats', subst is 'Helvetica'" >> >> So, looks like the problem with ZapfDingbats is that >> ATSFontFindFromPostScriptName can't locate it using that name for some >> reason. > > Well, that's that, then. Unfortunately, I didn't find any documentation > regarding ATSFontFindFromPostScriptName on the web. But maybe the > PostScript name is simply slightly different ("Zap-Dingbats" or > "Dingbats" would come to mind). Is there any way to check that? > http://fontforge.sourceforge.net/ might help (if you don't have it and > don't want to build it, you can also send me the font off-list and I > have a look at it), but I really don't know enough about fonts and the > Mac to know what's going on beneath the hood. > > -Stefan From sigmundv at gmail.com Sun May 29 23:07:35 2011 From: sigmundv at gmail.com (sigmundv at gmail.com) Date: Sun, 29 May 2011 23:07:35 +0200 Subject: [texworks] Background image Drag N' Drop installer In-Reply-To: <4DE1F547.7070201@gmail.com> References: <4DE11977.9090408@gmail.com> <4DE1F547.7070201@gmail.com> Message-ID: > > Note that I created > the image in Inkscape, and used some rather fancy clipping boxes etc. of > which I don't know how portable they are. Using TikZ (TikZ ist kein Zeichenprogramm) would make the image generation very portable. It doesn't output SVG though, but still it outputs vector graphics (PDF/EPS - I know, PDF is technically not an image format). /Sigmund -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Mon May 30 00:19:16 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sun, 29 May 2011 15:19:16 -0700 Subject: [texworks] Background image Drag N' Drop installer In-Reply-To: References: <4DE11977.9090408@gmail.com> <4DE1F547.7070201@gmail.com> Message-ID: On Sun, May 29, 2011 at 2:07 PM, sigmundv at gmail.com wrote: >> Note that I created >> the image in Inkscape, and used some rather fancy clipping boxes etc. of >> which I don't know how portable they are. > > Using TikZ (TikZ ist kein Zeichenprogramm) would make the image generation > very portable. It doesn't output SVG though, but still it outputs vector > graphics (PDF/EPS - I know, PDF is technically not an image format). > /Sigmund The final image format needs to be a bitmap such as PNG with spaces to hold icons as big as 128px square. This could be done in TikZ by using the Preview package and then applying ImageMagick's convert tool. If anyone puts in the time to draw up a background, I'm willing to take a look at it. If there is more than one submission, we could hold a vote to decide which to use. -Charlie From kloon at nus.edu.sg Mon May 30 09:27:25 2011 From: kloon at nus.edu.sg (Ng Kah Loon) Date: Mon, 30 May 2011 15:27:25 +0800 Subject: [texworks] Problem installing packages Message-ID: An HTML attachment was scrubbed... URL: From ne45 at leicester.ac.uk Mon May 30 13:57:31 2011 From: ne45 at leicester.ac.uk (Economides, Nicholas) Date: Mon, 30 May 2011 12:57:31 +0100 Subject: [texworks] Stata output Message-ID: Hi, I want to put a Stata output in my document and the only way to do this is to add the packaje sjlatex. The problem is that I don't know where to put the package's files, and how to make Miktex recognise it. I found some instructions on the web but they explain how to do it in the old version of Miktex, not in the Texworks. Any ideas/recommendations? Many thanks Nick From cursus.publicus at sacrumromanumimperium.org Mon May 30 15:41:35 2011 From: cursus.publicus at sacrumromanumimperium.org (Andreas Hirsch) Date: Mon, 30 May 2011 15:41:35 +0200 Subject: [texworks] Problem installing packages In-Reply-To: References: Message-ID: <4DE39E8F.20201@sacrumromanumimperium.org> Hi! quoting Ng Kah Loon, [30.05.2011 09:27 +0100]: > Hi, > > I am new to using TexWorks but I have been looking at online resources on how I > can add my own packages and .sty files which is required for typesetting my > documents. > > From I gather, it seems that we should add in folders (containing packages and > .sty files) in the directory > > /usr/local/texlive/texmf-local/tex/latex > > Am I right? For example, I need to use a package called tkz-graph, so I created > a folder called tkz-graph in the directory above and placed the .sty file inside. > > However, when I typeset my .tex file, I get an error message that says the > tkz-graph.sty file cannot be found. Did I do the right thing? > > I would really appreciate any assistance provided. You have to refresh the databse for the files, using mktexlsr \HTH -- Andreas Hirsch Klarweinstr. 5a 82467 Garmisch-Partenkirchen ++49 8821 947477 GPG PublicKey http://members.gaponline.de/afj/keys/afj_pub.asc Fingerprint 81D6 6C24 3AA8 E250 E034 CAF5 A1E8 D5E8 806C 3CB8 From ne45 at leicester.ac.uk Mon May 30 17:18:34 2011 From: ne45 at leicester.ac.uk (Economides, Nicholas) Date: Mon, 30 May 2011 16:18:34 +0100 Subject: [texworks] Problem installing packages In-Reply-To: <4DE39E8F.20201@sacrumromanumimperium.org> References: , <4DE39E8F.20201@sacrumromanumimperium.org> Message-ID: Hi, the thing is that everyone say that we have to refresh the database for the files, but since most of us do not have a degree in programming, you guys should be a bit more specific. Anyway, I found a way to do this and I hope Ng Kah Loon will find it helpful as well: find the file called mo_admin.exe which should be located at the path miktex 2.9/miktex/bin/ Once you run it, you should get the miktex options. At the general page, click the "refresh FNDB" button, and then the "update formats" button This should help Miktex/Latex understand that you have just added something new. Before you do that, you should make sure that you pasted the package folder that you have downloaded in to the path tex/latex I believe after you have done that it should work. Nick ________________________________________ From: texworks-bounces at tug.org [texworks-bounces at tug.org] On Behalf Of Andreas Hirsch [cursus.publicus at sacrumromanumimperium.org] Sent: Monday, May 30, 2011 2:41 PM To: Discuss the TeXworks front end. Subject: Re: [texworks] Problem installing packages Hi! quoting Ng Kah Loon, [30.05.2011 09:27 +0100]: > Hi, > > I am new to using TexWorks but I have been looking at online resources on how I > can add my own packages and .sty files which is required for typesetting my > documents. > > From I gather, it seems that we should add in folders (containing packages and > .sty files) in the directory > > /usr/local/texlive/texmf-local/tex/latex > > Am I right? For example, I need to use a package called tkz-graph, so I created > a folder called tkz-graph in the directory above and placed the .sty file inside. > > However, when I typeset my .tex file, I get an error message that says the > tkz-graph.sty file cannot be found. Did I do the right thing? > > I would really appreciate any assistance provided. You have to refresh the databse for the files, using mktexlsr \HTH -- Andreas Hirsch Klarweinstr. 5a 82467 Garmisch-Partenkirchen ++49 8821 947477 GPG PublicKey http://members.gaponline.de/afj/keys/afj_pub.asc Fingerprint 81D6 6C24 3AA8 E250 E034 CAF5 A1E8 D5E8 806C 3CB8 From reinhard.kotucha at web.de Mon May 30 18:06:16 2011 From: reinhard.kotucha at web.de (Reinhard Kotucha) Date: Mon, 30 May 2011 18:06:16 +0200 Subject: [texworks] Stata output In-Reply-To: References: Message-ID: <19939.49272.926619.185313@zaphod.ms25.net> On 2011-05-30 at 12:57:31 +0100, Economides, Nicholas wrote: > Hi, > > I want to put a Stata output in my document and the only way to do > this is to add the packaje sjlatex. The problem is that I don't > know where to put the package's files, and how to make Miktex > recognise it. I found some instructions on the web but they > explain how to do it in the old version of Miktex, not in the > Texworks. Any ideas/recommendations? It has nothing to do with TeXworks. Please consult the MiKTeX documentation. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha at web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- From esperanto at swing.be Mon May 30 18:18:51 2011 From: esperanto at swing.be (Alain Delmotte) Date: Mon, 30 May 2011 18:18:51 +0200 Subject: [texworks] Problem installing packages In-Reply-To: References: , <4DE39E8F.20201@sacrumromanumimperium.org> Message-ID: <4DE3C36B.9090209@swing.be> Hi! Sorry but Ng Kah Loon is not using MikTeX but TeXLive. When you install TeXLive, there is a folder created in the Start menu, in which you could find the "TeX Live Manager". Start the manager! In the "Actions" menu you have the entry "Update Filename database". For MikTeX there is an equivalent system: MikTeX Options, where you find the update filename database. Regards, Alain Delmotte Le 30/05/2011 17:18, Economides, Nicholas a ?crit : > Hi, > > the thing is that everyone say that we have to refresh the database for the files, but since most of us do not have a degree in programming, you guys should be a bit more specific. > > Anyway, I found a way to do this and I hope Ng Kah Loon will find it helpful as well: > > find the file called mo_admin.exe which should be located at the path miktex 2.9/miktex/bin/ > Once you run it, you should get the miktex options. > At the general page, click the "refresh FNDB" button, and then the "update formats" button > > This should help Miktex/Latex understand that you have just added something new. > > Before you do that, you should make sure that you pasted the package folder that you have downloaded in to the path tex/latex > > I believe after you have done that it should work. > > Nick > ________________________________________ > From: texworks-bounces at tug.org [texworks-bounces at tug.org] On Behalf Of Andreas Hirsch [cursus.publicus at sacrumromanumimperium.org] > Sent: Monday, May 30, 2011 2:41 PM > To: Discuss the TeXworks front end. > Subject: Re: [texworks] Problem installing packages > > Hi! > > quoting Ng Kah Loon, [30.05.2011 09:27 +0100]: >> Hi, >> >> I am new to using TexWorks but I have been looking at online resources on how I >> can add my own packages and .sty files which is required for typesetting my >> documents. >> >> From I gather, it seems that we should add in folders (containing packages and >> .sty files) in the directory >> >> /usr/local/texlive/texmf-local/tex/latex >> >> Am I right? For example, I need to use a package called tkz-graph, so I created >> a folder called tkz-graph in the directory above and placed the .sty file inside. >> >> However, when I typeset my .tex file, I get an error message that says the >> tkz-graph.sty file cannot be found. Did I do the right thing? >> >> I would really appreciate any assistance provided. > > You have to refresh the databse for the files, using > > mktexlsr > > \HTH > > -- > Andreas Hirsch > Klarweinstr. 5a > 82467 Garmisch-Partenkirchen > ++49 8821 947477 > GPG PublicKey http://members.gaponline.de/afj/keys/afj_pub.asc > Fingerprint 81D6 6C24 3AA8 E250 E034 CAF5 A1E8 D5E8 806C 3CB8 > > From reinhard.kotucha at web.de Mon May 30 18:23:35 2011 From: reinhard.kotucha at web.de (Reinhard Kotucha) Date: Mon, 30 May 2011 18:23:35 +0200 Subject: [texworks] Problem installing packages In-Reply-To: References: <4DE39E8F.20201@sacrumromanumimperium.org> Message-ID: <19939.50311.261815.196063@zaphod.ms25.net> On 2011-05-30 at 16:18:34 +0100, Economides, Nicholas wrote: > Hi, > > the thing is that everyone say that we have to refresh the database > for the files, but since most of us do not have a degree in > programming, you guys should be a bit more specific. Please read the mails more carefully before confusing people. Andreas' answer was specific enough and what you propose doesn't work in this case. > Anyway, I found a way to do this and I hope Ng Kah Loon will find > it helpful as well: > > find the file called mo_admin.exe which should be located at the > path miktex 2.9/miktex/bin/ Once you run it, you should get the > miktex options. At the general page, click the "refresh FNDB" > button, and then the "update formats" button > > This should help Miktex/Latex understand that you have just added > something new. > > Before you do that, you should make sure that you pasted the > package folder that you have downloaded in to the path tex/latex > > I believe after you have done that it should work. Is everything so complicated under MiKTeX? Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha at web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- From reinhard.kotucha at web.de Mon May 30 18:29:50 2011 From: reinhard.kotucha at web.de (Reinhard Kotucha) Date: Mon, 30 May 2011 18:29:50 +0200 Subject: [texworks] Problem installing packages In-Reply-To: <4DE3C36B.9090209@swing.be> References: <4DE39E8F.20201@sacrumromanumimperium.org> <4DE3C36B.9090209@swing.be> Message-ID: <19939.50686.971309.911038@zaphod.ms25.net> On 2011-05-30 at 18:18:51 +0200, Alain Delmotte wrote: > Hi! > > Sorry but Ng Kah Loon is not using MikTeX but TeXLive. > > When you install TeXLive, there is a folder created in the > Start menu, in which you could find the "TeX Live Manager". Which Start menu? Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha at web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- From chuck at sharpsteen.net Mon May 30 19:52:27 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Mon, 30 May 2011 10:52:27 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> Message-ID: On Sun, May 29, 2011 at 4:25 AM, Jonathan Kew wrote: > On my Mac (running OS X 10.6), at least, the font's PS name is ZapfDingbatsITC. > > Maybe we could enhance the code to try both ZapfDingbats and ZapfDingbatsITC? > > JK I replaced the declaration of `myName` at the beginning of `GlobalParams::loadPlatformFont`: char * myName = copyString(fontName); With: char *myName; if ( strcmp((const char*) fontName, "ZapfDingbats") == 0 ) { myName = copyString("ZapfDingbatsITC"); } else { myName = copyString(fontName); } And it works: http://i.imgur.com/m0BCk.png However, the log output is a little worrisome: QFileSystemWatcher::removePaths: list is empty Lookup font: Times-Roman ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/98Da6fN1.ttf Lookup font: Times-Bold ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/gfWpzQXB.ttf Lookup font: Times-Italic ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/L7ThyTJd.ttf Lookup font: Times-BoldItalic ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/xFpzSIW0.ttf Lookup font: Helvetica ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/PlNgba9C.ttf Lookup font: Helvetica-Bold ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/8KYyCUil.ttf Lookup font: Helvetica-Oblique ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/r2VM1GCT.ttf Lookup font: Helvetica-BoldOblique ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/gKH1ob2W.ttf Lookup font: Courier ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/NeCalckZ.ttf Lookup font: Courier-Bold ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/03fSA2NP.ttf Lookup font: Courier-Oblique ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/YLybIE9j.ttf Lookup font: Courier-BoldOblique ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/aT8tcGz3.ttf Lookup font: Symbol ATSFontFindFromPostScriptName found fontRef found 'glyf' table found in file: /System/Library/Fonts/Symbol.ttf Lookup font: ZapfDingbatsITC ATSFontFindFromPostScriptName found fontRef found 'glyf' table found in file: /System/Library/Fonts/ZapfDingbats.ttf Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Those memory warnings are new. From esperanto at swing.be Mon May 30 19:55:36 2011 From: esperanto at swing.be (Alain Delmotte) Date: Mon, 30 May 2011 19:55:36 +0200 Subject: [texworks] Problem installing packages In-Reply-To: <19939.50686.971309.911038@zaphod.ms25.net> References: <4DE39E8F.20201@sacrumromanumimperium.org> <4DE3C36B.9090209@swing.be> <19939.50686.971309.911038@zaphod.ms25.net> Message-ID: <4DE3DA18.40604@swing.be> OK! I answer from my machine, which is in French, you'll translate, menu "D?marrer" Alain Le 30/05/2011 18:29, Reinhard Kotucha a ?crit : > On 2011-05-30 at 18:18:51 +0200, Alain Delmotte wrote: > > > Hi! > > > > Sorry but Ng Kah Loon is not using MikTeX but TeXLive. > > > > When you install TeXLive, there is a folder created in the > > Start menu, in which you could find the "TeX Live Manager". > > Which Start menu? > > Regards, > Reinhard > From hospes.primus at verizon.net Mon May 30 19:59:57 2011 From: hospes.primus at verizon.net (David Perry) Date: Mon, 30 May 2011 13:59:57 -0400 Subject: [texworks] Problem installing packages In-Reply-To: <19939.50311.261815.196063@zaphod.ms25.net> References: <4DE39E8F.20201@sacrumromanumimperium.org> <19939.50311.261815.196063@zaphod.ms25.net> Message-ID: <4DE3DB1D.5010404@verizon.net> On 5/30/2011 12:23 PM, Reinhard Kotucha wrote: > Is everything so complicated under MiKTeX? No. Normally when you use a package that is not installed, MiKTeK will automatically download and install it for you (if you have given it permission to do so when you first installed MiKTeX). The package in question here, sjlatex, is one that MiKTeX does not know about (the only one I've ever encountered, although there are undoubtedly more out there). MiKTeX creates items in the Windows Start menu that give easy access to the various options, including the ability to rebuild formats if you have had to add a package manually. David From chuck at sharpsteen.net Mon May 30 20:06:48 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Mon, 30 May 2011 11:06:48 -0700 Subject: [texworks] Problem installing packages In-Reply-To: References: Message-ID: On Mon, May 30, 2011 at 12:27 AM, Ng Kah Loon wrote: > Hi, > I am new to using TexWorks but I have been looking at online resources on > how I can add my own packages and .sty files which is required for > typesetting my documents. > From I gather, it seems that we should add in folders (containing packages > and .sty files) in the directory > /usr/local/texlive/texmf-local/tex/latex > Am I right? For example, I need to use a package called tkz-graph, so I > created a folder called tkz-graph in the directory above and placed the .sty > file inside. > However, when I typeset my .tex file, I get an error message that says the > tkz-graph.sty file cannot be found. Did I do the right thing? > I would really appreciate any assistance provided. > Regards, > K L Ng Which operating system are you using? The details of where to put .sty files are different for Window, Linux and OS X. -Charlie From cursus.publicus at sacrumromanumimperium.org Mon May 30 20:15:47 2011 From: cursus.publicus at sacrumromanumimperium.org (Andreas Hirsch) Date: Mon, 30 May 2011 20:15:47 +0200 Subject: [texworks] Problem installing packages In-Reply-To: References: Message-ID: <4DE3DED3.9090703@sacrumromanumimperium.org> quoting Charlie Sharpsteen, [30.05.2011 20:06 +0100]: > On Mon, May 30, 2011 at 12:27 AM, Ng Kah Loon wrote: >> Hi, >> I am new to using TexWorks but I have been looking at online resources on >> how I can add my own packages and .sty files which is required for >> typesetting my documents. >> From I gather, it seems that we should add in folders (containing packages >> and .sty files) in the directory >> /usr/local/texlive/texmf-local/tex/latex >> Am I right? For example, I need to use a package called tkz-graph, so I >> created a folder called tkz-graph in the directory above and placed the .sty >> file inside. >> However, when I typeset my .tex file, I get an error message that says the >> tkz-graph.sty file cannot be found. Did I do the right thing? >> I would really appreciate any assistance provided. >> Regards, >> K L Ng > > Which operating system are you using? The details of where to put > .sty files are different for Window, Linux and OS X. if we talk about absolute paths, you are right so let us be more precise: if TL ist installed to /texlive there will be a folder TL2010 and a folder texmf-local in it in the last one, the same hierachy, i.e /tex/latex should exist as in TL2010 \HTH -- Andreas Hirsch Klarweinstr. 5a 82467 Garmisch-Partenkirchen ++49 8821 947477 GPG PublicKey http://members.gaponline.de/afj/keys/afj_pub.asc Fingerprint 81D6 6C24 3AA8 E250 E034 CAF5 A1E8 D5E8 806C 3CB8 From reinhard.kotucha at web.de Mon May 30 20:19:52 2011 From: reinhard.kotucha at web.de (Reinhard Kotucha) Date: Mon, 30 May 2011 20:19:52 +0200 Subject: [texworks] Problem installing packages In-Reply-To: <4DE3DA18.40604@swing.be> References: <4DE39E8F.20201@sacrumromanumimperium.org> <4DE3C36B.9090209@swing.be> <19939.50686.971309.911038@zaphod.ms25.net> <4DE3DA18.40604@swing.be> Message-ID: <19939.57288.712442.353819@zaphod.ms25.net> On 2011-05-30 at 19:55:36 +0200, Alain Delmotte wrote: > OK! > > I answer from my machine, which is in French, you'll > translate, menu "D?marrer" You are obviously under Windows but he installed the files at /usr/local/texlive/texmf-local/tex/latex Regards, Reinhard > Alain > > Le 30/05/2011 18:29, Reinhard Kotucha a ?crit : > > On 2011-05-30 at 18:18:51 +0200, Alain Delmotte wrote: > > > > > Hi! > > > > > > Sorry but Ng Kah Loon is not using MikTeX but TeXLive. > > > > > > When you install TeXLive, there is a folder created in the > > > Start menu, in which you could find the "TeX Live Manager". > > > > Which Start menu? > > > > Regards, > > Reinhard > > > -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha at web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- From sigmundv at gmail.com Mon May 30 20:39:39 2011 From: sigmundv at gmail.com (sigmundv at gmail.com) Date: Mon, 30 May 2011 20:39:39 +0200 Subject: [texworks] Problem installing packages In-Reply-To: References: Message-ID: On Mon, May 30, 2011 at 09:27, Ng Kah Loon wrote: > I would really appreciate any assistance provided. > The best and easiest way to install new packages in TeXLive is to use the tlmgr tool (see http://www.tug.org/texlive/doc/texlive-en/texlive-en.html#x1-450005). /Sigmund -------------- next part -------------- An HTML attachment was scrubbed... URL: From sigmundv at gmail.com Mon May 30 20:49:14 2011 From: sigmundv at gmail.com (sigmundv at gmail.com) Date: Mon, 30 May 2011 20:49:14 +0200 Subject: [texworks] Stata output In-Reply-To: References: Message-ID: On Mon, May 30, 2011 at 13:57, Economides, Nicholas wrote: > Any ideas/recommendations? > > Follow the instructions on the following page: http://docs.miktex.org/2.9/manual/pkgmgt.html. /Sigmund -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Mon May 30 20:48:54 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Mon, 30 May 2011 20:48:54 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> Message-ID: <4DE3E696.6070004@gmail.com> Hi, On 2011-05-30 19:52, Charlie Sharpsteen wrote: > On Sun, May 29, 2011 at 4:25 AM, Jonathan Kew wrote: >> Maybe we could enhance the code to try both ZapfDingbats and ZapfDingbatsITC? > I replaced the declaration of `myName` at the beginning of > `GlobalParams::loadPlatformFont`: > > char * myName = copyString(fontName); > > With: > > char *myName; > if ( strcmp((const char*) fontName, "ZapfDingbats") == 0 ) { > myName = copyString("ZapfDingbatsITC"); > } else { > myName = copyString(fontName); > } Crude, but for debugging purposes effective (though ultimately, we should probably try "ZapfDingbats" first; who knows if that isn't available on some systems, or if Apple changes it in the future...). > Lookup font: ZapfDingbatsITC > ATSFontFindFromPostScriptName found fontRef > found 'glyf' table > found in file: /System/Library/Fonts/ZapfDingbats.ttf > Bogus memory allocation size Strange. My guess would be that the .ttf has some problems, but we'll see. Can you check (by adding "std:cerr <<" lines which of the lines following the "found in file" message succeed? If it runs until the "return gTrue;", the problem is (hopefully) not in our patch. Otherwise, we know where to start digging. HTH Stefan From chuck at sharpsteen.net Tue May 31 04:43:20 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Mon, 30 May 2011 19:43:20 -0700 Subject: [texworks] Background image Drag N' Drop installer In-Reply-To: <4DE1F547.7070201@gmail.com> References: <4DE11977.9090408@gmail.com> <4DE1F547.7070201@gmail.com> Message-ID: On Sun, May 29, 2011 at 12:27 AM, Stefan L?ffler wrote: > Hi, > > On 2011-05-28 18:25, Charlie Sharpsteen wrote: >> This looks great! Although I think we need to remove the icon images >> as they will be provided by the icons of the actual app and folder. > > Sure, no problem. In fact, without the icons the svg becomes smaller and > more portable (not to mention less prone to license violations connected > to the apps folder icon ;)). > >> Having the SVG file would be interesting as we could possibly insert a >> variable for the version number that gets filled in during >> configuration. Then something like ImageMagick could be used to render >> the SVG to a PNG. > > Yeah, that was the (ultimate) idea. If it works, one could even add the > revision number - but if it doesn't, sticking with just the version is > fine as well, and with only a few releases per year (at most) easy to > keep track of manually. > > Anyway, I attached the (somewhat cleaned) svg file, plus the same pngs > in case the conversion doesn't work out of the box. Note that I created > the image in Inkscape, and used some rather fancy clipping boxes etc. of > which I don't know how portable they are. > > Cheers, > Stefan Allright, I added the SVG file and the PNG without version number to the Git repository. It seems that Inkscape is the only thing that can faithfully render an Inkscape SVG to PNG. ImageMagick's `convert` utility fails miserably. `svg2png` comes close, but it trips over positioning the E in TeX. So, the background without version number is used by default and packagers will have to export a new background from the SVG template if they are packing up a specific release. Also, it turned out that the best way to arrange the contents of the disk image was to use AppleScript since it automates the task rather than re-using a .DS_Store file from a folder whose contents were arranged by hand and hope it still works. The steps required for packaging are now: make package # If you want a nicely formatted DMG ./set_dmg_layout.scpt -Charlie From st.loeffler at gmail.com Tue May 31 07:22:46 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Tue, 31 May 2011 07:22:46 +0200 Subject: [texworks] Background image Drag N' Drop installer In-Reply-To: References: <4DE11977.9090408@gmail.com> <4DE1F547.7070201@gmail.com> Message-ID: <4DE47B26.2090407@gmail.com> Hi, On 2011-05-29 23:07, sigmundv at gmail.com wrote: > > Note that I created > the image in Inkscape, and used some rather fancy clipping boxes > etc. of > which I don't know how portable they are. > > > Using TikZ (TikZ ist kein Zeichenprogramm) would make the image > generation very portable. It doesn't output SVG though, but still it > outputs vector graphics (PDF/EPS - I know, PDF is technically not an > image format). Just for clarification: I didn't refer to "portable" in the sense of cross-platform compatibility (svg is simply a text file, so it should be loadable/editable on any system), but rather in the sense of "I don't know which tools can render it properly" (and sadly, Charlie confirmed these doubts). Anyway, I figured that none of this actually matters. Using the mac-installer-background-no-version.png, it should be easy to add the version number with just about any image editing tool. You can try the following command line, for example (assuming the environment variable TW_VERSION is set to the string you want to add): convert mac-installer-background-no-version.png -fill white -font 'FreeSans-Mittel' -pointsize 20 -draw "gravity SouthWest text 17,7 '$TW_VERSION'" mac-installer-background.png Of course, the font is specific to the installation, something like Helvetica would probably be more Mac'ish. Cheers, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From jingleihu at gmail.com Wed Jun 1 10:00:05 2011 From: jingleihu at gmail.com (Jinglei Hu) Date: Wed, 1 Jun 2011 10:00:05 +0200 Subject: [texworks] low sensitivity of two finger scroll up/down built-in pdf viewer Message-ID: <2246C44A-B853-4F0D-A43F-0CE3E0CF87BC@gmail.com> Dear developers, I have been trying TeXworks 0.4.1 r.829(personal) on Mac OSX SL 10.6.7, and found that two finger guesture scroll down/up is much less sensitive in TeXworks built-in pdf viewer than that in systme built-in quick look. Plus, I got few feature requests: (a) to include 'Clear Menu' in File->Open Recent option. (b) to enable full screen tex file editing mode. Thanks for the nice work. Best, Jinglei Hu -------------- next part -------------- An HTML attachment was scrubbed... URL: From kloon at nus.edu.sg Wed Jun 1 18:20:43 2011 From: kloon at nus.edu.sg (Ng Kah Loon) Date: Thu, 2 Jun 2011 00:20:43 +0800 Subject: [texworks] Problem installing packages In-Reply-To: <19939.50311.261815.196063@zaphod.ms25.net> Message-ID: Well, many thanks for the responses so far....but I am sorry I still cannot get it...can anyone help to explain how I can run mktexlsr? I am using MacBook Air and TexWorks is installed in my 60GB Macintosh HD....I don't know what is the path.... Please assist, thank you very much! On 31/5/11 12:23 AM, "Reinhard Kotucha" wrote: >On 2011-05-30 at 16:18:34 +0100, Economides, Nicholas wrote: > > > Hi, > > > > the thing is that everyone say that we have to refresh the database > > for the files, but since most of us do not have a degree in > > programming, you guys should be a bit more specific. > >Please read the mails more carefully before confusing people. >Andreas' answer was specific enough and what you propose doesn't work >in this case. > > > Anyway, I found a way to do this and I hope Ng Kah Loon will find > > it helpful as well: > > > > find the file called mo_admin.exe which should be located at the > > path miktex 2.9/miktex/bin/ Once you run it, you should get the > > miktex options. At the general page, click the "refresh FNDB" > > button, and then the "update formats" button > > > > This should help Miktex/Latex understand that you have just added > > something new. > > > > Before you do that, you should make sure that you pasted the > > package folder that you have downloaded in to the path tex/latex > > > > I believe after you have done that it should work. > >Is everything so complicated under MiKTeX? > >Regards, > Reinhard > >-- >-------------------------------------------------------------------------- >-- >Reinhard Kotucha Phone: >+49-511-3373112 >Marschnerstr. 25 >D-30167 Hannover >mailto:reinhard.kotucha at web.de >-------------------------------------------------------------------------- >-- >Microsoft isn't the answer. Microsoft is the question, and the answer is >NO. >-------------------------------------------------------------------------- >-- From herbs at wideopenwest.com Wed Jun 1 18:50:02 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Wed, 1 Jun 2011 11:50:02 -0500 Subject: [texworks] Problem installing packages In-Reply-To: References: Message-ID: <93E77B03-9665-483C-A7DD-E7DE85377C30@wideopenwest.com> On Jun 1, 2011, at 11:20 AM, Ng Kah Loon wrote: > Well, many thanks for the responses so far....but I am sorry I still > cannot get it...can anyone help to explain how I can run mktexlsr? > > I am using MacBook Air and TexWorks is installed in my 60GB Macintosh > HD....I don't know what is the path.... > > Please assist, thank you very much! Howdy, What TeX distribution are you using? Have you tried to use Terminal.app and run sudo mktexlsr giving your admin password? Good Luck, Herb Schulz (herbs at wideopenwest dot com) From chuck at sharpsteen.net Wed Jun 1 19:23:36 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Wed, 1 Jun 2011 10:23:36 -0700 Subject: [texworks] low sensitivity of two finger scroll up/down built-in pdf viewer In-Reply-To: <2246C44A-B853-4F0D-A43F-0CE3E0CF87BC@gmail.com> References: <2246C44A-B853-4F0D-A43F-0CE3E0CF87BC@gmail.com> Message-ID: On Wed, Jun 1, 2011 at 1:00 AM, Jinglei Hu wrote: > Dear developers, > I have been trying TeXworks 0.4.1 r.829(personal) on Mac OSX SL 10.6.7, and > found that two finger guesture scroll down/up is much less sensitive in > TeXworks built-in pdf viewer than that in ?systme built-in quick look. I would guess this is because the TeXworks PDF viewer displays documents one page at a time. Each time you scroll to the top or bottom of a page the viewer pauses, loads another page, and resets the scrollbar. This seems to me like something that could cause "choppy" scrolling behavior. I guess the real test is: Does two-finger scrolling work as expected in the TeXworks text editor? > Plus, I got few feature requests: > (a) to include 'Clear Menu' in File->Open Recent option. > (b) to enable full screen tex file editing mode. > Thanks for the nice work. > Best, Jinglei Hu From chuck at sharpsteen.net Wed Jun 1 19:35:31 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Wed, 1 Jun 2011 10:35:31 -0700 Subject: [texworks] Problem installing packages In-Reply-To: References: <19939.50311.261815.196063@zaphod.ms25.net> Message-ID: On Wed, Jun 1, 2011 at 9:20 AM, Ng Kah Loon wrote: > Well, many thanks for the responses so far....but I am sorry I still > cannot get it...can anyone help to explain how I can run mktexlsr? > > I am using MacBook Air and TexWorks is installed in my 60GB Macintosh > HD....I don't know what is the path.... > > Please assist, thank you very much! Good to know you are using a Mac---most of the replies in this thread assumed you were running Windows. Assuming you are using MacTeX or TeX Live as your distribution, the first place you should turn for package installation is the TeX Live Manager (or `tlmgr`). A nice Mac GUI is available at: http://code.google.com/p/mactlmgr And was probably installed to /Applications/TeX if you installed the full MacTeX distribution. For packages like tkz-graph that aren't available through tlmgr, you should place your LaTeX *.sty files and other package bits in: ~/Library/texmf/tex/latex (or if you are using TeX Live instead of MacTeX) ~/texmf/tex/latex Then just pop open /Applications/Utilities/Termina.app and type `mktexlsr`. No sudo required. Hope this helps, -Charlie From herbs at wideopenwest.com Wed Jun 1 20:23:04 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Wed, 1 Jun 2011 13:23:04 -0500 Subject: [texworks] Problem installing packages In-Reply-To: References: <19939.50311.261815.196063@zaphod.ms25.net> Message-ID: <9971E86B-5669-42A2-B75E-B8DD6D099366@wideopenwest.com> On Jun 1, 2011, at 12:35 PM, Charlie Sharpsteen wrote: > On Wed, Jun 1, 2011 at 9:20 AM, Ng Kah Loon wrote: >> Well, many thanks for the responses so far....but I am sorry I still >> cannot get it...can anyone help to explain how I can run mktexlsr? >> >> I am using MacBook Air and TexWorks is installed in my 60GB Macintosh >> HD....I don't know what is the path.... >> >> Please assist, thank you very much! > > Good to know you are using a Mac---most of the replies in this thread > assumed you were running Windows. > > Assuming you are using MacTeX or TeX Live as your distribution, the > first place you should turn for package installation is the TeX Live > Manager (or `tlmgr`). A nice Mac GUI is available at: > > http://code.google.com/p/mactlmgr > > And was probably installed to /Applications/TeX if you installed the > full MacTeX distribution. > > > For packages like tkz-graph that aren't available through tlmgr, you > should place your LaTeX *.sty files and other package bits in: > > ~/Library/texmf/tex/latex > > (or if you are using TeX Live instead of MacTeX) > ~/texmf/tex/latex > > Then just pop open /Applications/Utilities/Termina.app and type > `mktexlsr`. No sudo required. > > Hope this helps, > > -Charlie Howdy, Just to note that placing items in your personal tree (~/Library/texmf/...) doesn't require the use of mktexlsr (or, the synonym, texhash). That tree is searched directly. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From chuck at sharpsteen.net Wed Jun 1 23:38:44 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Wed, 1 Jun 2011 14:38:44 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DE3E696.6070004@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> Message-ID: On Mon, May 30, 2011 at 11:48 AM, Stefan L?ffler wrote: > Hi, > > On 2011-05-30 19:52, Charlie Sharpsteen wrote: >> On Sun, May 29, 2011 at 4:25 AM, Jonathan Kew wrote: >>> Maybe we could enhance the code to try both ZapfDingbats and ZapfDingbatsITC? >> I replaced the declaration of `myName` at the beginning of >> `GlobalParams::loadPlatformFont`: >> >> ? ? char * myName = copyString(fontName); >> >> With: >> >> ? ? char *myName; >> ? ? if ( strcmp((const char*) fontName, "ZapfDingbats") == 0 ) { >> ? ? ? myName = copyString("ZapfDingbatsITC"); >> ? ? } else { >> ? ? ? myName = copyString(fontName); >> ? ? } > > Crude, but for debugging purposes effective (though ultimately, we > should probably try "ZapfDingbats" first; who knows if that isn't > available on some systems, or if Apple changes it in the future...). I cleaned the implementation up a little bit by placing the substitution inside the first `while` loop along with the other tricks that get tried if `ATSFontFindFromPostScriptName` returns `kATSUInvalidFontID`: https://github.com/Sharpie/TeXworks/commit/037a148 >> Lookup font: ZapfDingbatsITC >> ? ?ATSFontFindFromPostScriptName found fontRef >> ? ?found 'glyf' table >> ? ?found in file: /System/Library/Fonts/ZapfDingbats.ttf >> Bogus memory allocation size > > Strange. My guess would be that the .ttf has some problems, but we'll see. > Can you check (by adding "std:cerr <<" lines which of the lines > following the "found in file" message succeed? If it runs until the > "return gTrue;", the problem is (hopefully) not in our patch. Otherwise, > we know where to start digging. > > HTH > Stefan I also bumped up the debugging verbosity a bit and extended the messages to the `getDisplayFont` method which is what calls `loadPlatformFont`---this includes messages that get printed every time the variable `myName` is altered so that it is different than what was copied from `fontName`. The results were interesting: Lookup font: Times-Roman Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/Lgp7uLyf.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Times-Bold Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/WhxA2P62.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Times-Italic Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/tTwspGOu.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Times-BoldItalic Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/7vtq0Lms.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Helvetica Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/YstMMD3G.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Helvetica-Bold Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/bYuUncqC.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Helvetica-Oblique Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/G1HQTZHK.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Helvetica-BoldOblique Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/Bn1ZK7yN.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Courier Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/w2aox6iO.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Courier-Bold Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/Esqo3EQX.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Courier-Oblique Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/935QMecc.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Courier-BoldOblique Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table no TTF file found, checking for .dfont ATSFontGetTableDirectory succeeded font converted to /tmp/yGgX6wZZ.ttf returning temporary TTF file. Finished getDisplayFont. Lookup font: Symbol Loading font. ATSFontFindFromPostScriptName found fontRef found 'glyf' table found in file: /System/Library/Fonts/Symbol.ttf returning TTF file. Finished getDisplayFont. Lookup font: ZapfDingbats Loading font. Substituting ZapfDingbatsITC for ZapfDingbats. ATSFontFindFromPostScriptName found fontRef found 'glyf' table found in file: /System/Library/Fonts/ZapfDingbats.ttf returning TTF file. Finished getDisplayFont. Lookup font: Times-Roman Finished getDisplayFont. Lookup font: Times-Bold Finished getDisplayFont. Lookup font: Times-Italic Finished getDisplayFont. Lookup font: Times-BoldItalic Finished getDisplayFont. Lookup font: Helvetica Finished getDisplayFont. Lookup font: Helvetica-Bold Finished getDisplayFont. Lookup font: Helvetica-Oblique Finished getDisplayFont. Lookup font: Helvetica-BoldOblique Finished getDisplayFont. Lookup font: Courier Finished getDisplayFont. Lookup font: Courier-Bold Finished getDisplayFont. Lookup font: Courier-Oblique Finished getDisplayFont. Lookup font: Courier-BoldOblique Finished getDisplayFont. Lookup font: Symbol Finished getDisplayFont. Lookup font: ZapfDingbats Finished getDisplayFont. Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size Bogus memory allocation size ZapfDingbats is the only font for which `loadPlatformFont` has to alter the `fontName` in order for `ATSFontFindFromPostScriptName` to get a match. It looks like whatever is happening to produce the memory errors is happening outside of `GlobalParamsMac.cc`, but may be influenced by the substitution that occurs within `loadPlatformFont`. -Charlie From st.loeffler at gmail.com Thu Jun 2 17:00:44 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 02 Jun 2011 17:00:44 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> Message-ID: <4DE7A59C.9080506@gmail.com> Hi, On 2011-06-01 23:38, Charlie Sharpsteen wrote: > I cleaned the implementation up a little bit by placing the > substitution inside the first `while` loop along with the other tricks > that get tried if `ATSFontFindFromPostScriptName` returns > `kATSUInvalidFontID`: > > https://github.com/Sharpie/TeXworks/commit/037a148 Looking good, thanks. > I also bumped up the debugging verbosity a bit and extended the > messages to the `getDisplayFont` method which is what calls > `loadPlatformFont`---this includes messages that get printed every > time the variable `myName` is altered so that it is different than > what was copied from `fontName`. The results were interesting: > > Lookup font: ZapfDingbats > Loading font. > Substituting ZapfDingbatsITC for ZapfDingbats. > ATSFontFindFromPostScriptName found fontRef > found 'glyf' table > found in file: /System/Library/Fonts/ZapfDingbats.ttf > returning TTF file. > Finished getDisplayFont. > > Bogus memory allocation size > Bogus memory allocation size > Bogus memory allocation size > Bogus memory allocation size > Bogus memory allocation size > Bogus memory allocation size > Bogus memory allocation size > Bogus memory allocation size > > > ZapfDingbats is the only font for which `loadPlatformFont` has to > alter the `fontName` in order for `ATSFontFindFromPostScriptName` to > get a match. It looks like whatever is happening to produce the memory > errors is happening outside of `GlobalParamsMac.cc`, but may be > influenced by the substitution that occurs within `loadPlatformFont`. Yes, it's quite definitely happending outside our code. Whether it's influenced by the substitution I'm not so sure, though. As far as I can see, all those substitutions work on a local copy myName of fontName, so I don't see how this should cause problems. Anyway, this is quite easy to test: Could you open the testcase pdf file (in a text editor) and replace all occurrences of ZapfDingbats by ZapfDingbatsITC? That way, I hope poppler will look for the correct file straight away and the substitution should not kick in (though checking with some debugging output lines can't hurt). If the "Bogus..." lines still occur the problem probably is in the font file itself... Alternatively, you can replace another font (e.g., "Times-Roman" > "Times-RomanTest") in the pdf and add subsitution lines for replacing "Times-RomanTest" back to "Times-Roman" in the poppler source. HTH Stefan PS: Thanks for persevering :). From chuck at sharpsteen.net Thu Jun 2 18:19:21 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 2 Jun 2011 09:19:21 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DE7A59C.9080506@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> Message-ID: On Thu, Jun 2, 2011 at 8:00 AM, Stefan L?ffler wrote: > Hi, > > On 2011-06-01 23:38, Charlie Sharpsteen wrote: >> I cleaned the implementation up a little bit by placing the >> substitution inside the first `while` loop along with the other tricks >> that get tried if `ATSFontFindFromPostScriptName` returns >> `kATSUInvalidFontID`: >> >> ? ? https://github.com/Sharpie/TeXworks/commit/037a148 > > Looking good, thanks. > >> I also bumped up the debugging verbosity a bit and extended the >> messages to the `getDisplayFont` method which is what calls >> `loadPlatformFont`---this includes messages that get printed every >> time the variable `myName` is altered so that it is different than >> what was copied from `fontName`. ?The results were interesting: >> >> Lookup font: ZapfDingbats >> Loading font. >> ? ?Substituting ZapfDingbatsITC for ZapfDingbats. >> ? ?ATSFontFindFromPostScriptName found fontRef >> ? ?found 'glyf' table >> ? ?found in file: /System/Library/Fonts/ZapfDingbats.ttf >> ? ?returning TTF file. >> Finished getDisplayFont. >> >> Bogus memory allocation size >> Bogus memory allocation size >> Bogus memory allocation size >> Bogus memory allocation size >> Bogus memory allocation size >> Bogus memory allocation size >> Bogus memory allocation size >> Bogus memory allocation size >> >> >> ZapfDingbats is the only font for which `loadPlatformFont` has to >> alter the `fontName` in order for `ATSFontFindFromPostScriptName` to >> get a match. It looks like whatever is happening to produce the memory >> errors is happening outside of `GlobalParamsMac.cc`, but may be >> influenced by the substitution that occurs within `loadPlatformFont`. > > Yes, it's quite definitely happending outside our code. Whether it's > influenced by the substitution I'm not so sure, though. As far as I can > see, all those substitutions work on a local copy myName of fontName, so > I don't see how this should cause problems. > Anyway, this is quite easy to test: > Could you open the testcase pdf file (in a text editor) and replace all > occurrences of ZapfDingbats by ZapfDingbatsITC? That way, I hope poppler > will look for the correct file straight away and the substitution should > not kick in (though checking with some debugging output lines can't > hurt). If the "Bogus..." lines still occur the problem probably is in > the font file itself... > Alternatively, you can replace another font (e.g., "Times-Roman" > > "Times-RomanTest") in the pdf and add subsitution lines for replacing > "Times-RomanTest" back to "Times-Roman" in the poppler source. > > HTH > Stefan > > PS: Thanks for persevering :). Allright, I did some poking around: - Changing ZapfDingbats to ZapfDingbatsITC in base-14-font.pdf does not solve the Bogus memory allocation errors, however it does cause all the dingbat glyphs to be replaced with .notdef boxes. - Changing Helvitical to HelviticaFoo and altering the ZapfDingbat substitution to operate on it instead had no effect. - The errors are coming from the memory allocator for the Goo objects that Poppler uses. - I followed the function calls out of GlobalParamsMac.cc and into SplashOutputDev.cc. They don't occur in `SplashOutputDev::doUpdateFont` which is the function that calls `getDisplayFont` from GlobalParamsMac.cc. Not sure what else to do at this point. -Charlie From st.loeffler at gmail.com Thu Jun 2 23:29:53 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 02 Jun 2011 23:29:53 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> Message-ID: <4DE800D1.7080700@gmail.com> Hi, On 2011-06-02 18:19, Charlie Sharpsteen wrote: > Allright, I did some poking around: > > - Changing ZapfDingbats to ZapfDingbatsITC in base-14-font.pdf does > not solve the Bogus memory allocation errors, however it does cause > all the dingbat glyphs to be replaced with .notdef boxes. Hm, this is unexpected (for me, anyway). Am I right in assuming that in this case, none of the substitution, .dfont handling and stuff kicks in but it simply returns the .ttf file? If that is the case, I don't understand why all glyphs come out as .notdef. Unless there is some other ZapfDingbats-specific code somewhere... Does anyone with more experience with/knowledge about fonts have any ideas? > - Changing Helvitical to HelviticaFoo and altering the ZapfDingbat > substitution to operate on it instead had no effect. OK. Unfortunately, Helvetica is the default substitution for all missing fonts, AFAIK. So maybe picking another one would be a good idea. Anyway, does it find Helvetica properly? > - The errors are coming from the memory allocator for the Goo > objects that Poppler uses. Yes, I found the error message there as well. Could you find out which one of the *malloc it is (e.g., by simply altering the different error messages so they are unique)? > - I followed the function calls out of GlobalParamsMac.cc and into > SplashOutputDev.cc. They don't occur in > `SplashOutputDev::doUpdateFont` which is the function that calls > `getDisplayFont` from GlobalParamsMac.cc. > > Not sure what else to do at this point. Well, the more we learn about this, the more it seems that there are some hacks or others at work - either in poppler, in fontconfig, or in the font itself, that are causing this. The only other thing I can imagine that could be done is to run everything through a debugger, break at the error message output and look at the backtrace (and possible the variables) to find out where this is coming from. Anyway, I'll have a look at the code again to see if I can find anything related to ZapfDingats, but I need to get some sleep first ;). Cheers, Stefan From chuck at sharpsteen.net Fri Jun 3 02:42:06 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 2 Jun 2011 17:42:06 -0700 Subject: [texworks] Another TeXworks mac build (with a buildsystem!) In-Reply-To: References: Message-ID: The CMake buildsystem I wrote for TeXworks is starting to stabilize---I don't forsee any major changes from this point on. Mac packaging tasks are pretty much complete. The last remaining issue with the Mac build has to do with the Poppler library and doesn't involve the build system. I feel like it may be getting to the point where we could start thinking about merging this work back into the SVN repository. I've started to pay attention to documentation so it will be easier for other people to extend and maintain the work that I have done. Taking a page from the literate programming book, I have been cleaning up my comments in the CMake files so that a documentation generator like Docco can turn them into something that can serve as a README. The preliminary results are here: http://sharpie.github.com/TeXworks If there is anything else I should do to help integrate my code back into the main repository, please let me know! -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Fri Jun 3 04:48:47 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Fri, 3 Jun 2011 14:48:47 +1200 Subject: [texworks] syntax-patterns.txt Message-ID: Hi, Just wanted to check a couple of things please - got into a mind maze with this stuff. With syntax-patterns.txt which dialect of regular expressions is being used please? In that dialect does .* mean anything many times? Can () be used to choose which part of an expression is colourised? For e.g. skyblue N .*\{(http[s]://.*)} -- Would colour only the actual address? Paul From st.loeffler at gmail.com Fri Jun 3 12:31:49 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Fri, 03 Jun 2011 12:31:49 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> Message-ID: <4DE8B815.1090409@gmail.com> Hi again, On 2011-06-02 18:19, Charlie Sharpsteen wrote: > Allright, I did some poking around: > > - Changing ZapfDingbats to ZapfDingbatsITC in base-14-font.pdf does > not solve the Bogus memory allocation errors, however it does cause > all the dingbat glyphs to be replaced with .notdef boxes. I did some searching now. ZapfDingbats is indeed handled specially. From the looks of poppler/BuiltinFontTables.cc, the glyph widths are hard-coded, and a special encoding table (see poppler/FontEncodingTables.cc) is used. Apparently, this is chosen by Postscript font name. So, this explains why a font named ZapfDingbatsITC doesn't get the correct encoding. But since the "Bogus..." messages didn't go away, I'm beginning to think more and more that there is some peculiarity about the font file that causes poppler to throw these messages. Maybe some header field is empty or missing that poppler would expect? > - Changing Helvitical to HelviticaFoo and altering the ZapfDingbat > substitution to operate on it instead had no effect. No effect meaning that the "Bogus..." messages didn't change, right? So they are still coming form ZapfDingbats, not from the replaced Helvetica? > - I followed the function calls out of GlobalParamsMac.cc and into > SplashOutputDev.cc. They don't occur in > `SplashOutputDev::doUpdateFont` which is the function that calls > `getDisplayFont` from GlobalParamsMac.cc. > > Not sure what else to do at this point. Hm, I wonder... The "Bogus..." messages always occur after all "Lookup font..." messages right? This might suggest that they occur not in the initialization phase but in the actual drawing phase (possibly in SplashOutputDev::drawChar). HTH Stefan From st.loeffler at gmail.com Fri Jun 3 12:52:07 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Fri, 03 Jun 2011 12:52:07 +0200 Subject: [texworks] syntax-patterns.txt In-Reply-To: References: Message-ID: <4DE8BCD7.1070500@gmail.com> Hi, On 2011-06-03 04:48, Paul A Norman wrote: > Just wanted to check a couple of things please - got into a mind maze > with this stuff. Yeah, that can happen terribly easily with regexps ;). > With syntax-patterns.txt which dialect of regular expressions is being > used please? The Qt dialect (http://doc.trolltech.com/4.7/qregexp.html#details). In fact, the string given in syntax-patterns.txt is simply wrapped into a QRegExp object (see src/TeXHighlighter.cpp at 226). > In that dialect does .* mean anything many times? Yes, anything zero or more times (one or more would be .+). The quantifiers are also greedy (they match as much as they possibly can). > Can () be used to choose which part of an expression is colourised? > For e.g. > > skyblue N .*\{(http[s]://.*)} > > -- Would colour only the actual address? No, not at the moment, unfortunately. It should be possible to use look-ahead assertions to match a string only if it followed by a certain string (without including the second in the match), but look-behind assertions are not supported, unfortunately. In principle, colorizing the captured text could probably be added to the code, but it would have drawbacks for people who are lazy and just write, e.g., "(W|w)arning" instead of "(?:W|w)arning". BTW: You probably want something like "\{(https?://[^}]*)\}". HTH Stefan From paul.a.norman at gmail.com Sat Jun 4 01:27:20 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sat, 4 Jun 2011 11:27:20 +1200 Subject: [texworks] syntax-patterns.txt In-Reply-To: <4DE8BCD7.1070500@gmail.com> References: <4DE8BCD7.1070500@gmail.com> Message-ID: Thanks very much Stefan, Paul On 3 June 2011 22:52, Stefan L?ffler wrote: > Hi, > > On 2011-06-03 04:48, Paul A Norman wrote: >> Just wanted to check a couple of things please - got ?into a mind maze >> with this stuff. > > Yeah, that can happen terribly easily with regexps ;). > >> With syntax-patterns.txt which dialect of regular expressions is being >> used please? > > The Qt dialect (http://doc.trolltech.com/4.7/qregexp.html#details). In > fact, the string given in syntax-patterns.txt is simply wrapped into a > QRegExp object (see src/TeXHighlighter.cpp at 226). > >> In that dialect does .* mean ?anything many times? > > Yes, anything zero or more times (one or more would be .+). The > quantifiers are also greedy (they match as much as they possibly can). > >> Can () be used to choose which part of an expression is colourised? >> For e.g. >> >> skyblue N .*\{(http[s]://.*)} >> >> ? ? -- Would colour only the actual address? > > No, not at the moment, unfortunately. It should be possible to use > look-ahead assertions to match a string only if it followed by a certain > string (without including the second in the match), but look-behind > assertions are not supported, unfortunately. > > In principle, colorizing the captured text could probably be added to > the code, but it would have drawbacks for people who are lazy and just > write, e.g., "(W|w)arning" instead of "(?:W|w)arning". > > BTW: You probably want something like "\{(https?://[^}]*)\}". > > HTH > Stefan > From suresh.amritapuri at gmail.com Sat Jun 4 03:05:43 2011 From: suresh.amritapuri at gmail.com (Suresh Kumar) Date: Fri, 3 Jun 2011 18:05:43 -0700 Subject: [texworks] ctrl + T not working Message-ID: Hi I am using texworks Version 0.4.1 r.829 on ubuntu 10.04. I find that Ctrl + T (pressing T while pressing cntrl) is not working. However the menu typeset -> typeset works as well as the arrow symbol available just below the menu bar. Any suggestions? thanks suresh -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Sat Jun 4 22:47:08 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sat, 4 Jun 2011 13:47:08 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DE800D1.7080700@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> Message-ID: On Thu, Jun 2, 2011 at 2:29 PM, Stefan L?ffler wrote: On 2011-06-02 18:19, Charlie Sharpsteen wrote: > > - Changing ZapfDingbats to ZapfDingbatsITC in base-14-font.pdf does > > not solve the Bogus memory allocation errors, however it does cause > > all the dingbat glyphs to be replaced with .notdef boxes. > > Hm, this is unexpected (for me, anyway). Am I right in assuming that in > this case, none of the substitution, .dfont handling and stuff kicks in > but it simply returns the .ttf file? If that is the case, I don't > understand why all glyphs come out as .notdef. Unless there is some > other ZapfDingbats-specific code somewhere... Does anyone with more > experience with/knowledge about fonts have any ideas? On OS X 10.6.x, there is no .dfont file, just a .ttf file. I haven't done much bug hunting on 10.5.x where ZapfDingbats is a .dfont, but some quick tests I did there shows that the behavior is mostly the same. > - The errors are coming from the memory allocator for the Goo > > objects that Poppler uses. > > Yes, I found the error message there as well. Could you find out which > one of the *malloc it is (e.g., by simply altering the different error > messages so they are unique)? The errors all come from the `gmallocn` allocator. On Fri, Jun 3, 2011 at 3:31 AM, Stefan L?ffler wrote: > > > - Changing Helvitical to HelviticaFoo and altering the ZapfDingbat > > substitution to operate on it instead had no effect. > > No effect meaning that the "Bogus..." messages didn't change, right? So > they are still coming form ZapfDingbats, not from the replaced Helvetica? No effect meaning that the substitution of "Helvitica" for "HelviticaFoo" produces no side effects such as "Bogus" messages from the Goo allocator unlike the substitution of "ZapfDingbatsITC" for "ZapfDingbats". Should have been more clear about that :). I also tried a similar test with Courier and got no error messages. > > - I followed the function calls out of GlobalParamsMac.cc and into > > SplashOutputDev.cc. They don't occur in > > `SplashOutputDev::doUpdateFont` which is the function that calls > > `getDisplayFont` from GlobalParamsMac.cc. > > > > Not sure what else to do at this point. > > Hm, I wonder... The "Bogus..." messages always occur after all "Lookup > font..." messages right? This might suggest that they occur not in the > initialization phase but in the actual drawing phase (possibly in > SplashOutputDev::drawChar). > Good guess about `SplashOutputDev::drawChar`. Getting Poppler to build in a GDB-friendly way took some hair pulling---the Autotools build uses libtool and libtool "helpfully" nukes object files after it gets done linking libraries. Previously, I got into a fight with libtool when compiling Poppler for the the Leopard builds as it was also "helpfully" stripping some essential compiler flags. I am now officially not a fan of libtool, it seriously needs a `--dont-try-to-be-clever` flag. Fortunately the Poppler CMake build doesn't try to pull such shenanigans. It faithfully passes compiler flags and leaves object files alone. I expanded `poppler-mac-font-handling.patch` to add the Mac font handling option to the Poppler CMake build as well as the Autotools build: https://github.com/Sharpie/TeXworks/commit/251eb23 As I recall, lack of CMake support may have been an issue that kept Jonathan's patch out of the official Poppler tree: http://lists.freedesktop.org/archives/poppler/2009-July/004972.html Anyway, after getting TeXworks and Poppler to run through GDB, a backtrace from the error message indicates that the problem occurs in `SplashFTFont::makeGlyph` at `SplashFTFont.cc:244` which is a couple steps down the call chain from `SplashOutputDev::drawChar`. I'll try to look over this later to see if I can figure anything out, but here is the full backtrace: Formatted: https://gist.github.com/1008336 Raw: https://gist.github.com/raw/1008336/1c01061723261e5d3b6d583ff059a82ac0f00482/texworks_gdb_log.mdown Let me know if anything jumps out! -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From jfkthame at googlemail.com Sun Jun 5 00:38:42 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Sat, 4 Jun 2011 23:38:42 +0100 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> Message-ID: <588384FA-9826-4B8F-9AE7-5AB260AC7D41@gmail.com> On 4 Jun 2011, at 21:47, Charlie Sharpsteen wrote: > > Anyway, after getting TeXworks and Poppler to run through GDB, a backtrace from the error message indicates that the problem occurs in `SplashFTFont::makeGlyph` at `SplashFTFont.cc:244` which is a couple steps down the call chain from `SplashOutputDev::drawChar`. I'll try to look over this later to see if I can figure anything out, but here is the full backtrace: > > Formatted: > https://gist.github.com/1008336 > > Raw: > https://gist.github.com/raw/1008336/1c01061723261e5d3b6d583ff059a82ac0f00482/texworks_gdb_log.mdown > > Let me know if anything jumps out! So at the lowest level, it's complaining about trying to allocate some kind of object of size zero; the goo allocator considers that invalid. Looks like this is happening on the space character, probably (c=32 in your call stack). I wonder if there's something about the space glyph in this version of ZapfDingbats that breaks an assumption in poppler. Space would be unusual in that it has no contours; but that would be true in most fonts, of course, so I don't know why this particular one causes trouble when other fonts apparently work ok. (Of course, TeX doesn't usually generate space glyphs at all, but I'd expect them to be present in PDFs from other sources that poppler handles without problems.) JK From st.loeffler at gmail.com Sun Jun 5 09:22:50 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 05 Jun 2011 09:22:50 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> Message-ID: <4DEB2ECA.6090008@gmail.com> Hi, finally, the pieces of the puzzle are starting to fit together :). On 2011-06-04 22:47, Charlie Sharpsteen wrote: > > > - Changing Helvitical to HelviticaFoo and altering the ZapfDingbat > > substitution to operate on it instead had no effect. > > No effect meaning that the "Bogus..." messages didn't change, > right? So > they are still coming form ZapfDingbats, not from the replaced > Helvetica? > > > No effect meaning that the substitution of "Helvitica" for > "HelviticaFoo" produces no side effects such as "Bogus" messages from > the Goo allocator unlike the substitution of "ZapfDingbatsITC" for > "ZapfDingbats". Should have been more clear about that :). I also > tried a similar test with Courier and got no error messages. OK, so it really is just a ZapfDingbats issue, and not an issue with the substitution code. > > > - I followed the function calls out of GlobalParamsMac.cc and into > > SplashOutputDev.cc. They don't occur in > > `SplashOutputDev::doUpdateFont` which is the function that calls > > `getDisplayFont` from GlobalParamsMac.cc. > > > > Not sure what else to do at this point. > > Hm, I wonder... The "Bogus..." messages always occur after all "Lookup > font..." messages right? This might suggest that they occur not in the > initialization phase but in the actual drawing phase (possibly in > SplashOutputDev::drawChar). > > > Good guess about `SplashOutputDev::drawChar`. Getting Poppler to > build in a GDB-friendly way took some hair pulling---the Autotools > build uses libtool and libtool "helpfully" nukes object files after it > gets done linking libraries. Previously, I got into a fight with > libtool when compiling Poppler for the the Leopard builds as it was > also "helpfully" stripping some essential compiler flags. > > I am now officially not a fan of libtool, it seriously needs a > `--dont-try-to-be-clever` flag. > > Fortunately the Poppler CMake build doesn't try to pull such > shenanigans. It faithfully passes compiler flags and leaves object > files alone. I expanded `poppler-mac-font-handling.patch` to add the > Mac font handling option to the Poppler CMake build as well as the > Autotools build: > > https://github.com/Sharpie/TeXworks/commit/251eb23 > > As I recall, lack of CMake support may have been an issue that kept > Jonathan's patch out of the official Poppler tree: > > http://lists.freedesktop.org/archives/poppler/2009-July/004972.html > > > Anyway, after getting TeXworks and Poppler to run through GDB, a > backtrace from the error message indicates that the problem occurs in > `SplashFTFont::makeGlyph` at `SplashFTFont.cc:244` which is a couple > steps down the call chain from `SplashOutputDev::drawChar`. I'll try > to look over this later to see if I can figure anything out, but here > is the full backtrace: > > Formatted: > https://gist.github.com/1008336 > > Raw: > > https://gist.github.com/raw/1008336/1c01061723261e5d3b6d583ff059a82ac0f00482/texworks_gdb_log.mdown > > > Let me know if anything jumps out! Awesome work! In fact, I think the solution jumped out. From looking at the source code, it seems that bitmap->h (which is the number of rows to allocate) is 0, hence the warnings. My guess is it is caused by a zero-dimension "glyph" for the space character. Anyway, it should be fixed easily (see attached patch). So, hopefully this settles that once and for all. Just for the record (and for submitting the patches upstream): did this happen with an unpatched poppler as well? I.e., are those zero-height glyphs picked up by fontconfig as well, or do they require/use other font files that don't show this issue? Thanks again for the immense amount of work you've put into this! Cheers, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: poppler-bogus-memory-allocation-fix.diff Type: text/x-patch Size: 464 bytes Desc: not available URL: From st.loeffler at gmail.com Sun Jun 5 09:30:59 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 05 Jun 2011 09:30:59 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <588384FA-9826-4B8F-9AE7-5AB260AC7D41@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <588384FA-9826-4B8F-9AE7-5AB260AC7D41@gmail.com> Message-ID: <4DEB30B3.3090603@gmail.com> On 2011-06-05 00:38, Jonathan Kew wrote: > So at the lowest level, it's complaining about trying to allocate some kind of object of size zero; the goo allocator considers that invalid. > > Looks like this is happening on the space character, probably (c=32 in your call stack). > > I wonder if there's something about the space glyph in this version of ZapfDingbats that breaks an assumption in poppler. Space would be unusual in that it has no contours; but that would be true in most fonts, of course, so I don't know why this particular one causes trouble when other fonts apparently work ok. I don't think it's about contours. Instead, from looking at the code, it happens when poppler is trying to copy the bitmap (rasterized) glyph, which in our special case turns out to have height 0. Apparently, most other fonts have spaces with a non-zero height ;). > (Of course, TeX doesn't usually generate space glyphs at all, but I'd expect them to be present in PDFs from other sources that poppler handles without problems.) All of this font handling is actually not so relevant for standard TeX docs, as there fonts are embedded AFAIK. The testcase that failed actually tests compliance with the PDF standard for non-embedded base-14 fonts (which is the only case system fonts are needed). Still, I think it's important to investigate and resolve these issues before they get out of hand and cause real problems in the future. Cheers, -Stefan From chuck at sharpsteen.net Sun Jun 5 21:56:45 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sun, 5 Jun 2011 12:56:45 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DEB2ECA.6090008@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> Message-ID: On Sun, Jun 5, 2011 at 12:22 AM, Stefan L?ffler wrote: > Hi, > > finally, the pieces of the puzzle are starting to fit together :). > Indeed. It is amazing what a good backtrace can do :) Anyway, after getting TeXworks and Poppler to run through GDB, a backtrace > from the error message indicates that the problem occurs in > `SplashFTFont::makeGlyph` at `SplashFTFont.cc:244` which is a couple steps > down the call chain from `SplashOutputDev::drawChar`. I'll try to look over > this later to see if I can figure anything out, but here is the full > backtrace: > > Formatted: > https://gist.github.com/1008336 > > Raw: > > https://gist.github.com/raw/1008336/1c01061723261e5d3b6d583ff059a82ac0f00482/texworks_gdb_log.mdown > > > Let me know if anything jumps out! > > > Awesome work! In fact, I think the solution jumped out. From looking at the > source code, it seems that bitmap->h (which is the number of rows to > allocate) is 0, hence the warnings. My guess is it is caused by a > zero-dimension "glyph" for the space character. Anyway, it should be fixed > easily (see attached patch). So, hopefully this settles that once and for > all. > The patch you attached handles things nicely! No more errors from gmallocn. > Just for the record (and for submitting the patches upstream): did this > happen with an unpatched poppler as well? I.e., are those zero-height glyphs > picked up by fontconfig as well, or do they require/use other font files > that don't show this issue? > I never noticed it before, but this error *do* happen with the Fontconfig build as well. Makes sense as Fontconfig is using the same Font file. Your patch also fixes the Fontconfig build. I guess the last remaining issue that plagues (sort of) the Mac build of Poppler are the .notdef glyphs that show up in the Symbol font: One on Snow Leopard: http://i.imgur.com/m0BCk.png Two on Leopard: http://i.imgur.com/LEBbh.png I don't know if it is really worth hunting these down and eliminating them as TeXworks is not a general-purpose PDF viewer. It might help with getting patches accepted upstream, but these issues are present in the Fontconfig build as well so we're not really upsetting the status quo by leaving them alone. -Charlie > Thanks again for the immense amount of work you've put into this! > You're welcome! Thanks for all of the great typesetting I have been able to do using TeXworks! > Cheers, > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From t34www at googlemail.com Tue Jun 7 01:28:58 2011 From: t34www at googlemail.com (T T) Date: Tue, 7 Jun 2011 00:28:58 +0100 Subject: [texworks] where does python27.dll come from? Message-ID: Hi, Current stable release (0.4.1) fails on systems without MSVC Redistributable installed: http://groups.google.com/group/comp.text.tex/msg/36564e311f8dccae This is due to python27.dll being build with MS toolchain rather than mingw like the rest of TW. Is this intentional? For TeX Live it would be much preferable to stick to mingw for the whole thing. Cheers, Tomek From st.loeffler at gmail.com Tue Jun 7 16:18:50 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 07 Jun 2011 16:18:50 +0200 Subject: [texworks] where does python27.dll come from? In-Reply-To: References: Message-ID: <4DEE334A.3050905@gmail.com> Hi, On 2011-06-07 01:28, T T wrote: > Current stable release (0.4.1) fails on systems without MSVC > Redistributable installed: > > http://groups.google.com/group/comp.text.tex/msg/36564e311f8dccae > > This is due to python27.dll being build with MS toolchain rather than > mingw like the rest of TW. Is this intentional? For TeX Live it > would be much preferable to stick to mingw for the whole thing. No, it's not intentional, it was the least bumpy road at the time ;). The file (as well as those in the Lib/ folder) come from the official Python installer for Windows (http://www.python.org/ftp/python/2.7.1/python-2.7.1.msi). I did look into building it myself (I use http://mingw-cross-env.nongnu.org/ to cross-compile Windows binaries on Linux) briefly, but from what I found on the internet it doesn't seem to be easy (needs messing with the sources, makefiles, etc.). I just stumbled across http://code.google.com/p/mingw-and-ndk/, though, which apparently includes such a patch, so maybe I'll give it another try. Anyway, if someone else has useful information about this, it would be very welcome. In the worst case, you could just disable Python scripting, I guess. AFAIK, it's not used heavily, almost all scripts I've seen so far use the built-in QtScript. Cheers, Stefan From st.loeffler at gmail.com Tue Jun 7 16:27:04 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 07 Jun 2011 16:27:04 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> Message-ID: <4DEE3538.9070406@gmail.com> Hi, On 2011-06-05 21:56, Charlie Sharpsteen wrote: > On Sun, Jun 5, 2011 at 12:22 AM, Stefan L?ffler > wrote: > > Just for the record (and for submitting the patches upstream): did > this happen with an unpatched poppler as well? I.e., are those > zero-height glyphs picked up by fontconfig as well, or do they > require/use other font files that don't show this issue? > > > I never noticed it before, but this error *do* happen with the > Fontconfig build as well. Makes sense as Fontconfig is using the same > Font file. Your patch also fixes the Fontconfig build. > > I guess the last remaining issue that plagues (sort of) the Mac build > of Poppler are the .notdef glyphs that show up in the Symbol font: > > One on Snow Leopard: > > http://i.imgur.com/m0BCk.png > > Two on Leopard: > > http://i.imgur.com/LEBbh.png > > I don't know if it is really worth hunting these down and eliminating > them as TeXworks is not a general-purpose PDF viewer. It might help > with getting patches accepted upstream, but these issues are present > in the Fontconfig build as well so we're not really upsetting the > status quo by leaving them alone. I'm inclined to close this matter. If Apple changes font encodings between releases (it's not even the same glyphs that are .notdef'ed!) we can't help it. Besides, as I pointed out before, TeX documents normally have their fonts embedded, AFAIK. Fixing this would probably need some digging through the encoding tables and adding OS version switches there (though I'm not even sure if it's (easily) possible to have a conditional compilation depending on the OS version...). Speaking of upstream: how do we go about submitting the patches? If you want, I guess it's best if you would submit the patches, as you have all the relevant data (what was broken where, ...) and can answer any questions that may arise. If not, I could submit them as well, of course, but it would be a lot like "here you are, do with it what you want" ;). Cheers, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Tue Jun 7 16:29:36 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 07 Jun 2011 16:29:36 +0200 Subject: [texworks] ctrl + T not working In-Reply-To: References: Message-ID: <4DEE35D0.6010906@gmail.com> Hi, On 2011-06-04 03:05, Suresh Kumar wrote: > I am using texworks Version 0.4.1 r.829 on ubuntu 10.04. I find that > Ctrl + T (pressing T while pressing cntrl) is not working. However > the menu typeset -> typeset works as well as the arrow symbol > available just below the menu bar. > Any suggestions? Do you have anything else that might be associated with Ctrl+T? Customized shortcuts, maybe, or some component of the OS (compiz is notorious for all sorts of key sequences, for example)? Also, when did this occur? Did you just started using TeXworks, or did things work as expected before? In the latter case: when did they stop working? Regards, Stefan From chuck at sharpsteen.net Tue Jun 7 19:59:55 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 7 Jun 2011 10:59:55 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DEE3538.9070406@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> Message-ID: On Tue, Jun 7, 2011 at 7:27 AM, Stefan L?ffler wrote: > > I guess the last remaining issue that plagues (sort of) the Mac build of Poppler are the .notdef glyphs that show up in the Symbol font: > One on Snow Leopard: > ? ??http://i.imgur.com/m0BCk.png > Two on Leopard: > ? ??http://i.imgur.com/LEBbh.png > I don't know if it is really worth hunting these down and eliminating them as TeXworks is not a general-purpose PDF viewer. ?It might help with getting patches accepted upstream, but these issues are present in the Fontconfig build as well so we're not really upsetting the status quo by leaving them alone. > > I'm inclined to close this matter. If Apple changes font encodings between releases (it's not even the same glyphs that are .notdef'ed!) we can't help it. Besides, as I pointed out before, TeX documents normally have their fonts embedded, AFAIK. Fixing this would probably need some digging through the encoding tables and adding OS version switches there (though I'm not even sure if it's (easily) possible to have a conditional compilation depending on the OS version...). I'm not too fired up about fixing this either. > > Speaking of upstream: how do we go about submitting the patches? If you want, I guess it's best if you would submit the patches, as you have all the relevant data (what was broken where, ...) and can answer any questions that may arise. If not, I could submit them as well, of course, but it would be a lot like "here you are, do with it what you want" ;). > > Cheers, > Stefan I think we should do the following: 1. Merge the updates to `poppler-mac-font-handling.patch` and the new `poppler-bogus-memory-allocation-fix.patch` back into the TeXworks SVN repository. I have exported these patches and attached them to the end of this email. 2. I'll roll up a new 0.5.0 release that uses Quartz instead of Fontconfig. That way when we submit the patches back to Poppler, we can say "X people tried it on Snow Leopard, Y people on Leopard, and it didn't blow their computers up". 3. Re-submit the patches for inclusion in the Poppler source if there are no issues with the 0.5.0 build. Perhaps we could also consider downgrading the changes to the buildsystem so that Fontconfig is stil the default, but "mac" is now an option. ?This would be a smaller change to the Poppler status quo which might help the patches get accepted. Jonathan, any thoughts on trying another submission to Poppler? -Charlie -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Add-ZapfDingbats-PostScript-name-as-a-special-case.patch Type: application/octet-stream Size: 2307 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-Add-Mac-font-handling-to-Poppler-CMake-buildsystem.patch Type: application/octet-stream Size: 3477 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0003-Add-patch-to-fix-memory-allocation-for-Splash-Glyphs.patch Type: application/octet-stream Size: 1298 bytes Desc: not available URL: From st.loeffler at gmail.com Tue Jun 7 21:04:47 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 07 Jun 2011 21:04:47 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> Message-ID: <4DEE764F.6030600@gmail.com> On 2011-06-07 19:59, Charlie Sharpsteen wrote: > On Tue, Jun 7, 2011 at 7:27 AM, Stefan L?ffler wrote: >> Speaking of upstream: how do we go about submitting the patches? If you want, I guess it's best if you would submit the patches, as you have all the relevant data (what was broken where, ...) and can answer any questions that may arise. If not, I could submit them as well, of course, but it would be a lot like "here you are, do with it what you want" ;). > I think we should do the following: > > 1. Merge the updates to `poppler-mac-font-handling.patch` and the new > `poppler-bogus-memory-allocation-fix.patch` back into the TeXworks SVN > repository. I have exported these patches and attached them to the end > of this email. Thanks. I committed them as r835. > 2. I'll roll up a new 0.5.0 release that uses Quartz instead of > Fontconfig. That way when we submit the patches back to Poppler, we > can say "X people tried it on Snow Leopard, Y people on Leopard, and > it didn't blow their computers up". Sounds fine (though I hope "blowing up computers" is never a side effect, no matter how badly things go - not because of the poppler build, anyway ;)). > 3. Re-submit the patches for inclusion in the Poppler source if there > are no issues with the 0.5.0 build. Perhaps we could also consider > downgrading the changes to the buildsystem so that Fontconfig is stil > the default, but "mac" is now an option. This would be a smaller > change to the Poppler status quo which might help the patches get > accepted. Yeah, why not. Cheers, Stefan From jfkthame at googlemail.com Tue Jun 7 21:11:14 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Tue, 7 Jun 2011 20:11:14 +0100 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.907040 6@gmail.com> Message-ID: <2549F3EF-F107-4D2A-9F24-B778E38EC672@gmail.com> On 7 Jun 2011, at 18:59, Charlie Sharpsteen wrote: > > I think we should do the following: > > 1. Merge the updates to `poppler-mac-font-handling.patch` and the new > `poppler-bogus-memory-allocation-fix.patch` back into the TeXworks SVN > repository. I have exported these patches and attached them to the end > of this email. > > 2. I'll roll up a new 0.5.0 release that uses Quartz instead of > Fontconfig. That way when we submit the patches back to Poppler, we > can say "X people tried it on Snow Leopard, Y people on Leopard, and > it didn't blow their computers up". > > 3. Re-submit the patches for inclusion in the Poppler source if there > are no issues with the 0.5.0 build. Perhaps we could also consider > downgrading the changes to the buildsystem so that Fontconfig is stil > the default, but "mac" is now an option. This would be a smaller > change to the Poppler status quo which might help the patches get > accepted. > > Jonathan, any thoughts on trying another submission to Poppler? I think it'd be good to try and get this into the upstream code, so that we (you) don't have to maintain separate patches and deal with merging when future poppler releases come out. Go for it! JK From paul.a.norman at gmail.com Wed Jun 8 06:05:45 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 8 Jun 2011 16:05:45 +1200 Subject: [texworks] syntax-patterns.txt In-Reply-To: References: <4DE8BCD7.1070500@gmail.com> Message-ID: Hi, One small thing that I have find useful is to make my footnotes grey out in the editor, makes them interfere less with the text when skim reading for editing, and also helps me conversely spot where they are. Under my latex section in syntax-patterns.txt [Latex] ... gray Y \\footnote\{.+\} Also as I sometimes move the \end{document} up through the document when troubleshooting any starnge errors (normally caused through pasting in something from a 'strange' character set) ... # LaTeX \begin or \end {document} red N \\(?:begin|end)\{document\} Any one else done anything like these or improved upon anything else? Paul On 4 June 2011 11:27, Paul A Norman wrote: > Thanks very much Stefan, > > Paul > > On 3 June 2011 22:52, Stefan L?ffler wrote: >> Hi, >> >> On 2011-06-03 04:48, Paul A Norman wrote: >>> Just wanted to check a couple of things please - got ?into a mind maze >>> with this stuff. >> >> Yeah, that can happen terribly easily with regexps ;). >> >>> With syntax-patterns.txt which dialect of regular expressions is being >>> used please? >> >> The Qt dialect (http://doc.trolltech.com/4.7/qregexp.html#details). In >> fact, the string given in syntax-patterns.txt is simply wrapped into a >> QRegExp object (see src/TeXHighlighter.cpp at 226). >> >>> In that dialect does .* mean ?anything many times? >> >> Yes, anything zero or more times (one or more would be .+). The >> quantifiers are also greedy (they match as much as they possibly can). >> >>> Can () be used to choose which part of an expression is colourised? >>> For e.g. >>> >>> skyblue N .*\{(http[s]://.*)} >>> >>> ? ? -- Would colour only the actual address? >> >> No, not at the moment, unfortunately. It should be possible to use >> look-ahead assertions to match a string only if it followed by a certain >> string (without including the second in the match), but look-behind >> assertions are not supported, unfortunately. >> >> In principle, colorizing the captured text could probably be added to >> the code, but it would have drawbacks for people who are lazy and just >> write, e.g., "(W|w)arning" instead of "(?:W|w)arning". >> >> BTW: You probably want something like "\{(https?://[^}]*)\}". >> >> HTH >> Stefan >> > From L.Santiago at warwick.ac.uk Wed Jun 8 19:03:48 2011 From: L.Santiago at warwick.ac.uk (Santiago, Lualhati) Date: Wed, 8 Jun 2011 18:03:48 +0100 Subject: [texworks] Message from TeXworks user Message-ID: Hello, I have just installed the latest TeXworks version: (May 2011) TeXworks 0.4.1 released and it has stopped working (it no longer converts my work into pdf or dvi). It used to work perfectly before. It says: latexmk.exe: The Perl interpreter could not be found. I never had this problem with the previous version. It never required me to install the Perl interpreter. Please, could you help me to recover my TeXworks? I do not know how to fix this problem. I have tried to return to the previous version I had, but it is no longer available on the web. I have come very used to TeXworks and preferred it over other editors. Thank you for your help and time, I would really appreciate it. Best regards, Santiago ----- configuration info ----- TeXworks version : 0.3r670 (MiKTeX 2.9) Install location : C:/Program Files (x86)/MiKTeX 2.9/miktex/bin/miktex-texworks.exe Library path : C:\Users\Lulu\AppData\Local\MiKTeX\2.9\TeXworks\ pdfTeX location : C:/Program Files (x86)/MiKTeX 2.9/miktex/bin/pdftex.exe Operating system : Windows Microsoft Windows 7 Business Edition, 64-bit (build 7600) Qt4 version : 4.7.0 (build) / 4.7.0 (runtime) ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Wed Jun 8 20:07:35 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Wed, 8 Jun 2011 11:07:35 -0700 Subject: [texworks] Message from TeXworks user In-Reply-To: References: Message-ID: On Wed, Jun 8, 2011 at 10:03 AM, Santiago, Lualhati wrote: > Hello, > > I have just installed the latest TeXworks version: (May 2011) TeXworks 0.4.1 > released and it has stopped working (it no longer converts my work into pdf > or dvi). It used to work perfectly before. > > It says: latexmk.exe: The Perl interpreter could not be found. This problem is not with TeXworks directly, but `latexmk` which is the program being called to compile your TeX document into PDF. `latexmk` is a Perl script that takes care of compiling and recompiling LaTeX document the proper number of times such that all bibliography information is present and all table/figure/equation references are resolves---and much more. Running a Perl script will require that a Perl interpreter is installed. > I never had this problem with the previous version. It never required me to > install the Perl interpreter. Have you used `latexmk` to compile documents before? > Please, could you help me to recover my TeXworks? I do not know how to fix > this problem. I have tried to return to the previous version I had, but it > is no longer available on the web. > > I have come very used to TeXworks and preferred it over other editors. > > Thank you for your help and time, I would really appreciate it. > > Best regards, > > Santiago From chuck at sharpsteen.net Wed Jun 8 22:07:36 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Wed, 8 Jun 2011 13:07:36 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DEE3538.9070406@gmail.com> References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> Message-ID: On Tue, Jun 7, 2011 at 7:27 AM, Stefan L?ffler wrote: > Hi, > > On 2011-06-05 21:56, Charlie Sharpsteen wrote: > > On Sun, Jun 5, 2011 at 12:22 AM, Stefan L?ffler > wrote: >> >> Just for the record (and for submitting the patches upstream): did this >> happen with an unpatched poppler as well? I.e., are those zero-height glyphs >> picked up by fontconfig as well, or do they require/use other font files >> that don't show this issue? > > I never noticed it before, but this error *do* happen with the Fontconfig > build as well. Makes sense as Fontconfig is using the same Font file. ?Your > patch also fixes the Fontconfig build. > I guess the last remaining issue that plagues (sort of) the Mac build of > Poppler are the .notdef glyphs that show up in the Symbol font: > One on Snow Leopard: > ? ??http://i.imgur.com/m0BCk.png > Two on Leopard: > ? ??http://i.imgur.com/LEBbh.png > I don't know if it is really worth hunting these down and eliminating them > as TeXworks is not a general-purpose PDF viewer. ?It might help with getting > patches accepted upstream, but these issues are present in the Fontconfig > build as well so we're not really upsetting the status quo by leaving them > alone. > > I'm inclined to close this matter. If Apple changes font encodings between > releases (it's not even the same glyphs that are .notdef'ed!) we can't help > it. Besides, as I pointed out before, TeX documents normally have their > fonts embedded, AFAIK. Fixing this would probably need some digging through > the encoding tables and adding OS version switches there (though I'm not > even sure if it's (easily) possible to have a conditional compilation > depending on the OS version...). It appears there was more to the Symbol font situation on Leopard. When testing a new binary, I noticed that Helvetica was being substituted for Symbol, but only on OS X 10.5.x. I re-applied the debugging patch and it turned out that for the Symbol font, the check for a TrueType font: version != TAG('t','r','u','e') Was evaluating to false for some reason. It shouldn't have as the value of `version` was 1953658213 which does decode to "true" when split into char values. The `TAG` macro expands to four separate bitwise operations--so possibly the logical comparison was not being made against the total result of the `TAG` computation. I added a set of perentheses around the entire `TAG` definition and TeXworks stopped substituting Helvitica for Symbol. The result still has one .notdef character, but at least it is in the same place as the Snow Leopard version. Attached is a patch that I think fixes the preprocessor definitions in GlobalParamsMac.cc. -Charlie -------------- next part -------------- A non-text attachment was scrubbed... Name: Fix-preprocessor-definitions-in-GlobalParamsMac.cc.patch Type: application/octet-stream Size: 2917 bytes Desc: not available URL: From jfkthame at googlemail.com Wed Jun 8 22:24:03 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Wed, 8 Jun 2011 21:24:03 +0100 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DCFC2B0.4020905@gmail.com> <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.907040 6@gmail.com> Message-ID: <8944D1E5-791D-460C-ABEC-43A553B8A5EE@gmail.com> On 8 Jun 2011, at 21:07, Charlie Sharpsteen wrote: > Attached is a patch that I think fixes the preprocessor definitions in > GlobalParamsMac.cc. Oops - yes, those macros were not well coded, and could behave incorrectly depending how they're actually used. Your patch looks good, thanks. JK From st.loeffler at gmail.com Thu Jun 9 07:23:45 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 09 Jun 2011 07:23:45 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> Message-ID: <4DF058E1.7080905@gmail.com> Hi, On 2011-06-08 22:07, Charlie Sharpsteen wrote: > It appears there was more to the Symbol font situation on Leopard. > When testing a new binary, I noticed that Helvetica was being > substituted for Symbol, but only on OS X 10.5.x. [...] I added a set > of perentheses around the entire `TAG` definition and TeXworks stopped > substituting Helvitica for Symbol. The result still has one .notdef > character, but at least it is in the same place as the Snow Leopard > version. OK, the mu - well, it's a fairly common character (my keyboard even has a special combination AltG+M for it), so Apple may have decided to move it to some other place to be consistent with other fonts, for example. Anyway, it's good that it's consistent now. > Attached is a patch that I think fixes the preprocessor definitions in > GlobalParamsMac.cc. Thanks, committed as r836. -Stefan From st.loeffler at gmail.com Thu Jun 9 08:14:12 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 09 Jun 2011 08:14:12 +0200 Subject: [texworks] where does python27.dll come from? In-Reply-To: References: Message-ID: <4DF064B4.2070305@gmail.com> Hi again, On 2011-06-07 01:28, T T wrote: > Current stable release (0.4.1) fails on systems without MSVC > Redistributable installed: > > http://groups.google.com/group/comp.text.tex/msg/36564e311f8dccae > > This is due to python27.dll being build with MS toolchain rather than > mingw like the rest of TW. Is this intentional? For TeX Live it > would be much preferable to stick to mingw for the whole thing. It seems I finally manager to cross-compile Python statically - this has the additional benefit of getting rid of the Lib/ folder. I'm no Python build-expert, though, so I couldn't test if everything works correctly. FWIW, Tw starts (in Wine), and simple makeBold and DateTime scripts work. For your (and everybody else's) testing purposes, I uploaded a build to http://web.student.tuwien.ac.at/~e0325258/projects/c/texworks/releases/TeXworks-w32-0.5-r836.zip Cheers, Stefan From chuck at sharpsteen.net Thu Jun 9 20:27:36 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 9 Jun 2011 11:27:36 -0700 Subject: [texworks] Another experimental Mac build Message-ID: Hey everyone, I just posted two new Mac binaries: For Leopard: https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-836-d471e94-Leopard.dmg For Snow Leopard: https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-836-d471e94-SLeopard.dmg ** NOTE: These links are semi-permanent. Old builds may be deleted in order to free disk space for new builds. ** This build is entirely skippable as there are no new features or user-visible changes. The purpose of this build is to field-test changes to Poppler that retrieve missing font information directly from OS X rather than the X11-based Fontconfig library. TeX normally embeds all information into the PDF files it generates, so this change should have no impact on normal TeXworks usage. If anyone downloads this release and runs into problems with font rendering, please let me know---I am planning to submit patches to the Poppler project in a few weeks if TeXworks is still running smoothly. Other minor changes/improvements compared to the 0.4.1 build: - The TeXworks manual is now packaged into the Application and available via the Help menu. - The Drag N' Drop installer has been sexed up quite a bit. The current background image is modified from the Firefox Drag N' Drop installer---if anyone designs a background specific to TeXworks, send me a PNG file and I'll consider using it! -Charlie From brainy-kid at gmx.net Thu Jun 9 17:15:28 2011 From: brainy-kid at gmx.net (Katrin Schaar) Date: Thu, 09 Jun 2011 17:15:28 +0200 Subject: [texworks] message from TeXworks user(MiKTeX) Message-ID: <4DF0E390.9080109@gmx.net> Hi everybody, I?m trying to produce a pdf-file using MikTex. Everytime I want to compile the file, I receive following error: " You are attempting to make a LaTeX format from a source file that is older than 5 years." I receive the same message, no matter if I use MikTeX 2.8 oder 2.9 (which I just installed today, respectively). Can you help me and send some advice? Greetz, Katrin From chuck at sharpsteen.net Fri Jun 10 05:38:29 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 9 Jun 2011 20:38:29 -0700 Subject: [texworks] message from TeXworks user(MiKTeX) In-Reply-To: <4DF0E390.9080109@gmx.net> References: <4DF0E390.9080109@gmx.net> Message-ID: On Thu, Jun 9, 2011 at 8:15 AM, Katrin Schaar wrote: > Hi everybody, > > I?m trying to produce a pdf-file using MikTex. > Everytime I want to compile the file, I receive following error: > > " You are attempting to make a LaTeX format from a source file that is older > than 5 years." > > I receive the same message, no matter if I use MikTeX 2.8 oder 2.9 (which I > just installed today, respectively). > > Can you help me and send some advice? > > Greetz, > Katrin Never seen this one before. You may try asking on the TeX Stackexchange---lots of LaTeX experts hang out there: http://tex.stackexchange.com Good luck! -Charlie From nomosnomos at gmail.com Fri Jun 10 06:57:13 2011 From: nomosnomos at gmail.com (Dohyun Kim) Date: Fri, 10 Jun 2011 13:57:13 +0900 Subject: [texworks] Another experimental Mac build In-Reply-To: References: Message-ID: 2011/6/10 Charlie Sharpsteen : > Hey everyone, > > I just posted two new Mac binaries: > > ? ?For Leopard: > ? ?https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-836-d471e94-Leopard.dmg > > ? ?For Snow Leopard: > ? ?https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-836-d471e94-SLeopard.dmg > > ** NOTE: These links are semi-permanent. Old builds may be deleted in > order to free disk space for new builds. ** > > > This build is entirely skippable as there are no new features or > user-visible changes. ?The purpose of this build is to field-test > changes to Poppler that retrieve missing font information directly > from OS X rather than the X11-based Fontconfig library. TeX normally > embeds all information into the PDF files it generates, so this change > should have no impact on normal TeXworks usage. ?If anyone downloads > this release and runs into problems with font rendering, please let me > know---I am planning to submit patches to the Poppler project in a few > weeks if TeXworks is still running smoothly. > I can't see any difference from the previous build. When base14-fonts.pdf being opened, it turns out that the following fonts are still working: Times New Roman.ttf for Times HelveticaLight.ttf for Helvetica (for Helverica-Bold as well) /usr/X11/lib/X11/fonts/Type1/cour.pfa for Courier Again, mu character of Symbol face is still an empty box. It seems that fontconfig library, instead of OSX native engine, is still being used. I have installed Snow Leopard build. Best, -- Dohyun Kim College of Law, Dongguk University Seoul, Republic of Korea From esperanto at swing.be Fri Jun 10 09:39:47 2011 From: esperanto at swing.be (Alain Delmotte) Date: Fri, 10 Jun 2011 09:39:47 +0200 Subject: [texworks] where does python27.dll come from? In-Reply-To: <4DF064B4.2070305@gmail.com> References: <4DF064B4.2070305@gmail.com> Message-ID: <4DF1CA43.8030502@swing.be> Hi Stefan, I downloaded and unzipped, but TeXworks doesn't start, even if I want to start it as administrator. Regards, Alain Le 9/06/2011 08:14, Stefan L?ffler a ?crit : > Hi again, > > On 2011-06-07 01:28, T T wrote: >> Current stable release (0.4.1) fails on systems without MSVC >> Redistributable installed: >> >> http://groups.google.com/group/comp.text.tex/msg/36564e311f8dccae >> >> This is due to python27.dll being build with MS toolchain rather than >> mingw like the rest of TW. Is this intentional? For TeX Live it >> would be much preferable to stick to mingw for the whole thing. > > It seems I finally manager to cross-compile Python statically - this has > the additional benefit of getting rid of the Lib/ folder. I'm no Python > build-expert, though, so I couldn't test if everything works correctly. > FWIW, Tw starts (in Wine), and simple makeBold and DateTime scripts work. > > For your (and everybody else's) testing purposes, I uploaded a build to > http://web.student.tuwien.ac.at/~e0325258/projects/c/texworks/releases/TeXworks-w32-0.5-r836.zip > > Cheers, > Stefan > From kakuto at fuk.kindai.ac.jp Fri Jun 10 16:14:27 2011 From: kakuto at fuk.kindai.ac.jp (Akira Kakuto) Date: Fri, 10 Jun 2011 23:14:27 +0900 Subject: [texworks] where does python27.dll come from? In-Reply-To: <4DF1CA43.8030502@swing.be> References: <4DF1CA43.8030502@swing.be> Message-ID: <130771526767249500006d71@sniffer> Dear Alain Delmotte, > I downloaded and unzipped, but TeXworks doesn't start, even > if I want to start it as administrator. python27.dll is not necessary, but the Lib directory and its contents seem to be necessary. If I recover Lib, then TeXworks-w32-0.5-r836.zip works fine on Windows XP without python27.dll. Thanks, Akira From P.Taylor at Rhul.Ac.Uk Fri Jun 10 16:17:10 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Fri, 10 Jun 2011 15:17:10 +0100 Subject: [texworks] TeXworks 0.2.3 (R.466) -- alternative previewer Message-ID: <4DF22766.7040106@Rhul.Ac.Uk> Is there any way to configure TeXworks to use Adobe Acrobat or Adobe Reader as its integrated previewer ? There are a number of issues w.r.t. the integrated previewer which make it less than ideal for me, and I would find it far more convenient if the just-compiled document could automatically open based on filetype association or through a settable preference rather than use the current integrated previewer. Philip Taylor From chuck at sharpsteen.net Fri Jun 10 17:17:44 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Fri, 10 Jun 2011 08:17:44 -0700 Subject: [texworks] Another experimental Mac build In-Reply-To: References: Message-ID: On Thu, Jun 9, 2011 at 9:57 PM, Dohyun Kim wrote: > 2011/6/10 Charlie Sharpsteen : >> Hey everyone, >> >> I just posted two new Mac binaries: >> >> ? ?For Leopard: >> ? ?https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-836-d471e94-Leopard.dmg >> >> ? ?For Snow Leopard: >> ? ?https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.5.0-836-d471e94-SLeopard.dmg >> >> ** NOTE: These links are semi-permanent. Old builds may be deleted in >> order to free disk space for new builds. ** >> >> >> This build is entirely skippable as there are no new features or >> user-visible changes. ?The purpose of this build is to field-test >> changes to Poppler that retrieve missing font information directly >> from OS X rather than the X11-based Fontconfig library. TeX normally >> embeds all information into the PDF files it generates, so this change >> should have no impact on normal TeXworks usage. ?If anyone downloads >> this release and runs into problems with font rendering, please let me >> know---I am planning to submit patches to the Poppler project in a few >> weeks if TeXworks is still running smoothly. >> > > I can't see any difference from the previous build. > When base14-fonts.pdf being opened, it turns out that > the following fonts are still working: > > Times New Roman.ttf ?for Times > HelveticaLight.ttf ?for Helvetica (for Helverica-Bold as well) > /usr/X11/lib/X11/fonts/Type1/cour.pfa ?for Courier > > Again, mu character of Symbol face is still an empty box. > It seems that fontconfig library, instead of OSX native engine, > is still being used. ?I have installed Snow Leopard build. Ooops, you are right---it looks like the Snow Leopard build was still including Fontconfig. I just replaced the binary with a new build that doesn't include it. Thanks for testing! -Charlie > Best, > -- > Dohyun Kim From esperanto at swing.be Fri Jun 10 20:57:00 2011 From: esperanto at swing.be (Alain Delmotte) Date: Fri, 10 Jun 2011 20:57:00 +0200 Subject: [texworks] where does python27.dll come from? In-Reply-To: <130771526767249500006d71@sniffer> References: <4DF1CA43.8030502@swing.be> <130771526767249500006d71@sniffer> Message-ID: <4DF268FC.5020203@swing.be> Hi, yes keeping the Lib directory enables TeXworks. The few macros in Python I have work (but they are not very sophisticated). Are there other tests to perform? Regards, Alain Le 10/06/2011 16:14, Akira Kakuto a ?crit : > Dear Alain Delmotte, > >> I downloaded and unzipped, but TeXworks doesn't start, even >> if I want to start it as administrator. > > python27.dll is not necessary, but the Lib directory and > its contents seem to be necessary. If I recover Lib, then > TeXworks-w32-0.5-r836.zip works fine on Windows XP > without python27.dll. > > Thanks, > Akira > > > From paul.a.norman at gmail.com Sat Jun 11 02:49:36 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sat, 11 Jun 2011 12:49:36 +1200 Subject: [texworks] TeXworks 0.2.3 (R.466) -- alternative previewer In-Reply-To: <4DF22766.7040106@Rhul.Ac.Uk> References: <4DF22766.7040106@Rhul.Ac.Uk> Message-ID: Dear Philip, There has been a bit of discussion on this before. Bruno and I looked into it. Does depend what other utilities are available already on Linux distributions and on Mac Os. I have had a bit of a hack that as far as I know only works on WIndows, are you on that? If so this might help you ... http://code.google.com/p/texworks/issues/detail?id=261#c65 Paul On 11 June 2011 02:17, Philip TAYLOR (Webmaster, Ret'd) wrote: > Is there any way to configure TeXworks to use Adobe Acrobat > or Adobe Reader as its integrated previewer ? ?There are a number > of issues w.r.t. the integrated previewer which make it less than > ideal for me, and I would find it far more convenient if the > just-compiled document could automatically open based on > filetype association or through a settable preference rather than > use the current integrated previewer. > > Philip Taylor > From paul.a.norman at gmail.com Sat Jun 11 02:53:35 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sat, 11 Jun 2011 12:53:35 +1200 Subject: [texworks] Open Pdf in Acrobat Reader -- Windows only Message-ID: Open Pdf in Acrobat Reader -- Useful when acrobat reader needs to be used to check something like \pdfmarks Regrettably at present this is Windows only - Bruno and I tried! http://code.google.com/p/texworks/issues/detail?id=261#c65 ** Before Use - See license and disclaimer in Script File (Was: http://code.google.com/p/texworks/issues/detail?id=261#c35) Utilises a hightech in-built human observational facility for determing the poppler preview page number :) (your eyes) NEW: Each call of this script will open a new instance of acrobat reader (a work around for a DDE issue if the document is requested for a new page number) ** Under Windows at least the the acrobat reader pdf appears to still need to be closed prior to TeXworks Typesetting taking place. Text highlighted in the Tw editor would be used as a specified "named destination" (if you have any) see hyperref package, otherwise a page number is requested (optional - the box can be canceled). Feedback -- code for Linuix and Mac Os - ;) appreciated please, Paul http://code.google.com/p/texworks/issues/detail?id=261#c65 http://TWScript.PaulANorman.com From st.loeffler at gmail.com Sat Jun 11 09:26:05 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sat, 11 Jun 2011 09:26:05 +0200 Subject: [texworks] TeXworks 0.2.3 (R.466) -- alternative previewer In-Reply-To: References: <4DF22766.7040106@Rhul.Ac.Uk> Message-ID: <4DF3188D.4060200@gmail.com> Hi, On 2011-06-11 02:49, Paul A Norman wrote: > I have had a bit of a hack that as far as I know only works on > WIndows, are you on that? If so this might help you ... > > http://code.google.com/p/texworks/issues/detail?id=261#c65 Note that for this to work, you need scripting, which isn't available in Tw 0.2.3 (r466) which you quoted in the subject line. Upgrading to the 0.4 series fixes that (if you're in particular need for stability, I recommend waiting for 0.4.2, though, which is to appear soon). Regards, Stefan From t34www at googlemail.com Sun Jun 12 03:54:46 2011 From: t34www at googlemail.com (T T) Date: Sun, 12 Jun 2011 02:54:46 +0100 Subject: [texworks] where does python27.dll come from? In-Reply-To: <4DF064B4.2070305@gmail.com> References: <4DF064B4.2070305@gmail.com> Message-ID: On 9 June 2011 07:14, Stefan L?ffler wrote: > Hi again, > > On 2011-06-07 01:28, T T wrote: >> Current stable release (0.4.1) fails on systems without MSVC >> Redistributable installed: >> >> http://groups.google.com/group/comp.text.tex/msg/36564e311f8dccae >> >> This is due to python27.dll being build with MS toolchain rather than >> mingw like the rest of TW. ?Is this intentional? ?For TeX Live it >> would be much preferable to stick to mingw for the whole thing. > > It seems I finally manager to cross-compile Python statically - this has > the additional benefit of getting rid of the Lib/ folder. I'm no Python > build-expert, though, so I couldn't test if everything works correctly. > FWIW, Tw starts (in Wine), and simple makeBold and DateTime scripts work. > > For your (and everybody else's) testing purposes, I uploaded a build to > http://web.student.tuwien.ac.at/~e0325258/projects/c/texworks/releases/TeXworks-w32-0.5-r836.zip Thanks, Stefan. This is excellent work. Please let me know if/when there will be a stable release of this build. I would like to pull it into TL as soon as it's available, so it can get some testing before TL'11 gets released. Cheers, Tomek From st.loeffler at gmail.com Sun Jun 12 16:06:07 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 12 Jun 2011 16:06:07 +0200 Subject: [texworks] where does python27.dll come from? In-Reply-To: <4DF1CA43.8030502@swing.be> References: <4DF064B4.2070305@gmail.com> <4DF1CA43.8030502@swing.be> Message-ID: <4DF4C7CF.7020208@gmail.com> Hi, On 2011-06-10 09:39, Alain Delmotte wrote: > I downloaded and unzipped, but TeXworks doesn't start, even if I want > to start it as administrator. Thanks for testing and reporting. As pointed out in the thread, the Lib folder is indeed still necessary (it seems it picked up a different Lib folder on my machine - one shouldn't mix different python installs ;)). Anyway, using the one from the older releases is not ideal, as they were taken from the MSVC build. Therefore, they might depend on libraries etc. and might even be incompatible with the built-in mingw library. Anyway, I've uploaded a new version where this problem hopefully is solved: http://web.student.tuwien.ac.at/~e0325258/projects/c/texworks/releases/TeXworks-w32-0.5-r843.zip Regards, Stefan From P.Taylor at Rhul.Ac.Uk Sun Jun 12 15:23:42 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Sun, 12 Jun 2011 14:23:42 +0100 Subject: [texworks] TeXworks 0.2.3 (R.466) -- alternative previewer In-Reply-To: <4DF3188D.4060200@gmail.com> References: <4DF22766.7040106@Rhul.Ac.Uk> <4DF3188D.4060200@gmail.com> Message-ID: <4DF4BDDE.3090501@Rhul.Ac.Uk> My sincere thanks to both Paul Norman & Stefan L?ffler for their replies. It transpired that I was running an out-of date version of TeXworks, so I have now carried out a full update on my TeX Live 2010 installation [1] and this has brought with it a more recent TeXworks, as a result of which I shall shortly be able to try Paul's and Stefan's suggestions. And to clarify, yes indeed I am a very happy Windows (XP) user (not sure I would be anywhere near so happy with more recent versions of Windows !). Philip Taylor -------- [1] It also resulted in a near-disaster, in that TikZ/PGF no longer behaves as it did, and I was in the middle of a project in which TikZ plays a vital role. Fortunately I was able to track the problem down to TikZ's redefinition of \end, and subsequently to work around the problems that causes. From P.Taylor at Rhul.Ac.Uk Sun Jun 12 15:32:51 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Sun, 12 Jun 2011 14:32:51 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? Message-ID: <4DF4C003.7020908@Rhul.Ac.Uk> Dear fellow TeXworkers -- I am a strong believe in the importance of layout, and would never trust a mere editor (not even TeXworks) to perform layout for me. So why is it that when I type \def \foo { and then press at the start of the blank line below the "{" (which is itself indented with one tab), TeXworks insists in entering alertenv}<> and putting the cursor between the angle-brackets ? I have no idea what "alertenv" is, nor do I want it inserted; how may this be avoided, please ? Philip Taylor From esperanto at swing.be Sun Jun 12 21:30:30 2011 From: esperanto at swing.be (Alain Delmotte) Date: Sun, 12 Jun 2011 21:30:30 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF4C003.7020908@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> Message-ID: <4DF513D6.3050209@swing.be> Hi Philip, This is coming from auto-completion. if you keep pressing [Tab] you will have a lot more. alertenv is coming from the tw-beamer.txt file, but if you press [Tab] long you will also have those from tw-latex.txt. All the files are in the C:\Users\\TeXworks\completion folder. I think this is a negative side effect. Should we suppress all the entries of the type: ==== first piece from tw-beamer.txt {altenv}<#INS#>{?}{?}{?}{?}#RET##RET#\end{altenv} {actionenv}<#INS#>#RET##RET#\end{actionenv} {beamercolorbox}{#INS#}#RET##RET#\end{beamercolorbox} {beamercolorbox}[?]{#INS#}#RET##RET#\end{beamercolorbox} ==== from tw-latex.txt {array}#RET##INS##RET#\end{array}? {abstract}#RET##INS##RET#\end{abstract}? {align}#RET##INS##RET#\end{align}? {align*}#RET##INS##RET#\end{align*}? The same happens with \ \beamerbutton{#INS#} \beamergotobutton{#INS#} \beamerreturnbutton{#INS#} \beamerskipbutton{#INS#} We should ask the users which type of completion code they use. And perhaps adapt the completion files. Now for Philip, if you are not using auto-completion, which I regret because it is very, very interesting - see the manual-- you could empty the folder, so no definition would be loaded. Regards, Alain Le 12/06/2011 15:32, Philip TAYLOR (Webmaster, Ret'd) a ?crit : Dear fellow TeXworkers -- I am a strong believe in the importance of layout, and would never trust a mere editor (not even TeXworks) to perform layout for me. So why is it that when I type \def \foo { and then press at the start of the blank line below the "{" (which is itself indented with one tab), TeXworks insists in entering alertenv}<> and putting the cursor between the angle-brackets ? I have no idea what "alertenv" is, nor do I want it inserted; how may this be avoided, please ? Philip Taylor From chuck at sharpsteen.net Sun Jun 12 21:45:26 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sun, 12 Jun 2011 12:45:26 -0700 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF513D6.3050209@swing.be> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> Message-ID: On Sun, Jun 12, 2011 at 12:30 PM, Alain Delmotte wrote: > Now for Philip, if you are not using auto-completion, which I regret because > it is very, very interesting - see the manual-- you could empty the folder, > so no definition would be loaded. > > Regards, > > Alain It seems like there should be a Preferences option for disabling auto-completion. -Charlie From P.Taylor at Rhul.Ac.Uk Sun Jun 12 22:00:33 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Sun, 12 Jun 2011 21:00:33 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> Message-ID: <4DF51AE1.6040403@Rhul.Ac.Uk> Charlie Sharpsteen wrote: > It seems like there should be a Preferences option for disabling > auto-completion. Yes please. Despite Alain's suggestion [1] that it would prove very interesting, I have managed without it for 64 years and it is now probably a bit late to come to terms with a need for it ! ** Phil. -------- [1] Alain Delmotte wrote: > Now for Philip, if you are not using auto-completion, which I regret > because it is very, very interesting - see the manual-- you could empty > the folder, so no definition would be loaded. > > Regards, > > Alain From P.Taylor at Rhul.Ac.Uk Sun Jun 12 22:07:15 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Sun, 12 Jun 2011 21:07:15 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF513D6.3050209@swing.be> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> Message-ID: <4DF51C73.3070501@Rhul.Ac.Uk> Alain Delmotte wrote: > This is coming from auto-completion. > if you keep pressing [Tab] you will have a lot more. > > alertenv is coming from the tw-beamer.txt file, but if you press [Tab] > long you will also have those from tw-latex.txt. This seems very odd : would it not make sense for TeXworks to inspect the currently selected typesetting engine, and then /if/ the user wants auto-completion, to offer completions only from the set that are known to be compatible with the engine selected ? In my case, I work exclusively with XeTeX, so neither Beamer nor LaTeX completions could possibly be of any interest. ** Phil. From paul.a.norman at gmail.com Mon Jun 13 01:36:36 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 13 Jun 2011 11:36:36 +1200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF51C73.3070501@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51C73.3070501@Rhul.Ac.Uk> Message-ID: Hi, Its probably worth mentioning that the range of autocompletition(s) shown is limited by typing a letter or two after the { e.g. {c will only show auto completions for c.... and {ce Is even more restrictive getting you to {center} \end{center}? --straight away, the Crtl- then moving you to the bullet point ? when you want to get there after typing/pasting something into the environment area. I wonder, if this is a concern needing addressing, (flying a kite here) ... Then if as Crtl- is needed to activate the second auto-completion function - moving to the bullet(s) if present - is it worth considering changing the initialising key stroke for the first part of auto-competition from a simple to Crtl- as well? Perhaps in preferences as a choice, to accommodate the many users presently now successfully using auto-completion as it already works? > would it not make sense for TeXworks > to inspect the currently selected typesetting engine, > ... to offer completions > only from the set that are known to be compatible with the > engine selected ? Things might not be quite as straight forward but might be possible by focussing on individual .txt files in ... /completion/ I (and others) already use Tw for processes which I appreciate (and supply) auto-completion for, which do not relate directly to any particular typesetting engine, e.g. direct editing of a bibliography file, Tw QtScript files (an old list soon to be updated hopefully:- http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm ), and a range of other things. > I work exclusively with XeTeX, > so neither Beamer nor LaTeX completions could possibly be of > any interest. I did not realise there was no cross over at all with LaTeX, XeTeX is going to be interesting new territory for me then. Paul On 13 June 2011 08:07, Philip TAYLOR (Webmaster, Ret'd) wrote: > > > Alain Delmotte wrote: > >> This is coming from auto-completion. >> if you keep pressing [Tab] you will have a lot more. >> >> alertenv is coming from the tw-beamer.txt file, but if you press [Tab] >> long you will also have those from tw-latex.txt. > > This seems very odd : would it not make sense for TeXworks > to inspect the currently selected typesetting engine, and > then /if/ the user wants auto-completion, to offer completions > only from the set that are known to be compatible with the > engine selected ? ?In my case, I work exclusively with XeTeX, > so neither Beamer nor LaTeX completions could possibly be of > any interest. > > ** Phil. > From nomosnomos at gmail.com Mon Jun 13 03:24:06 2011 From: nomosnomos at gmail.com (Dohyun Kim) Date: Mon, 13 Jun 2011 10:24:06 +0900 Subject: [texworks] Another experimental Mac build In-Reply-To: References: Message-ID: 2011/6/11 Charlie Sharpsteen : > > Ooops, you are right---it looks like the Snow Leopard build was still > including Fontconfig. I just replaced the binary with a new build that > doesn't include it. > Thanks. This build is almost OK for base14-fonts.pdf, except for the "mu" character of Symbol.ttf which is still an empty box. BTW I have found an another issue: http://dl.dropbox.com/u/15254523/pltx.pdf Upon testing this file with new TW build, now I cannot see any Japanese characters. This PDF file was produced from a tex file as follows with platex -> dvipdfmx commands on TeX Live 2010 distribution. \documentclass{jsarticle} \begin{document} ???(????) \end{document} With previous TW build with fontconfig library, there was no such issue, though Japanese characters were rendered with sans-serif family instead of serif. Ryumin-Light is a Japanese font of serif family. Well... I personally have doubts about these efforts to do away with fontconfig library, because font substitution of non-embedded fonts can be managed with my ~/.fonts.conf file when TW supports fontconfig. Certainly, this must be my own personal preference, as this cannot be expected for vast majority of users who are not familiar with fontconfig. Best, -- Dohyun Kim College of Law, Dongguk University Seoul, Republic of Korea From esperanto at swing.be Mon Jun 13 07:56:00 2011 From: esperanto at swing.be (Alain Delmotte) Date: Mon, 13 Jun 2011 07:56:00 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF51AE1.6040403@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> Message-ID: <4DF5A670.50105@swing.be> Philip, There is another solution, but you'll have to take the reflex to do: just add a space after { This {[return] [Tab] would create the problem This {[space][return] [Tab] not I know, it is not optimal; but on the other hand completion is very interesting. I was not using it before, but now, after trying in TW, yes. And I am also close to retirement. This offers some help not to forges closing sentences,... (example from LaTeX the \end{...} after a \begin{...} The solution of using [Ctrl]+[Tab] for both action, is not possible because after the first, if you get for example {center} \end{center}? the second [Ctrl]+[Tab] would bring you to the bullet point (I think). Philip, I would like to create a completion file for you about XeTeX. Are there instructions in XeTeX specific and not part of Plain TeX? (Which already has a completion file. Regards, Alain Le 12/06/2011 22:00, Philip TAYLOR (Webmaster, Ret'd) a ?crit : > > > Charlie Sharpsteen wrote: > >> It seems like there should be a Preferences option for >> disabling >> auto-completion. > > Yes please. Despite Alain's suggestion [1] that it would prove > very interesting, I have managed without it for 64 years and it > is now probably a bit late to come to terms with a need for > it ! > > ** Phil. > -------- > [1] Alain Delmotte wrote: > > > Now for Philip, if you are not using auto-completion, > which I regret > > because it is very, very interesting - see the manual-- > you could empty > > the folder, so no definition would be loaded. > > > > Regards, > > > > Alain > From chuck at sharpsteen.net Mon Jun 13 09:49:57 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Mon, 13 Jun 2011 00:49:57 -0700 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF51AE1.6040403@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> Message-ID: On Sun, Jun 12, 2011 at 1:00 PM, Philip TAYLOR (Webmaster, Ret'd) wrote: > > > Charlie Sharpsteen wrote: > >> It seems like there should be a Preferences option for disabling >> auto-completion. > > Yes please. ?Despite Alain's suggestion [1] that it would prove > very interesting, I have managed without it for 64 years and it > is now probably a bit late to come to terms with a need for it ! > > ** Phil. I added a preference option that enables/disables tab completion. Patch is here: https://github.com/Sharpie/TeXworks/commit/0a09d61.patch Seems to work on my machine. Definitely needs testing on Linux and Windows. -Charlie From paul.a.norman at gmail.com Mon Jun 13 09:53:55 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 13 Jun 2011 19:53:55 +1200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> Message-ID: Might perhaps be helpful to have something on a completion/ .txt file by file basis? Paul On 13 June 2011 19:49, Charlie Sharpsteen wrote: > On Sun, Jun 12, 2011 at 1:00 PM, Philip TAYLOR (Webmaster, Ret'd) > wrote: >> >> >> Charlie Sharpsteen wrote: >> >>> It seems like there should be a Preferences option for disabling >>> auto-completion. >> >> Yes please. ?Despite Alain's suggestion [1] that it would prove >> very interesting, I have managed without it for 64 years and it >> is now probably a bit late to come to terms with a need for it ! >> >> ** Phil. > > I added a preference option that enables/disables tab completion. Patch is here: > > ? ?https://github.com/Sharpie/TeXworks/commit/0a09d61.patch > > Seems to work on my machine. Definitely needs testing on Linux and Windows. > > -Charlie > > From jfkthame at googlemail.com Mon Jun 13 10:09:03 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Mon, 13 Jun 2011 09:09:03 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> Message-ID: On 13 Jun 2011, at 08:49, Charlie Sharpsteen wrote: > On Sun, Jun 12, 2011 at 1:00 PM, Philip TAYLOR (Webmaster, Ret'd) > wrote: >> >> >> Charlie Sharpsteen wrote: >> >>> It seems like there should be a Preferences option for disabling >>> auto-completion. >> >> Yes please. Despite Alain's suggestion [1] that it would prove >> very interesting, I have managed without it for 64 years and it >> is now probably a bit late to come to terms with a need for it ! >> >> ** Phil. > > I added a preference option that enables/disables tab completion. Patch is here: > > https://github.com/Sharpie/TeXworks/commit/0a09d61.patch > > Seems to work on my machine. Definitely needs testing on Linux and Windows. > > -Charlie > I haven't actually tested it but this looks like it'd work fine. However, I think it'd be better to avoid reading the preference setting on every keystroke; instead, store the current value somewhere global (or should it be per-document?), initializing it from the settings file at startup and updating it if the user actually changes the prefs. JK From jfkthame at googlemail.com Mon Jun 13 10:12:29 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Mon, 13 Jun 2011 09:12:29 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> Message-ID: <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> On 13 Jun 2011, at 08:53, Paul A Norman wrote: > Might perhaps be helpful to have something on a completion/ > .txt file by file basis? > I was originally thinking of doing this - that's one reason for supporting multiple files, rather than just dumping everything into a single text file - but didn't get around to it. At that point it would probably need to be a separate preference panel, though, to avoid over-filling the Editor panel. And maybe that's too much UI for one little feature.... hmmm. Not sure. JK > Paul > > On 13 June 2011 19:49, Charlie Sharpsteen wrote: >> On Sun, Jun 12, 2011 at 1:00 PM, Philip TAYLOR (Webmaster, Ret'd) >> wrote: >>> >>> >>> Charlie Sharpsteen wrote: >>> >>>> It seems like there should be a Preferences option for disabling >>>> auto-completion. >>> >>> Yes please. Despite Alain's suggestion [1] that it would prove >>> very interesting, I have managed without it for 64 years and it >>> is now probably a bit late to come to terms with a need for it ! >>> >>> ** Phil. >> >> I added a preference option that enables/disables tab completion. Patch is here: >> >> https://github.com/Sharpie/TeXworks/commit/0a09d61.patch >> >> Seems to work on my machine. Definitely needs testing on Linux and Windows. >> >> -Charlie >> >> > From P.Taylor at Rhul.Ac.Uk Mon Jun 13 10:18:07 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Mon, 13 Jun 2011 09:18:07 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> Message-ID: <4DF5C7BF.8090701@Rhul.Ac.Uk> Charlie Sharpsteen wrote: > I added a preference option that enables/disables tab completion. Patch is here: > > https://github.com/Sharpie/TeXworks/commit/0a09d61.patch > > Seems to work on my machine. Definitely needs testing on Linux and Windows. Many thanks, Charlie. As a "typical" Windows user, I do not (of course) ever build any TeX Live binaries from source, but if anyone can compile in Charlie's patch and let me have a copy I will be very happy to test. Target platform = Win(32)/XP. ** Phil. From P.Taylor at Rhul.Ac.Uk Mon Jun 13 10:51:43 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Mon, 13 Jun 2011 09:51:43 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF5A670.50105@swing.be> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <4DF5A670.50105@swing.be> Message-ID: <4DF5CF9F.9010101@Rhul.Ac.Uk> Alain Delmotte wrote: > There is another solution, but you'll have to take the reflex to do: > just add a space after { > > This {[return] > [Tab] > > would create the problem > > This {[space][return] > [Tab] > > not Understood, and after faffing around trying other techniques, I usually fall back on this one, but I hate it in principle : setting a document with tabs can cause documents to look different in different environments, but at least the implied nesting is usually honoured, but setting a document with a mixture of tabs and spaces can be an absolute disaster in terms of portability -- implied nesting frequently flies straight out of the window when one views such a document in a different environment :-( > Philip, I would like to create a completion file for you about XeTeX. > Are there instructions in XeTeX specific and not part of Plain TeX? > (Which already has a completion file. Probably :-) But please, do not do this : I do not use auto-completion, do not expect to want to use auto-completion, and above all do not want you to waste your valuable time writing something for me that I am very unlikely to use. So I am extremely grateful to you for your kind offer, but I really prefer to create my documents entirely by hand ! P.S. > Plain TeX? (Which already has a completion file. In that case, why does a Beamer autocompletion kick in when I have typed something that is pure TeX (i.e., 100% Plain compatible, looking nothing like a call to Beamer) rather than a Plain autocompletion ? I type \def \foo { and at that point autocompletion kicks in with a Beamer entity, yet this is the entire document and there is nothing that should lead TeXworks to believe I am creating a Beamer-based document. Of course, any Plain autocompletion would have to be complete and utter guesswork : no editor in the world, no matter how intelligent, could possibly guess on the basis of \def \foo { >tab> what the next intended construct is most likely to be ! ** Phil. From paul.a.norman at gmail.com Mon Jun 13 12:37:06 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 13 Jun 2011 22:37:06 +1200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> Message-ID: On 13 June 2011 20:12, Jonathan Kew wrote: > > On 13 Jun 2011, at 08:53, Paul A Norman wrote: > >> Might perhaps be helpful to have something on a completion/ >> .txt ?file by file basis? >> > > I was originally thinking of doing this - that's one reason for supporting multiple files, rather than just dumping everything into a single text file - but didn't get around to it. At that point it would probably need to be a separate preference panel, though, to avoid over-filling the Editor panel. And maybe that's too much UI for one little feature.... hmmm. Not sure. What about a set height slideshowable QListView populated at startup with QCheckBox(es) from the /completion/*.txt files' list? Paul > > JK > >> Paul >> >> On 13 June 2011 19:49, Charlie Sharpsteen wrote: >>> On Sun, Jun 12, 2011 at 1:00 PM, Philip TAYLOR (Webmaster, Ret'd) >>> wrote: >>>> >>>> >>>> Charlie Sharpsteen wrote: >>>> >>>>> It seems like there should be a Preferences option for disabling >>>>> auto-completion. >>>> >>>> Yes please. ?Despite Alain's suggestion [1] that it would prove >>>> very interesting, I have managed without it for 64 years and it >>>> is now probably a bit late to come to terms with a need for it ! >>>> >>>> ** Phil. >>> >>> I added a preference option that enables/disables tab completion. Patch is here: >>> >>> ? ?https://github.com/Sharpie/TeXworks/commit/0a09d61.patch >>> >>> Seems to work on my machine. Definitely needs testing on Linux and Windows. >>> >>> -Charlie >>> >>> >> > > > From st.loeffler at gmail.com Mon Jun 13 15:18:55 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Mon, 13 Jun 2011 15:18:55 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF4C003.7020908@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> Message-ID: <4DF60E3F.1030104@gmail.com> Hi, On 2011-06-12 15:32, Philip TAYLOR (Webmaster, Ret'd) wrote: > So why is it that when I type > > \def \foo > { > > and then press at the start of the blank line > below the "{" (which is itself indented with one tab), > TeXworks insists in entering > > alertenv}<> > > and putting the cursor between the angle-brackets ? Because it's a bug ;). Seriously, I've found this behavior myself some time ago, started to patch it, but apparently got side-tracked by other things. Anyway, IMO it's definitely not intended that autocompletion is triggered on an empty line (or one containing only whitespaces). > I have no idea what "alertenv" is, nor do I want > it inserted; how may this be avoided, please ? By downloading r844 or later (hopefully). I just committed my patch and uploaded new builds. HTH Stefan From st.loeffler at gmail.com Mon Jun 13 15:30:39 2011 From: st.loeffler at gmail.com (=?windows-1252?Q?Stefan_L=F6ffler?=) Date: Mon, 13 Jun 2011 15:30:39 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF51C73.3070501@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51C73.3070501@Rhul.Ac.Uk> Message-ID: <4DF610FF.8030100@gmail.com> Hi, On 2011-06-12 22:07, Philip TAYLOR (Webmaster, Ret'd) wrote: > This seems very odd : would it not make sense for TeXworks > to inspect the currently selected typesetting engine, and > then /if/ the user wants auto-completion, to offer completions > only from the set that are known to be compatible with the > engine selected ? In my case, I work exclusively with XeTeX, > so neither Beamer nor LaTeX completions could possibly be of > any interest. unfortunately, the situation is more difficult, because there is no direct connection between the engine and the syntax. First of all, you can use different engines on a single document (think, e.g., latex, bibtex, makeindex, ...). And secondly, an engine may be arbitrarily complex (e.g., a shell/batch/perl/etc. script that invokes other commands) and does not necessarily work only for a single type of sources. Other things might come to mind. You could inspect the document preamble, e.g., to look for the beamer class and activate the corresponding auto-completion only if it is found. But this again doesn't cover the case that some company, journal, university, or other build their own classes on top of beamer - in which case the autocompletion would be valid although "beamer" is never mentioned in the file. In addition, what do you do in a sub-document (which uses the "%!TeX root" syntax)? There, you have no preamble at all to look for. All in all, TeX & Co. are very complex languages, and safe of building a *TeX parser into Tw, there's no reliable way of guessing what the user wants. In fact, I see just one way: asking the user. This is definitely on my todo list, but in a larger scope - and before I can start that, we need to get Tw ready for TL'11 and I'll need to discuss this in-depth with Jonathan. Cheers, Stefan From st.loeffler at gmail.com Mon Jun 13 15:35:43 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Mon, 13 Jun 2011 15:35:43 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> Message-ID: <4DF6122F.3030006@gmail.com> Hi, On 2011-06-13 09:49, Charlie Sharpsteen wrote: > I added a preference option that enables/disables tab completion. > Patch is here: > https://github.com/Sharpie/TeXworks/commit/0a09d61.patch > > Seems to work on my machine. Definitely needs testing on Linux and Windows. Thanks for the patch. I share Jonathan's concerns about reading the settings on every key stroke. In addition, I'd rather not add a GUI option at this time. At the moment, we're in the TL'11 testing phase, and I expect a 0.4.2 bugfix release soon (essentially, as soon as the resolution of issue 469/505 is confirmed and the new python approach is reported working). If we were to change the interface now, this would entail a new translation round, which takes quite some time. That said, if you could split the patch in two (a code and a GUI part) I could commit the new code (so power-users can disable autocompletion from the configuration file/registry) and postpone the GUI part. In that case, please open a issue at GC (mails tend to get buried ;)). Thanks, Stefan From esperanto at swing.be Mon Jun 13 15:39:17 2011 From: esperanto at swing.be (Alain Delmotte) Date: Mon, 13 Jun 2011 15:39:17 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF60E3F.1030104@gmail.com> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF60E3F.1030104@gmail.com> Message-ID: <4DF61305.5060604@swing.be> Stefan, In 844 there is again python27.dll Is this to be used? Didn't you compile as previously for 843? Regards, Aalain Le 13/06/2011 15:18, Stefan L?ffler a ?crit : > Hi, > > On 2011-06-12 15:32, Philip TAYLOR (Webmaster, Ret'd) wrote: >> So why is it that when I type >> >> \def \foo >> { >> >> and then press at the start of the blank line >> below the "{" (which is itself indented with one tab), >> TeXworks insists in entering >> >> alertenv}<> >> >> and putting the cursor between the angle-brackets ? > > Because it's a bug ;). Seriously, I've found this behavior myself some > time ago, started to patch it, but apparently got side-tracked by other > things. Anyway, IMO it's definitely not intended that autocompletion is > triggered on an empty line (or one containing only whitespaces). > >> I have no idea what "alertenv" is, nor do I want >> it inserted; how may this be avoided, please ? > > By downloading r844 or later (hopefully). I just committed my patch and > uploaded new builds. > > HTH > Stefan > From st.loeffler at gmail.com Mon Jun 13 15:45:17 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Mon, 13 Jun 2011 15:45:17 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> Message-ID: <4DF6146D.5060009@gmail.com> Hi, On 2011-06-13 12:37, Paul A Norman wrote: > On 13 June 2011 20:12, Jonathan Kew wrote: >> On 13 Jun 2011, at 08:53, Paul A Norman wrote: >> >>> Might perhaps be helpful to have something on a completion/ >>> .txt file by file basis? >>> >> I was originally thinking of doing this - that's one reason for supporting multiple files, rather than just dumping everything into a single text file - but didn't get around to it. At that point it would probably need to be a separate preference panel, though, to avoid over-filling the Editor panel. And maybe that's too much UI for one little feature.... hmmm. Not sure. > What about a set height slideshowable QListView populated at startup > with QCheckBox(es) from the /completion/*.txt files' > list? Yes, something of the sort. However, I think that right now, this would be a lot of work and much UI for one little feature. In particular (as elaborated a bit elsewhere in this thread), Tw has no way of knowing/guessing what kind of file you're working on. Consequently, you'd have to constantly change either global or per-file settings if working with different types of files - which is not very convenient IMO. Anyway, this might change in the future... HTH Stefan From st.loeffler at gmail.com Mon Jun 13 15:49:40 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Mon, 13 Jun 2011 15:49:40 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF61305.5060604@swing.be> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF60E3F.1030104@gmail.com> <4DF61305.5060604@swing.be> Message-ID: <4DF61574.5080805@gmail.com> Hi, On 2011-06-13 15:39, Alain Delmotte wrote: > In 844 there is again python27.dll > > Is this to be used? Didn't you compile as previously for 843? Yes, and no. The builds I upload to GC are still using the established build process - python27.dll and all. Only the builds I uploaded to my webspace are using the experimental build system without the DLL. After all, I didn't see any confirmation yet that that build worked as expected on its own. If it does, I'll adapt the GC builds accordingly. Cheers, Stefan From joelcsalomon at gmail.com Mon Jun 13 17:44:49 2011 From: joelcsalomon at gmail.com (Joel C. Salomon) Date: Mon, 13 Jun 2011 11:44:49 -0400 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF5A670.50105@swing.be> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <4DF5A670.50105@swing.be> Message-ID: <4DF63071.3080607@gmail.com> On 06/13/2011 01:56 AM, Alain Delmotte wrote: > There is another solution, but you'll have to take the reflex to do: > just add a space after { Trouble is that source control gets tricky sometimes with trailing spaces. I like auto-complete, & don?t want to give it up, but the behavior of Tab at start-of-line is so counterintuitive I?d almost rather give up the feature ? or at least not have it active at start-of-line. It?s that annoying. > The solution of using [Ctrl]+[Tab] for both action, is not possible > because after the first, if you get for example > {center} > > \end{center}? > > the second [Ctrl]+[Tab] would bring you to the bullet point (I think). If start-of-line auto-complete is so useful, then auto-complete needs a different shortcut. I almost don?t care what, but Tab is a misfeature. ?Joel From esperanto at swing.be Mon Jun 13 18:00:39 2011 From: esperanto at swing.be (Alain Delmotte) Date: Mon, 13 Jun 2011 18:00:39 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF61574.5080805@gmail.com> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF60E3F.1030104@gmail.com> <4DF61305.5060604@swing.be> <4DF61574.5080805@gmail.com> Message-ID: <4DF63427.3020902@swing.be> Hi! OK it works fine at the start of a line. But if I do \def {[Tab] [Tab] after the { I get the completion proposals. As for the python scripts, all mine work. Regards, Alain Le 13/06/2011 15:49, Stefan L?ffler a ?crit : > Hi, > > On 2011-06-13 15:39, Alain Delmotte wrote: >> In 844 there is again python27.dll >> >> Is this to be used? Didn't you compile as previously for 843? > > Yes, and no. The builds I upload to GC are still using the established > build process - python27.dll and all. Only the builds I uploaded to my > webspace are using the experimental build system without the DLL. > > After all, I didn't see any confirmation yet that that build worked as > expected on its own. If it does, I'll adapt the GC builds accordingly. > > Cheers, > Stefan > From chuck at sharpsteen.net Mon Jun 13 18:25:32 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Mon, 13 Jun 2011 09:25:32 -0700 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF6122F.3030006@gmail.com> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <4DF6122F.3030006@gmail.com> Message-ID: On Mon, Jun 13, 2011 at 6:35 AM, Stefan L?ffler wrote: > Hi, > > On 2011-06-13 09:49, Charlie Sharpsteen wrote: >> I added a preference option that enables/disables tab completion. >> Patch is here: >> ? ? https://github.com/Sharpie/TeXworks/commit/0a09d61.patch >> >> Seems to work on my machine. Definitely needs testing on Linux and Windows. > > Thanks for the patch. I share Jonathan's concerns about reading the > settings on every key stroke. > In addition, I'd rather not add a GUI option at this time. At the > moment, we're in the TL'11 testing phase, and I expect a 0.4.2 bugfix > release soon (essentially, as soon as the resolution of issue 469/505 is > confirmed and the new python approach is reported working). If we were > to change the interface now, this would entail a new translation round, > which takes quite some time. > > That said, if you could split the patch in two (a code and a GUI part) I > could commit the new code (so power-users can disable autocompletion > from the configuration file/registry) and postpone the GUI part. In that > case, please open a issue at GC (mails tend to get buried ;)). > > Thanks, > Stefan I split the commit into two parts. The non-GUI part: Overview: https://github.com/Sharpie/TeXworks/commit/31b3c75 Patch: https://github.com/Sharpie/TeXworks/commit/31b3c75.patch And the part that affects the preferences pane: Overview: https://github.com/Sharpie/TeXworks/commit/ee7fbaf Patch: https://github.com/Sharpie/TeXworks/commit/ee7fbaf.patch I also cleaned up the implementation so that the settings file is not being read with every keystroke. If only the first patch is applied, users will have to edit the TeXworks preference file and set a value for `autocompleteEnabled` to toggle autocompletion. On OS X, this file is a XML-based plist that has been compiled to a binary (Seriously, XML *is* like violence---if it doesn't work, compile it for concentrated application!). The following command-line incantations will edit the settings file when entered into a console: To disable: defaults write org.tug.TeXworks autocompleteEnabled -boolean NO To enable: defaults write org.tug.TeXworks autocompleteEnabled -boolean YES TeXworks will have to be restarted in order for changes to the configuration file to have effect. I will also open an issue on the GC tracker. -Charlie From chuck at sharpsteen.net Mon Jun 13 21:31:24 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Mon, 13 Jun 2011 12:31:24 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DF058E1.7080905@gmail.com> References: <4E5C1822-84FB-4F7D-8DFD-F3DD605C9C27@gmail.com> <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> Message-ID: Allright, looks like we have a new wrinkle in that pTeX does not embed fonts: http://tug.org/pipermail/texworks/2011q2/004361.html The font in question is a CJK font, "Ryumin-Light-Identity-H". It looks like Fontconfig chooses a more or less appropriate fallback while the Quartz backend just iteratively peels hyphenated sections from the font name then gives up and substitutes Helvetica. Another thing to note is that the fallback used by Fontconfig can be customized by editing `~/.fonts.conf`. So, unless anyone has some good ideas on how to add fallback support to the Quartz font handler, we may be back to the question of "should we implement native mac fonts or just use Fontconfig?" The only downside that I have found with Fontconfig is that users won't see non-embedded fonts unless their copy of OS X has X11 installed. X11 is installed by default in OS X 10.5.x and 10.6.x, but could be missing if the user customized their installation and optimized for size. Not sure what the situation is for 10.7, but I guess we will find out next month. Thoughts? -Charlie From chuck at sharpsteen.net Mon Jun 13 21:36:19 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Mon, 13 Jun 2011 12:36:19 -0700 Subject: [texworks] Another experimental Mac build In-Reply-To: References: Message-ID: 2011/6/12 Dohyun Kim : > 2011/6/11 Charlie Sharpsteen : >> >> Ooops, you are right---it looks like the Snow Leopard build was still >> including Fontconfig. I just replaced the binary with a new build that >> doesn't include it. >> > > Thanks. > This build is almost OK for base14-fonts.pdf, > except for the "mu" character of Symbol.ttf which is still an empty box. The missing glyph in the Symbol font is due to some sort of encoding issue. The same missing glyph also shows up with builds of Poppler that use Fontconfig. We decided not to spend the time hunting it down as most PDF files viewed by TeXworks have embedded fonts. > BTW I have found an another issue: > http://dl.dropbox.com/u/15254523/pltx.pdf > Upon testing this file with new TW build, > now I cannot see any Japanese characters. > > This PDF file was produced from a tex file as follows > with platex -> dvipdfmx commands on TeX Live 2010 distribution. > > \documentclass{jsarticle} > \begin{document} > ???(????) > \end{document} > > With previous TW build with fontconfig library, > there was no such issue, though Japanese characters > were rendered with sans-serif family instead of serif. > Ryumin-Light is a Japanese font of serif family. > > Well... I personally have doubts about these efforts > to do away with fontconfig library, because > font substitution of non-embedded fonts can be managed > with my ~/.fonts.conf file when TW supports fontconfig. > Certainly, this must be my own personal preference, > as this cannot be expected for vast majority of users > who are not familiar with fontconfig. > > Best, > -- > Dohyun Kim > College of Law, Dongguk University > Seoul, Republic of Korea Thanks for this testcase! It looks like pTeX does not embed all fonts used in the document which breaks some assumptions we made while building the Quartz font backend. If we can't find a resolution for this issue, we may end up sticking with Fontconfig. Thanks again for testing! -Charlie From sigmundv at gmail.com Mon Jun 13 21:59:14 2011 From: sigmundv at gmail.com (sigmundv at gmail.com) Date: Mon, 13 Jun 2011 21:59:14 +0200 Subject: [texworks] Mac issues Message-ID: Hi, Why do I see so many discussions on Mac specific stuff on this list? There is hardly anything Windows or Linux specific discussed. Why is this? Is TeXworks used more on Mac OS X than on Windows or Linux? Or is Mac OS X just so much different? Sigmund -------------- next part -------------- An HTML attachment was scrubbed... URL: From herbs at wideopenwest.com Mon Jun 13 22:20:44 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Mon, 13 Jun 2011 15:20:44 -0500 Subject: [texworks] Mac issues In-Reply-To: References: Message-ID: <3880E611-7ADF-42A1-BCAF-C5D24E72C496@wideopenwest.com> On Jun 13, 2011, at 2:59 PM, sigmundv at gmail.com wrote: > Hi, > > Why do I see so many discussions on Mac specific stuff on this list? There > is hardly anything Windows or Linux specific discussed. Why is this? Is > TeXworks used more on Mac OS X than on Windows or Linux? Or is Mac OS X just > so much different? > > > Sigmund Howdy, While it may appear to you that most of the discussion is Mac related it appear to me the other way round. I see much more Linux and especially Windows discussion here. Most of the recent development has first appeared on the Windows version of TeXworks. If I had to guess TeXworks is probably much more heavily used on Windows and Linux than the Mac. TeXworks is modelled on TeXShop which is a popular front end on the Mac. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From P.Taylor at Rhul.Ac.Uk Mon Jun 13 20:53:24 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Mon, 13 Jun 2011 19:53:24 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF6146D.5060009@gmail.com> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> <4DF6146D.5060009@gmail.com> Message-ID: <4DF65CA4.1020009@Rhul.Ac.Uk> Stefan L?ffler wrote: > In particular (as > elaborated a bit elsewhere in this thread), Tw has no way of > knowing/guessing what kind of file you're working on. This part I don't understand. When I open a file in TeXworks, the first thing I do is to go to the dropdown menu alongside the green "Typeset" arrow and select the engine needed to process that file. Once I have done that, TeXworks /knows/ what kind of file I am working on, and could then offer autocompletion appropriate to that kind of file. Prior to setting the typesetting engine, autocompletion must be completely inappropriate since, as you say, "Tw has no way of knowing/guessing what kind of file you're working on". ** Phil. From P.Taylor at Rhul.Ac.Uk Mon Jun 13 20:56:19 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Mon, 13 Jun 2011 19:56:19 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF60E3F.1030104@gmail.com> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF60E3F.1030104@gmail.com> Message-ID: <4DF65D53.1000207@Rhul.Ac.Uk> Stefan L?ffler wrote: > By downloading r844 or later (hopefully). I just committed my patch and > uploaded new builds. Thank you ! And please forgive my naivety, but when you say "download r844 or later", are we talking about "download from TLnet", "download from CTAN", or "download from somewhere else" ? ** Phil (who recently removed all but "basic" from his "completion" folder and now has a TeXworks that doesn't manifest the previous odd behaviour). From bpj at melroch.se Mon Jun 13 23:02:49 2011 From: bpj at melroch.se (BPJ) Date: Mon, 13 Jun 2011 23:02:49 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF6146D.5060009@gmail.com> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> <4DF6146D.5060009@gmail.com> Message-ID: <4DF67AF9.8090802@melroch.se> 2011-06-13 15:45, Stefan L?ffler skrev: > Hi, > > On 2011-06-13 12:37, Paul A Norman wrote: >> On 13 June 2011 20:12, Jonathan Kew wrote: >>> On 13 Jun 2011, at 08:53, Paul A Norman wrote: >>> >>>> Might perhaps be helpful to have something on acompletion/ >>>> .txt file by file basis? >>>> >>> I was originally thinking of doing this - that's one reason for supporting multiple files, rather than just dumping everything into a single text file - but didn't get around to it. At that point it would probably need to be a separate preference panel, though, to avoid over-filling the Editor panel. And maybe that's too much UI for one little feature.... hmmm. Not sure. >> What about a set height slideshowable QListView populated at startup >> with QCheckBox(es) from the/completion/*.txt files' >> list? > > Yes, something of the sort. However, I think that right now, this would > be a lot of work and much UI for one little feature. In particular (as > elaborated a bit elsewhere in this thread), Tw has no way of > knowing/guessing what kind of file you're working on. Consequently, > you'd have to constantly change either global or per-file settings if > working with different types of files - which is not very convenient > IMO. Anyway, this might change in the future... > > HTH > Stefan > What are you talking about here? A long list with all the autocompletion snippets, or a short(er) one with the filenames from /completion/ ? If the latter I definitely think it's worth it. Given that each /completion/*.txt file contains snippets appropriate for one kind of documents it makes eminent sense to be able to (de)activate those completion files which are not relevant for a particular file. In fact I've refrained from creating my own completion files inter alia because I want to minimize the number of currently irrelevant alternatives popping up, and moving files in and out of /completion/ and restarting TW isn't all that practical. /bpj From joseph.wright at morningstar2.co.uk Mon Jun 13 23:04:46 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Mon, 13 Jun 2011 22:04:46 +0100 Subject: [texworks] Mac issues In-Reply-To: References: Message-ID: <4DF67B6E.2080407@morningstar2.co.uk> On 13/06/2011 20:59, sigmundv at gmail.com wrote: > Hi, > > Why do I see so many discussions on Mac specific stuff on this list? There > is hardly anything Windows or Linux specific discussed. Why is this? Is > TeXworks used more on Mac OS X than on Windows or Linux? Or is Mac OS X just > so much different? This list covers both TeXworks user issues and items relating to TeXworks development. There is some overlap between interested parties, so this makes sense, but does from time to time make things a bit developer-heavy. There has been a reasonable amount of Mac-related stuff recently as there have been some issues building TeXworks binaries on that platform. The lead developer (Stefan) builds on Windows, and building on Linux is currently pretty easy, and so there has been less recent discussion on these. As noted by others, in the past we've seen a lot of discussion about various platforms. -- Joseph Wright From chuck at sharpsteen.net Mon Jun 13 23:06:38 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Mon, 13 Jun 2011 14:06:38 -0700 Subject: [texworks] Mac issues In-Reply-To: References: Message-ID: On Mon, Jun 13, 2011 at 12:59 PM, sigmundv at gmail.com wrote: > Hi, > Why do I see so many discussions on Mac specific stuff on this list? There > is hardly anything Windows or Linux specific discussed. Why is this? Is > TeXworks used more on Mac OS X than on Windows or Linux? Or is Mac OS X just > so much different? > > Sigmund Recently there has been a lot of Mac-specific activity related to updating the procedures for building/packaging TeXworks on the Mac. The last "offical" Mac release occurred about a year and a half ago, so some of the recent discussions concern cleaning out Mac-specific cobwebs and getting stable packages built for end users. -Charlie From bpj at melroch.se Mon Jun 13 23:09:00 2011 From: bpj at melroch.se (BPJ) Date: Mon, 13 Jun 2011 23:09:00 +0200 Subject: [texworks] Mac issues In-Reply-To: <3880E611-7ADF-42A1-BCAF-C5D24E72C496@wideopenwest.com> References: <3880E611-7ADF-42A1-BCAF-C5D24E72C496@wideopenwest.com> Message-ID: <4DF67C6C.20100@melroch.se> 2011-06-13 22:20, Herbert Schulz skrev: > While it may appear to you that most of the discussion is Mac > related it appear to me the other way round. I see much more > Linux and especially Windows discussion here. Most of the > recent development has first appeared on the Windows version of > TeXworks. I'm on Linux, don't particularly like Windows, and through my glasses I see mostly Windows-related discussion here, so it definitely depends on what angle you're looking from. /bpj From reinhard.kotucha at web.de Tue Jun 14 00:21:18 2011 From: reinhard.kotucha at web.de (Reinhard Kotucha) Date: Tue, 14 Jun 2011 00:21:18 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF65CA4.1020009@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> <4DF6146D.5060009@gmail.com> <4DF65CA4.1020009@Rhul.Ac.Uk> Message-ID: <19958.36190.619405.824796@zaphod.ms25.net> On 2011-06-13 at 19:53:24 +0100, Philip TAYLOR (Webmaster, Ret'd) wrote: > Stefan L?ffler wrote: > > > In particular (as elaborated a bit elsewhere in this thread), Tw > > has no way of knowing/guessing what kind of file you're working > > on. > > This part I don't understand. When I open a file in TeXworks, the > first thing I do is to go to the dropdown menu alongside the green > "Typeset" arrow and select the engine needed to process that file. > Once I have done that, TeXworks /knows/ what kind of file I am > working on, and could then offer autocompletion appropriate to that > kind of file. Prior to setting the typesetting engine, > autocompletion must be completely inappropriate since, as you say, > "Tw has no way of knowing/guessing what kind of file you're working > on". Even if you specify a particular engine, it's still not clear which type of file you want to process. Suppose you select "plain TeX" but the file contains the line "\input texinfo.tex". After loading this file, the escape character is "@" instead of "\". This breaks command completion and syntax highlighting and it's extremely difficult for an editor to find out what to do. The problem you reported is a good example. Plain TeX can more or less considered as a programming language, whereas LaTeX is supposed to be a markup language, i.e. a file format. One would expect then that it's easier to support command completion and syntax highlighting in LaTeX. This is definitely true, but Beamer re-defines standard LaTeX list environments. Hence, if you want to provide proper command completion and syntax highlighting, you have to evaluate the whole file. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha at web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- From paul.a.norman at gmail.com Tue Jun 14 01:02:03 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 14 Jun 2011 11:02:03 +1200 Subject: [texworks] Pine Needles Was - Re: Mac issues Message-ID: Hi, I remember when first doing Statistics doing that exercise of measuring pine-needles. For any one who hasn't done it, you, as randomly as any human can do anything, gather small piles of loose pine-needles (the leaves of pine trees). You then accurately measure the length of the pine-needles in millimetres and then enter the data and graph the number of pine needles (Y axis) against measurement of length points on the X axis. Allowing for local variations and conditions you nearly always end up with a graph that pretty well much conforms to the natural distribution bell shape curve. Its quite remarkable really. Computer usage and choice of OS for varoius resons does not conform to a bell shaped natural distribution curve. Nor is it a flat line. For various historical commercial and economic stragety reasons it is a biased curve perhaps best shown by this picture: http://en.wikipedia.org/wiki/File:Operating_system_usage_share.svg The median derived figures (with all the inherent assumptions about what this represents about PC OS) for May 2011 look like this: "Usage share of web client operating systems" http://en.wikipedia.org/wiki/Usage_share_of_operating_systems Windows all versions: 86.37% Mac OS X: 7.40% OS (iPhone) (2.80%) Linux (2.07%) Statistically the order of magnitude for the "Windows all versions" compared to to other versions quells and submerges many of the other considerations that might be entered into (especially about people not being likely to be using iOs Phones to run TeXworks etc etc) So from the very nature of things there will be more Users asking TeXworks questions from a Windows perspective. It show no bias on the part of the TeXworks project- just a reflection of what is out there. Whatever can be said, it was a good policy decision for the TeXworks project to be designed from inception to try and encourage more Windows and Linux users onto *TeX through making a good Editor like the Mac system already had. I use Windows and Ubuntu (--not as much as I would like), and never at present a Mac of any kind. But I have always been impressed with the even handed approach that has existed here for all the different OS-es, human lanngauages, and of courcse the *TeX attitude to different alphabets. What I have seen so far is an effort from C++ code contributors, Script contributors, and help manual writers and many others as well, to try and reach across the boundaries of any sort and make this project work. The present focus on solving Mac issues is needed. I do not use a Mac as I have said, but in the attitude of this project even earlier joined in putting a plea out for any one with Mac programming experience to help. I hope that this genuine cross-platform and multi language approach can be fostered and encouraged in this project, for it is a really good things that has been happening, and I am sure that there is no deliberate effort on any ones part to bias the project in any way, just differing needs for attention on different things from time to time. Its is good that User experience and Developer and Scripting talk cross over on the list. Both groups have to sight subject lines that might not be of interest, but in the end every one gets the chance to spot something they may have a need to contribute on, and also to make suggestions when a technical issue is being decided that may have enormous implications for User experience. Paul On 14 June 2011 09:09, BPJ wrote: > 2011-06-13 22:20, Herbert Schulz skrev: >> >> While it may appear to you that most of the discussion is Mac >> related it appear to me the other way round. I see much more >> Linux and especially Windows discussion here. Most of the >> recent development has first appeared on the Windows version of >> TeXworks. > > I'm on Linux, don't particularly like Windows, and through my > glasses I see mostly Windows-related discussion here, so it > definitely depends on what angle you're looking from. > > /bpj > From P.Taylor at Rhul.Ac.Uk Tue Jun 14 00:40:32 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Mon, 13 Jun 2011 23:40:32 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <19958.36190.619405.824796@zaphod.ms25.net> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> <4DF6146D.5060009@gmail.com> <4DF65CA4.1020009@Rhul.Ac.Uk> <19958.36190.619405.824796@zaphod.ms25.net> Message-ID: <4DF691E0.5030502@Rhul.Ac.Uk> Reinhard Kotucha wrote: > Even if you specify a particular engine, it's still not clear which > type of file you want to process. Suppose you select "plain TeX" but > the file contains the line "\input texinfo.tex". After loading this > file, the escape character is "@" instead of "\". This breaks command > completion and syntax highlighting and it's extremely difficult for an > editor to find out what to do. > > The problem you reported is a good example. Plain TeX can more or > less considered as a programming language, whereas LaTeX is supposed > to be a markup language, i.e. a file format. One would expect then > that it's easier to support command completion and syntax highlighting > in LaTeX. This is definitely true, but Beamer re-defines standard > LaTeX list environments. Hence, if you want to provide proper command > completion and syntax highlighting, you have to evaluate the whole > file. Yes, I agree that no matter which engine you select, you /may/ have a pathological file that does not follow the normal markup pattern for that engine, so in an ideal world you could then switch auto-completion on the fly. But a default behaviour that uses the engine to determine which set of auto-completes is most likely to be relevant is surely not an unreasonable behaviour, is it ? ** Phil. From paul.a.norman at gmail.com Tue Jun 14 02:32:38 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 14 Jun 2011 12:32:38 +1200 Subject: [texworks] Mac issues In-Reply-To: <4DF67B6E.2080407@morningstar2.co.uk> References: <4DF67B6E.2080407@morningstar2.co.uk> Message-ID: > The lead developer (Stefan) builds on Windows Just to clear this up in case anyone is still wondering what happens ... I believe that for a long time now Stefan has been on Ubuntu and currently uses MingGW cross-compile to build for Windows. >From bottom of this message:-- http://tug.org/mailman/htdig/texworks/2011q1/004001.html Sun Mar 27 14:34:02 CEST 2011 "I cross-compile Tw for Windows from Linux via MinGW. Regards, Stefan" Paul On 14 June 2011 09:04, Joseph Wright wrote: > On 13/06/2011 20:59, sigmundv at gmail.com wrote: >> Hi, >> >> Why do I see so many discussions on Mac specific stuff on this list? There >> is hardly anything Windows or Linux specific discussed. Why is this? Is >> TeXworks used more on Mac OS X than on Windows or Linux? Or is Mac OS X just >> so much different? > > This list covers both TeXworks user issues and items relating to > TeXworks development. There is some overlap between interested parties, > so this makes sense, but does from time to time make things a bit > developer-heavy. > > There has been a reasonable amount of Mac-related stuff recently as > there have been some issues building TeXworks binaries on that platform. > The lead developer (Stefan) builds on Windows, and building on Linux is > currently pretty easy, and so there has been less recent discussion on > these. As noted by others, in the past we've seen a lot of discussion > about various platforms. > -- > Joseph Wright > From paul.a.norman at gmail.com Tue Jun 14 02:38:27 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 14 Jun 2011 12:38:27 +1200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF691E0.5030502@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> <4DF6146D.5060009@gmail.com> <4DF65CA4.1020009@Rhul.Ac.Uk> <19958.36190.619405.824796@zaphod.ms25.net> <4DF691E0.5030502@Rhul.Ac.Uk> Message-ID: Hi, At a pinch I wouldn't mind even a drop down type widget with checkable boxes that lets me choose which completion scenarios to use. Else as I wrote earlier how does Tw know I'm working directly on a bibliography file etc etc? That's pretty well much Typesetting Engine independent as are some other things. Paul On 14 June 2011 10:40, Philip TAYLOR (Webmaster, Ret'd) wrote: > > > Reinhard Kotucha wrote: > >> Even if you specify a particular engine, it's still not clear which >> type of file you want to process. ?Suppose you select "plain TeX" but >> the file contains the line "\input texinfo.tex". ?After loading this >> file, the escape character is "@" instead of "\". ?This breaks command >> completion and syntax highlighting and it's extremely difficult for an >> editor to find out what to do. >> >> The problem you reported is a good example. ?Plain TeX can more or >> less considered as a programming language, whereas LaTeX is supposed >> to be a markup language, i.e. a file format. ?One would expect then >> that it's easier to support command completion and syntax highlighting >> in LaTeX. ?This is definitely true, but Beamer re-defines standard >> LaTeX list environments. ?Hence, if you want to provide proper command >> completion and syntax highlighting, you have to evaluate the whole >> file. > > Yes, I agree that no matter which engine you select, you /may/ > have a pathological file that does not follow the normal markup > pattern for that engine, so in an ideal world you could then > switch auto-completion on the fly. ?But a default behaviour that > uses the engine to determine which set of auto-completes is > most likely to be relevant is surely not an unreasonable > behaviour, is it ? > > ** Phil. > From herbs at wideopenwest.com Tue Jun 14 02:46:04 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Mon, 13 Jun 2011 19:46:04 -0500 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> <4DF6146D.5060009@gmail.com> <4DF65CA4.1020009@Rhul.Ac.Uk> <19958.36190.619405.824796@zaphod.ms25.net> <4DF691E0.5030502@Rhul.Ac.Uk> Message-ID: On Jun 13, 2011, at 7:38 PM, Paul A Norman wrote: > Hi, > > At a pinch I wouldn't mind even a drop down type widget with checkable > boxes that lets me choose which completion scenarios to use. > > Else as I wrote earlier how does Tw know I'm working directly on a > bibliography file etc etc? > > That's pretty well much Typesetting Engine independent as are some other things. > > Paul > > > > On 14 June 2011 10:40, Philip TAYLOR (Webmaster, Ret'd) > wrote: >> >> >> Reinhard Kotucha wrote: >> >>> Even if you specify a particular engine, it's still not clear which >>> type of file you want to process. Suppose you select "plain TeX" but >>> the file contains the line "\input texinfo.tex". After loading this >>> file, the escape character is "@" instead of "\". This breaks command >>> completion and syntax highlighting and it's extremely difficult for an >>> editor to find out what to do. >>> >>> The problem you reported is a good example. Plain TeX can more or >>> less considered as a programming language, whereas LaTeX is supposed >>> to be a markup language, i.e. a file format. One would expect then >>> that it's easier to support command completion and syntax highlighting >>> in LaTeX. This is definitely true, but Beamer re-defines standard >>> LaTeX list environments. Hence, if you want to provide proper command >>> completion and syntax highlighting, you have to evaluate the whole >>> file. >> >> Yes, I agree that no matter which engine you select, you /may/ >> have a pathological file that does not follow the normal markup >> pattern for that engine, so in an ideal world you could then >> switch auto-completion on the fly. But a default behaviour that >> uses the engine to determine which set of auto-completes is >> most likely to be relevant is surely not an unreasonable >> behaviour, is it ? >> >> ** Phil. >> > Howdy, The command-completion file would have to be related to the extension of the file being edited and also the default engine being used to compile that file via the % !TEX program = xxxxx line. The other way to do it would simply be to have another ``magic line'' that defined which command completion file to use; that would probably be the easiest thing to do. E.g., % !TEX commandcompletion = xxxxx with xxxxx being latex, etc. I'd suggest that the default commandcompletion (i.e., when no line is given) is latex only because that is the most common use. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From paul.a.norman at gmail.com Tue Jun 14 03:47:40 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 14 Jun 2011 13:47:40 +1200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> <4DF6146D.5060009@gmail.com> <4DF65CA4.1020009@Rhul.Ac.Uk> <19958.36190.619405.824796@zaphod.ms25.net> <4DF691E0.5030502@Rhul.Ac.Uk> Message-ID: Hi, I was thinking that it may be necessary to allow for more than one auto-completion file at a time. People are able to write their own specialist needs and general subsets as well (even copy and paste to smaller files and do away with, or comment, tw-latex.txt if you want to reduce any perceived redundant options for your/team needs. For example, I can write completion files up as necessary macros (when QtScript is not being used for interaction on content) for any major .sty we write ourselves (or any special package used) e.g... cp:={\cappar #INS#} dp:=\doDropCap{#INS#} rH:=\ReverseHeading% No Logos, Drop Cap Paragragh, Line, or TOC entry#RET#% Use \coma for printing , in Heading or sub heading#RET# [#RET# TopHeading = #INS#text,#RET# SubHeading = ?text,#RET# subLine = false,#RET# putinToc = true#RET# ]#RET# {?double column section main story text}#RET#\begin{multicols}{\value{columns}}#RET#?#RET#\end{multicols} That is why I was thinking of a check box list populated from the configuration/completion directory. It would help reduce the number of options showing on the tab key to what is currently useful for any User. Paul On 14 June 2011 12:46, Herbert Schulz wrote: > > On Jun 13, 2011, at 7:38 PM, Paul A Norman wrote: > >> Hi, >> >> At a pinch I wouldn't mind even a drop down type widget with checkable >> boxes that lets me choose which completion scenarios to use. >> >> Else as I wrote earlier how does Tw know I'm working directly on a >> bibliography file etc etc? >> >> That's pretty well much Typesetting Engine independent as are some other things. >> >> Paul >> >> >> >> On 14 June 2011 10:40, Philip TAYLOR (Webmaster, Ret'd) >> wrote: >>> >>> >>> Reinhard Kotucha wrote: >>> >>>> Even if you specify a particular engine, it's still not clear which >>>> type of file you want to process. ?Suppose you select "plain TeX" but >>>> the file contains the line "\input texinfo.tex". ?After loading this >>>> file, the escape character is "@" instead of "\". ?This breaks command >>>> completion and syntax highlighting and it's extremely difficult for an >>>> editor to find out what to do. >>>> >>>> The problem you reported is a good example. ?Plain TeX can more or >>>> less considered as a programming language, whereas LaTeX is supposed >>>> to be a markup language, i.e. a file format. ?One would expect then >>>> that it's easier to support command completion and syntax highlighting >>>> in LaTeX. ?This is definitely true, but Beamer re-defines standard >>>> LaTeX list environments. ?Hence, if you want to provide proper command >>>> completion and syntax highlighting, you have to evaluate the whole >>>> file. >>> >>> Yes, I agree that no matter which engine you select, you /may/ >>> have a pathological file that does not follow the normal markup >>> pattern for that engine, so in an ideal world you could then >>> switch auto-completion on the fly. ?But a default behaviour that >>> uses the engine to determine which set of auto-completes is >>> most likely to be relevant is surely not an unreasonable >>> behaviour, is it ? >>> >>> ** Phil. >>> >> > > Howdy, > > The command-completion file would have to be related to the extension of the file being edited and also the default engine being used to compile that file via the > > % !TEX program = xxxxx > > line. The other way to do it would simply be to have another ``magic line'' that defined which command completion file to use; that would probably be the easiest thing to do. E.g., > > % !TEX commandcompletion = xxxxx > > with xxxxx being latex, etc. I'd suggest that the default commandcompletion (i.e., when no line is given) is latex only because that is the most common use. > > Good Luck, > > Herb Schulz > (herbs at wideopenwest dot com) > > > > > From P.Taylor at Rhul.Ac.Uk Tue Jun 14 08:54:44 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Tue, 14 Jun 2011 07:54:44 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF513D6.3050209@swing.be> <4DF51AE1.6040403@Rhul.Ac.Uk> <62FA2E86-5DB0-455E-9D61-EDA1D61FD783@gmail.com> <4DF6146D.5060009@gmail.com> <4DF65CA4.1020009@Rhul.Ac.Uk> <19958.36190.619405.824796@zaphod.ms25.net> <4DF691E0.5030502@Rhul.Ac.Uk> Message-ID: <4DF705B4.5090307@Rhul.Ac.Uk> Herbert Schulz wrote: > Howdy, > > The command-completion file would have to be related to the extension of the file being edited and also the default engine being used to compile that file via the > > % !TEX program = xxxxx > > line. The other way to do it would simply be to have another ``magic line'' that defined which command completion file to use; that would probably be the easiest thing to do. E.g., > > % !TEX commandcompletion = xxxxx > > with xxxxx being latex, etc. I'd suggest that the default commandcompletion (i.e., when no line is given) is latex only because that is the most common use. Should not the default command-completion be "no completion at all" ? Is it really safe to assume that the majority of TeXwork users want command completion enabled ? FWIW, it is (IMHO) a great shame that the default extension for LaTeX is ".tex" : if the default extension were specified in the format file, we could have had ".ltx" for LaTeX, ".ctx" for ConTeXt, and so on, whereas in the current scheme of things ".tex" is horribly overloaded. ** Phil. From st.loeffler at gmail.com Tue Jun 14 10:56:14 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 14 Jun 2011 10:56:14 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF65D53.1000207@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF60E3F.1030104@gmail.com> <4DF65D53.1000207@Rhul.Ac.Uk> Message-ID: <4DF7222E.1030708@gmail.com> Hi, On 2011-06-13 20:56, Philip TAYLOR (Webmaster, Ret'd) wrote: > Stefan L?ffler wrote: > >> By downloading r844 or later (hopefully). I just committed my patch and >> uploaded new builds. > > Thank you ! And please forgive my naivety, but when you say "download > r844 or later", are we talking about "download from TLnet", "download > from CTAN", or "download from somewhere else" ? ah, sorry. It's "download from somewhere else", namely http://code.google.com/p/texworks/downloads/list where all the Tw binaries (for Windows, anyway) are uploaded. Arguably, frequent changes only happen to "experimental" builds, but in the phase we're in right now these are (almost) as stable as the "stable" releases. TL only takes stable releases, AFAIK (and doesn't upgrade them - but then again, all Tw stable releases have been made just in time for a new TL release so far ;)). CTAN doesn't host Tw, I think (or if it does, this is maintained by someone else). > ** Phil (who recently removed all but "basic" from his "completion" > folder and now has a TeXworks that doesn't manifest the previous > odd behaviour). This is easily explainable: the basic scheme only includes stuff like greek characters, but no environments, so all the "{" business is bypassed. HTH Stefan From st.loeffler at gmail.com Tue Jun 14 10:58:28 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 14 Jun 2011 10:58:28 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF63427.3020902@swing.be> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF60E3F.1030104@gmail.com> <4DF61305.5060604@swing.be> <4DF61574.5080805@gmail.com> <4DF63427.3020902@swing.be> Message-ID: <4DF722B4.9040207@gmail.com> Hi, On 2011-06-13 18:00, Alain Delmotte wrote: > OK it works fine at the start of a line. Great! > But if I do > \def {[Tab] > > [Tab] after the { I get the completion proposals. That's how it is supposed to work. Arguably, Tab might not be the best possible shortcut in the special case that you actually do want to insert a tab character at that place, but I don't want to change this behavior out of the blue in a bugfix release. > As for the python scripts, all mine work. Thanks for testing. Regards, Stefan From st.loeffler at gmail.com Tue Jun 14 11:16:05 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 14 Jun 2011 11:16:05 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> Message-ID: <4DF726D5.4020503@gmail.com> On 2011-06-13 21:31, Charlie Sharpsteen wrote: > Allright, looks like we have a new wrinkle in that pTeX does not embed fonts: > > http://tug.org/pipermail/texworks/2011q2/004361.html > > The font in question is a CJK font, "Ryumin-Light-Identity-H". It > looks like Fontconfig chooses a more or less appropriate fallback > while the Quartz backend just iteratively peels hyphenated sections > from the font name then gives up and substitutes Helvetica. I guess fontconfig uses some more elaborate substitution routines. The one in the Quartz backend really only work if you have some garbage attached to the font name, some variant (e.g., bold-italic) is not available. > So, unless anyone has some good ideas on how to add fallback support > to the Quartz font handler, we may be back to the question of "should > we implement native mac fonts or just use Fontconfig?" FWIW, Tw and evince on Linux (both using poppler+fontconfig) show the file properly, whereas Adobe Acrobat complains about missing language supports and only displays dots... What font is substituted by Fontconfig, anyway? Is there any obvious relation to the requested font? > The only downside that I have found with Fontconfig is that users > won't see non-embedded fonts unless their copy of OS X has X11 > installed. X11 is installed by default in OS X 10.5.x and 10.6.x, but > could be missing if the user customized their installation and > optimized for size. Not sure what the situation is for 10.7, but I > guess we will find out next month. Could be take a similar approach to the one on Windows? There, poppler is patched such that it looks for fonts in a subdirectory alongside the main binary. That way, important base fonts (all, or just a subset as for Windows which doesn't come with a suitable ZapfDingbats) can be provided by the TeXworks application. To quote the PDF standard: "these [14 base] fonts, or their font metrics and suitable substitution fonts, must be available to the consumer application." I don't know how this fits into the bundling-of-apps scheme, though. -Stefan From st.loeffler at gmail.com Tue Jun 14 11:25:17 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Tue, 14 Jun 2011 11:25:17 +0200 Subject: [texworks] Mac issues In-Reply-To: References: Message-ID: <4DF728FD.4020004@gmail.com> Hi, On 2011-06-13 21:59, sigmundv at gmail.com wrote: > Why do I see so many discussions on Mac specific stuff on this list? > There is hardly anything Windows or Linux specific discussed. Why is this? I'd like to think because things just work there ;). > Is TeXworks used more on Mac OS X than on Windows or Linux? Or is Mac > OS X just so much different? These peaks in activity have come and gone in the past. We had lots of "Building on Windows" discussions, and we had lots of "Scripting" discussions, and usually the one or other post wondering if Tw "focuses on Windows" or "is turning into a scripting engine". Personally, I think this high activity results from a combination of two things: first of all, above-average activity from a few people, and secondly a complex/difficult to decide issue. In this particular case: Tw has been started on the Mac (I think), but with Jonathan's other obligations piling up, there haven't been Mac builds in a long time. Consequently, development has focused elsewhere (i.e., Mac-specific issues were never addressed or even discovered). This of course was a bad thing, as Tw aims to be cross-platform compatible. Now, Charlie has thankfully stepped up and worked hard to produce an easy and reliable way to produce Mac builds. Of course, several rough edges have turned up as a consequence, and therefore a lot of posts on this list have dealt with the Mac in the recent past. But no worries, once everything works again as it should on the Mac, the number of Mac-specific posts will become smaller again. In the meantime, do you have anything non-Mac-specific to discuss? :) -Stefan From t34www at googlemail.com Tue Jun 14 11:29:27 2011 From: t34www at googlemail.com (T T) Date: Tue, 14 Jun 2011 10:29:27 +0100 Subject: [texworks] where does python27.dll come from? In-Reply-To: <4DF4C7CF.7020208@gmail.com> References: <4DF064B4.2070305@gmail.com> <4DF1CA43.8030502@swing.be> <4DF4C7CF.7020208@gmail.com> Message-ID: On 12 June 2011 15:06, Stefan L?ffler wrote: > > Thanks for testing and reporting. As pointed out in the thread, the Lib > folder is indeed still necessary (it seems it picked up a different Lib > folder on my machine - one shouldn't mix different python installs ;)). > Anyway, using the one from the older releases is not ideal, as they were > taken from the MSVC build. Therefore, they might depend on libraries > etc. and might even be incompatible with the built-in mingw library. Are you sure? I thought all those .pyc files under Lib are platform independent, which seems to be even stated in the python docs: http://docs.python.org/tutorial/modules.html#compiled-python-files (I ask because in TeX Live these files are currently in the common part of the package, not in the platform specific one.) Cheers, Tomek From P.Taylor at Rhul.Ac.Uk Tue Jun 14 12:33:57 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Tue, 14 Jun 2011 11:33:57 +0100 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF7222E.1030708@gmail.com> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF60E3F.1030104@gmail.com> <4DF65D53.1000207@Rhul.Ac.Uk> <4DF7222E.1030708@gmail.com> Message-ID: <4DF73915.10407@Rhul.Ac.Uk> Stefan L?ffler wrote: > ah, sorry. It's "download from somewhere else", namely > http://code.google.com/p/texworks/downloads/list where all the Tw > binaries (for Windows, anyway) are uploaded. Arguably, frequent changes > only happen to "experimental" builds, but in the phase we're in right > now these are (almost) as stable as the "stable" releases. TL only takes > stable releases, AFAIK (and doesn't upgrade them - but then again, all > Tw stable releases have been made just in time for a new TL release so > far ;)). CTAN doesn't host Tw, I think (or if it does, this is > maintained by someone else). OK, understood. Unfortunately now a supplementary -- I have downloaded TeXworks-w32-0.5-r844.zip and unzipped it using Filzip, but the paths in it don't match a TeX Live 2010 configuration. Under TL 2010, the binaries (such as TeXworks.exe) would be found in .../bin/win32/, but there are no subdirectories under .../bin/win32/ so I do not know where to place the four directories found in the ZIP file : "fonts", "Lib", "poppler-data" and "texworks-help", nor am I sure if "python27.dll" should also go in .../bin/win32/ Obviously this is a generic packaging, not one tailored for TeX Live, but I wonder where the elements other than the executable image are intended to go ? The "README.txt" gives generic advice ("Just extract the contents of the Zip file wherever you want and then run the extracted TeXworks.exe.") but really I'd like to put them where TeX Live would have put them during a normal install. >> ** Phil (who recently removed all but "basic" from his "completion" >> folder and now has a TeXworks that doesn't manifest the previous >> odd behaviour). > > This is easily explainable: the basic scheme only includes stuff like > greek characters, but no environments, so all the "{" business is bypassed. Yes, I was really saying how happy I was :-) (Until I looked into the "basic" set, and saw that if I used a tab after certain control sequences they would mysteriously mutate into something apparently unrelated, at which point I deleted the basic set too !). From herbs at wideopenwest.com Tue Jun 14 14:05:57 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Tue, 14 Jun 2011 07:05:57 -0500 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF4C003.7020908@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> Message-ID: <3257E256-F51B-440C-ABC7-896DD098BB44@wideopenwest.com> On Jun 12, 2011, at 8:32 AM, Philip TAYLOR (Webmaster, Ret'd) wrote: > Dear fellow TeXworkers -- > > I am a strong believe in the importance of layout, and > would never trust a mere editor (not even TeXworks) to > perform layout for me. So why is it that when I type > > > \def \foo > { > > and then press at the start of the blank line > below the "{" (which is itself indented with one tab), > TeXworks insists in entering > > alertenv}<> > > and putting the cursor between the angle-brackets ? > > I have no idea what "alertenv" is, nor do I want > it inserted; how may this be avoided, please ? > > Philip Taylor Howdy, Getting back to this original question... note that the TAB is pressed after a newline. Shouldn't a newline be a left hand terminator for a search term and since it's empty (i.e., nothing or white space) before the terminator a TAB should be entered? Good Luck, Herb Schulz (herbs at wideopenwest dot com) From paul.a.norman at gmail.com Wed Jun 15 01:10:24 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 15 Jun 2011 11:10:24 +1200 Subject: [texworks] Auto-completion - Document Jumps Message-ID: Hi, Was wondering if multicols is useful enough to get into the default LaTeX list somewhere? \begin{multicols}{#INS#}#RET#?#RET#\end{multicols}#RET# Of course that would be in present format ... {multicols}{#INS#}#RET#?#RET#\end{multicols}#RET# Also through the recent discussion I realised that there is a useful by product to all this. Didn't spot it in the manual during a quick look so here goes -- Aside from auto-completion, any number of the following can be sprinkled through a document ... %? %: if you want a strong Tags entry? ... and they provide a convenient keyboard jump to location using Crtl- (forwards), and SHIFT-Crtl- (backwards) -- useful when editing in one place and then needing to mark and go elsewhere and pick something up and go back etc etc On Windows (Xp at least) with Number Lock on using the Numeric Keypad 0149 Should get you a bullet (for more see http://www.allgraphicdesign.com/graphicsblog/2008/02/13/how-to-make-keyboard-bullets-stars-hearts-french-accents-copyright-symbols-more-with-the-alt-key/ ) MacOS I think - Option+8 Use the Keycaps program to check where various characters are on your keyboard? Linux varies? http://en.wikipedia.org/wiki/Bullet_(typography) Paul P.S. a simple script for inserting bullets if keyboard is too difficult // TeXworksScript // Title: Make Bullet // Description: Inserts a bullet for autocompletion // Author: Paul Norman // Version: 0.1 // Date: 2011-03-05 // Script-Type: standalone // Context: TeXDocument // Shortcut: Alt+M, Alt+B TW.target.insertText("\u2022"); From hospes.primus at verizon.net Wed Jun 15 02:47:32 2011 From: hospes.primus at verizon.net (David J. Perry) Date: Tue, 14 Jun 2011 20:47:32 -0400 Subject: [texworks] Auto-completion - Document Jumps In-Reply-To: References: Message-ID: Paul, This is a very useful trick! I often need to mark spots in a long document and go back and forth. Thanks. David ----- Original Message ----- From: "Paul A Norman" To: "Discuss the TeXworks front end." Sent: Tuesday, June 14, 2011 7:10 PM Subject: [texworks] Auto-completion - Document Jumps > Aside from auto-completion, any number of the following can be > sprinkled through a document ... > > %? > %: if you want a strong Tags entry? > > ... and they provide a convenient keyboard jump to location using > > Crtl- (forwards), > and SHIFT-Crtl- (backwards) > > -- useful when editing in one place and then needing to mark and go > elsewhere and pick something up and go back etc etc > > On Windows (Xp at least) with Number Lock on using the Numeric Keypad > 0149 > > Should get you a bullet (for more see > http://www.allgraphicdesign.com/graphicsblog/2008/02/13/how-to-make-keyboard-bullets-stars-hearts-french-accents-copyright-symbols-more-with-the-alt-key/ > ) > > MacOS I think - Option+8 > Use the Keycaps program to check where various characters are on your > keyboard? > > Linux varies? > http://en.wikipedia.org/wiki/Bullet_(typography) > > Paul > > P.S. a simple script for inserting bullets if keyboard is too difficult > > // TeXworksScript > // Title: Make Bullet > // Description: Inserts a bullet for autocompletion > // Author: Paul Norman > // Version: 0.1 > // Date: 2011-03-05 > // Script-Type: standalone > // Context: TeXDocument > // Shortcut: Alt+M, Alt+B > > TW.target.insertText("\u2022"); > From paul.a.norman at gmail.com Wed Jun 15 04:25:30 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 15 Jun 2011 14:25:30 +1200 Subject: [texworks] Auto-completion - Document Jumps In-Reply-To: References: Message-ID: David, Although there are always rough edges that surface in any project, and I don't want to overstate it, but the clear careful thinking that Jonathan and the others had at the very beginning of this project often continues to come out and make things like this possible. May sound funny, but I've often noticed that there is a sort of symmetry in careful project design policy, where one instance of a thoughtful approach to something, often lends itself to other at first unrecognised needs latter. When things are done knowledgeably and with wisdom and understanding, it generates a kind of conceptual depth that reaps other rewards. Haste and expediency can undo all of that! Sort of a practical/functional side to -- patterns in design | designs in pattern May be without commercial pressures for production geared around market revenues, OpenSource, if it does not invent its own needless pressures, can eventually go further than some commercial approaches can take us? :) Paul On 15 June 2011 12:47, David J. Perry wrote: > Paul, > > This is a very useful trick! ?I often need to mark spots in a long document > and go back and forth. ?Thanks. > > David > > ----- Original Message ----- From: "Paul A Norman" > To: "Discuss the TeXworks front end." > Sent: Tuesday, June 14, 2011 7:10 PM > Subject: [texworks] Auto-completion - Document Jumps > > >> Aside from auto-completion, any number of the following can be >> sprinkled through a document ... >> >> %? >> %: ? if you want a strong Tags entry? >> >> ... and they provide a convenient keyboard jump to location using >> >> Crtl- (forwards), >> and SHIFT-Crtl- (backwards) >> >> -- useful when editing in one place and then needing to mark and go >> elsewhere ?and pick something up and go back etc etc >> >> On Windows (Xp at least) with Number Lock on using the Numeric Keypad >> 0149 >> >> Should get you a bullet (for more see >> >> http://www.allgraphicdesign.com/graphicsblog/2008/02/13/how-to-make-keyboard-bullets-stars-hearts-french-accents-copyright-symbols-more-with-the-alt-key/ >> ) >> >> MacOS I think - ?Option+8 >> Use the Keycaps program to check where various characters are on your >> keyboard? >> >> Linux varies? >> http://en.wikipedia.org/wiki/Bullet_(typography) >> >> Paul >> >> P.S. a simple script for inserting bullets if keyboard is too difficult >> >> // TeXworksScript >> // Title: ?Make Bullet >> // Description: Inserts a bullet for autocompletion >> // Author: ?Paul Norman >> // Version: 0.1 >> // Date: 2011-03-05 >> // Script-Type: standalone >> // Context: TeXDocument >> // Shortcut: Alt+M, Alt+B >> >> TW.target.insertText("\u2022"); >> > > From esperanto at swing.be Wed Jun 15 08:44:35 2011 From: esperanto at swing.be (Alain Delmotte) Date: Wed, 15 Jun 2011 08:44:35 +0200 Subject: [texworks] Auto-completion - Document Jumps In-Reply-To: References: Message-ID: <4DF854D3.6060907@swing.be> Hi Paul, This is a .js script, how to make it Python? ------------------------ # TeXworksScript # Title: Make Bullet # Description: Inserts a bullet for autocompletion # Author: Paul Norman # Version: 0.1 # Date: 2011-03-05 # Script-Type: standalone # Context: TeXDocument # Shortcut: Alt+M, Alt+B TW.target.insertText("\u2022") ------------------------ doesn't work for me. Thanks, Alain Le 15/06/2011 01:10, Paul A Norman a ?crit : > P.S. a simple script for inserting bullets if keyboard is too difficult > > // TeXworksScript > // Title: Make Bullet > // Description: Inserts a bullet for autocompletion > // Author: Paul Norman > // Version: 0.1 > // Date: 2011-03-05 > // Script-Type: standalone > // Context: TeXDocument > // Shortcut: Alt+M, Alt+B > > TW.target.insertText("\u2022"); > > From paul.a.norman at gmail.com Wed Jun 15 09:26:41 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 15 Jun 2011 19:26:41 +1200 Subject: [texworks] Auto-completion - Document Jumps In-Reply-To: <4DF854D3.6060907@swing.be> References: <4DF854D3.6060907@swing.be> Message-ID: Dear Alain, Good to see you on the list lately - been back in Africa at all? Python is not yet a strength of mine--on a long to do list, I really like the look of it :) Head looks great... # TeXworksScript # Title: Make Bullet # Description: Inserts a bullet for autocompletion # Author: Paul Norman # Version: 0.1 # Date: 2011-06-15 # Script-Type: standalone # Context: TeXDocument # Shortcut: Alt+M, Alt+B TW.target.insertText(u"\u2022") Indentation and spacing is everything in Python from what I recall. This works, note the u in-front of the quote mark for Python encoding needs here. Here is a link to a script for writing new scripts :) helps get the head consistently in order. http://code.google.com/p/texworks/issues/detail?id=261#c41 re the QtScript version ... Have you got Alt+M, Alt+B assigned to any other Script at all? Does the Script appear in Script manager? Or on the Script menu? .js is one of the standard QtScript extensions. Or did I misunderstand and you just want to do it in python anyway? paul On 15 June 2011 18:44, Alain Delmotte wrote: > Hi Paul, > > This is a .js script, how to make it Python? > > ------------------------ > # TeXworksScript > # Title: ?Make Bullet > # Description: Inserts a bullet for autocompletion > # Author: ?Paul Norman > # Version: 0.1 > # Date: 2011-03-05 > # Script-Type: standalone > # Context: TeXDocument > # Shortcut: Alt+M, Alt+B > The header look right Python is not my strength in scripting but ... For python try this, note the leading u TW.target.insertText(u"\u2022") or perhaps mybullet = str(u"\u2022") TW.target.insertText(mybullet) > ------------------------ > doesn't work for me. > > Thanks, > > Alain > > Le 15/06/2011 01:10, Paul A Norman a ?crit : >> >> P.S. a simple script for inserting bullets if keyboard is too difficult >> >> // TeXworksScript >> // Title: ?Make Bullet >> // Description: Inserts a bullet for autocompletion >> // Author: ?Paul Norman >> // Version: 0.1 >> // Date: 2011-03-05 >> // Script-Type: standalone >> // Context: TeXDocument >> // Shortcut: Alt+M, Alt+B >> >> ?TW.target.insertText("\u2022"); >> >> > > > From paul.a.norman at gmail.com Wed Jun 15 09:34:07 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 15 Jun 2011 19:34:07 +1200 Subject: [texworks] Auto-completion - Document Jumps In-Reply-To: References: <4DF854D3.6060907@swing.be> Message-ID: Appologies please ignore tail of last message below your quote Alain. Paul On 15 June 2011 19:26, Paul A Norman wrote: > Dear Alain, > > Good to see you on the list lately - been back in Africa at all? > > Python is not yet a strength of mine--on a long to do list, I really > like the look of it :) > > Head looks great... > > # TeXworksScript > # Title: ?Make Bullet > # Description: Inserts a bullet for autocompletion > # Author: ?Paul Norman > # Version: 0.1 > # Date: 2011-06-15 > # Script-Type: standalone > # Context: TeXDocument > # Shortcut: Alt+M, Alt+B > > TW.target.insertText(u"\u2022") > > Indentation and spacing is everything in Python from what I recall. > This works, note the u in-front of the quote mark for Python encoding > needs here. > > Here is a link to a script for writing new scripts :) helps get the > head consistently in order. > > http://code.google.com/p/texworks/issues/detail?id=261#c41 > > re the QtScript version ... > > Have you got Alt+M, Alt+B ?assigned to any other Script at all? > > Does the Script appear in Script manager? Or on the Script menu? > > .js is ?one of the standard QtScript ?extensions. > > Or did I misunderstand and you just want to do it in python anyway? > > paul > > > On 15 June 2011 18:44, Alain Delmotte wrote: >> Hi Paul, >> >> This is a .js script, how to make it Python? >> >> ------------------------ >> # TeXworksScript >> # Title: ?Make Bullet >> # Description: Inserts a bullet for autocompletion >> # Author: ?Paul Norman >> # Version: 0.1 >> # Date: 2011-03-05 >> # Script-Type: standalone >> # Context: TeXDocument >> # Shortcut: Alt+M, Alt+B >> > > The header look right > > Python is not my strength in scripting but ... > > For python try this, note the leading u > > ?TW.target.insertText(u"\u2022") > > or perhaps > > ?mybullet = str(u"\u2022") > > ?TW.target.insertText(mybullet) > > > > >> ------------------------ >> doesn't work for me. >> >> Thanks, >> >> Alain >> >> Le 15/06/2011 01:10, Paul A Norman a ?crit : >>> >>> P.S. a simple script for inserting bullets if keyboard is too difficult >>> >>> // TeXworksScript >>> // Title: ?Make Bullet >>> // Description: Inserts a bullet for autocompletion >>> // Author: ?Paul Norman >>> // Version: 0.1 >>> // Date: 2011-03-05 >>> // Script-Type: standalone >>> // Context: TeXDocument >>> // Shortcut: Alt+M, Alt+B >>> >>> ?TW.target.insertText("\u2022"); >>> >>> >> >> >> > From esperanto at swing.be Wed Jun 15 11:11:45 2011 From: esperanto at swing.be (Alain Delmotte) Date: Wed, 15 Jun 2011 11:11:45 +0200 Subject: [texworks] Auto-completion - Document Jumps In-Reply-To: References: <4DF854D3.6060907@swing.be> Message-ID: <4DF87751.5000904@swing.be> Dear Paul, Thanks! It works (I was not expecting anything else!) And yes, I want to program in Python. The .js did work of course! Yes I was in Kinshasa the seond half of April. Alain Le 15/06/2011 09:26, Paul A Norman a ?crit : > Dear Alain, > > Good to see you on the list lately - been back in Africa at all? > > Python is not yet a strength of mine--on a long to do list, I really > like the look of it :) > > Head looks great... > > # TeXworksScript > # Title: Make Bullet > # Description: Inserts a bullet for autocompletion > # Author: Paul Norman > # Version: 0.1 > # Date: 2011-06-15 > # Script-Type: standalone > # Context: TeXDocument > # Shortcut: Alt+M, Alt+B > > TW.target.insertText(u"\u2022") > > Indentation and spacing is everything in Python from what I recall. > This works, note the u in-front of the quote mark for Python encoding > needs here. > > Here is a link to a script for writing new scripts :) helps get the > head consistently in order. > > http://code.google.com/p/texworks/issues/detail?id=261#c41 > > re the QtScript version ... > > Have you got Alt+M, Alt+B assigned to any other Script at all? > > Does the Script appear in Script manager? Or on the Script menu? > > .js is one of the standard QtScript extensions. > > Or did I misunderstand and you just want to do it in python anyway? > > paul > > > On 15 June 2011 18:44, Alain Delmotte wrote: >> Hi Paul, >> >> This is a .js script, how to make it Python? >> >> ------------------------ >> # TeXworksScript >> # Title: Make Bullet >> # Description: Inserts a bullet for autocompletion >> # Author: Paul Norman >> # Version: 0.1 >> # Date: 2011-03-05 >> # Script-Type: standalone >> # Context: TeXDocument >> # Shortcut: Alt+M, Alt+B >> > > The header look right > > Python is not my strength in scripting but ... > > For python try this, note the leading u > > TW.target.insertText(u"\u2022") > > or perhaps > > mybullet = str(u"\u2022") > > TW.target.insertText(mybullet) > > > > >> ------------------------ >> doesn't work for me. >> >> Thanks, >> >> Alain >> >> Le 15/06/2011 01:10, Paul A Norman a ?crit : >>> >>> P.S. a simple script for inserting bullets if keyboard is too difficult >>> >>> // TeXworksScript >>> // Title: Make Bullet >>> // Description: Inserts a bullet for autocompletion >>> // Author: Paul Norman >>> // Version: 0.1 >>> // Date: 2011-03-05 >>> // Script-Type: standalone >>> // Context: TeXDocument >>> // Shortcut: Alt+M, Alt+B >>> >>> TW.target.insertText("\u2022"); >>> >>> >> >> >> > > From paul.a.norman at gmail.com Wed Jun 15 11:46:36 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 15 Jun 2011 21:46:36 +1200 Subject: [texworks] Auto-completion - Document Jumps In-Reply-To: <4DF87751.5000904@swing.be> References: <4DF854D3.6060907@swing.be> <4DF87751.5000904@swing.be> Message-ID: On 15 June 2011 21:11, Alain Delmotte wrote: > Dear Paul, > > Thanks! It works (I was not expecting anything else!) > And yes, I want to program in Python. The .js did work of course! > tiu estas bona ?i estis mia plezuro > Yes I was in Kinshasa the seond half of April. > > Alain > > Le 15/06/2011 09:26, Paul A Norman a ?crit : >> >> Dear Alain, >> >> Good to see you on the list lately - been back in Africa at all? >> >> Python is not yet a strength of mine--on a long to do list, I really >> like the look of it :) >> >> Head looks great... >> >> # TeXworksScript >> # Title: ?Make Bullet >> # Description: Inserts a bullet for autocompletion >> # Author: ?Paul Norman >> # Version: 0.1 >> # Date: 2011-06-15 >> # Script-Type: standalone >> # Context: TeXDocument >> # Shortcut: Alt+M, Alt+B >> >> TW.target.insertText(u"\u2022") >> >> Indentation and spacing is everything in Python from what I recall. >> This works, note the u in-front of the quote mark for Python encoding >> needs here. >> >> Here is a link to a script for writing new scripts :) helps get the >> head consistently in order. >> >> http://code.google.com/p/texworks/issues/detail?id=261#c41 >> >> re the QtScript version ... >> >> Have you got Alt+M, Alt+B ?assigned to any other Script at all? >> >> Does the Script appear in Script manager? Or on the Script menu? >> >> .js is ?one of the standard QtScript ?extensions. >> >> Or did I misunderstand and you just want to do it in python anyway? >> >> paul >> >> >> On 15 June 2011 18:44, Alain Delmotte ?wrote: >>> >>> Hi Paul, >>> >>> This is a .js script, how to make it Python? >>> >>> ------------------------ >>> # TeXworksScript >>> # Title: ?Make Bullet >>> # Description: Inserts a bullet for autocompletion >>> # Author: ?Paul Norman >>> # Version: 0.1 >>> # Date: 2011-03-05 >>> # Script-Type: standalone >>> # Context: TeXDocument >>> # Shortcut: Alt+M, Alt+B >>> >> >> The header look right >> >> Python is not my strength in scripting but ... >> >> For python try this, note the leading u >> >> ?TW.target.insertText(u"\u2022") >> >> or perhaps >> >> ? mybullet = str(u"\u2022") >> >> ?TW.target.insertText(mybullet) >> >> >> >> >>> ------------------------ >>> doesn't work for me. >>> >>> Thanks, >>> >>> Alain >>> >>> Le 15/06/2011 01:10, Paul A Norman a ?crit : >>>> >>>> P.S. a simple script for inserting bullets if keyboard is too difficult >>>> >>>> // TeXworksScript >>>> // Title: ?Make Bullet >>>> // Description: Inserts a bullet for autocompletion >>>> // Author: ?Paul Norman >>>> // Version: 0.1 >>>> // Date: 2011-03-05 >>>> // Script-Type: standalone >>>> // Context: TeXDocument >>>> // Shortcut: Alt+M, Alt+B >>>> >>>> ?TW.target.insertText("\u2022"); >>>> >>>> >>> >>> >>> >> >> > > > From esperanto at swing.be Wed Jun 15 18:23:35 2011 From: esperanto at swing.be (Alain Delmotte) Date: Wed, 15 Jun 2011 18:23:35 +0200 Subject: [texworks] Auto-completion - Document Jumps In-Reply-To: References: <4DF854D3.6060907@swing.be> <4DF87751.5000904@swing.be> Message-ID: <4DF8DC87.3080409@swing.be> Hei! Do you speak Esperanto? I was in Kinshasa for a conference and a crash course of Esperanto. They like very much the langage. Regards, Alain Le 15/06/2011 11:46, Paul A Norman a ?crit : > On 15 June 2011 21:11, Alain Delmotte wrote: >> Dear Paul, >> >> Thanks! It works (I was not expecting anything else!) >> And yes, I want to program in Python. The .js did work of course! >> > tiu estas bona ?i estis mia plezuro > >> Yes I was in Kinshasa the seond half of April. >> >> Alain >> >> Le 15/06/2011 09:26, Paul A Norman a ?crit : >>> >>> Dear Alain, >>> >>> Good to see you on the list lately - been back in Africa at all? >>> >>> Python is not yet a strength of mine--on a long to do list, I really >>> like the look of it :) >>> >>> Head looks great... >>> >>> # TeXworksScript >>> # Title: Make Bullet >>> # Description: Inserts a bullet for autocompletion >>> # Author: Paul Norman >>> # Version: 0.1 >>> # Date: 2011-06-15 >>> # Script-Type: standalone >>> # Context: TeXDocument >>> # Shortcut: Alt+M, Alt+B >>> >>> TW.target.insertText(u"\u2022") >>> >>> Indentation and spacing is everything in Python from what I recall. >>> This works, note the u in-front of the quote mark for Python encoding >>> needs here. >>> >>> Here is a link to a script for writing new scripts :) helps get the >>> head consistently in order. >>> >>> http://code.google.com/p/texworks/issues/detail?id=261#c41 >>> >>> re the QtScript version ... >>> >>> Have you got Alt+M, Alt+B assigned to any other Script at all? >>> >>> Does the Script appear in Script manager? Or on the Script menu? >>> >>> .js is one of the standard QtScript extensions. >>> >>> Or did I misunderstand and you just want to do it in python anyway? >>> >>> paul >>> >>> >>> On 15 June 2011 18:44, Alain Delmotte wrote: >>>> >>>> Hi Paul, >>>> >>>> This is a .js script, how to make it Python? >>>> >>>> ------------------------ >>>> # TeXworksScript >>>> # Title: Make Bullet >>>> # Description: Inserts a bullet for autocompletion >>>> # Author: Paul Norman >>>> # Version: 0.1 >>>> # Date: 2011-03-05 >>>> # Script-Type: standalone >>>> # Context: TeXDocument >>>> # Shortcut: Alt+M, Alt+B >>>> >>> >>> The header look right >>> >>> Python is not my strength in scripting but ... >>> >>> For python try this, note the leading u >>> >>> TW.target.insertText(u"\u2022") >>> >>> or perhaps >>> >>> mybullet = str(u"\u2022") >>> >>> TW.target.insertText(mybullet) >>> >>> >>> >>> >>>> ------------------------ >>>> doesn't work for me. >>>> >>>> Thanks, >>>> >>>> Alain >>>> >>>> Le 15/06/2011 01:10, Paul A Norman a ?crit : >>>>> >>>>> P.S. a simple script for inserting bullets if keyboard is too difficult >>>>> >>>>> // TeXworksScript >>>>> // Title: Make Bullet >>>>> // Description: Inserts a bullet for autocompletion >>>>> // Author: Paul Norman >>>>> // Version: 0.1 >>>>> // Date: 2011-03-05 >>>>> // Script-Type: standalone >>>>> // Context: TeXDocument >>>>> // Shortcut: Alt+M, Alt+B >>>>> >>>>> TW.target.insertText("\u2022"); >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> >> > > From paul.a.norman at gmail.com Wed Jun 15 23:44:00 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 16 Jun 2011 09:44:00 +1200 Subject: [texworks] Auto-completion - Document Jumps In-Reply-To: <4DF8DC87.3080409@swing.be> References: <4DF854D3.6060907@swing.be> <4DF87751.5000904@swing.be> <4DF8DC87.3080409@swing.be> Message-ID: On 16 June 2011 04:23, Alain Delmotte wrote: > Hei! > > Do you speak Esperanto? No just always been fascinated by Latin derived/connected downstream languages > I was in Kinshasa for a conference and a crash course of Esperanto. They > like very much the langage. > > Regards, > > Alain > Le 15/06/2011 11:46, Paul A Norman a ?crit : >> >> On 15 June 2011 21:11, Alain Delmotte ?wrote: >>> >>> Dear Paul, >>> >>> Thanks! It works (I was not expecting anything else!) >>> And yes, I want to program in Python. The .js did work of course! >>> >> ?tiu estas bona ?i estis mia plezuro >> >>> Yes I was in Kinshasa the seond half of April. >>> >>> Alain >>> >>> Le 15/06/2011 09:26, Paul A Norman a ?crit : >>>> >>>> Dear Alain, >>>> >>>> Good to see you on the list lately - been back in Africa at all? >>>> >>>> Python is not yet a strength of mine--on a long to do list, I really >>>> like the look of it :) >>>> >>>> Head looks great... >>>> >>>> # TeXworksScript >>>> # Title: ?Make Bullet >>>> # Description: Inserts a bullet for autocompletion >>>> # Author: ?Paul Norman >>>> # Version: 0.1 >>>> # Date: 2011-06-15 >>>> # Script-Type: standalone >>>> # Context: TeXDocument >>>> # Shortcut: Alt+M, Alt+B >>>> >>>> TW.target.insertText(u"\u2022") >>>> >>>> Indentation and spacing is everything in Python from what I recall. >>>> This works, note the u in-front of the quote mark for Python encoding >>>> needs here. >>>> >>>> Here is a link to a script for writing new scripts :) helps get the >>>> head consistently in order. >>>> >>>> http://code.google.com/p/texworks/issues/detail?id=261#c41 >>>> >>>> re the QtScript version ... >>>> >>>> Have you got Alt+M, Alt+B ?assigned to any other Script at all? >>>> >>>> Does the Script appear in Script manager? Or on the Script menu? >>>> >>>> .js is ?one of the standard QtScript ?extensions. >>>> >>>> Or did I misunderstand and you just want to do it in python anyway? >>>> >>>> paul >>>> >>>> >>>> On 15 June 2011 18:44, Alain Delmotte ? ?wrote: >>>>> >>>>> Hi Paul, >>>>> >>>>> This is a .js script, how to make it Python? >>>>> >>>>> ------------------------ >>>>> # TeXworksScript >>>>> # Title: ?Make Bullet >>>>> # Description: Inserts a bullet for autocompletion >>>>> # Author: ?Paul Norman >>>>> # Version: 0.1 >>>>> # Date: 2011-03-05 >>>>> # Script-Type: standalone >>>>> # Context: TeXDocument >>>>> # Shortcut: Alt+M, Alt+B >>>>> >>>> >>>> The header look right >>>> >>>> Python is not my strength in scripting but ... >>>> >>>> For python try this, note the leading u >>>> >>>> ?TW.target.insertText(u"\u2022") >>>> >>>> or perhaps >>>> >>>> ? mybullet = str(u"\u2022") >>>> >>>> ?TW.target.insertText(mybullet) >>>> >>>> >>>> >>>> >>>>> ------------------------ >>>>> doesn't work for me. >>>>> >>>>> Thanks, >>>>> >>>>> Alain >>>>> >>>>> Le 15/06/2011 01:10, Paul A Norman a ?crit : >>>>>> >>>>>> P.S. a simple script for inserting bullets if keyboard is too >>>>>> difficult >>>>>> >>>>>> // TeXworksScript >>>>>> // Title: ?Make Bullet >>>>>> // Description: Inserts a bullet for autocompletion >>>>>> // Author: ?Paul Norman >>>>>> // Version: 0.1 >>>>>> // Date: 2011-03-05 >>>>>> // Script-Type: standalone >>>>>> // Context: TeXDocument >>>>>> // Shortcut: Alt+M, Alt+B >>>>>> >>>>>> ?TW.target.insertText("\u2022"); >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> > > > From paul.a.norman at gmail.com Sat Jun 18 09:00:13 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Sat, 18 Jun 2011 19:00:13 +1200 Subject: [texworks] SCRIPTING: TW.deleteLate() Message-ID: Hi, Should TW.deleteLater() be callled on Dialogues once they are completely finished? i.e. var convertImage = TW.createUI("blah.blah/xxx.ui); var ans = convertImage.exec(); TW.deleteLater(convertImage) ; I have had some memory issues that seem to have been solved by this. Is that the right way to handle this? Anything else that TW.deleteLater() should be used for at all please? Paul From st.loeffler at gmail.com Sun Jun 19 10:19:27 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 19 Jun 2011 10:19:27 +0200 Subject: [texworks] SCRIPTING: TW.deleteLate() In-Reply-To: References: Message-ID: <4DFDB10F.1040909@gmail.com> Hi, On 2011-06-18 09:00, Paul A Norman wrote: > Should TW.deleteLater() be callled on Dialogues once they are > completely finished? The short answer is: yes. > i.e. > > var convertImage = TW.createUI("blah.blah/xxx.ui); > > var ans = convertImage.exec(); > > TW.deleteLater(convertImage) ; > > > I have had some memory issues that seem to have been solved by this. > Is that the right way to handle this? The longer answer is a little more complicated. Everything that "creates" a pointer (in sloppy C++ terms) allocates memory for that. This remains allocated until the pointer is "destroyed" again. This can happen automatically by a number of mechanisms, but not for these dialogs. In particular, the dialog is not tied to a particular invocation of a script (i.e., it's not destroyed automatically when the script ends) to allow reusing it (and possibly its data). Ultimately, it all comes down to what is often referred to as "ownership": the owner is responsible for destroying a pointer, whereas everyone else has to be aware that their copy of the pointer may be invalidated at any time. For the sake of completeness: if you specify a parent (e.g., TW.createUI("file.ui", TW.target)), then the dialog will be destroyed when TW.target is destroyed (if it still exists by then). Usually, this won't help you much, though, as the script creating the dialog could be called hundreds of times before TW.target is destroyed. > Anything else that TW.deleteLater() should be used for at all please? Basically, anything that creates a pointer for the script and returns it is a good candidate for deleteLater(). So from quickly browsing through TWScriptAPI.h/.cpp, progressDialog will need a deleteLater() as well. HTH Stefan From site4000 at free.fr Mon Jun 20 00:02:33 2011 From: site4000 at free.fr (site4000 at free.fr) Date: Mon, 20 Jun 2011 00:02:33 +0200 Subject: [texworks] Problem with TW viewer : asymptote and layers Message-ID: <4DFE71F9.3070608@free.fr> Hello, I use Windows Seven 64 bits, TL2010 up to date with TLContrib and run TeXworks 0.4.0 (r.759). I got the following Asymptote code here : http://asymptote.sourceforge.net/gallery/spectrum.asy Here it is : import graph; usepackage("ocg"); settings.tex="pdflatex"; // Dan Bruton algorithm pen nm2rgb(real wl, real gamma=0.8, bool intensity=true) { triple rgb; if(wl>= 380&& wl<= 440) {rgb=((440-wl)/60,0,1);} if(wl> 440&& wl<= 490) {rgb=(0,(wl-440)/50,1);} if(wl> 490&& wl<= 510) {rgb=(0,1,(510-wl)/20);} if(wl> 510&& wl<= 580) {rgb=((wl-510)/70,1,0);} if(wl> 580&& wl<= 645) {rgb=(1,(645-wl)/65,0);} if(wl> 645&& wl<= 780) {rgb=(1,0,0);} real Intensity=1; if(intensity) { if(wl>= 700) {Intensity=0.3+0.7*(780-wl)/80;} else if(wl<= 420) {Intensity=0.3+0.7*(wl-380)/40;} } return rgb((Intensity*rgb.x)**gamma,(Intensity*rgb.y)**gamma, (Intensity*rgb.z)**gamma); } real width=1; real height=50; begin("spectrum"); for(real i=380 ; i<= 780 ; i += width) { draw((i,0)--(i,height),width+nm2rgb(wl=i,false)+squarecap); } begin("Extinction",false); // nested for(real i=380 ; i<= 780 ; i += width) { draw((i,0)--(i,height),width+nm2rgb(wl=i,true)+squarecap); } end(); end(); begin("Wavelength"); xaxis(scale(0.5)*"$\lambda$(nm)",BottomTop,380,780, RightTicks(scale(0.5)*rotate(90)*Label(),step=2,Step=10),above=true); end(); // From Astronomical Data Center(NASA) // Neutral only real[] Na={423.899, 424.208, 427.364, 427.679, 428.784, 429.101, 432.14, 432.462, 434.149, 434.474, 439.003, 439.334, 441.989, 442.325, 449.418, 449.766, 454.163, 454.519, 568.2633, 568.8204, 588.995, 589.5924}; begin("Na absorption"); for(int i=0; i< Na.length; ++i) { draw((Na[i],0)--(Na[i],height),0.1*width+squarecap); } end(); begin("Na emission"); for(int i=0; i< Na.length; ++i) { draw((Na[i],0)--(Na[i],-height),0.1*width+nm2rgb(Na[i],false)+squarecap); } end(); // Neutral only real[] Zn={388.334, 396.543, 411.321, 429.288, 429.833, 462.981, 468.014, 472.215, 481.053 , 506.866, 506.958, 518.198, 530.865, 531.024, 531.102, 577.21, 577.55, 577.711, 623.79, 623.917, 636.234, 647.918, 692.832, 693.847, 694.32, 779.936}; begin("Zn absorption",false); for(int i=0; i< Zn.length; ++i) { draw((Zn[i],0)--(Zn[i],height),width+squarecap); } end(); begin("Zn emission",false); for(int i=0; i< Zn.length; ++i) { draw((Zn[i],0)--(Zn[i],-height),width+nm2rgb(Zn[i],false)+squarecap); } end(); shipout(bbox(2mm,Fill(white))); (When you compile this code with asymptote, it produces a pdf file with 7 layers) Then I tried to use the Asymptote code above in the latex following document : \documentclass{article} \usepackage[utf8]{inputenc} \usepackage[T1]{fontenc} \usepackage{asymptote} %\usepackage{ocg} \begin{document} \begin{asy} import graph; usepackage("ocg"); settings.tex="pdflatex"; // Dan Bruton algorithm pen nm2rgb(real wl, real gamma=0.8, bool intensity=true) { triple rgb; if(wl >= 380 && wl <= 440) {rgb=((440-wl)/60,0,1);} if(wl > 440 && wl <= 490) {rgb=(0,(wl-440)/50,1);} if(wl > 490 && wl <= 510) {rgb=(0,1,(510-wl)/20);} if(wl > 510 && wl <= 580) {rgb=((wl-510)/70,1,0);} if(wl > 580 && wl <= 645) {rgb=(1,(645-wl)/65,0);} if(wl > 645 && wl <= 780) {rgb=(1,0,0);} real Intensity=1; if(intensity) { if(wl >= 700) {Intensity=0.3+0.7*(780-wl)/80;} else if(wl <= 420) {Intensity=0.3+0.7*(wl-380)/40;} } return rgb((Intensity*rgb.x)**gamma,(Intensity*rgb.y)**gamma, (Intensity*rgb.z)**gamma); } real width=1; real height=50; begin("spectrum"); for(real i=380 ; i <= 780 ; i += width) { draw((i,0)--(i,height),width+nm2rgb(wl=i,false)+squarecap); } begin("Extinction",false); // nested for(real i=380 ; i <= 780 ; i += width) { draw((i,0)--(i,height),width+nm2rgb(wl=i,true)+squarecap); } end(); end(); begin("Wavelength"); xaxis(scale(0.5)*"$\lambda$(nm)",BottomTop,380,780, RightTicks(scale(0.5)*rotate(90)*Label(),step=2,Step=10),above=true); end(); // From Astronomical Data Center(NASA) // Neutral only real[] Na={423.899, 424.208, 427.364, 427.679, 428.784, 429.101, 432.14, 432.462, 434.149, 434.474, 439.003, 439.334, 441.989, 442.325, 449.418, 449.766, 454.163, 454.519, 568.2633, 568.8204, 588.995, 589.5924}; begin("Na absorption"); for(int i=0; i < Na.length; ++i) { draw((Na[i],0)--(Na[i],height),0.1*width+squarecap); } end(); begin("Na emission"); for(int i=0; i < Na.length; ++i) { draw((Na[i],0)--(Na[i],-height),0.1*width+nm2rgb(Na[i],false)+squarecap); } end(); // Neutral only real[] Zn={388.334, 396.543, 411.321, 429.288, 429.833, 462.981, 468.014, 472.215, 481.053 , 506.866, 506.958, 518.198, 530.865, 531.024, 531.102, 577.21, 577.55, 577.711, 623.79, 623.917, 636.234, 647.918, 692.832, 693.847, 694.32, 779.936}; begin("Zn absorption",false); for(int i=0; i < Zn.length; ++i) { draw((Zn[i],0)--(Zn[i],height),width+squarecap); } end(); begin("Zn emission",false); for(int i=0; i < Zn.length; ++i) { draw((Zn[i],0)--(Zn[i],-height),width+nm2rgb(Zn[i],false)+squarecap); } end(); shipout(bbox(2mm,Fill(white))); \end{asy} \end{document} When I compile this code with pdflatex (pdflatex+asy+pdflatex), there's non problem (I fact there is a problem because there is no more layers but that another problem and it doesn't come from TeXworks) but if you uncomment the fifth line (%\usepackage{ocg}) and then compile again with pdflatex (pdflatex+asy+pdflatex), everything disappear. However, if you read the pdf with acrobat, there's no problem with it. Arthur From paul.a.norman at gmail.com Mon Jun 20 00:45:54 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 20 Jun 2011 10:45:54 +1200 Subject: [texworks] Problem with TW viewer : asymptote and layers In-Reply-To: <4DFE71F9.3070608@free.fr> References: <4DFE71F9.3070608@free.fr> Message-ID: Dear Arthur, If you are looking for layers in the TeXworks previewer then I do not believe that you will currently find them in any release of TeXworks. The previewer is based on Poppler a different engine to the acrobat reader pdf viewer. There has been talk on the list here about seeing if layers can be activated in the TeXworks previewer, but at present the feature is not available to r759 Here is a link to a previous discussion on the topic. http://tug.org/mailman/mmsearch/texworks?config=texworks&restrict=&exclude=&method=and&format=long&sort=score&words=layers Paul On 20 June 2011 10:02, wrote: > Hello, > > I use Windows Seven 64 bits, TL2010 up to date with TLContrib and run > TeXworks 0.4.0 (r.759). > > I got the following Asymptote code here : > http://asymptote.sourceforge.net/gallery/spectrum.asy > > Here it is : > > import graph; > usepackage("ocg"); > settings.tex="pdflatex"; > > // Dan Bruton algorithm > pen nm2rgb(real wl, real gamma=0.8, bool intensity=true) { > ?triple rgb; > ?if(wl>= 380&& ?wl<= 440) {rgb=((440-wl)/60,0,1);} > ?if(wl> ? 440&& ?wl<= 490) {rgb=(0,(wl-440)/50,1);} > ?if(wl> ? 490&& ?wl<= 510) {rgb=(0,1,(510-wl)/20);} > ?if(wl> ? 510&& ?wl<= 580) {rgb=((wl-510)/70,1,0);} > ?if(wl> ? 580&& ?wl<= 645) {rgb=(1,(645-wl)/65,0);} > ?if(wl> ? 645&& ?wl<= 780) {rgb=(1,0,0);} > > ?real Intensity=1; > ?if(intensity) { > ? ?if(wl>= 700) {Intensity=0.3+0.7*(780-wl)/80;} > ? ?else if(wl<= 420) {Intensity=0.3+0.7*(wl-380)/40;} > ?} > > ?return rgb((Intensity*rgb.x)**gamma,(Intensity*rgb.y)**gamma, > ? ? ? ? ? ? (Intensity*rgb.z)**gamma); > } > > real width=1; > real height=50; > > begin("spectrum"); > for(real i=380 ; i<= 780 ; i += width) { > ?draw((i,0)--(i,height),width+nm2rgb(wl=i,false)+squarecap); > } > begin("Extinction",false); // nested > for(real i=380 ; i<= 780 ; i += width) { > ?draw((i,0)--(i,height),width+nm2rgb(wl=i,true)+squarecap); > } > end(); > end(); > > begin("Wavelength"); > xaxis(scale(0.5)*"$\lambda$(nm)",BottomTop,380,780, > ? ? ?RightTicks(scale(0.5)*rotate(90)*Label(),step=2,Step=10),above=true); > end(); > > // From Astronomical Data Center(NASA) > // Neutral only > real[] Na={423.899, 424.208, 427.364, 427.679, 428.784, 429.101, > ? ? ? ? ? 432.14, 432.462, 434.149, 434.474, 439.003, 439.334, 441.989, > 442.325, > ? ? ? ? ? 449.418, 449.766, 454.163, 454.519, 568.2633, 568.8204, 588.995, > ? ? ? ? ? 589.5924}; > begin("Na absorption"); > for(int i=0; i< ?Na.length; ++i) { > ?draw((Na[i],0)--(Na[i],height),0.1*width+squarecap); > } > end(); > > begin("Na emission"); > for(int i=0; i< ?Na.length; ++i) { > ?draw((Na[i],0)--(Na[i],-height),0.1*width+nm2rgb(Na[i],false)+squarecap); > } > end(); > > // Neutral only > real[] Zn={388.334, 396.543, 411.321, 429.288, 429.833, 462.981, > ? ? ? ? ? 468.014, 472.215, 481.053 , 506.866, 506.958, 518.198, 530.865, > ? ? ? ? ? 531.024, 531.102, 577.21, 577.55, 577.711, 623.79, 623.917, > 636.234, > ? ? ? ? ? 647.918, 692.832, 693.847, 694.32, 779.936}; > begin("Zn absorption",false); > for(int i=0; i< ?Zn.length; ++i) { > ?draw((Zn[i],0)--(Zn[i],height),width+squarecap); > } > end(); > > begin("Zn emission",false); > for(int i=0; i< ?Zn.length; ++i) { > ?draw((Zn[i],0)--(Zn[i],-height),width+nm2rgb(Zn[i],false)+squarecap); > } > end(); > > shipout(bbox(2mm,Fill(white))); > > > > > (When you compile this code with asymptote, it produces a pdf file with 7 > layers) > > Then I tried to use the Asymptote code above in the latex following document > : > > > > > > \documentclass{article} > > \usepackage[utf8]{inputenc} > > \usepackage[T1]{fontenc} > > \usepackage{asymptote} > > %\usepackage{ocg} > > \begin{document} > > \begin{asy} > > import graph; > > usepackage("ocg"); > > settings.tex="pdflatex"; > > // Dan Bruton algorithm > > pen nm2rgb(real wl, real gamma=0.8, bool intensity=true) { > > triple rgb; > > if(wl >= 380 && wl <= 440) {rgb=((440-wl)/60,0,1);} > > if(wl > 440 && wl <= 490) {rgb=(0,(wl-440)/50,1);} > > if(wl > 490 && wl <= 510) {rgb=(0,1,(510-wl)/20);} > > if(wl > 510 && wl <= 580) {rgb=((wl-510)/70,1,0);} > > if(wl > 580 && wl <= 645) {rgb=(1,(645-wl)/65,0);} > > if(wl > 645 && wl <= 780) {rgb=(1,0,0);} > > real Intensity=1; > > if(intensity) { > > if(wl >= 700) {Intensity=0.3+0.7*(780-wl)/80;} > > else if(wl <= 420) {Intensity=0.3+0.7*(wl-380)/40;} > > } > > return rgb((Intensity*rgb.x)**gamma,(Intensity*rgb.y)**gamma, > > (Intensity*rgb.z)**gamma); > > } > > real width=1; > > real height=50; > > begin("spectrum"); > > for(real i=380 ; i <= 780 ; i += width) { > > draw((i,0)--(i,height),width+nm2rgb(wl=i,false)+squarecap); > > } > > begin("Extinction",false); // nested > > for(real i=380 ; i <= 780 ; i += width) { > > draw((i,0)--(i,height),width+nm2rgb(wl=i,true)+squarecap); > > } > > end(); > > end(); > > begin("Wavelength"); > > xaxis(scale(0.5)*"$\lambda$(nm)",BottomTop,380,780, > > RightTicks(scale(0.5)*rotate(90)*Label(),step=2,Step=10),above=true); > > end(); > > // From Astronomical Data Center(NASA) > > // Neutral only > > real[] Na={423.899, 424.208, 427.364, 427.679, 428.784, 429.101, > > 432.14, 432.462, 434.149, 434.474, 439.003, 439.334, 441.989, 442.325, > > 449.418, 449.766, 454.163, 454.519, 568.2633, 568.8204, 588.995, > > 589.5924}; > > begin("Na absorption"); > > for(int i=0; i < Na.length; ++i) { > > draw((Na[i],0)--(Na[i],height),0.1*width+squarecap); > > } > > end(); > > begin("Na emission"); > > for(int i=0; i < Na.length; ++i) { > > draw((Na[i],0)--(Na[i],-height),0.1*width+nm2rgb(Na[i],false)+squarecap); > > } > > end(); > > // Neutral only > > real[] Zn={388.334, 396.543, 411.321, 429.288, 429.833, 462.981, > > 468.014, 472.215, 481.053 , 506.866, 506.958, 518.198, 530.865, > > 531.024, 531.102, 577.21, 577.55, 577.711, 623.79, 623.917, 636.234, > > 647.918, 692.832, 693.847, 694.32, 779.936}; > > begin("Zn absorption",false); > > for(int i=0; i < Zn.length; ++i) { > > draw((Zn[i],0)--(Zn[i],height),width+squarecap); > > } > > end(); > > begin("Zn emission",false); > > for(int i=0; i < Zn.length; ++i) { > > draw((Zn[i],0)--(Zn[i],-height),width+nm2rgb(Zn[i],false)+squarecap); > > } > > end(); > > shipout(bbox(2mm,Fill(white))); > > \end{asy} > > \end{document} > > > > When I compile this code with pdflatex (pdflatex+asy+pdflatex), there's non > problem (I fact there is a problem because there is no more layers but that > another problem and it doesn't come from TeXworks) but if you uncomment the > fifth line (%\usepackage{ocg}) > and then compile again with pdflatex (pdflatex+asy+pdflatex), everything > disappear. However, if you read the pdf with acrobat, there's no problem > with it. > > > Arthur > > > > > From paul.a.norman at gmail.com Mon Jun 20 01:07:49 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 20 Jun 2011 11:07:49 +1200 Subject: [texworks] Document Version-ing and synctex Previewing Message-ID: Hi, For security of work, I both sync the files to storage(-s), and manually version number my .tex document(s) from time to time (one long monolithic) - not any version-ing on includes or like to worry about here. E.g. These-Fair-Isles-01.tex These-Fair-Isles-02.tex These-Fair-Isles-03.tex And use a document pre-header of ... %& -job-name=These-Fair-Isles Which nicely, under MiKTeX at least, makes the pdf as: These-Fair-Isles.pdf and keeps it that way no matter what my document name version number is. This means that the current document can always be linked to, and there is no obsolete .pdf garbage collection needed, i.e. no great list of These-Fair-Isles-01.pdf, These-Fair-Isles-02.pdf, These-Fair-Isles-03.pdf ... pdfs to be cleaned up later. (All the .aux files etc nicely show up for deletion on File/Remove Aux Files) Is there any setting I can put in the document to tell syntax to work on the document named in the top most header, %& -job-name=These-Fair-Isles Or is there a similar command line I can include in the top of the document's header, so that Tw synctex preview will work please? I.e. I would be working say at the moment in These-Fair-Isles-11.tex (or what ever) but always previewing and syncing to These-Fair-Isles.pdf Paul From chuck at sharpsteen.net Mon Jun 20 01:18:42 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sun, 19 Jun 2011 16:18:42 -0700 Subject: [texworks] Problem with TW viewer : asymptote and layers In-Reply-To: <4DFE71F9.3070608@free.fr> References: <4DFE71F9.3070608@free.fr> Message-ID: On Sun, Jun 19, 2011 at 3:02 PM, wrote: > Hello, > > I use Windows Seven 64 bits, TL2010 up to date with TLContrib and run > TeXworks 0.4.0 (r.759). > > I got the following Asymptote code here : > http://asymptote.sourceforge.net/gallery/spectrum.asy > > Here it is : > When I compile this code with pdflatex (pdflatex+asy+pdflatex), there's non > problem (I fact there is a problem because there is no more layers but that > another problem and it doesn't come from TeXworks) but if you uncomment the > fifth line (%\usepackage{ocg}) > and then compile again with pdflatex (pdflatex+asy+pdflatex), everything > disappear. However, if you read the pdf with acrobat, there's no problem > with it. > > > Arthur TeXworks uses the Poppler library to render PDF files: http://poppler.freedesktop.org At the moment, TeXworks does not make use of Poppler's support for optional content groups. There is a feature request open for adding layer support: http://code.google.com/p/texworks/issues/detail?id=498 However, it looks like there may be some barriers to supporting Asymptote layers. I loaded up your example PDF in Poppler's demo viewer and got: "Error: Could not find a OCG with Ref (12:0)" "Error: Could not find a OCG with Ref (13:0)" "Error: Could not find a OCG with Ref (14:0)" "Error: Could not find a OCG with Ref (15:0)" "Error: Could not find a OCG with Ref (16:0)" "Error: Could not find a OCG with Ref (17:0)" "Error: Could not find a OCG with Ref (18:0)" "Error: Could not find a OCG with Ref (12:0)" "Error: Could not find a OCG with Ref (13:0)" "Error: Could not find a OCG with Ref (14:0)" "Error: Could not find a OCG with Ref (15:0)" "Error: Could not find a OCG with Ref (16:0)" "Error: Could not find a OCG with Ref (17:0)" "Error: Could not find a OCG with Ref (18:0)" So, Poppler may not be able to work with the layers produced by Asymptote and the OCG package. Someone may need to put in some serious development time in order to fix this. -Charlie From chuck at sharpsteen.net Mon Jun 20 01:27:28 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Sun, 19 Jun 2011 16:27:28 -0700 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: Message-ID: On Sun, Jun 19, 2011 at 4:07 PM, Paul A Norman wrote: > Hi, > > For security of work, I both sync the files to storage(-s), and > manually version number my .tex document(s) from time to time (one > long monolithic) - not any version-ing on includes or like to worry > about here. > > E.g. > > These-Fair-Isles-01.tex > These-Fair-Isles-02.tex > These-Fair-Isles-03.tex > > And use a document pre-header of ... > > ? ? %& -job-name=These-Fair-Isles > > Which nicely, under MiKTeX at least, makes the pdf as: > ? ? ?These-Fair-Isles.pdf > and keeps it that way no matter what my document name version number is. > > This means that the current document can always be linked to, and > there is no obsolete .pdf garbage collection needed, > ?i.e. no great list of These-Fair-Isles-01.pdf, > These-Fair-Isles-02.pdf, These-Fair-Isles-03.pdf ... pdfs ?to be > cleaned up later. > > (All the .aux files etc nicely show up for deletion on File/Remove Aux Files) > > Is there any setting I can put in the document to tell syntax to work > on the document named in the top most header, > > ? ? %& -job-name=These-Fair-Isles > > Or is there a similar command line I can include in the top of the > document's header, so that Tw synctex preview will work please? > > I.e. I would be working say at the moment in These-Fair-Isles-11.tex > (or what ever) > but always previewing ?and syncing to These-Fair-Isles.pdf > > Paul Have you considered using a version control system such as Git, Mercurial or SVN? Then you would just have one copy, These-Fair-Isles.tex, and the ability to rewind to any prior version. Plus, distributed systems like Git and Mercurial offer even more security of work by allowing you to easily mirror your documents across multiple computers in case the proverbial bolt of lightning strikes your main machine. -Charlie From paul.a.norman at gmail.com Mon Jun 20 01:40:33 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 20 Jun 2011 11:40:33 +1200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: Message-ID: Thanks for the suggestions Charlie, We have a reasonable mirroring operation in place covering both local and external storage. The reason for version numbering the documents is that it fits in with our local setup, and makes restoration of any lost text, through local diffing with Win-merge fast and effective, (opensource http://winmerge.org/ hopefully soon to be corss-platform https://bitbucket.org/grimmdp/winmerge ) . What I'm looking for is a way to tell TeXworks which pdf to use for syncing with the source text. Paul On 20 June 2011 11:27, Charlie Sharpsteen wrote: > On Sun, Jun 19, 2011 at 4:07 PM, Paul A Norman wrote: >> Hi, >> >> For security of work, I both sync the files to storage(-s), and >> manually version number my .tex document(s) from time to time (one >> long monolithic) - not any version-ing on includes or like to worry >> about here. >> >> E.g. >> >> These-Fair-Isles-01.tex >> These-Fair-Isles-02.tex >> These-Fair-Isles-03.tex >> >> And use a document pre-header of ... >> >> ? ? %& -job-name=These-Fair-Isles >> >> Which nicely, under MiKTeX at least, makes the pdf as: >> ? ? ?These-Fair-Isles.pdf >> and keeps it that way no matter what my document name version number is. >> >> This means that the current document can always be linked to, and >> there is no obsolete .pdf garbage collection needed, >> ?i.e. no great list of These-Fair-Isles-01.pdf, >> These-Fair-Isles-02.pdf, These-Fair-Isles-03.pdf ... pdfs ?to be >> cleaned up later. >> >> (All the .aux files etc nicely show up for deletion on File/Remove Aux Files) >> >> Is there any setting I can put in the document to tell syntax to work >> on the document named in the top most header, >> >> ? ? %& -job-name=These-Fair-Isles >> >> Or is there a similar command line I can include in the top of the >> document's header, so that Tw synctex preview will work please? >> >> I.e. I would be working say at the moment in These-Fair-Isles-11.tex >> (or what ever) >> but always previewing ?and syncing to These-Fair-Isles.pdf >> >> Paul > > Have you considered using a version control system such as Git, > Mercurial or SVN? Then you would just have one copy, > These-Fair-Isles.tex, and the ability to rewind to any prior version. > Plus, distributed systems like Git and Mercurial offer even more > security of work by allowing you to easily mirror your documents > across multiple computers in case the proverbial bolt of lightning > strikes your main machine. > > -Charlie > > From site4000 at free.fr Mon Jun 20 01:17:20 2011 From: site4000 at free.fr (site4000 at free.fr) Date: Mon, 20 Jun 2011 01:17:20 +0200 Subject: [texworks] Problem with TW viewer : asymptote and layers In-Reply-To: References: <4DFE71F9.3070608@free.fr> Message-ID: <4DFE8380.1090101@free.fr> Ok, thanks Paul. Le 20/06/2011 00:45, Paul A Norman a ?crit : > Dear Arthur, > > If you are looking for layers in the TeXworks previewer then I do not > believe that you will currently find them in any release of TeXworks. > > The previewer is based on Poppler a different engine to the acrobat > reader pdf viewer. > > There has been talk on the list here about seeing if layers can be > activated in the TeXworks previewer, but at present the feature is not > available to r759 > > Here is a link to a previous discussion on the topic. > > http://tug.org/mailman/mmsearch/texworks?config=texworks&restrict=&exclude=&method=and&format=long&sort=score&words=layers > > Paul > > On 20 June 2011 10:02, wrote: >> Hello, >> >> I use Windows Seven 64 bits, TL2010 up to date with TLContrib and run >> TeXworks 0.4.0 (r.759). >> >> I got the following Asymptote code here : >> http://asymptote.sourceforge.net/gallery/spectrum.asy >> >> Here it is : >> >> import graph; >> usepackage("ocg"); >> settings.tex="pdflatex"; >> >> // Dan Bruton algorithm >> pen nm2rgb(real wl, real gamma=0.8, bool intensity=true) { >> triple rgb; >> if(wl>= 380&& wl<= 440) {rgb=((440-wl)/60,0,1);} >> if(wl> 440&& wl<= 490) {rgb=(0,(wl-440)/50,1);} >> if(wl> 490&& wl<= 510) {rgb=(0,1,(510-wl)/20);} >> if(wl> 510&& wl<= 580) {rgb=((wl-510)/70,1,0);} >> if(wl> 580&& wl<= 645) {rgb=(1,(645-wl)/65,0);} >> if(wl> 645&& wl<= 780) {rgb=(1,0,0);} >> >> real Intensity=1; >> if(intensity) { >> if(wl>= 700) {Intensity=0.3+0.7*(780-wl)/80;} >> else if(wl<= 420) {Intensity=0.3+0.7*(wl-380)/40;} >> } >> >> return rgb((Intensity*rgb.x)**gamma,(Intensity*rgb.y)**gamma, >> (Intensity*rgb.z)**gamma); >> } >> >> real width=1; >> real height=50; >> >> begin("spectrum"); >> for(real i=380 ; i<= 780 ; i += width) { >> draw((i,0)--(i,height),width+nm2rgb(wl=i,false)+squarecap); >> } >> begin("Extinction",false); // nested >> for(real i=380 ; i<= 780 ; i += width) { >> draw((i,0)--(i,height),width+nm2rgb(wl=i,true)+squarecap); >> } >> end(); >> end(); >> >> begin("Wavelength"); >> xaxis(scale(0.5)*"$\lambda$(nm)",BottomTop,380,780, >> RightTicks(scale(0.5)*rotate(90)*Label(),step=2,Step=10),above=true); >> end(); >> >> // From Astronomical Data Center(NASA) >> // Neutral only >> real[] Na={423.899, 424.208, 427.364, 427.679, 428.784, 429.101, >> 432.14, 432.462, 434.149, 434.474, 439.003, 439.334, 441.989, >> 442.325, >> 449.418, 449.766, 454.163, 454.519, 568.2633, 568.8204, 588.995, >> 589.5924}; >> begin("Na absorption"); >> for(int i=0; i< Na.length; ++i) { >> draw((Na[i],0)--(Na[i],height),0.1*width+squarecap); >> } >> end(); >> >> begin("Na emission"); >> for(int i=0; i< Na.length; ++i) { >> draw((Na[i],0)--(Na[i],-height),0.1*width+nm2rgb(Na[i],false)+squarecap); >> } >> end(); >> >> // Neutral only >> real[] Zn={388.334, 396.543, 411.321, 429.288, 429.833, 462.981, >> 468.014, 472.215, 481.053 , 506.866, 506.958, 518.198, 530.865, >> 531.024, 531.102, 577.21, 577.55, 577.711, 623.79, 623.917, >> 636.234, >> 647.918, 692.832, 693.847, 694.32, 779.936}; >> begin("Zn absorption",false); >> for(int i=0; i< Zn.length; ++i) { >> draw((Zn[i],0)--(Zn[i],height),width+squarecap); >> } >> end(); >> >> begin("Zn emission",false); >> for(int i=0; i< Zn.length; ++i) { >> draw((Zn[i],0)--(Zn[i],-height),width+nm2rgb(Zn[i],false)+squarecap); >> } >> end(); >> >> shipout(bbox(2mm,Fill(white))); >> >> >> >> >> (When you compile this code with asymptote, it produces a pdf file with 7 >> layers) >> >> Then I tried to use the Asymptote code above in the latex following document >> : >> >> >> >> >> >> \documentclass{article} >> >> \usepackage[utf8]{inputenc} >> >> \usepackage[T1]{fontenc} >> >> \usepackage{asymptote} >> >> %\usepackage{ocg} >> >> \begin{document} >> >> \begin{asy} >> >> import graph; >> >> usepackage("ocg"); >> >> settings.tex="pdflatex"; >> >> // Dan Bruton algorithm >> >> pen nm2rgb(real wl, real gamma=0.8, bool intensity=true) { >> >> triple rgb; >> >> if(wl>= 380&& wl<= 440) {rgb=((440-wl)/60,0,1);} >> >> if(wl> 440&& wl<= 490) {rgb=(0,(wl-440)/50,1);} >> >> if(wl> 490&& wl<= 510) {rgb=(0,1,(510-wl)/20);} >> >> if(wl> 510&& wl<= 580) {rgb=((wl-510)/70,1,0);} >> >> if(wl> 580&& wl<= 645) {rgb=(1,(645-wl)/65,0);} >> >> if(wl> 645&& wl<= 780) {rgb=(1,0,0);} >> >> real Intensity=1; >> >> if(intensity) { >> >> if(wl>= 700) {Intensity=0.3+0.7*(780-wl)/80;} >> >> else if(wl<= 420) {Intensity=0.3+0.7*(wl-380)/40;} >> >> } >> >> return rgb((Intensity*rgb.x)**gamma,(Intensity*rgb.y)**gamma, >> >> (Intensity*rgb.z)**gamma); >> >> } >> >> real width=1; >> >> real height=50; >> >> begin("spectrum"); >> >> for(real i=380 ; i<= 780 ; i += width) { >> >> draw((i,0)--(i,height),width+nm2rgb(wl=i,false)+squarecap); >> >> } >> >> begin("Extinction",false); // nested >> >> for(real i=380 ; i<= 780 ; i += width) { >> >> draw((i,0)--(i,height),width+nm2rgb(wl=i,true)+squarecap); >> >> } >> >> end(); >> >> end(); >> >> begin("Wavelength"); >> >> xaxis(scale(0.5)*"$\lambda$(nm)",BottomTop,380,780, >> >> RightTicks(scale(0.5)*rotate(90)*Label(),step=2,Step=10),above=true); >> >> end(); >> >> // From Astronomical Data Center(NASA) >> >> // Neutral only >> >> real[] Na={423.899, 424.208, 427.364, 427.679, 428.784, 429.101, >> >> 432.14, 432.462, 434.149, 434.474, 439.003, 439.334, 441.989, 442.325, >> >> 449.418, 449.766, 454.163, 454.519, 568.2633, 568.8204, 588.995, >> >> 589.5924}; >> >> begin("Na absorption"); >> >> for(int i=0; i< Na.length; ++i) { >> >> draw((Na[i],0)--(Na[i],height),0.1*width+squarecap); >> >> } >> >> end(); >> >> begin("Na emission"); >> >> for(int i=0; i< Na.length; ++i) { >> >> draw((Na[i],0)--(Na[i],-height),0.1*width+nm2rgb(Na[i],false)+squarecap); >> >> } >> >> end(); >> >> // Neutral only >> >> real[] Zn={388.334, 396.543, 411.321, 429.288, 429.833, 462.981, >> >> 468.014, 472.215, 481.053 , 506.866, 506.958, 518.198, 530.865, >> >> 531.024, 531.102, 577.21, 577.55, 577.711, 623.79, 623.917, 636.234, >> >> 647.918, 692.832, 693.847, 694.32, 779.936}; >> >> begin("Zn absorption",false); >> >> for(int i=0; i< Zn.length; ++i) { >> >> draw((Zn[i],0)--(Zn[i],height),width+squarecap); >> >> } >> >> end(); >> >> begin("Zn emission",false); >> >> for(int i=0; i< Zn.length; ++i) { >> >> draw((Zn[i],0)--(Zn[i],-height),width+nm2rgb(Zn[i],false)+squarecap); >> >> } >> >> end(); >> >> shipout(bbox(2mm,Fill(white))); >> >> \end{asy} >> >> \end{document} >> >> >> >> When I compile this code with pdflatex (pdflatex+asy+pdflatex), there's non >> problem (I fact there is a problem because there is no more layers but that >> another problem and it doesn't come from TeXworks) but if you uncomment the >> fifth line (%\usepackage{ocg}) >> and then compile again with pdflatex (pdflatex+asy+pdflatex), everything >> disappear. However, if you read the pdf with acrobat, there's no problem >> with it. >> >> >> Arthur >> >> >> >> >> > > From paul.a.norman at gmail.com Mon Jun 20 08:17:05 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 20 Jun 2011 18:17:05 +1200 Subject: [texworks] SCRIPTING: TW.deleteLate() In-Reply-To: <4DFDB10F.1040909@gmail.com> References: <4DFDB10F.1040909@gmail.com> Message-ID: Thanks Stefan, Feeling my way a bit with this. Appreciate any suggestions, warnings, about what I am doing here.... running through it for long term understanding ... naively was not expecting to hit these issues with just Scripting. function myFunction() { var showMoreDialogue = TW.createUI(scriptPath + "showMore.ui"); dah dah dah -- Prep the dialogue var userAction = showMoreDialogue.exec(); dah dah dah TW.deleteLater(showMoreDialogue); } If a later call, in the same Script session, to myFunction() tries to do the following again, var showMoreDialogue = TW.createUI(scriptPath + "showMore.ui"); Debugger says, Uncaught exception at G:/latexportable/LaTexUtils/TeXWorks/texworks/config/scripts/Image Handling/convertImage.js:304: Error: cannot access member `createUI' of deleted QObject 304 var showMoreDialogue = TW.createUI(scriptPath + "showMore.ui"); So recognising that the Main dialogue emits a signal ".finished" function UIconnectVarious(connectAction) { // connectAction = "connect" | "disconnect" blah blah eval("convertImage.finished." + connectAction + "(dialog_finished)"); } function dialog_finished(resp) { // resp is code issued by dialogue at finishing 0 | 1 I think // function is used for saving settings, and ... UIconnectVarious("disconnect"); // delete various dialogue objects TW.deleteLater(showMoreDialogue); TW.deleteLater(confirmInfo); TW.deleteLater(preview); // Keep main dialogue Last TW.deleteLater(convertImage); } And I declare all potentially used dialogues globally, else TW.deleteLater() may be called on something that does not exist. var convertImage, showMoreDialogue, confirmInfo, preview; // dialogue Script Objects for later deletion (and re-use) Does TW.deleteLater() worry :) if it is dealing with is a script variable that never actually got made into a dialogue (depending upon User's choices)? I don't get debugger messages ... but then it may be to far up the chain to get a Script debugger message? Am I ok with this or should I test for className on objects ( more involved -- Script folding back to using QObject .toString() ) and if they don't have one, then not deleteLater() them? Or is no debugger message sufficient - no worries mate? (that's Aussie talk) This will be no surprise to you, but I was pleasantly surprised that using global variable names for the dialogues, meant that exec() called on them any where after creation and closing, would re-present the dialogue in the same state as last used. Which gives another (more preferable?) option which I am running with at present:-- Create all dialogues in script initialisation and immediately call .setVisible(false) ( and no exec() at that time obviously ) then just .exec() them when/as needed? And destroy them all on main dialogue . finished() I was avoiding this to keep memory usage down ( (re-)creating them on demand ), but doing this seems stable and ok, and so far no memory issues at all. Only seems to use 0.01 Gb pagefile for all four dialogues which is more than ok. Only draw back is a little screen flicker as the main.first dialogue opens and the other three open and hide. Any problems with this last approach at all? - it seems the tidiest. Just another question, I get the sense the way the debugger was responding that a created dialogue is potentially still around perhaps even after a Script closes? If so are they available to Script later? Or does Script finalisation end their lives? Paul On 19 June 2011 20:19, Stefan L?ffler wrote: > Hi, > > On 2011-06-18 09:00, Paul A Norman wrote: > > Should TW.deleteLater() be callled on Dialogues once they are > > completely finished? > > The short answer is: yes. > > > i.e. > > > > var convertImage = TW.createUI("blah.blah/xxx.ui); > > > > var ans = convertImage.exec(); > > > > TW.deleteLater(convertImage) ; > > > > > > I have had some memory issues that seem to have been solved by this. > > Is that the right way to handle this? > > The longer answer is a little more complicated. Everything that > "creates" a pointer (in sloppy C++ terms) allocates memory for that. > This remains allocated until the pointer is "destroyed" again. This can > happen automatically by a number of mechanisms, but not for these > dialogs. In particular, the dialog is not tied to a particular > invocation of a script (i.e., it's not destroyed automatically when the > script ends) to allow reusing it (and possibly its data). > Ultimately, it all comes down to what is often referred to as > "ownership": the owner is responsible for destroying a pointer, whereas > everyone else has to be aware that their copy of the pointer may be > invalidated at any time. > For the sake of completeness: if you specify a parent (e.g., > TW.createUI("file.ui", TW.target)), then the dialog will be destroyed > when TW.target is destroyed (if it still exists by then). Usually, this > won't help you much, though, as the script creating the dialog could be > called hundreds of times before TW.target is destroyed. > > > Anything else that TW.deleteLater() should be used for at all please? > > Basically, anything that creates a pointer for the script and returns it > is a good candidate for deleteLater(). So from quickly browsing through > TWScriptAPI.h/.cpp, progressDialog will need a deleteLater() as well. > > HTH > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gm at marris.fr Mon Jun 20 09:55:38 2011 From: gm at marris.fr (GM) Date: Mon, 20 Jun 2011 09:55:38 +0200 Subject: [texworks] line numbers Merge and text disappears In-Reply-To: References: Message-ID: <4DFEFCFA.5090904@marris.fr> Hello Le 30/01/2011 06:20, Paul A Norman a ?crit : > Line number appear as is overprinted on each other > > http://dl.dropbox.com/u/13401476/general_images/linenumbersMerge_text-dissapears.jpg I have this problem sometimes with windows7 for long files. And if I continue ignoring the problem ... texworks inevitably stops without being able to save the latest changes. GM From paul.a.norman at gmail.com Mon Jun 20 11:22:59 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Mon, 20 Jun 2011 21:22:59 +1200 Subject: [texworks] line numbers Merge and text disappears In-Reply-To: <4DFEFCFA.5090904@marris.fr> References: <4DFEFCFA.5090904@marris.fr> Message-ID: Hi GM, Yes I still get it on Xp, even today twice. I'm on v0.5 r804(official), what (Menu://Help/About TeXworks) version are you on please? Not sure if it is safe for text integrity to ignore it, and keep editing, one of the reasons I keep local version numbers of source documents. Does going Menu://Format/Line Numbers (Off and then again On) sort it out for you? Paul On 20 June 2011 19:55, GM wrote: > Hello > > Le 30/01/2011 06:20, Paul A Norman a ?crit : > > Line number appear as is overprinted on each other >> >> http://dl.dropbox.com/u/**13401476/general_images/** >> linenumbersMerge_text-**dissapears.jpg >> > > I have this problem sometimes with windows7 for long files. > And if I continue ignoring the problem ... texworks inevitably stops > without being able to save the latest changes. > > GM > -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Mon Jun 20 13:13:01 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Mon, 20 Jun 2011 13:13:01 +0200 Subject: [texworks] SCRIPTING: TW.deleteLate() In-Reply-To: References: <4DFDB10F.1040909@gmail.com> Message-ID: <4DFF2B3D.5050505@gmail.com> Hi, On 2011-06-20 08:17, Paul A Norman wrote: > Appreciate any suggestions, warnings, about what I am doing here.... > running through it for long term understanding ... naively was not > expecting to hit these issues with just Scripting. Exclamations of warnings below ;). Well, scripting is powerful - even more so in combination with C++, but of course there are also hidden dangers... > TW.deleteLater(showMoreDialogue); This deletes the TW object! The deleteLater() method is invoked from its own object and doesn't take any arguments (thought ECMA is quite lenient when it comes to the question of the number and types of arguments, so it apparently doesn't complain here). > > } > > > If a later call, in the same Script session, to myFunction() tries to > do the following again, > > > var showMoreDialogue = TW.createUI(scriptPath + "showMore.ui"); > > > Debugger says, > > > Uncaught exception at > G:/latexportable/LaTexUtils/TeXWorks/texworks/config/scripts/Image > Handling/convertImage.js:304: Error: cannot access member `createUI' > of deleted QObject > > 304 var showMoreDialogue = TW.createUI(scriptPath + "showMore.ui"); > It says here "cannot access member [...] of deleted QObject" - this means that you can't call member functions of the TW object anymore because that has been destroyed (though, normally, this should be impossible, *unless* of course you're mixing event loops - which can be a side effect of nesting dialogs; technicallities @ http://doc.trolltech.com/4.7/qobject.html#deleteLater). So you've effectively nuked your connection to Tw ;). > So recognising that the Main dialogue emits a signal ".finished" > Just a word of caution: as discussed before, connecting to signals is not guaranteed to be stable ATM. > Does TW.deleteLater() worry :) if it is dealing with is a script > variable that never actually got made into a dialogue (depending upon > User's choices)? > > > I don't get debugger messages ... but then it may be to far up the > chain to get a Script debugger message? > > > Am I ok with this or should I test for className on objects ( more > involved -- Script folding back to using QObject .toString() ) and if > they don't have one, then not deleteLater() them? > I can't tell off-hand. One thing that is sure is that it's safe to call deleteLater() multiple times. Note that deleteLater() implies that the object is not deleted immediately, but is scheduled for deletion when the control returns to the event loop. Normally, this is when the script ends (then, control returns to the main event loop), but dialogs can have their own event loops (so they can run modally), and in that case things might be more difficult. The more difficult question is what happens if a variable is "declared", but is not a QObject. So, e.g., what happens if you say var a = "test"; a.deleteLater(); I'd naively think that this causes an error, but depending on the implementation it might not (e.g., if all types are implicitly derived of or castable to QObject). Generally, though, I'm inclined to think that if there are no errors/messages, the implementation probably handles everything behind the scenes silently correctly. > Or is no debugger message sufficient - no worries mate? (that's Aussie > talk) > Yeah, I'd go with "no worries mate" ;). > This will be no surprise to you, but I was pleasantly surprised that > using global variable names for the dialogues, meant that exec() > called on them any where after creation and closing, would re-present > the dialogue in the same state as last used. > > > Which gives another (more preferable?) option which I am running with > at present:-- > > > Create all dialogues in script initialisation and immediately call > .setVisible(false) ( and no exec() at that time obviously ) then > just .exec() them when/as needed? > > > > And destroy them all on main dialogue . finished() > > > I was avoiding this to keep memory usage down ( (re-)creating them on > demand ), but doing this seems stable and ok, and so far no memory > issues at all. > > Only seems to use 0.01 Gb pagefile for all four dialogues which is > more than ok. > > > Only draw back is a little screen flicker as the main.first dialogue > opens and the other three open and hide. > > > Any problems with this last approach at all? - it seems the tidiest. > It's certainly tidy, but requires a lot of book-keeping (and doesn't cover some cases, where dialogs would be created on-the-fly based on user input). Plus, there is the flickering. So, all in all, I guess the first solution is the more general solution, but then again this is probably just a matter of taste. > Just another question, I get the sense the way the debugger was > responding that a created dialogue is potentially still around perhaps > even after a Script closes? > > If so are they available to Script later? Or does > Script finalisation end their lives? > Yes, maybe, and no (actually, these were 3 questions ;)); as I tried to point out in my previous mail, dialogs are not tied to the script, and it is the responsibility of the script that creates it to ensure that they get deleted properly. That said, this doesn't necessarily happen during the lifetime of the script. You must make sure you keep a reference to it, though, as the variables to use the dialog don't survive; e.g., dialogs could be kept in TW.globals for later use. HTH Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Mon Jun 20 14:27:11 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 21 Jun 2011 00:27:11 +1200 Subject: [texworks] SCRIPTING: TW.deleteLate() In-Reply-To: <4DFF2B3D.5050505@gmail.com> References: <4DFDB10F.1040909@gmail.com> <4DFF2B3D.5050505@gmail.com> Message-ID: Thanks Stefan, Just confirming for complete clarity ... So TW..deleteLater(showMoreDialogue); Must be ... ? showMoreDialogue.deleteLater(); Your .odt notes to me late last year (now in Scripting Api) noted to leave TW.deleteLater() alone ( http://twscript.paulanorman.com/docs/html/files/deleteLater.html ), I got confused when trying to work out how to get rid of dialogues. > Just a word of caution: as discussed before, connecting to signals is not guaranteed to > be stable ATM. For me, afaik, no problem with signals ever so far ever since UI became available in Scripting. Especially using the Qt supplied connection model style in last email: eval("convertImage.finished." + connectAction + "(dialog_finished)"); I haven't tried the other way. > and doesn't cover some cases, where dialogs would be created on-the-fly based on user input Ok, created and deleted locally in creating function then? Or when needed to be used in other functions once created, could just declare the var global say as a string = "I'm not a dialogue yet", not know whether the User initialised it or not as a dialogue, and at finalisation test the global var's .toString().indexOf() for either the dialogue QDialog className or "I'm not a dialogue yet", if appropriate then run .deleteLater() on it during Script finalisation? Otherwise if being used in more than one function once the User has made it, you'd never know whether and when to deletLater() on it or not. Could also test for initialisation on "I'm not a dialogue yet" in any function that wants to use it calling a function to do that test which can then create it if necessary? Note: I think a created scriptDialogueName.toString() call should give a string including the className of QDialog, and the name= of the object. > e.g., dialogs could be kept in TW.globals for later use. Had tried that when Script UI first came out, and thought it didn't work (might have to retry and make sure I got it right). Really like the idea! Thanks, Paul Paul On 20 June 2011 23:13, Stefan L?ffler wrote: > ** > Hi, > > > On 2011-06-20 08:17, Paul A Norman wrote: > > Appreciate any suggestions, warnings, about what I am doing here.... > running through it for long term understanding ... naively was not expecting > to hit these issues with just Scripting. > > > Exclamations of warnings below ;). > Well, scripting is powerful - even more so in combination with C++, but of > course there are also hidden dangers... > > TW.deleteLater(showMoreDialogue); > > > This deletes the TW object! The deleteLater() method is invoked from its > own object and doesn't take any arguments (thought ECMA is quite lenient > when it comes to the question of the number and types of arguments, so it > apparently doesn't complain here). > > > > } > > > If a later call, in the same Script session, to myFunction() tries to do > the following again, > > > var showMoreDialogue = TW.createUI(scriptPath + "showMore.ui"); > > > Debugger says, > > > Uncaught exception at > G:/latexportable/LaTexUtils/TeXWorks/texworks/config/scripts/Image > Handling/convertImage.js:304: Error: cannot access member `createUI' of > deleted QObject > > 304 var showMoreDialogue = TW.createUI(scriptPath + "showMore.ui"); > > > It says here "cannot access member [...] of deleted QObject" - this means > that you can't call member functions of the TW object anymore because that > has been destroyed (though, normally, this should be impossible, *unless* of > course you're mixing event loops - which can be a side effect of nesting > dialogs; technicallities @ > http://doc.trolltech.com/4.7/qobject.html#deleteLater). So you've > effectively nuked your connection to Tw ;). > > > So recognising that the Main dialogue emits a signal ".finished" > > > Just a word of caution: as discussed before, connecting to signals is not > guaranteed to be stable ATM. > > > Does TW.deleteLater() worry :) if it is dealing with is a script > variable that never actually got made into a dialogue (depending upon User's > choices)? > > > I don't get debugger messages ... but then it may be to far up the chain > to get a Script debugger message? > > > Am I ok with this or should I test for className on objects ( more > involved -- Script folding back to using QObject .toString() ) and if > they don't have one, then not deleteLater() them? > > > I can't tell off-hand. One thing that is sure is that it's safe to call > deleteLater() multiple times. Note that deleteLater() implies that the > object is not deleted immediately, but is scheduled for deletion when the > control returns to the event loop. Normally, this is when the script ends > (then, control returns to the main event loop), but dialogs can have their > own event loops (so they can run modally), and in that case things might be > more difficult. > The more difficult question is what happens if a variable is "declared", > but is not a QObject. So, e.g., what happens if you say > var a = "test"; > a.deleteLater(); > I'd naively think that this causes an error, but depending on the > implementation it might not (e.g., if all types are implicitly derived of or > castable to QObject). > > Generally, though, I'm inclined to think that if there are no > errors/messages, the implementation probably handles everything behind the > scenes silently correctly. > > > Or is no debugger message sufficient - no worries mate? (that's Aussie > talk) > > > Yeah, I'd go with "no worries mate" ;). > > > This will be no surprise to you, but I was pleasantly surprised that > using global variable names for the dialogues, meant that exec() called on > them any where after creation and closing, would re-present the dialogue in > the same state as last used. > > > Which gives another (more preferable?) option which I am running with at > present:-- > > > Create all dialogues in script initialisation and immediately call > .setVisible(false) ( and no exec() at that time obviously ) then just > .exec() them when/as needed? > > > > And destroy them all on main dialogue . finished() > > > I was avoiding this to keep memory usage down ( (re-)creating them on > demand ), but doing this seems stable and ok, and so far no memory issues > at all. > > Only seems to use 0.01 Gb pagefile for all four dialogues which is more > than ok. > > > Only draw back is a little screen flicker as the main.first dialogue > opens and the other three open and hide. > > > Any problems with this last approach at all? - it seems the tidiest. > > > It's certainly tidy, but requires a lot of book-keeping (and doesn't cover > some cases, where dialogs would be created on-the-fly based on user input). > Plus, there is the flickering. > > So, all in all, I guess the first solution is the more general solution, > but then again this is probably just a matter of taste. > > > Just another question, I get the sense the way the debugger was > responding that a created dialogue is potentially still around perhaps even > after a Script closes? > > If so are they available to Script later? Or does Script finalisation end > their lives? > > > Yes, maybe, and no (actually, these were 3 questions ;)); as I tried to > point out in my previous mail, dialogs are not tied to the script, and it is > the responsibility of the script that creates it to ensure that they get > deleted properly. That said, this doesn't necessarily happen during the > lifetime of the script. You must make sure you keep a reference to it, > though, as the variables to use the dialog don't survive; e.g., dialogs > could be kept in TW.globals for later use. > > HTH > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Mon Jun 20 17:00:14 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Mon, 20 Jun 2011 17:00:14 +0200 Subject: [texworks] SCRIPTING: TW.deleteLate() In-Reply-To: References: <4DFDB10F.1040909@gmail.com> <4DFF2B3D.5050505@gmail.com> Message-ID: <4DFF607E.10402@gmail.com> Hi, On 2011-06-20 14:27, Paul A Norman wrote: > Just confirming for complete clarity ... > > So TW..deleteLater(showMoreDialogue); > > Must be ... ? > > showMoreDialogue.deleteLater(); Yes, exactly. > Your .odt notes to me late last year (now in Scripting Api) noted to > leave TW.deleteLater() alone ( > http://twscript.paulanorman.com/docs/html/files/deleteLater.html ), I > got confused when trying to work out how to get rid of dialogues. Yes, you _should_ leave TW.deleteLater() alone, as that would kill the connection between the script and Tw itself. Back then, I told you to simply ignore it mainly because deleteLater is a method provided automatically for any QObject and it was nothing Tw specific that was added to the API. For dialogs, it turns out to be important, but only for the dialog variables. > > Just a word of caution: as discussed before, connecting to signals is > not guaranteed to > > be stable ATM. > > For me, afaik, no problem with signals ever so far ever since UI > became available in Scripting. > Especially using the Qt supplied connection model style in last email: > > eval("convertImage.finished." + connectAction + "(dialog_finished)"); > > I haven't tried the other way. OK. I just wanted to point it out. It may work (in particular for modal dialogs), but this depends on the way Qt handles things internally. I'm just not giving any guarantees (not that I could on other matters ;)). > > and doesn't cover some cases, where dialogs would be created > on-the-fly based on user input > > Ok, created and deleted locally in creating function then? Yes, that's an option. > Or when needed to be used in other functions once created, could > just declare the var global say as a string = "I'm not a dialogue > yet", not know whether the User initialised it or not as a dialogue, > and at finalisation test the global var's .toString().indexOf() for > either the dialogue QDialog className or "I'm not a dialogue yet", if > appropriate then run .deleteLater() on it during Script finalisation? I wouldn't use a string here, more something like null (and then test === null (I think that's supported in QtScript?)). Also, I'm not a real fan of global variables, but that's a matter of philosophy. Having an object that bundles all dialogs, for example, would be more OOP style, but in reality it doesn't matter that much IMHO. > Otherwise if being used in more than one function once the User has > made it, you'd never know whether and when to deletLater() on it or > not. Could also test for initialisation on "I'm not a dialogue > yet" in any function that wants to use it calling a function to do > that test which can then create it if necessary? "Create on demand" sounds like a sensible idea as well. The interesting question still is if deleteLater() can be called on a dialog not created. > > e.g., dialogs could be kept in TW.globals for later use. > > Had tried that when Script UI first came out, and thought it didn't > work (might have to retry and make sure I got it right). Really like > the idea! I naively think that it should work, but I haven't tried it. So maybe there is a subtle problem somewhere I don't know of. HTH Stefan From paul.a.norman at gmail.com Tue Jun 21 04:20:45 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 21 Jun 2011 14:20:45 +1200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: Message-ID: Ok, So when using %& -job-name=These-Fair-Isles in the source, if you directly manually open your output pdf in the Tw viewer, you can of course sync back to the source no problem, synctex knows the real source file name even though the produced .pdf has a different name. .. its syncing the other way which is the problem source -> preview, I think this would be an editor (Tw) specific. For current needs though, I'll just probably try to hook in on the TypeSet hook form script, and do a silent virtual auto saveAs using a version or time-stamp as part of the file name, perhaps into a subdirectory, and leave the main document always with the same name.and consequent .pdf name for syncing. Basically mean that there'll be an auto-backup each time the document is typeset. As .tex are really comaparitively quite small, this is quite good - could look at zipping as part of it. But antway, having researched this ... I see some very interesting switches for the Typeset command settings in preferences in -- http://www.google.com/codesearch#TCAOwTxChU8/trunk/src/TeXDocument.cpp&q=synctexoption%20package:http://texworks%5C.googlecode%5C.com&l=2464 if (!synctexSupported) args.removeAll("$synctexoption"); args.replaceInStrings("$synctexoption", "-synctex=1"); args.replaceInStrings("$fullname", fileInfo.fileName()); args.replaceInStrings("$basename", fileInfo.completeBaseName()); args.replaceInStrings("$suffix", fileInfo.suffix()); args.replaceInStrings("$directory", fileInfo.absoluteDir().absolutePath And was wondering about the general options for use in Edit/Preferences/Typesetting and setting Processing Tools up, or editing existing ones. I see $filename used there a bit, What other options are there please? Obviously $basename, $suffix, $directory as well. I can look these up in Qt I suppose according to fileInfo.. as shown above. Can these be combined with straight ascii/utf8 when editing Edit/Preferences/Typesetting and setting Processing Tools? And what other switches are built in please, good to know especially when adding exotic toolsets to processing tools. Paul Tw obviously picks up the document name changes .tex to .pdf an endeavours to scntex from source to that .pdf So looking inside the generated Paul On 20 June 2011 11:40, Paul A Norman wrote: > Thanks for the suggestions Charlie, > > We have a reasonable mirroring operation in place covering both local > and external storage. > > The reason for version numbering the documents is that it fits in with > our local setup, and makes restoration of any lost text, through local > diffing with Win-merge fast and effective, (opensource > http://winmerge.org/ hopefully soon to be corss-platform > https://bitbucket.org/grimmdp/winmerge ) . > > What I'm looking for is a way to tell TeXworks which pdf to use for > syncing with the source text. > > Paul > > > > On 20 June 2011 11:27, Charlie Sharpsteen wrote: > > On Sun, Jun 19, 2011 at 4:07 PM, Paul A Norman > wrote: > >> Hi, > >> > >> For security of work, I both sync the files to storage(-s), and > >> manually version number my .tex document(s) from time to time (one > >> long monolithic) - not any version-ing on includes or like to worry > >> about here. > >> > >> E.g. > >> > >> These-Fair-Isles-01.tex > >> These-Fair-Isles-02.tex > >> These-Fair-Isles-03.tex > >> > >> And use a document pre-header of ... > >> > >> %& -job-name=These-Fair-Isles > >> > >> Which nicely, under MiKTeX at least, makes the pdf as: > >> These-Fair-Isles.pdf > >> and keeps it that way no matter what my document name version number is. > >> > >> This means that the current document can always be linked to, and > >> there is no obsolete .pdf garbage collection needed, > >> i.e. no great list of These-Fair-Isles-01.pdf, > >> These-Fair-Isles-02.pdf, These-Fair-Isles-03.pdf ... pdfs to be > >> cleaned up later. > >> > >> (All the .aux files etc nicely show up for deletion on File/Remove Aux > Files) > >> > >> Is there any setting I can put in the document to tell syntax to work > >> on the document named in the top most header, > >> > >> %& -job-name=These-Fair-Isles > >> > >> Or is there a similar command line I can include in the top of the > >> document's header, so that Tw synctex preview will work please? > >> > >> I.e. I would be working say at the moment in These-Fair-Isles-11.tex > >> (or what ever) > >> but always previewing and syncing to These-Fair-Isles.pdf > >> > >> Paul > > > > Have you considered using a version control system such as Git, > > Mercurial or SVN? Then you would just have one copy, > > These-Fair-Isles.tex, and the ability to rewind to any prior version. > > Plus, distributed systems like Git and Mercurial offer even more > > security of work by allowing you to easily mirror your documents > > across multiple computers in case the proverbial bolt of lightning > > strikes your main machine. > > > > -Charlie > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Tue Jun 21 08:09:19 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 21 Jun 2011 08:09:19 +0200 Subject: [texworks] line numbers Merge and text disappears In-Reply-To: References: <4DFEFCFA.5090904@marris.fr> Message-ID: <4E00358F.5020409@gmail.com> Hi, On 2011-06-20 11:22, Paul A Norman wrote: > I'm on v0.5 r804(official), what (Menu://Help/About TeXworks) version > are you on please? I had another inspiration. Please test r845 or later - hopefully that fixes this issue finally. > Not sure if it is safe for text integrity to ignore it, and keep > editing, one of the reasons I keep local version numbers of source > documents. >From what I've seen so far, text integrity should not be affected - it seems to be a problem with rendering the text only. But then again, there might be more to it than meets the eye. HTH Stefan From st.loeffler at gmail.com Tue Jun 21 08:19:34 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Tue, 21 Jun 2011 08:19:34 +0200 Subject: [texworks] where does python27.dll come from? In-Reply-To: References: <4DF064B4.2070305@gmail.com> <4DF1CA43.8030502@swing.be> <4DF4C7CF.7020208@gmail.com> Message-ID: <4E0037F6.5030101@gmail.com> Hi, On 2011-06-14 11:29, T T wrote: > On 12 June 2011 15:06, Stefan L?ffler wrote: >> Thanks for testing and reporting. As pointed out in the thread, the Lib >> folder is indeed still necessary (it seems it picked up a different Lib >> folder on my machine - one shouldn't mix different python installs ;)). >> Anyway, using the one from the older releases is not ideal, as they were >> taken from the MSVC build. Therefore, they might depend on libraries >> etc. and might even be incompatible with the built-in mingw library. > Are you sure? No ;). > I thought all those .pyc files under Lib are platform > independent, which seems to be even stated in the python docs: > > http://docs.python.org/tutorial/modules.html#compiled-python-files > > (I ask because in TeX Live these files are currently in the common > part of the package, not in the platform specific one.) Indeed, this should be fine. What I was worried about was the fact that the .pyc were produced independently from the python library used (I'm not even sure if they used the same (minor) version). E.g., the .pyc originated from a MSVC build, whereas the library is MinGW. Plus, the MinGW library uses some (customized) statically included modules, and I'm not sure if that would have interfered with the dll. But again, I have neither tested this extensively, nor am I an expert of Python's internals. The fact that the old Lib folder worked suggests that it doesn't matter that much. Anyway, the recent upload (0.5 r846) uses the new build system, with the .pyc generated by the same python from which the library built into Tw was derived, so things should be safer now. Note, though, that I had to patch the sysconfig package to not assume a full posix build (otherwise, things like the Makefile or some headers would be required). I'm attaching the patch in case it matters to you. It's Windows-only, however, so it shouldn't interfere with other platforms. HTH Stefan PS: How about the schedule for the release? If the line-mangling issue is finally fixed now, I'll release Tw 0.4.2 soon (waiting for confirmation ATM). But if not, do you suggest releasing another version without that issue fixed by any particular date? -------------- next part -------------- A non-text attachment was scrubbed... Name: python-sysconfig-win.patch Type: text/x-patch Size: 613 bytes Desc: not available URL: From esperanto at swing.be Tue Jun 21 08:38:40 2011 From: esperanto at swing.be (Alain Delmotte) Date: Tue, 21 Jun 2011 08:38:40 +0200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: Message-ID: <4E003C70.6010507@swing.be> Hi! Le 20/06/2011 01:27, Charlie Sharpsteen a ?crit : > On Sun, Jun 19, 2011 at 4:07 PM, Paul A Norman wrote: > > Have you considered using a version control system such as Git, > Mercurial or SVN? Then you would just have one copy, > These-Fair-Isles.tex, and the ability to rewind to any prior version. > Plus, distributed systems like Git and Mercurial offer even more > security of work by allowing you to easily mirror your documents > across multiple computers in case the proverbial bolt of lightning > strikes your main machine. > > -Charlie > > As I understand the documentations, these version control system require to work over internet! Right? Is there a system which could completely be installed locally? I mean working on a machine not connected to Internet or which doesn't require to? -- Alain From paul.a.norman at gmail.com Tue Jun 21 08:51:30 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 21 Jun 2011 18:51:30 +1200 Subject: [texworks] line numbers Merge and text disappears In-Reply-To: <4E00358F.5020409@gmail.com> References: <4DFEFCFA.5090904@marris.fr> <4E00358F.5020409@gmail.com> Message-ID: On 21 June 2011 18:09, Stefan L?ffler wrote: > Hi, > > On 2011-06-20 11:22, Paul A Norman wrote: > > I'm on v0.5 r804(official), what (Menu://Help/About TeXworks) version > > are you on please? > > I had another inspiration. Please test r845 or later - hopefully that > fixes this issue finally. > Thanks, will do, noticed also that sometimes the cursor gets lost at the end of the line, and you have to click in the document elsewhere to regain it. > > > Not sure if it is safe for text integrity to ignore it, and keep > > editing, one of the reasons I keep local version numbers of source > > documents. > > >From what I've seen so far, text integrity should not be affected - it > seems to be a problem with rendering the text only. But then again, > there might be more to it than meets the eye. > One of the dangers has been not realising/noticing the line jumble up and that text has disappeared/hidden, and retyping or reinserting things (text graphics figures etc) and then later finding your document with double ups or old edits of text. That's one of the first reasons I have become so keen on local versioning as I go. Have made a hook script which prompts to save a date time stamped file name copy for the current document (same directory) after each typeset. (How does latexErrors.js know to not kick in after a non .tex typeset like a bibliography?) Looks like this in the dir listing: These-fair-Isles-2011-06-21--18-11-53.tex So they appear together in time sequence by name in the directory listing , and can so be zipped up and away en-block. Let me know if any one is interested and I'll try and put the script up. Paul > > HTH > Stefan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From esperanto at swing.be Tue Jun 21 08:57:15 2011 From: esperanto at swing.be (Alain Delmotte) Date: Tue, 21 Jun 2011 08:57:15 +0200 Subject: [texworks] where does python27.dll come from? In-Reply-To: <4E0037F6.5030101@gmail.com> References: <4DF064B4.2070305@gmail.com> <4DF1CA43.8030502@swing.be> <4DF4C7CF.7020208@gmail.com> <4E0037F6.5030101@gmail.com> Message-ID: <4E0040CB.2020900@swing.be> Hi! Le 21/06/2011 08:19, Stefan L?ffler a ?crit : > > Anyway, the recent upload (0.5 r846) uses the new build system, with the > .pyc generated by the same python from which the library built into Tw > was derived, so things should be safer now. > [...] > HTH > Stefan > > PS: How about the schedule for the release? If the line-mangling issue > is finally fixed now, I'll release Tw 0.4.2 soon (waiting for > confirmation ATM). But if not, do you suggest releasing another version > without that issue fixed by any particular date? I installed 0.5 r846 and everything seems to work for me, but, for the moment, I am not a strong tester. But it looks OK for me. Regards, Alain From paul.a.norman at gmail.com Tue Jun 21 09:01:36 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 21 Jun 2011 19:01:36 +1200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: <4E003C70.6010507@swing.be> References: <4E003C70.6010507@swing.be> Message-ID: Alain, Yes afaik - also a problem, as for you, when we are mobile w.o internet. Just trialled a hook script that automatically offers to make unique date-time named copies of main TeX document each time the document is typeset. That Script could be altered to optionally point to a any directory for saving, ... portable harddrive or a thumb storage perhaps. I'm also looking here when I get time: http://en.wikipedia.org/wiki/List_of_revision_control_software Paul On 21 June 2011 18:38, Alain Delmotte wrote: > Hi! > > Le 20/06/2011 01:27, Charlie Sharpsteen a ?crit : > >> On Sun, Jun 19, 2011 at 4:07 PM, Paul A Norman >> wrote: >> >> Have you considered using a version control system such as Git, >> Mercurial or SVN? Then you would just have one copy, >> These-Fair-Isles.tex, and the ability to rewind to any prior version. >> Plus, distributed systems like Git and Mercurial offer even more >> security of work by allowing you to easily mirror your documents >> across multiple computers in case the proverbial bolt of lightning >> strikes your main machine. >> >> -Charlie >> >> >> As I understand the documentations, these version control system require > to work over internet! Right? > > Is there a system which could completely be installed locally? I mean > working on a machine not connected to Internet or which doesn't require to? > > -- > Alain > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From esperanto at swing.be Tue Jun 21 09:54:00 2011 From: esperanto at swing.be (Alain Delmotte) Date: Tue, 21 Jun 2011 09:54:00 +0200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: <4E003C70.6010507@swing.be> Message-ID: <4E004E18.1070602@swing.be> Paul, I had a look to the link you provided. It seems that Bazaar could match our requirements; it is a distributed system, but it can be used purely locally (as I understand it). http://en.wikipedia.org/wiki/Bazaar_(software) Regards, Alain Le 21/06/2011 09:01, Paul A Norman a ?crit : > Alain, > > Yes afaik - also a problem, as for you, when we are mobile > w.o internet. > > Just trialled a hook script that automatically offers to > make unique date-time named copies of main TeX document each > time the document is typeset. That Script could be altered > to optionally point to a any directory for saving, ... > portable harddrive or a thumb storage perhaps. > > I'm also looking here when I get time: > http://en.wikipedia.org/wiki/List_of_revision_control_software > > Paul > > On 21 June 2011 18:38, Alain Delmotte > wrote: > > Hi! > > Le 20/06/2011 01:27, Charlie Sharpsteen a ?crit : > > On Sun, Jun 19, 2011 at 4:07 PM, Paul A > Norman > wrote: > > Have you considered using a version control system > such as Git, > Mercurial or SVN? Then you would just have one copy, > These-Fair-Isles.tex, and the ability to rewind to > any prior version. > Plus, distributed systems like Git and Mercurial > offer even more > security of work by allowing you to easily mirror > your documents > across multiple computers in case the proverbial > bolt of lightning > strikes your main machine. > > -Charlie > > > As I understand the documentations, these version > control system require to work over internet! Right? > > Is there a system which could completely be installed > locally? I mean working on a machine not connected to > Internet or which doesn't require to? > > -- > Alain > > > From paul.a.norman at gmail.com Tue Jun 21 10:51:05 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 21 Jun 2011 20:51:05 +1200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: <4E004E18.1070602@swing.be> References: <4E003C70.6010507@swing.be> <4E004E18.1070602@swing.be> Message-ID: Thanks Alain, That at first glance looks really really useful, and very well established and supported. Will explore it for our needs when I get time. I wonder of this sort of need is a possible aspect of the planned eventual Project Management side of TeXworks? Thanks again, paul On 21 June 2011 19:54, Alain Delmotte wrote: > Paul, > > I had a look to the link you provided. > > It seems that Bazaar could match our requirements; it is a distributed > system, but it can be used purely locally (as I understand it). > > http://en.wikipedia.org/wiki/**Bazaar_(software) > > Regards, > > Alain > > Le 21/06/2011 09:01, Paul A Norman a ?crit : > >> Alain, >> >> Yes afaik - also a problem, as for you, when we are mobile >> w.o internet. >> >> Just trialled a hook script that automatically offers to >> make unique date-time named copies of main TeX document each >> time the document is typeset. That Script could be altered >> to optionally point to a any directory for saving, ... >> portable harddrive or a thumb storage perhaps. >> >> I'm also looking here when I get time: >> http://en.wikipedia.org/wiki/**List_of_revision_control_**software >> >> Paul >> >> On 21 June 2011 18:38, Alain Delmotte > > wrote: >> >> Hi! >> >> Le 20/06/2011 01:27, Charlie Sharpsteen a ?crit : >> >> On Sun, Jun 19, 2011 at 4:07 PM, Paul A >> Norman> > > >> wrote: >> >> >> Have you considered using a version control system >> such as Git, >> Mercurial or SVN? Then you would just have one copy, >> These-Fair-Isles.tex, and the ability to rewind to >> any prior version. >> Plus, distributed systems like Git and Mercurial >> offer even more >> security of work by allowing you to easily mirror >> your documents >> across multiple computers in case the proverbial >> bolt of lightning >> strikes your main machine. >> >> -Charlie >> >> >> As I understand the documentations, these version >> control system require to work over internet! Right? >> >> Is there a system which could completely be installed >> locally? I mean working on a machine not connected to >> Internet or which doesn't require to? >> >> -- >> Alain >> >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From P.Taylor at Rhul.Ac.Uk Tue Jun 21 09:18:39 2011 From: P.Taylor at Rhul.Ac.Uk (Philip TAYLOR (Webmaster, Ret'd)) Date: Tue, 21 Jun 2011 08:18:39 +0100 Subject: [texworks] [Off-topic] Document Versioning In-Reply-To: References: <4E003C70.6010507@swing.be> Message-ID: <4E0045CF.6040706@Rhul.Ac.Uk> I have to say, without wishing to offend, that I am viewing the current thread with some amusement. I started work with the University of London in 1970, and at that time the central service used CDC machines with SCOPE, NOS and NOS/BE. Integrated into the operating system was the "UPDATE" utility, which through a few simple commands *DELETE 11-13 *INSERT and so on would make line-oriented changes to a source file in a non-destructive way such that, at any time, a user could revert to an earlier version of his/her program. As the Colleges of the University started to become more independent, the wiser of them bought Digital Vaxes, running VMS. A fundamental part of the VMS file system was the concept of a version number. Every time a change was made to a file, a new version was created, and thus the user could, at any time, revert to any earlier version of his/her file. Well, the world moved on. CDCs, UPDATE, VAXes and VMS were felt be be pass?; the more nerdish adopted Unix and its derivatives, real people adopted PCs. And integrated version control disappeared. Almost overnight. And it has taken almost thirty years for people to start to realise what a stupid mistake that was. ** Phil. From noelclaude at hotmail.com Tue Jun 21 17:36:56 2011 From: noelclaude at hotmail.com (Claude NOEL) Date: Tue, 21 Jun 2011 17:36:56 +0200 Subject: [texworks] Message from TeXworks user Message-ID: Which is the method for add fonts at Texworks? Thanks a lot for your help. Claude NOEL ----- configuration info ----- TeXworks version : 0.4.0r759 (official) Install location : C:/texlive/2010/tlpkg/texworks/texworks.exe Library path : C:/Users/Claude/.texlive2010/texmf-config/texworks\ pdfTeX location : C:/texlive/2010/bin/win32/pdftex.exe Operating system : Windows 7 Service Pack 1, 64-bit Qt4 version : 4.7.2 (build) / 4.7.2 (runtime) ------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Tue Jun 21 20:40:02 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 21 Jun 2011 11:40:02 -0700 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: <4E003C70.6010507@swing.be> References: <4E003C70.6010507@swing.be> Message-ID: https://scribtex.com/On Mon, Jun 20, 2011 at 11:38 PM, Alain Delmotte < esperanto at swing.be> wrote: > Hi! > > Le 20/06/2011 01:27, Charlie Sharpsteen a ?crit : > >> On Sun, Jun 19, 2011 at 4:07 PM, Paul A Norman >> wrote: >> >> Have you considered using a version control system such as Git, >> Mercurial or SVN? Then you would just have one copy, >> These-Fair-Isles.tex, and the ability to rewind to any prior version. >> Plus, distributed systems like Git and Mercurial offer even more >> security of work by allowing you to easily mirror your documents >> across multiple computers in case the proverbial bolt of lightning >> strikes your main machine. >> >> -Charlie >> >> >> As I understand the documentations, these version control system require > to work over internet! Right? > > Is there a system which could completely be installed locally? I mean > working on a machine not connected to Internet or which doesn't require to? > > -- > Alain > None of these version control systems require internet access. In fact, distributed systems like Git, Mercurial and Bazaar were specifically designed to support working in situations where internet access is unavailable. Even Subversion (SVN) can be installed and used locally although it is more difficult to share access when the SVN "central repository" is on your personal computer---unless you are very comfortable with turning your computer into a web server. If you are interested in using these systems, I would suggest: - Mercurial, as you can store a clone of your work to Bitbucket which offers unlimited private repositories. - Git, as you could sync your work to ScribTeX which also offers web-based editing and compiling for TeX documents. I make these suggestions because writing is often personal but you probably want to store a copy of your work somewhere online (so it is easily accessible from any computer) yet also have it private so only you can access it. Most distributed version control systems (git, mercurial, bazaar, etc) can also sync over SSH, so you can store clones on any server you have SSH access to. -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Tue Jun 21 20:57:53 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 21 Jun 2011 11:57:53 -0700 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: <4E003C70.6010507@swing.be> <4E004E18.1070602@swing.be> Message-ID: On Tue, Jun 21, 2011 at 1:51 AM, Paul A Norman wrote: > Thanks Alain, > > That at first glance looks really really useful, and very well established > and supported. > > Will explore it for our needs when I get time. > > I wonder of this sort of need is a possible aspect of the planned eventual > Project Management side of TeXworks? > > Thanks again, > paul > I played around with this a month ago---was thinking about integrating libgit2 into TeXworks. This would provide a cross-platform built-in way to store versioned information without requiring the user to install and configure additional version control software. Most modern version control systems can read Git repository dumps so it would be easy to export projects to another system of the user's preference. libgit2 still needs some work before it is fully ready though---it needs a networking stack and the ability to do tree-diffs between snapshots of a project. The networking stack is being built as part of a Summer of Code project and so there should be some exciting developments later this year. I've always felt that TeX is starting to lag behind other document preparation systems in the collaborative editing/review area. Microsoft Word has had "track changes" and other review systems for years. Apple just announced an Auto Save feature as part of OS X 10.7 that automatically tracks snapshots and allows one to browse the entire timeline of a document and drag document components back and forth between versions. We definitely have the tools to do similar things in the TeX world, but it is difficult to get an entire team of people to buy into them. Asking someone to learn TeX plus a version control system all at once can be a tough sell. If version control was built into the editor in a transparent fashion, it would be a lot easier for newcomers to deal with. -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Tue Jun 21 21:00:43 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 21 Jun 2011 12:00:43 -0700 Subject: [texworks] Message from TeXworks user In-Reply-To: References: Message-ID: On Tue, Jun 21, 2011 at 8:36 AM, Claude NOEL wrote: > > Which is the method for add fonts at Texworks? > Thanks a lot for your help. > Claude NOEL > Fonts are handled by the underlying TeX typesetting system. The details differ depending on if you are using pdfTeX, XeTeX or LuaTeX. You may want to check out this question on tex.stackexchange.com: http://tex.stackexchange.com/q/13219/17 Hopefully it will help. -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From reinhard.kotucha at web.de Tue Jun 21 23:58:38 2011 From: reinhard.kotucha at web.de (Reinhard Kotucha) Date: Tue, 21 Jun 2011 23:58:38 +0200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: <4E003C70.6010507@swing.be> <4E004E18.1070602@swing.be> Message-ID: <19969.5134.953990.399574@zaphod.ms25.net> On 2011-06-21 at 11:57:53 -0700, Charlie Sharpsteen wrote: > On Tue, Jun 21, 2011 at 1:51 AM, Paul A Norman wrote: > > > Thanks Alain, > > > > That at first glance looks really really useful, and very well > > established and supported. > > > > Will explore it for our needs when I get time. > > > > I wonder of this sort of need is a possible aspect of the planned > > eventual Project Management side of TeXworks? > > > > Thanks again, > > paul > > > > I played around with this a month ago---was thinking about > integrating libgit2 into > TeXworks. This would provide a cross-platform built-in way to store > versioned information without requiring the user to install and > configure additional version control software. Most modern version > control systems can read Git repository dumps so it would be easy > to export projects to another system of the user's > preference. libgit2 still needs some work before it is fully ready > though---it needs a networking stack and the ability to do > tree-diffs between snapshots of a project. The networking stack is > being built as part of a Summer of Code project and so there should > be some exciting developments later this year. > > I've always felt that TeX is starting to lag behind other document > preparation systems in the collaborative editing/review > area. Microsoft Word has had "track changes" and other review > systems for years. Apple just announced an Auto Save feature as > part of OS X 10.7 that automatically tracks snapshots and allows > one to browse the entire timeline of a document and drag document > components back and forth between versions. We definitely have the > tools to do similar things in the TeX world, but it is difficult to > get an entire team of people to buy into them. Asking someone to > learn TeX plus a version control system all at once can be a tough > sell. If version control was built into the editor in a transparent > fashion, it would be a lot easier for newcomers to deal with. People are using TeX with version control systems for decades. It's Microsoft which always lags behind. If you add libgit to TeXworks, will this help if people collaborate with others who are using other VC systems already? Wouldn't it be better to add an interface to external VC systems? Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha at web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ---------------------------------------------------------------------------- From chuck at sharpsteen.net Wed Jun 22 00:16:36 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 21 Jun 2011 15:16:36 -0700 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: <19969.5134.953990.399574@zaphod.ms25.net> References: <4E003C70.6010507@swing.be> <4E004E18.1070602@swing.be> <19969.5134.953990.399574@zaphod.ms25.net> Message-ID: On Tue, Jun 21, 2011 at 2:58 PM, Reinhard Kotucha wrote: > > I've always felt that TeX is starting to lag behind other document > > preparation systems in the collaborative editing/review > > area. Microsoft Word has had "track changes" and other review > > systems for years. Apple just announced an Auto Save feature as > > part of OS X 10.7 that automatically tracks snapshots and allows > > one to browse the entire timeline of a document and drag document > > components back and forth between versions. We definitely have the > > tools to do similar things in the TeX world, but it is difficult to > > get an entire team of people to buy into them. Asking someone to > > learn TeX plus a version control system all at once can be a tough > > sell. If version control was built into the editor in a transparent > > fashion, it would be a lot easier for newcomers to deal with. > > People are using TeX with version control systems for decades. > It's Microsoft which always lags behind. > > If you add libgit to TeXworks, will this help if people collaborate > with others who are using other VC systems already? Wouldn't it be > better to add an interface to external VC systems? > > Regards, > Reinhard The people that I am thinking about are those that have never used TeX or a version control system before---often it is just too overwhelming for them to learn both things at once. If we leveraged something like libgit2 to add basic version control that is largely transparent to end users, say just commit, revert and diff, that seems like it would serve the purpose of "lowering the entry barrier to the TeX world". It could also make life easier for the one person on the team who knows how to use a version control system as they would be able to import changelogs rather than manually checking in all of the changes generated by their teammates. -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Wed Jun 22 00:49:08 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 22 Jun 2011 10:49:08 +1200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: <4E003C70.6010507@swing.be> <4E004E18.1070602@swing.be> <19969.5134.953990.399574@zaphod.ms25.net> Message-ID: Thanks, I'm very interested in the one, Bazaa, that Alain Delmotte has turned up for no other reason than it apparently allows varying degrees of integration into the other version control systems mentioned recently here (which I have used in the past) as welll. Looks like it is nicely .py and truly natively cross platform. And it really is major with Canonical, yet is stand a lone personnel wise. I mean really major with Canonical ! What do others think? ANy experience with Bazaar? Paul On 22 June 2011 10:16, Charlie Sharpsteen wrote: > On Tue, Jun 21, 2011 at 2:58 PM, Reinhard Kotucha > wrote: > >> > I've always felt that TeX is starting to lag behind other document >> > preparation systems in the collaborative editing/review >> > area. Microsoft Word has had "track changes" and other review >> > systems for years. Apple just announced an Auto Save feature as >> > part of OS X 10.7 that automatically tracks snapshots and allows >> > one to browse the entire timeline of a document and drag document >> > components back and forth between versions. We definitely have the >> > tools to do similar things in the TeX world, but it is difficult to >> > get an entire team of people to buy into them. Asking someone to >> > learn TeX plus a version control system all at once can be a tough >> > sell. If version control was built into the editor in a transparent >> > fashion, it would be a lot easier for newcomers to deal with. >> >> People are using TeX with version control systems for decades. >> It's Microsoft which always lags behind. >> >> If you add libgit to TeXworks, will this help if people collaborate >> with others who are using other VC systems already? Wouldn't it be >> better to add an interface to external VC systems? >> >> Regards, >> Reinhard > > > The people that I am thinking about are those that have never used TeX or a > version control system before---often it is just too overwhelming for them > to learn both things at once. If we leveraged something like libgit2 to add > basic version control that is largely transparent to end users, say just > commit, revert and diff, that seems like it would serve the purpose of > "lowering the entry barrier to the TeX world". It could also make life > easier for the one person on the team who knows how to use a version control > system as they would be able to import changelogs rather than manually > checking in all of the changes generated by their teammates. > > -Charlie > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Wed Jun 22 01:26:41 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 21 Jun 2011 16:26:41 -0700 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: <4E003C70.6010507@swing.be> <4E004E18.1070602@swing.be> <19969.5134.953990.399574@zaphod.ms25.net> Message-ID: On Tue, Jun 21, 2011 at 3:49 PM, Paul A Norman wrote: > Thanks, > > I'm very interested in the one, Bazaa, that Alain Delmotte has turned up > for no other reason than it apparently allows varying degrees of > integration into the other version control systems mentioned recently here > (which I have used in the past) as welll. > > Looks like it is nicely .py and truly natively cross platform. > > And it really is major with Canonical, yet is stand a lone personnel wise. > I mean really major with Canonical ! > > What do others think? ANy experience with Bazaar? > > Paul > When choosing a version control system for a project, the first thing I think about is off-site hosting for a central repository since it is nice to always have access to a clone of the work no matter where I am and a backup no matter what happens at home. Documents and research papers are interesting in that some of them are likely to be private or access-restricted while others may be shared with others. Most repository hosts provide free accounts upon the condition that they be used to store material that is publicly available under open-source licenses and then make their money by charging for private repositories. Bitbucket, which works with Mercurial , is interesting in that it allows unlimited private repositories and charges based on the size of the team that has access to those private repos. If you like Python, Mercurial is also written in Python and used to manage the source code of Python its self. I have not used Bazaar for any personal projects, but to me the major selling point seems to be Launchpadwhich not only hosts repositories, but automatically builds and Linux packages and makes them available to package managers like apt. Of course, if you are comfortable setting up your own server to host a central repository it doesn't really matter which VCS you choose---go for the one that tickles your fancy. As long as the system you choose has support for dumping data to the 'git-fast-export' format, it will be easy to move projects to another system if you change your mind later. -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Wed Jun 22 03:26:49 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 22 Jun 2011 13:26:49 +1200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: <4E003C70.6010507@swing.be> <4E004E18.1070602@swing.be> <19969.5134.953990.399574@zaphod.ms25.net> Message-ID: Thanks Charlie, Some good helpful advice. I am thinking that as many of these systems accept command line instructions it may be possible to do it outside TeXworks?proper perhaps through Tw scripting leaving people free to use whatever versioning system they are already?familiar?and comfortable with. Perhaps scripts being provided to ease interaction with some of the more popular repository set ups?could?be a useful way forward? I think the point you make about making sure that whatever?set-up someone chooses to go with does allow export to one or more of the other main systems is worth focussing on. For now I'll probably look at possibilities with ?Bazaar when I get some time. Paul ... From?http://doc.bazaar.canonical.com/migration/en/why-switch-to-bazaar.html "Plays Well With Others "Bazaar?transparently?supports?foreign branches?for Subversion, Git and Mercurial repositories. This means you can use normal Bazaar clients and commands on these - special commands are generally not required! "See?our tutorial?for an introduction to using Bazaar as a Subversion client. As of Oct 2009, Git and Mercurial integration is less mature but rapidly progressing along the same lines. "...you can use?fast-export?to switch your code base across if and when another tool better meets your needs. "In short, choosing Bazaar is a very safe choice. Above all, it?s dead easy to use and suitable for?everyone?in your community/team, regardless of their role or platform of choice" On 22 June 2011 11:26, Charlie Sharpsteen wrote: > > On Tue, Jun 21, 2011 at 3:49 PM, Paul A Norman wrote: >> >> Thanks, >> I'm very?interested?in the one,?Bazaa,? that Alain Delmotte has turned up for no other reason than it apparently allows varying degrees of ?integration into the other version control ?systems mentioned recently here (which I have used in the past) as welll. >> Looks like it is?nicely?.py and?truly natively?cross platform. >> And it really is major with Canonical, yet is stand a lone personnel wise. >> I mean really major with Canonical ! >> What do others think? ANy experience with?Bazaar? >> Paul > > When choosing a version control system for a project, the first thing I think about is off-site hosting for a central repository since it is nice to always have access to a clone of the work no matter where I am and a backup no matter what happens at home. Documents and research papers are interesting in that some of them are likely to be private or access-restricted while others may be shared with others. Most repository hosts provide free accounts upon the condition that they be used to store material that is?publicly?available under open-source licenses and then make their money by charging for private repositories. Bitbucket, which works with?Mercurial, is interesting in that it allows unlimited private repositories and charges based on the size of the team that has access to those private repos. > If you like Python, Mercurial is also written in Python and used to manage the source code of Python its self. ?I have not used Bazaar for any personal projects, but to me the major selling point seems to be Launchpad which not only hosts repositories, but automatically builds and Linux packages and makes them available to package managers like apt. > Of course, if you are comfortable setting up your own server to host a central repository it doesn't really matter which VCS you choose---go for the one that tickles your fancy. ?As long as the system you choose has support for dumping data to the 'git-fast-export' format, it will be easy to move projects to another system if you change your mind later. > > -Charlie From chuck at sharpsteen.net Wed Jun 22 05:12:52 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 21 Jun 2011 20:12:52 -0700 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: <4E003C70.6010507@swing.be> <4E004E18.1070602@swing.be> <19969.5134.953990.399574@zaphod.ms25.net> Message-ID: On Tue, Jun 21, 2011 at 6:26 PM, Paul A Norman wrote: > Thanks Charlie, > > Some good helpful advice. > > I am thinking that as many of these systems accept command line > instructions it may be possible to do it outside TeXworks proper > perhaps through Tw scripting leaving people free to use whatever > versioning system they are already familiar and comfortable with. > This sounds like a great idea---better integration with version control systems would be a nice feature for TeXworks. However, I still think it could be beneficial to bake some sort of versioning system into TeXworks its self to provide functionality similar to what Word offers with a couple of menu items. This is due to two categories of past experiences that have been all to common for me when working on TeX documents in a team setting: - After arguing with the rest of your team and convincing them to install MikTeX/TeXLive/MacTeX/etc and give TeX a shot instead of doing the project in MS Word, everyone is already straining to learn a new system. The mere suggestion that collaboration be handled by downloading, installing, setting up and learning another tool (or multiple pieces of software for things like Mercurial that require Python to be installed) causes people to look at you like you just suggested that the team build a rocket ship and fly to the moon to gather cheese. - If the team spends a lot of time in a corporate or academic environment, they are likely working on machines that are locked down and managed by the local IT Gestapo. Getting additional software installed or configured properly to run off of every team member's USB stick can be a nightmare. Scripting support for external tools would be great for power users as it lets them have things exactly the way the like it. However, I think we could do something better for the newcomers who are already trying to wrap their head around TeX and just want some menu item or button that will "track changes" without having to install anything additional. -Charlie Perhaps scripts being provided to ease interaction with some of the > more popular repository set ups could be a useful way forward? > > I think the point you make about making sure that whatever set-up > someone chooses to go with does allow export to one or more of the > other main systems is worth focussing on. > > For now I'll probably look at possibilities with Bazaar when I get some > time. > > Paul ... > From > http://doc.bazaar.canonical.com/migration/en/why-switch-to-bazaar.html > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a.norman at gmail.com Wed Jun 22 08:54:17 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 22 Jun 2011 18:54:17 +1200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: <4E003C70.6010507@swing.be> <4E004E18.1070602@swing.be> <19969.5134.953990.399574@zaphod.ms25.net> Message-ID: Good points. May be Tw could foster a "TeX Toolset Suite" concept - which would make things easier for Administrators to see what works together safely. I'm not too fussed ... ... I just like the idea of not reinventing the wheel if there is one to go on the wagon, all set up already! (So I'm presenting from that basis here) ... Saves primary developer time for even more important or core Tw Road Map needs. Perhaps a Tw Scripting effort into this (below) would give Tw menu items (and with the planned road map, buttons and so on) without the User needing to possibly do anything more than download and set up Bazaar - within the gambit of a TeXworks recommended "TeX Toolset Suite" concept. For example JabRef has a port which applications like Tw can "talk" to it on, and easily sets up to paste LaTeX into TeXworks already I think. Flying a Kite here ... Maybe likewise it would be cool of other applications could "talk" to Tw on a port, and invoke recommended scripts, or pass their short cut key combos in. Back to versioning... Scripts attached to menus and buttons or even a Tw Script User Interface ( http://twscript.paulanorman.com/docs/html/TexWorksQtScripting.htm?DialogueScripts.html ), would make the whole Bazaar versioning thing seem seemless to Users if they did not want to be hands on. Preconfigure a Tw repository under /config perhaps? And/Or - "Our cross-platform GUI application is powerful enough that experts can spend most of their time in it, while being simple enough for casual users to feel comfortable." I looked into the Bazaar dependencies issue as I also think that there really is a point about users not wanting to get involved with it more than necessary. Apparently for the following distributions everything needed is bundled in - no python etc worries for Users. Windows, Red Hat, FreeBSD, Ubuntu, openSUSE, Solaris, Debian, Mandriva, AIX, Fedora, Gentoo, HP-UX, Mac OS X, Slackware, PC-BSD, gNewSense GNU/Linux, Trisquel, GNU/Linux, Exherbo, and even N800 Bzr 1.1 debs If in the extremely unlikely event it is actually necessary, might even still be faster and less time to fashion a Tw collection/distribution of it, or at least direct links to the necessary area. I am not uncomfortable with people getting Administrator clearance for necessary tools, especially if say Tw was profiling a "TeX Toolset Suite" concept, Administrators could quickly see what was wanted. I think that something like the text diffing application at http://winmerge.org/ I mentioned before is a great help. Also Qt based for their cross platform development. And perhaps JabRef http://jabref.sourceforge.net/ May be it is necessary to directly integrate these sorts of tools into the TeXworks code base as has been done with Poppler previewing ... - However I do think it would be good not to have to, make Tw code maintainence much easier if capable OpenSource projects could be relied on to maintain their aspects of a "TeX Toolset Suite" which Tw could foster and interrelate with perhaps? "Version Control for Everyone "We take great pride in making Bazaar easy to learn, easy to use and suitable for everyone, not just elite hackers. For example: "Our cross-platform GUI application is powerful enough that experts can spend most of their time in it, while being simple enough for casual users to feel comfortable. "In the command line tool, online help is provided for every command. http://doc.bazaar.canonical.com/migration/en/why-switch-to-bazaar.html Paul On 22 June 2011 15:12, Charlie Sharpsteen wrote: > On Tue, Jun 21, 2011 at 6:26 PM, Paul A Norman > wrote: >> >> Thanks Charlie, >> >> Some good helpful advice. >> >> I am thinking that as many of these systems accept command line >> instructions it may be possible to do it outside TeXworks?proper >> perhaps through Tw scripting leaving people free to use whatever >> versioning system they are already?familiar?and comfortable with. > > This sounds like a great idea---better integration with version control > systems would be a nice feature for TeXworks. However, I still think it > could be beneficial to bake some sort of versioning system into TeXworks its > self to provide functionality similar to what Word offers with a couple of > menu items. This is due to two categories of past?experiences?that have been > all to common for me when working on TeX documents in a team setting: > ? - After arguing with the rest of your team and convincing them to install > MikTeX/TeXLive/MacTeX/etc and give TeX a shot instead of doing the project > in MS Word, everyone is?already?straining to learn a new system. The mere > suggestion that collaboration be handled by downloading, ?installing, > setting up and learning another tool (or multiple pieces of software for > things like Mercurial that require Python to be installed) causes people to > look at you like you just suggested that the team build a rocket ship and > fly to the moon to gather cheese. > ? - If the team spends a lot of time in a corporate or academic environment, > they are likely working on machines that are locked down and managed by the > local IT Gestapo. Getting additional software installed or configured > properly to run off of every team member's USB stick can be a nightmare. > > Scripting support for external tools would be great for power users as it > lets them have things?exactly?the way the like it. ?However, I think we > could do something better for the newcomers who are?already?trying to wrap > their head around TeX and just want some menu item or button that will > "track changes" without having to install anything additional. > -Charlie > >> Perhaps scripts being provided to ease interaction with some of the >> more popular repository set ups?could?be a useful way forward? >> >> I think the point you make about making sure that whatever?set-up >> someone chooses to go with does allow export to one or more of the >> other main systems is worth focussing on. >> >> For now I'll probably look at possibilities with ?Bazaar when I get some >> time. >> >> Paul ... >> >> From?http://doc.bazaar.canonical.com/migration/en/why-switch-to-bazaar.html > From paul.a.norman at gmail.com Wed Jun 22 11:56:39 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 22 Jun 2011 21:56:39 +1200 Subject: [texworks] Document Version-ing and synctex Previewing In-Reply-To: References: Message-ID: This is what foxed me, these $fullname variables are not in the manual but in the wiki and it is referenced at the back of the manual under Beyond this Manual which points to http://code.google.com/p/texworks/wiki/AdvancedTypesettingTools for this topic. Is it worth having some of this stuff (or the stable elements of it) directly in the manual perhaps, or Table of contents pointing to even just the links, and in the index? Paul On 21 June 2011 14:20, Paul A Norman wrote: > Ok, > So when using > ? ? %& -job-name=These-Fair-Isles > ?in the source,??if you directly manually open your output pdf in the Tw > viewer, you can of course sync back to the source no problem, synctex knows > the real source file name even though the produced .pdf has a different > name. > .. its syncing the other way which is the problem source -> preview, I think > this would be an editor (Tw) specific. > For current needs though, I'll just?probably try to?hook in on?the?TypeSet > hook form script, and do a silent virtual auto saveAs using a version > or?time-stamp?as part of the?file name, perhaps into a subdirectory, and > leave the main document always with the same name.and consequent .pdf name > for syncing. > Basically?mean?that there'll be an?auto-backup?each time the document is > typeset. As .tex are really comaparitively quite small, ?this is quite good > - could look at zipping as part of it. > But antway, having researched this ... > I see some very?interesting?switches for the Typeset command settings in > preferences > in > --http://www.google.com/codesearch#TCAOwTxChU8/trunk/src/TeXDocument.cpp&q=synctexoption%20package:http://texworks%5C.googlecode%5C.com&l=2464 > > if (!synctexSupported) > args.removeAll("$synctexoption"); > > args.replaceInStrings("$synctexoption", "-synctex=1"); > args.replaceInStrings("$fullname", fileInfo.fileName()); > args.replaceInStrings("$basename", > fileInfo.completeBaseName()); > args.replaceInStrings("$suffix", fileInfo.suffix()); > args.replaceInStrings("$directory", > fileInfo.absoluteDir().absolutePath > > And was wondering about the?general?options for use in > Edit/Preferences/Typesetting and setting Processing Tools up, or editing > existing ones. > > I see $filename used there a bit, > > What other?options?are there please? Obviously $basename, $suffix, > $directory as well. > > I can look?these?up in Qt I suppose according to fileInfo.. as shown above. > > Can these be combined with straight ascii/utf8 when > editing?Edit/Preferences/Typesetting and setting Processing Tools? > > And what other switches are built in please, good to know especially when > adding exotic toolsets to processing tools. > > Paul > > > > > Tw obviously picks up the document name changes .tex to .pdf an endeavours > to scntex from source to that .pdf > So looking inside the generated > Paul > > > On 20 June 2011 11:40, Paul A Norman wrote: >> >> Thanks for the suggestions Charlie, >> >> We have a reasonable mirroring operation in place covering both local >> and external storage. >> >> The reason for version numbering the documents is that it fits in with >> our local setup, and makes restoration of any lost text, through local >> diffing with Win-merge fast and effective, (opensource >> http://winmerge.org/ hopefully soon to be corss-platform >> https://bitbucket.org/grimmdp/winmerge ) . >> >> What I'm looking for is a way to tell TeXworks which pdf to use for >> syncing with the source text. >> >> Paul >> >> >> >> On 20 June 2011 11:27, Charlie Sharpsteen wrote: >> > On Sun, Jun 19, 2011 at 4:07 PM, Paul A Norman >> > wrote: >> >> Hi, >> >> >> >> For security of work, I both sync the files to storage(-s), and >> >> manually version number my .tex document(s) from time to time (one >> >> long monolithic) - not any version-ing on includes or like to worry >> >> about here. >> >> >> >> E.g. >> >> >> >> These-Fair-Isles-01.tex >> >> These-Fair-Isles-02.tex >> >> These-Fair-Isles-03.tex >> >> >> >> And use a document pre-header of ... >> >> >> >> ? ? %& -job-name=These-Fair-Isles >> >> >> >> Which nicely, under MiKTeX at least, makes the pdf as: >> >> ? ? ?These-Fair-Isles.pdf >> >> and keeps it that way no matter what my document name version number >> >> is. >> >> >> >> This means that the current document can always be linked to, and >> >> there is no obsolete .pdf garbage collection needed, >> >> ?i.e. no great list of These-Fair-Isles-01.pdf, >> >> These-Fair-Isles-02.pdf, These-Fair-Isles-03.pdf ... pdfs ?to be >> >> cleaned up later. >> >> >> >> (All the .aux files etc nicely show up for deletion on File/Remove Aux >> >> Files) >> >> >> >> Is there any setting I can put in the document to tell syntax to work >> >> on the document named in the top most header, >> >> >> >> ? ? %& -job-name=These-Fair-Isles >> >> >> >> Or is there a similar command line I can include in the top of the >> >> document's header, so that Tw synctex preview will work please? >> >> >> >> I.e. I would be working say at the moment in These-Fair-Isles-11.tex >> >> (or what ever) >> >> but always previewing ?and syncing to These-Fair-Isles.pdf >> >> >> >> Paul >> > >> > Have you considered using a version control system such as Git, >> > Mercurial or SVN? Then you would just have one copy, >> > These-Fair-Isles.tex, and the ability to rewind to any prior version. >> > Plus, distributed systems like Git and Mercurial offer even more >> > security of work by allowing you to easily mirror your documents >> > across multiple computers in case the proverbial bolt of lightning >> > strikes your main machine. >> > >> > -Charlie >> > >> > > > From ramsey at math.hawaii.edu Thu Jun 23 06:54:03 2011 From: ramsey at math.hawaii.edu (ramsey at math.hawaii.edu) Date: Wed, 22 Jun 2011 18:54:03 -1000 (HST) Subject: [texworks] including a graphics eps file under the default installation Message-ID: <3685.128.171.50.51.1308804843.squirrel@kahuna.math.hawaii.edu> Dear Colleagues, Somehow, pdfLaTeX can't find my graphics file, even though it is in the same directory as the tex file that I'm creating. Here is the error message ! LaTeX Error: File `MSATvsFE5' not found. See the LaTeX manual or LaTeX Companion for explanation. Type H for immediate help. ... l.107 \includegraphics{MSATvsFE5} I've recently installed miktek2.8 on a Windows machine. Tom From henrikmidtiby at gmail.com Thu Jun 23 07:11:51 2011 From: henrikmidtiby at gmail.com (Henrik Skov Midtiby) Date: Thu, 23 Jun 2011 07:11:51 +0200 Subject: [texworks] including a graphics eps file under the default installation In-Reply-To: <3685.128.171.50.51.1308804843.squirrel@kahuna.math.hawaii.edu> References: <3685.128.171.50.51.1308804843.squirrel@kahuna.math.hawaii.edu> Message-ID: Hi Pdflatex does not support eps files, you should instead use graphics in either pdf, png or jpg files. Best regards, Henrik On 23 June 2011 06:54, wrote: > Dear Colleagues, > > Somehow, pdfLaTeX can't find my graphics file, even though it is in the > same directory as the tex file that I'm creating. > > Here is the error message > > ! LaTeX Error: File `MSATvsFE5' not found. > > See the LaTeX manual or LaTeX Companion for explanation. > Type ?H ?for immediate help. > ?... > > l.107 \includegraphics{MSATvsFE5} > > I've recently installed miktek2.8 on a Windows machine. > > Tom > From paul.a.norman at gmail.com Thu Jun 23 08:34:15 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Thu, 23 Jun 2011 18:34:15 +1200 Subject: [texworks] Scripting: TW.result and TW.target.consoleOutput Message-ID: HI, I have been reading through Issues, latexErrors,js and the Wiki, trying to glean how these operate please. var message = "
Progress Copy Completed:
" + fileDetail + "
"; TW.result = message; TW.result can receive an array? "texworks:" + filePath ... ... as an References: <4DF064B4.2070305@gmail.com> <4DF1CA43.8030502@swing.be> <4DF4C7CF.7020208@gmail.com> <4E0037F6.5030101@gmail.com> Message-ID: Hi Stefan, I was away for a few days, catching up with my mail now... On 21 June 2011 07:19, Stefan L?ffler wrote: > > PS: How about the schedule for the release? If the line-mangling issue > is finally fixed now, I'll release Tw 0.4.2 soon (waiting for > confirmation ATM). But if not, do you suggest releasing another version > without that issue fixed by any particular date? I would say the sooner, the better (Karl wants to be ready for release by the end of this month, I Cc him to this message), even if some minor issues are not fixed. Otherwise, TL will be released with what we have now (TW 0.4.1), which would be unfortunate, since it doesn't work on vanilla systems. Please, let me know ASAP whether and when you could release, so we can decide what to do. I would rather want to avoid putting 0.4.1 on DVD, because people will keep reporting broken TW for a whole year ;) (Karl, FYI, the issue is that TW 0.4.1 uses python compiled with MS toolchain and so requires appropriate runtime libs (msvcrXX.dll stuff), which are not installed by default.) Thanks (and sorry for the pressure), Tomek From st.loeffler at gmail.com Thu Jun 23 18:38:34 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 23 Jun 2011 18:38:34 +0200 Subject: [texworks] including a graphics eps file under the default installation In-Reply-To: <3685.128.171.50.51.1308804843.squirrel@kahuna.math.hawaii.edu> References: <3685.128.171.50.51.1308804843.squirrel@kahuna.math.hawaii.edu> Message-ID: <4E036C0A.7050108@gmail.com> Hi, On 2011-06-23 06:54, ramsey at math.hawaii.edu wrote: > Somehow, pdfLaTeX can't find my graphics file, even though it is in the > same directory as the tex file that I'm creating. please have a look at http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdftexgraphics pdfLaTeX doesn't support eps by default, but there are packages to work around that (e.g., epstopdf). HTH, Stefan PS: Alternatively, if you've used a previous workflow that supported eps directly before (e.g., tex -> dvi -> pdf), have a look at http://code.google.com/p/texworks/wiki/AdvancedTypesettingTools to see if/how to use that workflow in TeXworks. From st.loeffler at gmail.com Thu Jun 23 18:58:33 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 23 Jun 2011 18:58:33 +0200 Subject: [texworks] Scripting: TW.result and TW.target.consoleOutput In-Reply-To: References: Message-ID: <4E0370B9.20500@gmail.com> Hi, On 2011-06-23 08:34, Paul A Norman wrote: > I have been reading through Issues, latexErrors,js and the Wiki, > trying to glean how these operate please. > > var message = "
Progress Copy Completed:
href=\"texworks:" + fileDetail + "\">" + fileDetail + "
/>"; > > TW.result = message; > > TW.result can receive an array? TW.result in principle can receive any supported data, including arrays, or even objects, windows, ... For the AfterTypeset hook, however, only strings are used (i.e., whatever you put in there will be converted to a string internally (TeXDocument.cpp l.2632)). This has changed a bit over time (in some previous versions, arrays were supported separately, but this is no longer necessary). > "texworks:" + filePath ... > > ... as an the document in Tw editor. Yes, _if_ TW.result starts with "" (see TeXDocument.cpp l.2633). In that case, the return value is interpreted as html (or a subset of it, anyway), so " TW.result = message; > In a hook script this automatically opens a console panel by the name > of the Script Title, but nothing seems to happen in stanadalones Yes, TW.result was introduced precisely for the purpose to pass data from a script back to Tw. Of course, this only makes sense if Tw called the script for a particular reason of its own. This is the case for hook scripts, but not for standalone scripts (for which Tw just passes on the user's wish to run the script, but doesn't know what the script does or what data it might return). In fact, I think at the moment the AfterTypeset hook is the only one that actually uses TW.result (if it's non-empty, a new console tab is opened to display its contents - see TeXDocument.cpp l.2638). > And can TW.result = " ..... etc"; > > ... be put in a function or must it be the last statement in a script? No, you can put this anywhere you want. Alternatively, you can put the string as last statement instead of "undefined;" to implicitly set TW.result. > Can TW.target.consoleOutput be assigned to from a script? No, it is read-only (TeXDocument.h l.114). You can only open additional tabs in the AfterTypeset hook. HTH Stefan From st.loeffler at gmail.com Thu Jun 23 19:02:53 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Thu, 23 Jun 2011 19:02:53 +0200 Subject: [texworks] where does python27.dll come from? In-Reply-To: References: <4DF064B4.2070305@gmail.com> <4DF1CA43.8030502@swing.be> <4DF4C7CF.7020208@gmail.com> <4E0037F6.5030101@gmail.com> Message-ID: <4E0371BD.1050001@gmail.com> Hi, On 2011-06-23 11:13, T T wrote: > On 21 June 2011 07:19, Stefan L?ffler wrote: >> PS: How about the schedule for the release? If the line-mangling issue >> is finally fixed now, I'll release Tw 0.4.2 soon (waiting for >> confirmation ATM). But if not, do you suggest releasing another version >> without that issue fixed by any particular date? > I would say the sooner, the better (Karl wants to be ready for release > by the end of this month, I Cc him to this message), even if some > minor issues are not fixed. Otherwise, TL will be released with what > we have now (TW 0.4.1), which would be unfortunate, since it doesn't > work on vanilla systems. Please, let me know ASAP whether and when > you could release, so we can decide what to do. I would rather want > to avoid putting 0.4.1 on DVD, because people will keep reporting > broken TW for a whole year ;) OK. If nothing else comes up, I intend to release 0.4.2 on the weekend. Note, though, that the python problem is not a code problem, but only a build problem, so for this it would suffice to produce a 0.4.1build2 or something. But there still is the (now hopefully resolved?) crash/mangled line numbers issue that should be fixed if at all possible (otherwise, people will complain about Tw crashing without apparent reason for a whole year ;)). BTW (hopefully) only out of curiosity: how does TL handle (security) updates to "external"/binary programs like Tw? Cheers, Stefan From chuck at sharpsteen.net Thu Jun 23 20:03:08 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 23 Jun 2011 11:03:08 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4DF726D5.4020503@gmail.com> References: <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> <4DF726D5.4020503@gmail.com> Message-ID: On Tue, Jun 14, 2011 at 2:16 AM, Stefan L?ffler wrote: >> So, unless anyone has some good ideas on how to add fallback support >> to the Quartz font handler, we may be back to the question of "should >> we implement native mac fonts or just use Fontconfig?" > > FWIW, Tw and evince on Linux (both using poppler+fontconfig) show the > file properly, whereas Adobe Acrobat complains about missing language > supports and only displays dots... > What font is substituted by Fontconfig, anyway? Is there any obvious > relation to the requested font? Fontconfig uses `MS Gothic`, which I would never suspect to contain CJK glyphs. Dohyun noted that the glyphs used are correct, although they are sans-serif when a serif family would be the correct substitution. Interesting to note is that Preview (the standard OS X PDF viewer) appears to render the font correctly while TeXshop (which uses Apple's PDFKit library) shows gibberish. >> The only downside that I have found with Fontconfig is that users >> won't see non-embedded fonts unless their copy of OS X has X11 >> installed. X11 is installed by default in OS X 10.5.x and 10.6.x, but >> could be missing if the user customized their installation and >> optimized for size. Not sure what the situation is for 10.7, but I >> guess we will find out next month. > > Could be take a similar approach to the one on Windows? There, poppler > is patched such that it looks for fonts in a subdirectory alongside the > main binary. That way, important base fonts (all, or just a subset as > for Windows which doesn't come with a suitable ZapfDingbats) can be > provided by the TeXworks application. To quote the PDF standard: "these > [14 base] fonts, or their font metrics and suitable substitution fonts, > must be available to the consumer application." > I don't know how this fits into the bundling-of-apps scheme, though. > > -Stefan I guess we could do something like that---but I have absolutely no idea what a suitable selection of CJK fonts would be. Seems like it could be much easier to let Fontconfig find system fonts. Users could also override its choices using a Fonconfig configuration file. I don't really know where to go from here---keep Fontconfig or move to Quartz? Note that: - Fontconfig-based build will still run on systems without X11 installed, it just won't be able to display non-embedded fonts. - X11 is installed by default for Leopard and Snow Leopard. No idea about the upcoming Lion release next month, I would assume it is still there but can't say for sure. If anyone in the OS X developer program can comment without violating a non disclosure agreement, that would be awesome ;) From jfkthame at googlemail.com Thu Jun 23 20:14:55 2011 From: jfkthame at googlemail.com (Jonathan Kew) Date: Thu, 23 Jun 2011 19:14:55 +0100 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> <4DF726D5.4020503@gmail.com> Message-ID: <74397209-E189-4173-B273-B01AECCCD611@gmail.com> On 23 Jun 2011, at 19:03, Charlie Sharpsteen wrote: > On Tue, Jun 14, 2011 at 2:16 AM, Stefan L?ffler wrote: >>> So, unless anyone has some good ideas on how to add fallback support >>> to the Quartz font handler, we may be back to the question of "should >>> we implement native mac fonts or just use Fontconfig?" >> >> FWIW, Tw and evince on Linux (both using poppler+fontconfig) show the >> file properly, whereas Adobe Acrobat complains about missing language >> supports and only displays dots... >> What font is substituted by Fontconfig, anyway? Is there any obvious >> relation to the requested font? > > Fontconfig uses `MS Gothic`, which I would never suspect to contain > CJK glyphs. Dohyun noted that the glyphs used are correct, although > they are sans-serif when a serif family would be the correct > substitution. I'm not at all sure the TeXworks PDF viewer should be doing font substitutions like this. If I'm using TeX to typeset documents, I expect precise control over the final appearance, and I expect the viewer to accurately reflect this. Doing font substitution means that the preview of the typeset document may bear little resemblance to the output I'll get back from the printshop (for example), or the view that another user (with different local fonts) will see. That's not what TeX and PDF are designed for. If I wanted that behavior, I'd write a Word or HTML document. JK From chuck at sharpsteen.net Thu Jun 23 20:25:57 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 23 Jun 2011 11:25:57 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <74397209-E189-4173-B273-B01AECCCD611@gmail.com> References: <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> <4DF726D5.4020503@gmail.com> <74397209-E189-4173-B273-B01AECCCD611@gmail.com> Message-ID: On Thu, Jun 23, 2011 at 11:14 AM, Jonathan Kew wrote: > On 23 Jun 2011, at 19:03, Charlie Sharpsteen wrote: > > > On Tue, Jun 14, 2011 at 2:16 AM, Stefan L?ffler > wrote: > >>> So, unless anyone has some good ideas on how to add fallback support > >>> to the Quartz font handler, we may be back to the question of "should > >>> we implement native mac fonts or just use Fontconfig?" > >> > >> FWIW, Tw and evince on Linux (both using poppler+fontconfig) show the > >> file properly, whereas Adobe Acrobat complains about missing language > >> supports and only displays dots... > >> What font is substituted by Fontconfig, anyway? Is there any obvious > >> relation to the requested font? > > > > Fontconfig uses `MS Gothic`, which I would never suspect to contain > > CJK glyphs. Dohyun noted that the glyphs used are correct, although > > they are sans-serif when a serif family would be the correct > > substitution. > > I'm not at all sure the TeXworks PDF viewer should be doing font > substitutions like this. If I'm using TeX to typeset documents, I expect > precise control over the final appearance, and I expect the viewer to > accurately reflect this. Doing font substitution means that the preview of > the typeset document may bear little resemblance to the output I'll get back > from the printshop (for example), or the view that another user (with > different local fonts) will see. That's not what TeX and PDF are designed > for. If I wanted that behavior, I'd write a Word or HTML document. > > JK > That makes sense to me. However the core problem that came up with the switch to Quartz seems to be that pTeX does not embed fonts. Should strict interpretation of document fonts take precedence over usability for non-english speakers? Also worth noting is that TeXworks uses Fontconfig on Linux so we have already crossed this line to some degree. -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Thu Jun 23 20:31:11 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Thu, 23 Jun 2011 11:31:11 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DE0AE1B.8040705@gmail.com> <4DE20671.7090102@gmail.com> <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> <4DF726D5.4020503@gmail.com> <74397209-E189-4173-B273-B01AECCCD611@gmail.com> Message-ID: On Thu, Jun 23, 2011 at 11:25 AM, Charlie Sharpsteen wrote: > Should strict interpretation of document fonts take precedence over > usability for non-english speakers? > I suppose another approach would be to use Quartz for font discovery, but then fall back on Fontconfig (if available) for better fallback suggestions than "Helvetica". Or is that just crazy talk? -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From kakuto at fuk.kindai.ac.jp Fri Jun 24 00:08:05 2011 From: kakuto at fuk.kindai.ac.jp (Akira Kakuto) Date: Fri, 24 Jun 2011 07:08:05 +0900 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: Message-ID: <130886688526343700007ba8@sniffer> Dear Charlie, > That makes sense to me. However the core problem that came up with the > switch to Quartz seems to be that pTeX does not embed fonts. Should strict > interpretation of document fonts take precedence over usability for > non-english speakers? Also worth noting is that TeXworks uses Fontconfig on > Linux so we have already crossed this line to some degree. In order to embed fonts in pTeX, rewrite the file texmf/fonts/map/dvipdfmx/cid-x.map as follows, for example: %% %% ASCII pTeX Examples %% %% Ryumin and GothicBBB found in PostScript printers: rml H Ryumin-Light gbm H GothicBBB-Medium rmlv V Ryumin-Light gbmv V GothicBBB-Medium ----> change the above like %% %% ASCII pTeX Examples %% %% embed Hiragino fonts: rml H HiraMinProN-W3.otf gbm H HiraKakuProN-W6.otf rmlv V HiraMinProN-W3.otf gbmv V HiraKakuProN-W6.otf Best, Akira From paul.a.norman at gmail.com Fri Jun 24 00:48:29 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Fri, 24 Jun 2011 10:48:29 +1200 Subject: [texworks] line numbers Merge and text disappears In-Reply-To: References: <4DFEFCFA.5090904@marris.fr> <4E00358F.5020409@gmail.com> Message-ID: Hi, >> I had another inspiration. Please test r845 or later - hopefully that >> fixes this issue finally. I've been putting a lot of work through on Tw r846 (aware of TeXLive coming up also) and have the `sense' - what else can you say with a fickle problem - that this might be much improved if not actually solved. Scrolling the document also seems smoother, and also resizing the edit window is smoother, and wordwrap happens more evenly and looks better with a bigger margin at the right perhaps? Previously resizing the window gave you the sense of a micro jagged effect, not smooth by comparison with how smoothly it now happens. Will continue testing. Paul On 21 June 2011 18:51, Paul A Norman wrote: > > > On 21 June 2011 18:09, Stefan L?ffler wrote: >> >> Hi, >> >> On 2011-06-20 11:22, Paul A Norman wrote: >> > I'm on v0.5 r804(official), what (Menu://Help/About TeXworks) version >> > are you on please? >> >> I had another inspiration. Please test r845 or later - hopefully that >> fixes this issue finally. > > Thanks, will do, noticed also that sometimes the cursor gets lost at the end > of the line, and you have to click in the document elsewhere to regain it. >> >> > Not sure if it is safe for text integrity to ignore it, and keep >> > editing, one of the reasons I keep local version numbers of source >> > documents. >> >> >From what I've seen so far, text integrity should not be affected - it >> seems to be a problem with rendering the text only. But then again, >> there might be more to it than meets the eye. > > One of the dangers has been ?not realising/noticing the line jumble up and > that text has disappeared/hidden, and retyping or reinserting things (text > graphics figures etc) and then later finding your document with double ups > or old edits of text. > That's one of the first reasons I have become so keen on local versioning as > I go. > Have made a hook script?which?prompts to save a date time?stamped?file name > copy for the current document (same directory) after each typeset. (How does > latexErrors.js know to not kick in after a non .tex typeset like a > bibliography?) > Looks like this in the dir listing: > ??These-fair-Isles-2011-06-21--18-11-53.tex > So they appear together in time sequence by name in the?directory?listing , > and can so be zipped up and away en-block. > Let me know if any one is?interested?and I'll try and put the script up. > Paul > > >> >> HTH >> Stefan > > From t34www at googlemail.com Fri Jun 24 10:42:05 2011 From: t34www at googlemail.com (T T) Date: Fri, 24 Jun 2011 09:42:05 +0100 Subject: [texworks] where does python27.dll come from? In-Reply-To: <4E0371BD.1050001@gmail.com> References: <4DF064B4.2070305@gmail.com> <4DF1CA43.8030502@swing.be> <4DF4C7CF.7020208@gmail.com> <4E0037F6.5030101@gmail.com> <4E0371BD.1050001@gmail.com> Message-ID: On 23 June 2011 18:02, Stefan L?ffler wrote: > > OK. If nothing else comes up, I intend to release 0.4.2 on the weekend. Thanks. > Note, though, that the python problem is not a code problem, but only a > build problem, so for this it would suffice to produce a 0.4.1build2 or Sure. > something. But there still is the (now hopefully resolved?) > crash/mangled line numbers issue that should be fixed if at all possible > (otherwise, people will complain about Tw crashing without apparent > reason for a whole year ;)). Of course bug-fixed release would be better, so if that's available in time, we'll take it ;) > BTW (hopefully) only out of curiosity: how does TL handle (security) > updates to "external"/binary programs like Tw? The usual way, through tlmgr update. In fact, TW 0.4.1 has been already pushed out in TL'10 before the freeze. Cheers, Tomek From nishni_nowgorod at gaponline.de Sat Jun 25 15:25:54 2011 From: nishni_nowgorod at gaponline.de (Andreas Hirsch) Date: Sat, 25 Jun 2011 15:25:54 +0200 Subject: [texworks] TL2011 pretest on win7 Message-ID: <4E05E1E2.9090709@gaponline.de> Hi together, today I did a test on win7 prof. I changed the installation-directory for testing directories containing spaces. No problems there! Installation finished with any problems. I noticed that adding TL-bin to the Path is done by the installer. Some minor 'problems' - not concerning the 'main-TL': Supposing our win7-user didn't install any extracting program, the build-in is a little weak to see and to manage to extract a given local-texmf in the right hierarchy. To set up TeXWorks for latex-dvips-ps2pdf some extra work has to be done ... I tested compiling two files (pdflatex and latex-dvips-ps2pdf) - stored in a place containing spaces ;-) and also needing local sty-files: everything works smoothly! :) Thanks to everybody for the great affords you made to give aus TL2011! You will find a lot of screenshots here http://members.gaponline.de/afj/tl2011_pretest/ - feel free to use of suitable! (The command-line-box will not be needed in the final TL-installation, but for now the location has to be given) Andreas -- How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence? -- Peter Flynn -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 259 bytes Desc: OpenPGP digital signature URL: From st.loeffler at gmail.com Sun Jun 26 15:26:38 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 26 Jun 2011 15:26:38 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <4DF73915.10407@Rhul.Ac.Uk> References: <4DF4C003.7020908@Rhul.Ac.Uk> <4DF60E3F.1030104@gmail.com> <4DF65D53.1000207@Rhul.Ac.Uk> <4DF7222E.1030708@gmail.com> <4DF73915.10407@Rhul.Ac.Uk> Message-ID: <4E07338E.3010200@gmail.com> Hi, On 2011-06-14 12:33, Philip TAYLOR (Webmaster, Ret'd) wrote: > Stefan L?ffler wrote: > >> ah, sorry. It's "download from somewhere else", namely >> http://code.google.com/p/texworks/downloads/list where all the Tw >> binaries (for Windows, anyway) are uploaded. Arguably, frequent changes >> only happen to "experimental" builds, but in the phase we're in right >> now these are (almost) as stable as the "stable" releases. TL only takes >> stable releases, AFAIK (and doesn't upgrade them - but then again, all >> Tw stable releases have been made just in time for a new TL release so >> far ;)). CTAN doesn't host Tw, I think (or if it does, this is >> maintained by someone else). > > OK, understood. Unfortunately now a supplementary -- I have downloaded > TeXworks-w32-0.5-r844.zip and unzipped it using Filzip, but the > paths in it don't match a TeX Live 2010 configuration. Under TL 2010, > the binaries (such as TeXworks.exe) would be found in .../bin/win32/, > but there are no subdirectories under .../bin/win32/ so I do not > know where to place the four directories found in the ZIP file : > "fonts", "Lib", "poppler-data" and "texworks-help", nor am I sure > if "python27.dll" should also go in .../bin/win32/ Obviously > this is a generic packaging, not one tailored for TeX Live, but > I wonder where the elements other than the executable image > are intended to go ? The "README.txt" gives generic advice > ("Just extract the contents of the Zip file wherever you want > and then run the extracted TeXworks.exe.") but really I'd like > to put them where TeX Live would have put them during a normal > install. I had hoped that someone from the TL team would answer this question, but they are probably busy with the upcoming release. Anyway, I don't know how exactly things have been modified for TL, but chances are that it is sufficient to replace only the .exe in your case (there haven't been any changes to supplementary files, IIRC). Alternatively, you should be fine putting the whole content of the archive in some folder that is not in TL / the texmf tree and update your shortcuts (i.e., multiple instances of Tw should be able to run in parallel; very old versions may not work correctly with all settings, though). But on the other hand, you've deleted all autocompletion files now, anyway, so there's not that much point in putting too much effort into replacing the Tw executable. Plus, with TL'11 due soon, you'll get the latest updates, anyway :). HTH Stefan From st.loeffler at gmail.com Sun Jun 26 15:27:48 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 26 Jun 2011 15:27:48 +0200 Subject: [texworks] Unwanted side-effect of : how to avoid ? In-Reply-To: <3257E256-F51B-440C-ABC7-896DD098BB44@wideopenwest.com> References: <4DF4C003.7020908@Rhul.Ac.Uk> <3257E256-F51B-440C-ABC7-896DD098BB44@wideopenwest.com> Message-ID: <4E0733D4.2010008@gmail.com> Hi, On 2011-06-14 14:05, Herbert Schulz wrote: > Getting back to this original question... note that the TAB is pressed after a newline. Shouldn't a newline be a left hand terminator for a search term and since it's empty (i.e., nothing or white space) before the terminator a TAB should be entered? Yes, this has been fixed in r844. Cheers, Stefan From st.loeffler at gmail.com Sun Jun 26 15:32:18 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Sun, 26 Jun 2011 15:32:18 +0200 Subject: [texworks] TL2011 pretest on win7 In-Reply-To: <4E05E1E2.9090709@gaponline.de> References: <4E05E1E2.9090709@gaponline.de> Message-ID: <4E0734E2.3080106@gmail.com> Hi, On 2011-06-25 15:25, Andreas Hirsch wrote: > today I did a test on win7 prof. Thanks for testing :). > To set up TeXWorks for latex-dvips-ps2pdf some extra work has to be done ... Yes, this is sort of by design. By default, only pdf*tex is set up to encourage people to move to the new system, and to avoid confusion for new users (which would probably wonder what the different is if the outcome is pdf in all cases). Cheers, Stefan From st.loeffler at gmail.com Sun Jun 26 15:52:18 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 26 Jun 2011 15:52:18 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> <4DF726D5.4020503@gmail.com> <74397209-E189-4173-B273-B01AECCCD611@gmail.com> Message-ID: <4E073992.3050908@gmail.com> Hi, the way I see it, we have two requirements: 1) render embedded fonts correctly 2) support (at least) the 14 pdf base fonts even if not embedded I think (1) is fulfilled by poppler/freetype automatically (the Quartz vs. fontconfig issues only occur when setting up system fonts as replacements, right?). As for (2), the Quartz approach satisfies this by using system fonts, whereas fontconfig requires X11 fonts (which, however, seem to have become a sort of system fonts in recent OS Xs, anyway; if they don't - or there is a chance users don't have it - we should probably bundle the necessary font files with Tw, just to ensure we don't violate the PDF standard). Other than that, I don't think we have any strict requirements. In particular, I don't think the PDF standard mentions any other than the standard fonts anywhere (although I have to confess I haven't read all the 1300 something pages ;)). So, it is certainly nice to have good replacements, but not required. BTW: could it be that those fonts are available (and recognized properly) on CJK systems, anyway, and it's only non-CJK systems that require (and fail to find) suitable replacements? Likewise, the concern about fontconfig was that it can spam the file system, but apparently in recent versions this is no longer the case, either? So, all in all, I see two choices: bundle base-14 fonts (we do this partly for Windows as well), or drop good font substitution. I would tend to go with fontconfig here, for reasons of simple usability. But not being a Mac user this is nothing more than a gut feeling. Have I missed something? Jonathan, any thoughts? On 2011-06-23 20:31, Charlie Sharpsteen wrote: > On Thu, Jun 23, 2011 at 11:25 AM, Charlie Sharpsteen > > wrote: > > Should strict interpretation of document fonts take precedence > over usability for non-english speakers? > > > I suppose another approach would be to use Quartz for font discovery, > but then fall back on Fontconfig (if available) for better fallback > suggestions than "Helvetica". > > Or is that just crazy talk? Do you mean "(if available)" in the sense of: if installed (as a dynamic library of some sort) on the system? I guess bringing both systems to work together would be a lot of work... -Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Sun Jun 26 15:56:09 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Sun, 26 Jun 2011 15:56:09 +0200 Subject: [texworks] line numbers Merge and text disappears In-Reply-To: References: <4DFEFCFA.5090904@marris.fr> <4E00358F.5020409@gmail.com> Message-ID: <4E073A79.4010006@gmail.com> Hi, On 2011-06-24 00:48, Paul A Norman wrote: >>> I had another inspiration. Please test r845 or later - hopefully that >>> fixes this issue finally. > I've been putting a lot of work through on Tw r846 (aware of TeXLive > coming up also) and have the `sense' - what else can you say with a > fickle problem - that this might be much improved if not actually > solved. Thanks for testing :). Looking at the glass as being half-full, I decided that it was at least a significant improvement, so I made a 0.4.2 minor release out of it (and the other fixes we had since 0.4.1). > Scrolling the document also seems smoother, and also resizing the edit > window is smoother, and wordwrap happens more evenly and looks better > with a bigger margin at the right perhaps? > > Previously resizing the window gave you the sense of a micro jagged > effect, not smooth by comparison with how smoothly it now happens. I didn't change anything there, but I've updated Qt from 4.7.2 to 4.7.3 at some point (however I'm not sure when, unfortunately). So this could explain some of the usability enhancements... HTH Stefan From alain.delmotte at leliseron.org Tue Jun 28 08:38:52 2011 From: alain.delmotte at leliseron.org (Alain Delmotte) Date: Tue, 28 Jun 2011 08:38:52 +0200 Subject: [texworks] Problem with autocompletion Message-ID: <4E0976FC.1090109@leliseron.org> Hi! I encounter problems with the autocompletion system. If I type use[tab] I get \usepackage{} insertion between {} but then [tab] again: \usepackage[]{?} } insertion between [] and one more [tab] use]{?} } insertion after use So the system is not suppressing the characters after the insertion point. I had this with r843(?) and I installed 0.4.2 r852(official) with the same result. This breaks the ring use of completion; annoying. Regards, Alain From esperanto at swing.be Tue Jun 28 09:35:53 2011 From: esperanto at swing.be (Alain Delmotte) Date: Tue, 28 Jun 2011 09:35:53 +0200 Subject: [texworks] TL2011 pretest on win7 In-Reply-To: <4E0734E2.3080106@gmail.com> References: <4E05E1E2.9090709@gaponline.de> <4E0734E2.3080106@gmail.com> Message-ID: <4E098459.8070706@swing.be> Hi! Le 26/06/2011 15:32, Stefan L?ffler a ?crit : > Hi, > > On 2011-06-25 15:25, Andreas Hirsch wrote: >> today I did a test on win7 prof. > > Thanks for testing :). > >> To set up TeXWorks for latex-dvips-ps2pdf some extra work has to be done ... > > Yes, this is sort of by design. By default, only pdf*tex is set up to > encourage people to move to the new system, and to avoid confusion for > new users (which would probably wonder what the different is if the > outcome is pdf in all cases). OK I understand that, but many people are going to TeXworks with an existing background in (La)TeX, especially using eps figures and so need dvips... What are, in detail, the steps to compile, under TeXworks files with postscript commands? There are two, if I am not mistaken (latex-dvips-ps2pdf and straight pdflatex adding a package) but TeXworks has to be adapted in both cases. Further, are these solutions equivalent? I'll also be interested to pdflatex, biblatex, makeindex, pdflatex, pdflatex. How to achieve that? Regards, Alain From paul.a.norman at gmail.com Tue Jun 28 10:22:05 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Tue, 28 Jun 2011 20:22:05 +1200 Subject: [texworks] Problem with autocompletion In-Reply-To: <4E0976FC.1090109@leliseron.org> References: <4E0976FC.1090109@leliseron.org> Message-ID: HI, I can add that I have recently had some funny jumbles of text also, upon using auto-completion. Is this possibly due to fixing the issue? Paul On 28 June 2011 18:38, Alain Delmotte wrote: > Hi! > > I encounter problems with the autocompletion system. > > If I type > use[tab] > > I get > \usepackage{} > > insertion between {} > > > but then [tab] again: > \usepackage[]{?} > > } > > > insertion between [] > > > and one more [tab] > use]{?} > > } > > > insertion after use > > So the system is not suppressing the characters after the insertion point. > > I had this with r843(?) and I installed 0.4.2 r852(official) with the same > result. > > This breaks the ring use of completion; annoying. > > > Regards, > > > Alain > > > > > From joseph.wright at morningstar2.co.uk Tue Jun 28 10:46:48 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Tue, 28 Jun 2011 09:46:48 +0100 Subject: [texworks] TL2011 pretest on win7 In-Reply-To: <4E098459.8070706@swing.be> References: <4E05E1E2.9090709@gaponline.de> <4E0734E2.3080106@gmail.com> <4E098459.8070706@swing.be> Message-ID: <4E0994F8.0@morningstar2.co.uk> On 28/06/2011 08:35, Alain Delmotte wrote: > What are, in detail, the steps to compile, under TeXworks files with > postscript commands? > There are two, if I am not mistaken (latex-dvips-ps2pdf and straight > pdflatex adding a package) but TeXworks has to be adapted in both cases. > Further, are these solutions equivalent? With a modern TeX installation (which of course includes TL2011), pdfLaTeX automatically allows epstopdf to be run to convert any EPS graphics to PDF format for inclusion. So for graphic inclusion, there is nothing to do at the TeXworks end: it 'just works'. To run latex + dvips + ps2pdf you need a suitable script. There have been various discussions on this on the list (see for example the thread 'latex->dvips->ps2pdf on Windows', http://tug.org/mailman/htdig/texworks/2009q2/000819.html). The correct solution depends on the operating system, so it is not quite so straight forward. For example, on Windows one can write a small batch file to do the job. The key point, however, is that TeXworks is primarily aimed at new TeX users, for whom direct PDF output is likely to be the best approach. Experienced users may need to use DVI mode, but will also either (a) have a favoured editor or (b) be experienced enough to sort this out themselves. (Unless you are a heavy PStricks user then direct PDF output is normally okay for most people.) > I'll also be interested to pdflatex, biblatex, makeindex, pdflatex, > pdflatex. > How to achieve that? That needs something beyond TeX. MiKTeX has (pdf)texify for this purpose, and newer TeXLive's include latexmk, which again seeks to do the job. -- Joseph Wright From herbs at wideopenwest.com Tue Jun 28 14:19:16 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Tue, 28 Jun 2011 07:19:16 -0500 Subject: [texworks] TL2011 pretest on win7 In-Reply-To: <4E098459.8070706@swing.be> References: <4E05E1E2.9090709@gaponline.de> <4E0734E2.3080106@gmail.com> <4E098459.8070706@swing.be> Message-ID: On Jun 28, 2011, at 2:35 AM, Alain Delmotte wrote: > Hi! > > Le 26/06/2011 15:32, Stefan L?ffler a ?crit : >> Hi, >> >> On 2011-06-25 15:25, Andreas Hirsch wrote: >>> today I did a test on win7 prof. >> >> Thanks for testing :). >> >>> To set up TeXWorks for latex-dvips-ps2pdf some extra work has to be done ... >> >> Yes, this is sort of by design. By default, only pdf*tex is set up to >> encourage people to move to the new system, and to avoid confusion for >> new users (which would probably wonder what the different is if the >> outcome is pdf in all cases). > > OK I understand that, but many people are going to TeXworks with an existing background in (La)TeX, especially using eps figures and so need dvips... > > What are, in detail, the steps to compile, under TeXworks files with postscript commands? > There are two, if I am not mistaken (latex-dvips-ps2pdf and straight pdflatex adding a package) but TeXworks has to be adapted in both cases. > Further, are these solutions equivalent? > > I'll also be interested to pdflatex, biblatex, makeindex, pdflatex, pdflatex. > How to achieve that? > > Regards, > > Alain > Howdy, I'd suggest creating a latexmk tool which will take care of all of that, as well as run bibtex (or biber -- recent versions of latexmk will automatically choose) and/or makeindex automatically. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From herbs at wideopenwest.com Tue Jun 28 14:22:58 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Tue, 28 Jun 2011 07:22:58 -0500 Subject: [texworks] TL2011 pretest on win7 In-Reply-To: <4E0994F8.0@morningstar2.co.uk> References: <4E05E1E2.9090709@gaponline.de> <4E0734E2.3080106@gmail.com> <4E098459.8070706@swing.be> <4E0994F8.0@morningstar2.co.uk> Message-ID: <8A13D75D-8295-41DB-B122-9C50504617B5@wideopenwest.com> On Jun 28, 2011, at 3:46 AM, Joseph Wright wrote: > On 28/06/2011 08:35, Alain Delmotte wrote: >> What are, in detail, the steps to compile, under TeXworks files with >> postscript commands? >> There are two, if I am not mistaken (latex-dvips-ps2pdf and straight >> pdflatex adding a package) but TeXworks has to be adapted in both cases. >> Further, are these solutions equivalent? > > With a modern TeX installation (which of course includes TL2011), > pdfLaTeX automatically allows epstopdf to be run to convert any EPS > graphics to PDF format for inclusion. So for graphic inclusion, there is > nothing to do at the TeXworks end: it 'just works'. > ... Howdy, The side effect is that for each myfig.eps you also (unexpectedly) end up with a myfig-eps-converted-to.pdf which you don't have with the dvi->ps->pdf route. Also, depending upon the TeX distribution's setup that can be turned off; paranoid mode. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From joseph.wright at morningstar2.co.uk Tue Jun 28 14:40:35 2011 From: joseph.wright at morningstar2.co.uk (Joseph Wright) Date: Tue, 28 Jun 2011 13:40:35 +0100 Subject: [texworks] TL2011 pretest on win7 In-Reply-To: <8A13D75D-8295-41DB-B122-9C50504617B5@wideopenwest.com> References: <4E05E1E2.9090709@gaponline.de> <4E0734E2.3080106@gmail.com> <4E098459.8070706@swing.be> <4E0994F8.0@morningstar2.co.uk> <8A13D75D-8295-41DB-B122-9C50504617B5@wideopenwest.com> Message-ID: <4E09CBC3.7070002@morningstar2.co.uk> On 28/06/2011 13:22, Herbert Schulz wrote: > The side effect is that for each myfig.eps you also (unexpectedly) end up with a myfig-eps-converted-to.pdf which you don't have with the dvi->ps->pdf route. Also, depending upon the TeX distribution's setup that can be turned off; paranoid mode. Well, the naming is quite clear -:) There's a balance between this and compilation failing, and the later is not a great way to help newer users. So auto-conversion seems okay to me. (Of course, that is not actually a TeXworks issue per se.) On the 'turning off auto-convertion', that is again something well beyond the target audience for TeXworks. -- Joseph Wright From herbs at wideopenwest.com Tue Jun 28 14:57:43 2011 From: herbs at wideopenwest.com (Herbert Schulz) Date: Tue, 28 Jun 2011 07:57:43 -0500 Subject: [texworks] TL2011 pretest on win7 In-Reply-To: <4E09CBC3.7070002@morningstar2.co.uk> References: <4E05E1E2.9090709@gaponline.de> <4E0734E2.3080106@gmail.com> <4E098459.8070706@swing.be> <4E0994F8.0@morningstar2.co.uk> <8A13D75D-8295-41DB-B122-9C50504617B5@wideopenwest.com> <4E09CBC3.7070002@morningstar2.co.uk> Message-ID: <88686A64-ECAC-4CD0-90BD-168E6487A55D@wideopenwest.com> On Jun 28, 2011, at 7:40 AM, Joseph Wright wrote: > On 28/06/2011 13:22, Herbert Schulz wrote: >> The side effect is that for each myfig.eps you also (unexpectedly) end up with a myfig-eps-converted-to.pdf which you don't have with the dvi->ps->pdf route. Also, depending upon the TeX distribution's setup that can be turned off; paranoid mode. > > Well, the naming is quite clear -:) There's a balance between this and > compilation failing, and the later is not a great way to help newer > users. So auto-conversion seems okay to me. (Of course, that is not > actually a TeXworks issue per se.) > > On the 'turning off auto-convertion', that is again something well > beyond the target audience for TeXworks. > -- > Joseph Wright Howdy, I'm not sure how MikTeX has that set and admins may have set that variable to paranoid without user's knowing. Also, many folks are using older TeX distributions where the automatic conversion of eps doesn't work; the limited shell escape was first introduced in 2009. Good Luck, Herb Schulz (herbs at wideopenwest dot com) From chuck at sharpsteen.net Wed Jun 29 01:24:20 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Tue, 28 Jun 2011 16:24:20 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4E073992.3050908@gmail.com> References: <4DE22212.4070602@gmail.com> <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> <4DF726D5.4020503@gmail.com> <74397209-E189-4173-B273-B01AECCCD611@gmail.com> <4E073992.3050908@gmail.com> Message-ID: On Sun, Jun 26, 2011 at 6:52 AM, Stefan L?ffler wrote: > ** > Hi, > > the way I see it, we have two requirements: > 1) render embedded fonts correctly > 2) support (at least) the 14 pdf base fonts even if not embedded > > I think (1) is fulfilled by poppler/freetype automatically (the Quartz vs. > fontconfig issues only occur when setting up system fonts as replacements, > right?). > Yes, as far as I can tell Fontconfig/Quartz are only used to locate font files in cases where the document requires a font that is not embedded. > As for (2), the Quartz approach satisfies this by using system fonts, > whereas fontconfig requires X11 fonts (which, however, seem to have become a > sort of system fonts in recent OS Xs, anyway; if they don't - or there is a > chance users don't have it - we should probably bundle the necessary font > files with Tw, just to ensure we don't violate the PDF standard). > Fontconfig appears to use mostly system fonts with one or two X11 fonts thrown in. If the user does not have X11 installed, the main component that is missing are the Fontconfig configuration files that tell it where to find things. If we stuck with Fontconfig, a possible alternative to bundling the 14 required fonts would be to bundle a configuration file that tells Fontconfig where to locate system fonts. > Other than that, I don't think we have any strict requirements. In > particular, I don't think the PDF standard mentions any other than the > standard fonts anywhere (although I have to confess I haven't read all the > 1300 something pages ;)). > So, it is certainly nice to have good replacements, but not required. BTW: > could it be that those fonts are available (and recognized properly) on CJK > systems, anyway, and it's only non-CJK systems that require (and fail to > find) suitable replacements? > Likewise, the concern about fontconfig was that it can spam the file > system, but apparently in recent versions this is no longer the case, > either? > I didn't notice any "temp" files being accumulated on 10.5.x or 10.6.x. > So, all in all, I see two choices: bundle base-14 fonts (we do this partly > for Windows as well), or drop good font substitution. > > I would tend to go with fontconfig here, for reasons of simple usability. > But not being a Mac user this is nothing more than a gut feeling. > Have I missed something? Jonathan, any thoughts? > I'm leaning in the direction of sticking with Fontconfig as well. Mainly because although we have good Quartz support for the "base 14 fonts", they are very English-centric and Fontconfig appears to make better fallback and substitution choices for non-English languages. As a white boy from Alaska, I feel entirely unqualified to make these sorts of decisions :) However, I do need to know which library to build 0.4.2 against. -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From st.loeffler at gmail.com Wed Jun 29 07:55:10 2011 From: st.loeffler at gmail.com (=?UTF-8?B?U3RlZmFuIEzDtmZmbGVy?=) Date: Wed, 29 Jun 2011 07:55:10 +0200 Subject: [texworks] Problem with autocompletion In-Reply-To: <4E0976FC.1090109@leliseron.org> References: <4E0976FC.1090109@leliseron.org> Message-ID: <4E0ABE3E.3090205@gmail.com> Hi, On 2011-06-28 08:38, Alain Delmotte wrote: > So the system is not suppressing the characters after the insertion > point. > > I had this with r843(?) and I installed 0.4.2 r852(official) with the > same result. > > This breaks the ring use of completion; annoying. thanks for reporting, even though it is too late for 0.4.2 now. Oh well, seems we're heading for 0.4.3, then ;). BTW: it should not have appeared until r844 or later... Anyway, I think I fixed the problem in r855 - builds are uploading right now. Please test... Regards, Stefan PS: actually, the problem was more than just annoying, unfortunately. When doing something like "a b \doc", the beginning of the line (i.e., "a b ") was erased... From paul.a.norman at gmail.com Wed Jun 29 08:43:03 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 29 Jun 2011 18:43:03 +1200 Subject: [texworks] Problem with autocompletion In-Reply-To: <4E0ABE3E.3090205@gmail.com> References: <4E0976FC.1090109@leliseron.org> <4E0ABE3E.3090205@gmail.com> Message-ID: Yep r855 looking good. Paul On 29 June 2011 17:55, Stefan L?ffler wrote: > Hi, > > On 2011-06-28 08:38, Alain Delmotte wrote: >> So the system is not suppressing the characters after the insertion >> point. >> >> I had this with r843(?) and I installed 0.4.2 r852(official) with the >> same result. >> >> This breaks the ring use of completion; annoying. > > thanks for reporting, even though it is too late for 0.4.2 now. Oh well, > seems we're heading for 0.4.3, then ;). > BTW: it should not have appeared until r844 or later... > > Anyway, I think I fixed the problem in r855 - builds are uploading right > now. Please test... > > Regards, > Stefan > > PS: actually, the problem was more than just annoying, unfortunately. > When doing something like "a b \doc", the beginning of the > line (i.e., "a b ") was erased... > From esperanto at swing.be Wed Jun 29 08:44:03 2011 From: esperanto at swing.be (Alain Delmotte) Date: Wed, 29 Jun 2011 08:44:03 +0200 Subject: [texworks] Problem with autocompletion In-Reply-To: <4E0ABE3E.3090205@gmail.com> References: <4E0976FC.1090109@leliseron.org> <4E0ABE3E.3090205@gmail.com> Message-ID: <4E0AC9B3.5080805@swing.be> Hi Stefan! Thanks for the new version. After a short test I want to report that it works. I'll do longer tests (by using) later. Le 29/06/2011 07:55, Stefan L?ffler a ?crit : > > thanks for reporting, even though it is too late for 0.4.2 now. Oh well, > seems we're heading for 0.4.3, then ;). What do you mean it is too late for 0.4.2? Is this the version for TL2011? Thanks again, regards, Alain From t34www at googlemail.com Wed Jun 29 09:37:58 2011 From: t34www at googlemail.com (T T) Date: Wed, 29 Jun 2011 08:37:58 +0100 Subject: [texworks] Problem with autocompletion In-Reply-To: <4E0AC9B3.5080805@swing.be> References: <4E0976FC.1090109@leliseron.org> <4E0ABE3E.3090205@gmail.com> <4E0AC9B3.5080805@swing.be> Message-ID: On 29 June 2011 07:44, Alain Delmotte wrote: > Hi Stefan! > > Thanks for the new version. > After a short test I want to report that it works. > I'll do longer tests (by using) later. > > Le 29/06/2011 07:55, Stefan L?ffler a ?crit : >> >> thanks for reporting, even though it is too late for 0.4.2 now. Oh well, >> seems we're heading for 0.4.3, then ;). > > What do you mean it is too late for 0.4.2? > Is this the version for TL2011? Yes, it is, TL has been frozen yesterday, no further commits are allowed w/o Karl's approval. Stefan, is the bug critical enough for us to break the freeze? How long until you could make the official release? If it's not something major, we we can always update TW after the TL release. Cheers, Tomek From paul.a.norman at gmail.com Wed Jun 29 09:42:38 2011 From: paul.a.norman at gmail.com (Paul A Norman) Date: Wed, 29 Jun 2011 19:42:38 +1200 Subject: [texworks] Problem with autocompletion In-Reply-To: References: <4E0976FC.1090109@leliseron.org> <4E0ABE3E.3090205@gmail.com> <4E0AC9B3.5080805@swing.be> Message-ID: " is the bug critical enough for us to break the freeze" f.y.i. From testing I did, it appeared to break all auto-completion that I tried, though I may not have tried every kind of thing so some things may have been ok. Paul On 29 June 2011 19:37, T T wrote: > On 29 June 2011 07:44, Alain Delmotte wrote: >> Hi Stefan! >> >> Thanks for the new version. >> After a short test I want to report that it works. >> I'll do longer tests (by using) later. >> >> Le 29/06/2011 07:55, Stefan L?ffler a ?crit : >>> >>> thanks for reporting, even though it is too late for 0.4.2 now. Oh well, >>> seems we're heading for 0.4.3, then ;). >> >> What do you mean it is too late for 0.4.2? >> Is this the version for TL2011? > > Yes, it is, TL has been frozen yesterday, no further commits are > allowed w/o Karl's approval. > > Stefan, is the bug critical enough for us to break the freeze? ?How > long until you could make the official release? ?If it's not something > major, we we can always update TW after the TL release. > > Cheers, > > Tomek > > From st.loeffler at gmail.com Wed Jun 29 10:41:45 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Wed, 29 Jun 2011 10:41:45 +0200 Subject: [texworks] Problem with autocompletion In-Reply-To: References: <4E0976FC.1090109@leliseron.org> <4E0ABE3E.3090205@gmail.com> <4E0AC9B3.5080805@swing.be> Message-ID: <4E0AE549.8010202@gmail.com> Hi, On 2011-06-29 09:37, T T wrote: > On 29 June 2011 07:44, Alain Delmotte wrote: >> What do you mean it is too late for 0.4.2? >> Is this the version for TL2011? I mean: 0.4.2 was released last weekend, so it's too late to fix the issue in that version. > Yes, it is, TL has been frozen yesterday, no further commits are > allowed w/o Karl's approval. > > Stefan, is the bug critical enough for us to break the freeze? How > long until you could make the official release? If it's not something > major, we we can always update TW after the TL release. Depends on what measure you use for "critical". The program work in general, and auto-completion works upon first invocation. If you try to cycle through several auto-completion alternatives (by repeatedly pressing the Tab key) you run into problems, though: 1) you get unwanted/gibberish characters after the auto-completion string (as reported by Alain and Paul), 2) if you do auto-completion cycling somewhere in the middle of the line, all the text in front of the cursor is erased I'd consider (1) annoying, but not definitely not release-critical. As for (2), it causes data loss (not permanent, as undo works, but still), so effectively prevents the use of auto-completion. Of course, I'd like to see the bugfix included if possible, but there's no need to scrap already-printed DVDs (I'm exaggerating here, of course ;)). If r855 indeed fixes the problem (as it appears to), I intend to publish 0.4.3 when I get home from work (probably in about 8 hours). Sorry for the inconvenience, Stefan From st.loeffler at gmail.com Wed Jun 29 10:46:36 2011 From: st.loeffler at gmail.com (=?ISO-8859-1?Q?Stefan_L=F6ffler?=) Date: Wed, 29 Jun 2011 10:46:36 +0200 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: References: <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> <4DF726D5.4020503@gmail.com> <74397209-E189-4173-B273-B01AECCCD611@gmail.com> <4E073992.3050908@gmail.com> Message-ID: <4E0AE66C.7070103@gmail.com> Hi, On 2011-06-29 01:24, Charlie Sharpsteen wrote: > On Sun, Jun 26, 2011 at 6:52 AM, Stefan L?ffler > wrote: > > As for (2), the Quartz approach satisfies this by using system > fonts, whereas fontconfig requires X11 fonts (which, however, seem > to have become a sort of system fonts in recent OS Xs, anyway; if > they don't - or there is a chance users don't have it - we should > probably bundle the necessary font files with Tw, just to ensure > we don't violate the PDF standard). > > > Fontconfig appears to use mostly system fonts with one or two X11 > fonts thrown in. If the user does not have X11 installed, the main > component that is missing are the Fontconfig configuration files that > tell it where to find things. If we stuck with Fontconfig, a possible > alternative to bundling the 14 required fonts would be to bundle a > configuration file that tells Fontconfig where to locate system fonts. Sounds fine for me. Is there any way to use that only as a fallback if no system config-files are found? > > So, all in all, I see two choices: bundle base-14 fonts (we do > this partly for Windows as well), or drop good font substitution. > > I would tend to go with fontconfig here, for reasons of simple > usability. But not being a Mac user this is nothing more than a > gut feeling. > Have I missed something? Jonathan, any thoughts? > > > I'm leaning in the direction of sticking with Fontconfig as well. > Mainly because although we have good Quartz support for the "base 14 > fonts", they are very English-centric and Fontconfig appears to make > better fallback and substitution choices for non-English languages. As > a white boy from Alaska, I feel entirely unqualified to make these > sorts of decisions :) Well then, unless someone else has good points to raise, let's settle on fontconfig for the 0.4 series for now. We can still change our minds down the road, but fontconfig seems like the most user-friendly way right now. > However, I do need to know which library to build 0.4.2 against. You may want to wait another day or so until 0.4.3 is released (see the thread on "Problem with autocompletion"). Cheers, Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: From t34www at googlemail.com Wed Jun 29 11:21:12 2011 From: t34www at googlemail.com (T T) Date: Wed, 29 Jun 2011 10:21:12 +0100 Subject: [texworks] Problem with autocompletion In-Reply-To: <4E0AE549.8010202@gmail.com> References: <4E0976FC.1090109@leliseron.org> <4E0ABE3E.3090205@gmail.com> <4E0AC9B3.5080805@swing.be> <4E0AE549.8010202@gmail.com> Message-ID: On 29 June 2011 09:41, Stefan L?ffler wrote: > > Depends on what measure you use for "critical". The program work in > general, and auto-completion works upon first invocation. If you try to > cycle through several auto-completion alternatives (by repeatedly > pressing the Tab key) you run into problems, though: > 1) you get unwanted/gibberish characters after the auto-completion > string (as reported by Alain and Paul), > 2) if you do auto-completion cycling somewhere in the middle of the > line, all the text in front of the cursor is erased > > I'd consider (1) annoying, but not definitely not release-critical. > As for (2), it causes data loss (not permanent, as undo works, but > still), so effectively prevents the use of auto-completion. OK, that's sounds major enough to me. > Of course, I'd like to see the bugfix included if possible, but there's > no need to scrap already-printed DVDs (I'm exaggerating here, of course ;)). > > If r855 indeed fixes the problem (as it appears to), I intend to publish > 0.4.3 when I get home from work (probably in about 8 hours). > > Sorry for the inconvenience, No problem, bugs happen, that's just part of the process. If Karl doesn't object, I'll update TW tonight, otherwise we have the first bullet point for "known issues" list of TL'11 ;) Cheers, Tomek From chuck at sharpsteen.net Wed Jun 29 17:40:22 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Wed, 29 Jun 2011 08:40:22 -0700 Subject: [texworks] Mac OS TeXworks + fontconfig In-Reply-To: <4E0AE66C.7070103@gmail.com> References: <4DE3E696.6070004@gmail.com> <4DE7A59C.9080506@gmail.com> <4DE800D1.7080700@gmail.com> <4DEB2ECA.6090008@gmail.com> <4DEE3538.9070406@gmail.com> <4DF058E1.7080905@gmail.com> <4DF726D5.4020503@gmail.com> <74397209-E189-4173-B273-B01AECCCD611@gmail.com> <4E073992.3050908@gmail.com> <4E0AE66C.7070103@gmail.com> Message-ID: On Wed, Jun 29, 2011 at 1:46 AM, Stefan L?ffler wrote: > ** > Hi, > > > On 2011-06-29 01:24, Charlie Sharpsteen wrote: > > On Sun, Jun 26, 2011 at 6:52 AM, Stefan L?ffler wrote: > >> As for (2), the Quartz approach satisfies this by using system fonts, >> whereas fontconfig requires X11 fonts (which, however, seem to have become a >> sort of system fonts in recent OS Xs, anyway; if they don't - or there is a >> chance users don't have it - we should probably bundle the necessary font >> files with Tw, just to ensure we don't violate the PDF standard). >> > > Fontconfig appears to use mostly system fonts with one or two X11 fonts > thrown in. If the user does not have X11 installed, the main component that > is missing are the Fontconfig configuration files that tell it where to find > things. If we stuck with Fontconfig, a possible alternative to bundling the > 14 required fonts would be to bundle a configuration file that tells > Fontconfig where to locate system fonts. > > > Sounds fine for me. Is there any way to use that only as a fallback if no > system config-files are found? > Don't know, it was just an idea that occurred to me. Maybe I will play around with it someday. Given that X11 is installed by default on all Macs (but can be left out through customization of the install) it is unlikely that the base Fontconfig files will be absent. > So, all in all, I see two choices: bundle base-14 fonts (we do this >> partly for Windows as well), or drop good font substitution. >> >> I would tend to go with fontconfig here, for reasons of simple usability. >> But not being a Mac user this is nothing more than a gut feeling. >> Have I missed something? Jonathan, any thoughts? >> > > I'm leaning in the direction of sticking with Fontconfig as well. Mainly > because although we have good Quartz support for the "base 14 fonts", they > are very English-centric and Fontconfig appears to make better fallback and > substitution choices for non-English languages. As a white boy from Alaska, > I feel entirely unqualified to make these sorts of decisions :) > > > Well then, unless someone else has good points to raise, let's settle on > fontconfig for the 0.4 series for now. We can still change our minds down > the road, but fontconfig seems like the most user-friendly way right now. > > > However, I do need to know which library to build 0.4.2 against. > > > You may want to wait another day or so until 0.4.3 is released (see the > thread on "Problem with autocompletion"). > Sounds good to me. I will wait until 0.4.3 to build the next round of Mac binaries and they will use Fontconfig. -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuck at sharpsteen.net Thu Jun 30 01:53:57 2011 From: chuck at sharpsteen.net (Charlie Sharpsteen) Date: Wed, 29 Jun 2011 16:53:57 -0700 Subject: [texworks] Builds of TeXworks 0.4.3 for OS X Message-ID: Good evening, I just posted Mac binaries for 0.4.3: For Leopard: https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.4.3-858-cb9d633-Leopard.dmg For Snow Leopard: https://github.com/downloads/Sharpie/TeXworks/TeXworks.0.4.3-858-cb9d633-SLeopard.dmg ** NOTE: These links are semi-permanent. Old builds may be deleted in order to free disk space for new builds. ** These builds still use Fontconfig rather than Quartz to discover font files as Fontconfig provides better substitution suggestions for non-English fonts. This means that Mac users who run these builds on a computer that doesn't have OS X installed won't see any text that references fonts that are not embedded into the PDF document. This should not be a major concern as: - TeX embeds fonts into all documents it creates (with some exceptions, notably pTeX, unless configured to embed fonts). - X11 is installed by default since OS X 10.5.x---unless the user chose to customize the installation procedure and specifically unchecked the X11 option. This build was compiled against: Qt 4.7.3 Hunspell 1.3.2 Poppler 0.16.7 Lua 5.1.4 Enjoy! -Charlie -------------- next part -------------- An HTML attachment was scrubbed... URL: