Commit 5af7e9a3 authored by Atsuhito Kohda's avatar Atsuhito Kohda

Imported Upstream version 0.5~svn808

parent 5d893406
<!DOCTYPE plist PUBLIC
"-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleDocumentTypes</key>
<array>
<dict>
<key>CFBundleTypeExtensions</key>
<array>
<string>tex</string>
<string>ltx</string>
</array>
<key>CFBundleTypeIconFile</key>
<string>TeXworks-doc.icns</string>
<key>CFBundleTypeMIMETypes</key>
<array>
<string>text/plain</string>
</array>
<key>CFBundleTypeName</key>
<string>TeX Document</string>
<key>CFBundleTypeRole</key>
<string>Editor</string>
<key>LSIsAppleDefaultForType</key>
<true/>
</dict>
<dict>
<key>CFBundleTypeExtensions</key>
<array>
<string>pdf</string>
</array>
<key>CFBundleTypeIconFile</key>
<string>TeXworks-doc.icns</string>
<key>CFBundleTypeRole</key>
<string>Viewer</string>
<key>CFBundleTypeMIMETypes</key>
<array>
<string>application/pdf</string>
</array>
<key>LSItemContentTypes</key>
<array>
<string>com.adobe.pdf</string>
</array>
<key>CFBundleTypeName</key>
<string>PDF Document</string>
</dict>
</array>
<key>CFBundleIconFile</key>
<string>TeXworks.icns</string>
<key>CFBundleGetInfoString</key>
<string>TeXworks version 0.5 (r.1)&#xA;(C) 2007-2011 Jonathan Kew, Stefan L&#xF6;ffler&#xA;Released under GPL (v2.0 or later)</string>
<key>CFBundleExecutable</key>
<string>TeXworks</string>
<key>CFBundleIdentifier</key>
<string>org.tug.texworks</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleShortVersionString</key>
<string>0.5 (r.1)</string>
<key>CFBundleVersion</key>
<string>0.5 (r.1)</string>
<key>CSResourcesFileMapped</key>
<true/>
</dict>
</plist>
Introduction
============
This file describes do's and don'ts, good practices, and requirements when
packaging TeXworks.
When you have read this far, you are probably interested in packaging TeXworks.
First of all, thank you for your commitment, it is very welcome. Before you
start, however, you should check that no packages for the system you intend to
target exist already. Currently, packages for Windows and Ubuntu are provided by
the project maintainers, and packages for several other Linux distributions have
been contributed by members of the community.
If you package TeXworks successfully, please drop by the mailing list and tell
us about it :).
General guidelines
==================
This section describes how TeXworks should be packaged. It does not deal with
the building process itself, however (see the README and
http://code.google.com/p/texworks/w/list for some more information on that).
Instead, it deals with the principal decisions.
* TeXworks consists of the core program and plugins. If possibly, the plugins
should be made available separately (unless noted otherwise). The are to be
considered optional (Debian policy: they are suggested, not recommended,
meaning that running TeXworks without them is perfectly reasonable).
* All plugins that can be built should be built.
* Stable releases feature a copy of the manual. Like the plugins, this should
be packaged, preferably as a separate, optional package (Debian policy: a
suggested package).
* It is strongly recommended to distribute TeXworks with the poppler encoding
data as well as the 14 PDF base fonts or suitable (i.e., metrically
equivalent) replacements. On Linux, these are typically provided by the
system and/or packages which the TeXworks package should depend on. Note that
this is not a strict dependence, as TeXworks will run without poppler-data or
the base-14 fonts, but some files may not be displayed correctly (Debian
policy: the packages are recommended, meaning that they are found on all but
the most unusual systems). Note that when providing poppler-data and/or fonts
yourself in the package, you most likely will need to patch the poppler
library itself as well.
See below for further information on this issue and how to test proper
functionality.
Poppler
=======
As mentioned in the guidelines, there are several intricacies concerning the
poppler library.
In order to properly display PDF files without embedded fonts - and to conform
to the PDF standard - TeXworks package must ensure that the base 14 fonts are
available on the system. The preferable way to do that is to pull in system
packages and/or use alternative fonts found on the system. The remaining files
can be obtained, e.g., from http://www.ctan.org/tex-archive/fonts/urw/base35
(note that those fonts have been renamed according to
http://www.tug.org/fontname/html/URW-fonts.html which must be undone as poppler
expects the original filenames). The following pfb files are needed:
d050000l.pfb, n019003l.pfb, n019004l.pfb, n019023l.pfb, n019024l.pfb,
n021003l.pfb, n021004l.pfb, n021023l.pfb, n021024l.pfb, n022003l.pfb,
n022004l.pfb, n022023l.pfb, n022024l.pfb, s050000l.pfb.
If you provide the base 14 fonts yourself, you need to make sure poppler picks
them up. To achieve that, you most likely will need to patch poppler
accordingly. See lib-patches/poppler-win32-font-handling.patch for an example
for poppler-0.16 on Windows.
To check if the fonts are picked up correctly, use the base14-fonts testcase
from http://texworks.googlecode.com/svn/trunk/testcases/.
Moreover, the poppler library needs the poppler-data from
http://poppler.freedesktop.org/ (this particularly affects displaying CJK
documents). By default, TeXworks looks for a folder named "poppler-data"
alongside the main application on Windows and Mac (see src/TWApp.cpp -
TWApp::init()). It only sets this directory once while starting up, however, so
you need ensure poppler doesn't mess with it by building poppler with the
lib-patches/poppler-qt4-globalparams.patch patch.
To check if poppler-data is picked up properly, use the poppler-data testcase
from http://texworks.googlecode.com/svn/trunk/testcases/.
Other libraries and patches
===========================
* Qt 4.7.0 and 4.7.1 have a bug crashing TeXworks occasionally when using the
"Highlight current line" feature together with "Wrap Lines" due to a memory
overflow. Use lib-patches/qt-4_7-qpathclipper.patch to fix that.
Further information and help
============================
Homepage: http://www.tug.org/texworks/
Development: http://code.google.com/p/texworks/
Bugs: http://code.google.com/p/texworks/issues/list
Mailing list: http://tug.org/mailman/listinfo/texworks
......@@ -48,7 +48,7 @@
<key>CFBundleIconFile</key>
<string>TeXworks.icns</string>
<key>CFBundleGetInfoString</key>
<string>TeXworks version 0.4.0 (r.759)&#xA;(C) 2007-2011 Jonathan Kew, Stefan L&#xF6;ffler&#xA;Released under GPL (v2.0 or later)</string>
<string>TeXworks version 0.5 (r.1)&#xA;(C) 2007-2011 Jonathan Kew, Stefan L&#xF6;ffler&#xA;Released under GPL (v2.0 or later)</string>
<key>CFBundleExecutable</key>
<string>TeXworks</string>
<key>CFBundleIdentifier</key>
......@@ -60,9 +60,9 @@
<key>CFBundleSignature</key>
<string>????</string>
<key>CFBundleShortVersionString</key>
<string>0.4.0 (r.759)</string>
<string>0.5 (r.1)</string>
<key>CFBundleVersion</key>
<string>0.4.0 (r.759)</string>
<string>0.5 (r.1)</string>
<key>CSResourcesFileMapped</key>
<true/>
</dict>
......
......@@ -36,6 +36,12 @@ QMAKE_CXXFLAGS += -DTW_BUILD_ID=personal
# comment this out if poppler's xpdf headers are not available on the build system
QMAKE_CXXFLAGS += -DHAVE_POPPLER_XPDF_HEADERS
# maximum compression for resources (unless that only produces a 5% size decrease)
QMAKE_RESOURCE_FLAGS += -threshold 5 -compress 9
# avoid warnings about "#pragma mark" on non-Mac/non-XCode systems
QMAKE_CXXFLAGS_WARN_ON += -Wno-unknown-pragmas
# put all symbols in the dynamic symbol table to plugins can access them; if not
# given, plugin loading may fail with a debug warning for some plugins
# Note: only works for gnu compilers; need to check what flags to pass to other compilers
......@@ -157,12 +163,14 @@ HEADERS += src/TWApp.h \
src/PrefsDialog.h \
src/TemplateDialog.h \
src/HardWrapDialog.h \
src/ResourcesDialog.h \
src/ScriptManager.h \
src/ConfirmDelete.h \
src/TWVersion.h \
src/SvnRev.h \
src/synctex_parser.h \
src/synctex_parser_utils.h \
src/ClickableLabel.h \
src/ConfigurableApp.h \
src/TWSystemCmd.h
......@@ -176,6 +184,7 @@ FORMS += src/TeXDocument.ui \
src/ToolConfig.ui \
src/TemplateDialog.ui \
src/HardWrapDialog.ui \
src/ResourcesDialog.ui \
src/ScriptManager.ui \
src/ConfirmDelete.ui
......@@ -196,6 +205,7 @@ SOURCES += src/main.cpp \
src/PrefsDialog.cpp \
src/TemplateDialog.cpp \
src/HardWrapDialog.cpp \
src/ResourcesDialog.cpp \
src/ScriptManager.cpp \
src/ConfirmDelete.cpp \
src/synctex_parser.c \
......
......@@ -8,6 +8,11 @@ BINPATHS=":"
if [ -x /usr/share/libtool/config.guess ]; then
PLATFORM=`/usr/share/libtool/config.guess`
ARCH=`echo $PLATFORM | sed 's/-.*//;s/i.86/i386/'`
# At least on Debian, Ubuntu, Gentoo and LFS, config.guess seems to be in a
# subdirectory
elif [ -x /usr/share/libtool/config/config.guess ]; then
PLATFORM=`/usr/share/libtool/config/config.guess`
ARCH=`echo $PLATFORM | sed 's/-.*//;s/i.86/i386/'`
else
PLATFORM=`uname -s | tr A-Z a-z`
ARCH=`uname -m | tr A-Z a-z | sed 's/i.86/i386/'`
......@@ -63,10 +68,25 @@ case $PLATFORM in
*) OS=`echo $PLATFORM | sed 's/.*-//'`
esac
appendPath "/usr/local/texlive/2011/bin/$ARCH-$OS"
appendPath "/usr/local/texlive/2010/bin/$ARCH-$OS"
appendPath "/usr/local/texlive/2009/bin/$ARCH-$OS"
appendPath "/usr/local/texlive/2008/bin/$ARCH-$OS"
appendPath "/usr/local/texlive/2007/bin/$ARCH-$OS"
for TEXLIVEROOT in /usr/local/texlive/* /opt/texlive/*; do
# Check if this is really a folder (e.g., /opt/... might not exist)
if [ -d "$TEXLIVEROOT/bin/$ARCH-$OS" ]; then
# Check that this is of the form /texlive/1234
if [ -z `basename $TEXLIVEROOT | sed 's/[0-9]//g'` ]; then
# Paranoia: Make sure there actually is a bin/... subdirectory
if [ -d "$TEXLIVEROOT/bin/$ARCH-$OS" ]; then
appendPath "$TEXLIVEROOT/bin/$ARCH-$OS"
fi
fi
fi
done
# (3) append default paths that we should always check
appendPath "/usr/local/bin"
......
texworks lib-patches directory
TeXworks lib-patches directory
==============================
The Windows and Mac OS X builds of texworks are created using a slightly patched
......@@ -10,13 +10,17 @@ version of some libraries, to fix some bugs or provide some additional features
Poppler patches (poppler-*.patch)
---------------------------------
The Windows and Mac OS X builds of texworks are created using a slightly patched
version of poppler, to provide some added support for platform fonts (on OS X,
and when building with mingw32 on Windows) and to allow the use of a "local"
poppler-data directory as we cannot expect a system-wide poppler installation on
these platforms.
This directory contains the relevant patches, as used with poppler-0.12 for the
TeXworks 0.2 release.
version of poppler, to provide some added support for platform fonts (on OS X)
and to allow the use of a "local" poppler-data directory as we cannot expect a
system-wide poppler installation on these platforms.
This directory contains the relevant patches, as used with poppler-0.16.4 for
the TeXworks 0.4 release.
* poppler-qt4-globalparams.patch
Provides support for a "local" poppler-data.
* poppler-*-font-handling.patch
Adds/enhances font support for different platforms. (Only the patch relevant
for you platform is needed)
......
diff --git a/poppler/GlobalParams.h b/poppler/GlobalParams.h
index 7cb2ffc..f92ce41 100644
--- a/poppler/GlobalParams.h
+++ b/poppler/GlobalParams.h
@@ -33,8 +33,6 @@
#pragma interface
#endif
-#include "config.h"
-
#include <assert.h>
#include "poppler-config.h"
#include <stdio.h>
diff --git a/qt4/src/poppler-document.cc b/qt4/src/poppler-document.cc
index 877db52..2310c87 100644
index 04c56c6..d1d45d9 100644
--- a/qt4/src/poppler-document.cc
+++ b/qt4/src/poppler-document.cc
@@ -39,6 +39,7 @@
@@ -46,6 +46,7 @@
namespace Poppler {
int DocumentData::count = 0;
......@@ -23,41 +10,46 @@ index 877db52..2310c87 100644
Document *Document::load(const QString &filePath, const QByteArray &ownerPassword,
const QByteArray &userPassword)
diff --git a/qt4/src/poppler-private.cc b/qt4/src/poppler-private.cc
index d6e3265..075b3fd 100644
--- a/qt4/src/poppler-private.cc
+++ b/qt4/src/poppler-private.cc
@@ -234,8 +234,13 @@ namespace Debug {
count --;
if ( count == 0 )
{
- utf8Map = 0;
- delete globalParams;
+ if ( ownGlobalParams )
+ {
+ utf8Map = 0;
+ delete globalParams;
+ globalParams = NULL;
+ ownGlobalParams = gFalse;
+ }
}
}
@@ -253,8 +258,12 @@ namespace Debug {
if ( count == 0 )
{
- utf8Map = 0;
- globalParams = new GlobalParams();
+ if ( !globalParams )
+ {
+ utf8Map = 0;
+ globalParams = new GlobalParams();
+ ownGlobalParams = gTrue;
+ }
setErrorFunction(qt4ErrorFunction);
}
count ++;
diff --git a/qt4/src/poppler-private.h b/qt4/src/poppler-private.h
index acf3124..5d5c301 100644
index 7d0b1a3..9614e38 100644
--- a/qt4/src/poppler-private.h
+++ b/qt4/src/poppler-private.h
@@ -103,7 +103,11 @@ namespace Poppler {
if ( count == 0 )
{
- globalParams = new GlobalParams();
+ if ( !globalParams )
+ {
+ globalParams = new GlobalParams();
+ ownGlobalParams = gTrue;
+ }
setErrorFunction(qt4ErrorFunction);
}
count ++;
@@ -118,7 +122,15 @@ namespace Poppler {
delete m_fontInfoIterator;
count --;
- if ( count == 0 ) delete globalParams;
+ if ( count == 0 )
+ {
+ if ( ownGlobalParams )
+ {
+ delete globalParams;
+ globalParams = NULL;
+ ownGlobalParams = gFalse;
+ }
+ }
}
OutputDev *getOutputDev()
@@ -204,6 +216,7 @@ namespace Poppler {
@@ -177,6 +177,7 @@ namespace Poppler {
QColor paperColor;
int m_hints;
static int count;
......@@ -65,16 +57,3 @@ index acf3124..5d5c301 100644
};
class FontInfoData
diff --git a/qt4/src/poppler-qt4.h b/qt4/src/poppler-qt4.h
index fd384f5..4f5d639 100644
--- a/qt4/src/poppler-qt4.h
+++ b/qt4/src/poppler-qt4.h
@@ -1114,7 +1114,7 @@ QString subject = m_doc->info("Subject");
Destructor.
*/
~Document();
-
+
private:
Q_DISABLE_COPY(Document)
diff --git a/poppler/GlobalParamsWin.cc b/poppler/GlobalParamsWin.cc
index f989fb8..7ec1b8f 100644
--- a/poppler/GlobalParamsWin.cc
+++ b/poppler/GlobalParamsWin.cc
@@ -79,7 +79,8 @@ static struct {
{"Times-Italic", "n021023l.pfb", "timesi.ttf"},
{"Times-Roman", "n021003l.pfb", "times.ttf"},
// TODO: not sure if "wingding.ttf" is right
- {"ZapfDingbats", "d050000l.pfb", "wingding.ttf"},
+// no, the symbol sets are quite different
+ {"ZapfDingbats", "d050000l.pfb", NULL},
// those seem to be frequently accessed by PDF files and I kind of guess
// which font file do the refer to
@@ -153,6 +154,11 @@ static struct {
#define FONTS_SUBDIR "\\fonts"
+/* mingw32 lacks this symbol, so add it here if necessary */
+#ifndef SHGFP_TYPE_CURRENT
+#define SHGFP_TYPE_CURRENT 0
+#endif
+
static void GetWindowsFontDir(char *winFontDir, int cbWinFontDirLen)
{
BOOL (__stdcall *SHGetSpecialFolderPathFunc)(HWND hwndOwner,
@@ -239,7 +245,7 @@ void GlobalParams::setupBaseFonts(char * dir)
if (displayFonts->lookup(fontName))
continue;
- if (dir) {
+ if (dir && displayFontTab[i].t1FileName) {
GooString *fontPath = appendToPath(new GooString(dir), displayFontTab[i].t1FileName);
if (FileExists(fontPath->getCString())) {
AddFont(displayFonts, fontName, fontPath, displayFontT1);
@@ -274,10 +280,15 @@ DisplayFontParam *GlobalParams::getDisplayFont(GfxFont *font) {
DisplayFontParam * dfp;
GooString * fontName = font->getName();
char * substFontName = NULL;
+ char appDir[MAX_PATH];
if (!fontName) return NULL;
lockGlobalParams;
- setupBaseFonts(NULL);
+ if (::GetModuleFileName(0, appDir, MAX_PATH) > 0)
+ setupBaseFonts(appendToPath(grabPath(appDir), "fonts")->getCString());
+ else
+ setupBaseFonts(NULL);
+
dfp = (DisplayFontParam *)displayFonts->lookup(fontName);
if (!dfp) {
substFontName = findSubstituteName(fontName->getCString());
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content=
"HTML Tidy for Linux (vers 25 March 2009), see www.w3.org" />
<title>Acknowledgements</title>
<meta http-equiv="Content-Type" content=
"text/html; charset=utf-8" />
<meta name="generator" content=
"TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
<meta name="originator" content=
"TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
<!-- info,2,imgdir:images/,sec-filename,next,index=2,url-enc,html -->
<meta name="src" content="index.tex" />
<meta name="date" content="2011-03-20 12:48:00" />
<link rel="stylesheet" type="text/css" href="index.css" />
</head>
<body>
<!--l. 5-->
<p class="noindent"></p>
<div id="container">
<!--l. 5-->
<div class="crosslinks">
<p class="noindent">[<a href="bibname.html">next</a>] [<a href=
"CompilingTw.html">prev</a>] [<a href=
"CompilingTw.html#tailCompilingTw.html">prev-tail</a>] [<a href=
"#tailAcknowledgements.html">tail</a>] [<a href=
"index.html#Acknowledgements.html">up</a>]</p>
</div><!--l. 5-->
<p class="indent"></p>
<h1><a id="x51-58000C" name="x51-58000C"></a>Acknowledgements</h1>
<!--l. 7-->
<p class="indent">Microsoft, Windows, and the Windows logo are
registered trademarks of Microsoft Corporation in the United States
and other countries. <!--l. 9--></p>
<p class="indent">Apple, Mac, and Mac OS are trademarks of Apple
Inc., registered in the U.S. and other countries. <!--l. 11--></p>
<p class="indent">Google is a trademark of Google Inc.
<!--l. 13--></p>
<p class="indent">Unless noted otherwise, all icons are either part
of T<sub>E</sub>Xworks or part of the Tango Icon Library (<a href=
"http://tango.freedesktop.org/Tango_Icon_Library" class=
"url">http://tango.freedesktop.org/Tango_Icon_Library</a>).
<!--l. 15--></p>
<div class="crosslinks">
<p class="noindent">[<a href="bibname.html">next</a>] [<a href=
"CompilingTw.html">prev</a>] [<a href=
"CompilingTw.html#tailCompilingTw.html">prev-tail</a>] [<a href=
"Acknowledgements.html">front</a>] [<a href=
"index.html#Acknowledgements.html">up</a>]</p>
</div><!--l. 15-->
<p class="indent"><a id="tailAcknowledgements.html" name=
"tailAcknowledgements.html"></a></p>
</div>
</body>
</html>
This diff is collapsed.
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content=
"HTML Tidy for Linux (vers 25 March 2009), see www.w3.org" />
<title>7 Beyond this manual</title>
<meta http-equiv="Content-Type" content=
"text/html; charset=utf-8" />
<meta name="generator" content=
"TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
<meta name="originator" content=
"TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
<!-- info,2,imgdir:images/,sec-filename,next,index=2,url-enc,html -->
<meta name="src" content="index.tex" />
<meta name="date" content="2011-03-20 12:48:00" />
<link rel="stylesheet" type="text/css" href="index.css" />
<style type="text/css" xml:space="preserve">
/*<![CDATA[*/
em.c2 {font-weight: bold}
/*]]>*/
</style>
</head>
<body>
<!--l. 5-->
<p class="noindent"></p>
<div id="container">
<!--l. 5-->
<div class="crosslinks">
<p class="noindent">[<a href="CustomizingTw.html">next</a>]
[<a href="AdvanceduseScripting.html">prev</a>] [<a href=
"AdvanceduseScripting.html#tailAdvanceduseScripting.html">prev-tail</a>]
[<a href="#tailBeyondthismanual.html">tail</a>] [<a href=
"index.html#Beyondthismanual.html">up</a>]</p>
</div><!--l. 5-->
<p class="indent"></p>
<div class="chapternumber">
7
</div>
<h1><a id="x38-420007" name="x38-420007"></a>Beyond this
manual</h1><!--l. 7-->
<p class="indent">In this manual, the authors tried to give an
overview over T<sub>E</sub>Xworks and a concise introduction to get
you started. T<sub>E</sub>Xworks is constantly evolving and
improving, however, so the information presented here will never be
complete. <!--l. 9--></p>
<p class="indent">Additional, frequently updated documents are
posted in the wiki hosted by Google Code at <a href=
"http://code.google.com/p/texworks/w/list" class=
"url">http://code.google.com/p/texworks/w/list</a>. Particularly
noteworthy are the following pages:</p>
<dl class="description">
<dt class="description"><span class=
"ec-lmbx-12">SpellingDictionaries</span></dt>
<dd class="description">describes how to obtain and install
dictionaries for the spell-checker on various systems. <a href=
"http://code.google.com/p/texworks/wiki/SpellingDictionaries"
class="url">http://code.google.com/p/texworks/wiki/SpellingDictionaries</a></dd>
<dt class="description"><span class=
"ec-lmbx-12">TipsAndTricks</span></dt>
<dd class="description">provides a compilation of useful things to
know at a glance, such as the <span class=
"obeylines-h verb"><span class="ec-lmtt-12">%</span><span class=
"ec-lmtt-12">&nbsp;!TEX</span><span class=
"ec-lmtt-12">&nbsp;root</span></span> construct. <a href=
"http://code.google.com/p/texworks/wiki/TipsAndTricks" class=
"url">http://code.google.com/p/texworks/wiki/TipsAndTricks</a></dd>
<dt class="description"><span class=
"ec-lmbx-12">AdvancedTypesettingTools</span></dt>
<dd class="description">lists the configurations for several
typesetting tools that are not included in T<sub>E</sub>Xworks by
default, such as latexmk or the dvips workflows. <a href=
"http://code.google.com/p/texworks/wiki/AdvancedTypesettingTools"
class=
"url">http://code.google.com/p/texworks/wiki/AdvancedTypesettingTools</a></dd>
</dl><!--l. 16-->
<p class="indent">If you run into problems with
T<sub>E</sub>Xworks, it is advisable to browse the mailing list
archives accessible via <a href=
"http://tug.org/pipermail/texworks/" class=
"url">http://tug.org/pipermail/texworks/</a>. If you use
T<sub>E</sub>Xworks regularly or are interested in learning about
problems and solutions when using it for some other reason, you can
also consider subscribing to the list at <a href=
"http://tug.org/mailman/listinfo/texworks" class=
"url">http://tug.org/mailman/listinfo/texworks</a> to stay
up-to-date. For the occasional post to the mailing list, you can
also use the <em class="c2">Help</em><span class=
"lmsy-10x-x-120"></span><em class="c2">Email to mailing list</em>
menu item. Please make sure you replace the default subject by
something describing your issue and to include all information that
might help resolving it. That way, you are much more likely to get
many helpful replies. <!--l. 18--></p>
<p class="indent">If you find a bug in T<sub>E</sub>Xworks or want
to suggest a new feature for future versions, you should have a
look at the issue list at Google Code (<a href=
"http://code.google.com/p/texworks/issues/list" class=
"url">http://code.google.com/p/texworks/issues/list</a>). Before
posting a new item, please make sure that a similar report or
request is not already on the list and that the issue list is