texworks/texworks

Main codebase for TeXworks, a simple interface for working with TeX documents

Table Of Contents

About TeXworks

Getting Started

Contribution

Installation

Building TeXworks

License

About TeXworks

TeXworks is an environment for authoring TeX (LaTeX, ConTeXt, etc) documents, with a Unicode-based, TeX-aware editor, integrated PDF viewer, and a clean, simple interface accessible to casual and non-technical users.

TeXworks is inspired by Dick Koch's award-winning TeXShop program for macOS, which has made quality typesetting through TeX accessible to a wider community of users, without a technical or intimidating face. The goal of TeXworks is to deliver a similarly integrated, easy-to-use environment for users on all platforms, especially GNU/Linux and Windows.

Getting Started

TeXworks is a free and open-source software project. New users are encouraged to leverage this guide, outlining the fundamental process of creating, formatting, and generating PDF documents from within TeXworks.

Contribution

TeXworks thrives on an active community, and welcoming contributions is paramount. If you encounter bugs or have suggestions for improvement, please share them on our issues page. Additionally, you can engage in discussions with other users and developers via our mailing list. Visit the development page to fork a copy of the codebase and start contributing. Visit our homepage for more information. If you are new to contributing to open-source projects, we encourage you to visit this guide to help you get started.

Installation

Pre-built binaries for Windows, macOS, and Linux are available for immediate download from our official website.

Building TeXworks

Notes by Jonathan Kew, updated 2011-03-20, 2015-03-29, 2019-03-21, 2020-06-06 by Stefan Löffler

To build TeXworks from source, you will need to install

• CMake https://cmake.org/

as well as developer packages (or equivalent) for:

• Qt https://www.qt.io/download/
• Poppler https://poppler.freedesktop.org/
• Hunspell https://hunspell.github.io/

along with their dependencies (such as Freetype, fontconfig, zlib, etc.) If you also want to build the scripting plugins (optional), you additionally need development packages for Lua and/or Python. Details will depend on your platform. On Linux or similar systems, your package manager can probably provide all these. On the Mac, required libraries can be obtained, e.g., using Homebrew.

Using the latest stable versions of the dependencies is highly recommended, although TeXworks can be built with versions at least as old as CMake 3.1.0, Qt 5.2.3, poppler 0.24.5, and hunspell 1.2.9.

Once everything is set up, create a folder for building (e.g., "build") and run CMake in it to create a Makefile or Xcode project. Finally, run make or use Xcode to build the application.

Further tips on building TeXworks from source are available on some of the wiki pages:

• https://github.com/TeXworks/texworks/wiki/Building
• https://github.com/TeXworks/texworks/wiki/Building-on-Windows-(MinGW)
• https://github.com/TeXworks/texworks/wiki/Building-on-macOS-(Homebrew)

License

TeXworks is copyright (C) 2007-2024 by Stefan Löffler, Jonathan Kew, and Charlie Sharpsteen. Distributed under the terms of the GNU General Public License, version 2 or (at your option) any later version. See the file COPYING for details.

The SyncTeX code is copyright (c) 2008-2017 by Jérôme Laurens; see modules/synctex/synctex_parser.c for license details.

texworks's Issues

Feature request: new documents created in one folder

By default, new documents should be created in a new folder.
But a check box should allow the user to create a new document without a new 
directory level.
The idea behind is that a tex document is naturally made of various components, 
that should be 
preferably wrapped into one directory.

Original issue reported on code.google.com by [email protected] on 31 Aug 2008 at 5:22

Can't checkout svn copy

I have tried to checkout a copy of TeXworks from the svn repository using this:

svn checkout http://texworks.googlecode.com/svn/trunk/texworks-read-only

but I get this response:

svn: URL 'http://texworks.googlecode.com/svn/trunk/texworks-read-only'
doesn't exist

What do I do?

Thanks.

Stephen Moye

Original issue reported on code.google.com by [email protected] on 9 Sep 2008 at 6:59

Feature request: Derive spell checking language from babel commands

Problem:

Currently the spell checking language has to be selected through the 
menu. There doesn't seem to be a way to associate a language with a 
document. 
People writing documents in different languages (e.g. native and english) 
have to switch language whenever they load a new document. 

Possible solutions:

Emacs AUCTeX contains different approaches to resolve this problem:

1. It is possilble to associate emacs-specific settings with a document 
by defining emacs-variables within a specially formatted 
LaTeX %-commentsection at the end of the document. The variables are set 
upon document open. (A similar mechanism could be usefull for other 
things, too -- e.g. setting the TeX-processor.)

2. Using the flyspellbabel.el mode 
http://www.emacswiki.org/cgi-bin/wiki/FlyspellBabel emacs is able to 
derive the document language from the babel commands it contains. This 
even works for documents that contain sections in different languages. 
To me this appears to be the preferable approach. 

(Similarly it might be usefull to derive the input encoding from the 
corresponding \usepackage option.)

Original issue reported on code.google.com by [email protected] on 4 Oct 2008 at 10:22

Header line to specify TeX 'engine'?

Is it, or will it be, possible to have a TeXShop-like first line "%!TEX
TS-engine = " in TeXworks?

I have built and installed it on Ubuntu 8.04 successfully.

Stephen Moye

Original issue reported on code.google.com by [email protected] on 31 Jul 2008 at 8:00

Problem with translations

I just tried to use a ts-file for german translations (not finished yet).
Although I put the corresponding qm-file into res/resfiles/translations/ it
is not possible to switch to german in the preferences.
I use version r108.

Original issue reported on code.google.com by [email protected] on 4 Aug 2008 at 3:01

Attachments:

• TeXworks_de.qm

[Winodws] Cannot select in viewer

The "Select text" function seems to be broken in the PDF viewer with the
current release on Windows.  The cursor turns into the I-bar, but it is not
possible to select text. 

Original issue reported on code.google.com by [email protected] on 4 Sep 2008 at 12:14

Alt-Gr not working under Windows

With the precompiled version for Windows, the Alt Gr does not work, which
means you can't use the backslash :-(

Original issue reported on code.google.com by [email protected] on 29 Jul 2008 at 10:25

Feature request: Please support other editors than the built-in one for inverse search

The PDF viewer functionality alone is a very useful feature because it
supports inverse search.

Please make it possible to use the inverse search features with other
editors than the built-in one.

Original issue reported on code.google.com by [email protected] on 12 Sep 2008 at 9:38

Problems with Paths (windows)

I just tried to get the latest snapshot of TeXworks run on my Windows
system with MiKTeX. Unfortunatly if I try to add the correct path I always
get an "/" at the end which yields an "Invalid command-line option" when
running pdflatex. It did work with the former version though.
Am I doing anything wrong or is it a bug?

Apart from that, I suggest that paths should be editable by hand.

Original issue reported on code.google.com by [email protected] on 18 Aug 2008 at 7:42

Feature request: Make TW aware of version control systems

Problem:

One of the benefits of using TeX is, that documents can easily be handled 
by a VC system like SVN or CVS and edited cuncurrently by multiple users. 

However, when a user performs a 'svn update' the .tex files will change 
without TW being aware of it. This can result in unrecognized data loss 
when TW overwrites the updated file with its old version when the user 
hits save or typeset. 

Possible Solutions:

1. Both emacs and kile recognize when the currently opened file changes 
on disk. The user then has the option to reload the file. This makes the 
user aware of the issue. However, if the user made unsaved changes to the 
file before it was updated on disk, there is no simple way of keeping 
these changes. 

2. Emacs has integrated support for different VC systems (SVN, CVS, 
RCS, ...) and allows the user to make updates and commit changes directly 
from within the editor. 
This has the benefit, that the document version in the repository always 
gets merged with the most current version in the editor.
However, implementing such functionality is quite complex, as all kinds 
of situations like editing conflicts have to be handled. There's also a 
gazillion of different VC systems out there that people might want to be 
supported. Maybe it is possible to develop some abstration layer into 
which different VC systems can be hooked easily.

Original issue reported on code.google.com by [email protected] on 4 Oct 2008 at 10:40

Feature request: Add \end{<whatever>} by typing extra "}" after \begin{<whatever>}

Taken from WinEdt. If I type:

\begin{document}}

the second "}" causes the editor to automatically add the appropriate \end
statement, so I get

\begin{document}
*
\end{document}

with the cursor at the *.

Original issue reported on code.google.com by [email protected] on 24 Sep 2008 at 4:41

mouse cursor in editing window

Using TeXworks on Windows XP

The mouse cursor remains the editing Ibeam even when it is over the tools
bar and the menu.

Thanks for the software which I could suggest to my students.

Alain Delmotte

Original issue reported on code.google.com by [email protected] on 9 Aug 2008 at 2:57

New window takes all of screen height (including area under bottom panel bar)

What steps will reproduce the problem?
1. Start TW
2. The bottom frame of the main app window disappears under the menu
bar/panel at the bottom of the screen. (standard Ubuntu/Gnome)
3. I can't resize window, because the bottom-right resize area is
inaccessible (unless I hide the bottom panel.)

>> Maybe the main app window should try to use 95% of the screen height?

Original issue reported on code.google.com by [email protected] on 10 Jul 2008 at 2:21

Plural forms support in translation strings

There are three translation strings ("Found %1 occurrence(s)", "Replaced %1
occurrence(s) in %2 documents" and "Replaced %1 occurrence(s)") in
TeXDocument.cpp that need plural forms support for proper translation in
languages like Arabic.

See http://doc.trolltech.com/qq/qq19-plurals.html for more details.

Original issue reported on code.google.com by [email protected] on 1 Oct 2008 at 7:51

Feature Request: pdf file is not closed until the last referencing tex document is

What steps will reproduce the problem?
1. Open two files containing a modeline ("% !TEX root = ...") referencing
the same root document
2. Close either one of the files

What is the expected output? What do you see instead?
The pdf document is opened when the first of the two files is opened. It
should stay open as long as there is a tex document open that refers to it
but right now it is closed as soon as the first document referencing it is
closed.

What version of the product are you using? On what operating system?
Ubuntu 8.04, svn r174

Please provide any additional information below.
My idea would be reference counting in the pdf document. When it's opened
the count is set to 1. And instead of letting the tex document close it it
only decrements the reference counter. Once the counter has reached zero
the pdf document closes itself.

Original issue reported on code.google.com by st.loeffler on 30 Sep 2008 at 2:55

can't change page in viewer using up/down cursor keys, page-up/down

If the view in the preview is set to 'Fit to Page', the up and down cursor
keys as well as the page-up/down keys do not change the page (this can only 
be done using the left/right cursor keys). 

Using a larger magnification for the document (e.g., 'Fit to Width'), the
above mentioned keys will scroll within the page. I would expect that if
the edge of the page is reached, pressing the up (resp. down) cursor key
once more would change the page (cf., e.g., okular/kpdf).

(This is using r.132 on Linux, QT 4.4.0.)

Thanks!

Original issue reported on code.google.com by [email protected] on 27 Aug 2008 at 12:53

Remember directory last used by File > Open

It would be nice if File > Open could remember the last used directory.

And a working directory view in the left part of the Open File window would
be nice too.

Original issue reported on code.google.com by [email protected] on 10 Jul 2008 at 2:32

CMD-click with ConTeXt component files

I just testes TeXworksOSX-r103 with TeXworksOSX-libs-20080714:

I am working with ConTeXt files in ConTeXt's project structure: this means
you have files included by \component (like \input or \inclode in latex).

Typesetting this file works, just the CMD-click doesn't.

I remember it took Dick also some time to get this done in TeXShop ...

(but maybe CMD-click doesn't work at all cause it is too early?!)

Thanks, Steffen.

Original issue reported on code.google.com by [email protected] on 15 Jul 2008 at 9:13

wish-list: automatically run bibtex

What steps will reproduce the problem?
1. add a new \cite in the source tex file
2. compile by running pdflatex/latex/...
3.

What is the expected output? What do you see instead?
It should automatically run bibtex when an undefined citation is found
after compiling. Maybe it should automatically run latex twice after that.
Currently I have to do it manually.

What version of the product are you using? On what operating system?
0.0.0 r132
Windows XP SP3

Please provide any additional information below.

Original issue reported on code.google.com by yizhang84 on 30 Aug 2008 at 7:49

Feature Request: Filter (Multiple Replace)

On the Mac only the good old editor Alpha (resp. AlphaTK and AlphaX) had
this feature: "Filter".

This is a list that a user can write and save with multiple search/replace
actions defined. The japanese JeditX editor has something similar: the
option to save a collection of search/replace pairs, only without the
Alpha-like option of additionally specifing how the individual replace
should be performed (case sensitive, as regex).

I don't understand why this great feature as Alpha offers it, is not more
wide spread: it is extremely useful!!

For more information let me quote the Alpha-info entry regarding Filter here:

!! Filter: NewFilter.flt
!! Created: 2008-09-30 12:56:33
!! Description: 
!! 

!! SYNTAX : 
!!  searchString    replacementString    [option]
!!    where the three arguments are separated by one or more tabulations.
!!    The option is a (possibly empty) string containing 0 or 1 and/or
!!    one of the letters i and m with the following signification :
!!        0 (or nothing) for an ordinary textual search (default)
!!        1 for a search with regular expressions
!!        i for a case insensitive search
!!        m to match words exactly (not a substring of a word)
!!    The options can be combined in any order : 0m, im1, i, 0m etc.
!!    Put as many of these instructions as you want in your filter. Each
!!    filtering instruction must be on a single line.
!!    A line starting with two exclamation signs is considered a comment
!!    and not a filtering instruction. If the two exclamation points are
!!    immediately followed by the word includefilter (or inputfilter) and
!!    the name of a filter (possibly enclosed in double quotes), the
!!    instructions found in this filter will be loaded and executed:
!!       !!inputfilter  "name_of_filter"

Original issue reported on code.google.com by [email protected] on 30 Sep 2008 at 11:06

wish: change case

Wish list:
It would be good to have, maybe in the Edit or in a Source menu (if
planned), a command to change a selected text between upper and lower case.

Original issue reported on code.google.com by [email protected] on 17 Jul 2008 at 6:12

Arabic translation

A full Arabic translation (updated to match the plural forms patch as well)

Original issue reported on code.google.com by [email protected] on 1 Oct 2008 at 8:45

Attachments:

• TeXworks_ar.ts

Feature request: Hard wrapping

The current "soft" wrapping mode will re-flow when opened in a different
size window.  Traditionalists like their code "hard" wrapped, with a fixed
line width (flexible, but 64 characters seems to be a popular default).  

If this is implemented, a "rewrap" function would also be nice. This would
"tidy" lines to the set length, breaking at spaces.  

Original issue reported on code.google.com by [email protected] on 24 Sep 2008 at 4:45

Add list of extensions/default extension

At least on Windows it would be nice for the Save dialog to include the
.tex extension by default.  The "Filter" box usually achieves this, and it
would be nice to include the obvious TeX-related extensions.  I would
suggest .tex, .ltx and .bib.

Original issue reported on code.google.com by [email protected] on 3 Sep 2008 at 12:37

TW hrashes when changing spelling language

What steps will reproduce the problem?
1. Open a TeX file
2. Edit > Spelling > choose another language
3. TW crashes

What is the expected output? What do you see instead?
Red underlining disappears: good. TW disappears: bad. 

What version of the product are you using? On what operating system?
TW rev.99, Linux 64 bit

Please provide any additional information below.

With no TeX file open, changing language setting works just fine.

Original issue reported on code.google.com by [email protected] on 10 Jul 2008 at 1:38

Highlighter comment buggy

The line "10\% blabla" is badly highlighted as "\%" is a control sequence.

In TeXHighlighter.cpp file, I try to change line 58 from
rule.pattern = QRegExp("%.*");
to
rule.pattern = QRegExp("(^%.*)|([^\\\\]%.*)");
but it is still buggy. The char `a' in the line "bla% Comment" is badly 
highlighted and I dont understand why.

PS: Congratulations for this splendid work.

François Legendre

Original issue reported on code.google.com by [email protected] on 14 Aug 2008 at 8:58

crashed at once when a char "{" is typped in this file

There is a file attached here. When a char '{' is typed at the begin line
in this file, texworks is always crashed at once. 

I known the typped char "‘" is wrong for tex math, but texworks should be
not crashed.


Windows XP/SP3, TeXWorks-r167

Original issue reported on code.google.com by [email protected] on 30 Sep 2008 at 12:27

Attachments:

• crashfile.tex

palette or sidebar with tags and sections links

Wish list:
A very useful feature to navigate the document, like a tree showing the
structure of the document, with recognition of the sectioning commands and
also author-inserted tags

Original issue reported on code.google.com by [email protected] on 17 Jul 2008 at 6:04

Feature request: support by mail

Add a menu item to send a question to the texworks users mailing list
The UI should be well designed, in the sense that users should be helped to 
read the list through 
their mailer.

Original issue reported on code.google.com by [email protected] on 31 Aug 2008 at 5:04

The problem of INT_MAX's definition.

When I compiled the newest code of texworks, I encountered the problem of 
"INT_MAX" in line 72 of "src/TeXHighlighter.cpp" was not define. I added
the code of including limits.h in TeXHighlighter.cpp to solve the problem.

Original issue reported on code.google.com by LiYanrui.m2 on 15 Aug 2008 at 12:19

Feature request: scripting support

Scriptability through lua of course.

Original issue reported on code.google.com by [email protected] on 31 Aug 2008 at 5:13

• Blocking: #42

Current position in line

TeXworks shows which line you are editing and the current total lines. 
However, there is no way to see the current position in a line.  This might
be nice.

Original issue reported on code.google.com by [email protected] on 3 Sep 2008 at 12:39

wish list: Search across open files

It would be good to have the possibility to search and replace through all
the open files.

Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 2:29

Preferences for Editor do not work

Whatever I use at the preferences for the editor defaults, the values are
not used. When changing properties by "Format-Font" everything works as
expected.

I am using TeXworks (svn rev 105) on my Linux (Ubuntu 8.04) machine.

Original issue reported on code.google.com by [email protected] on 29 Jul 2008 at 5:18

Completion in references, citations

Since I haven't seen this on the list of planned features, I'd like to put
in a request for automatic completion of labels in \ref{} respectively
citation keys in \cite{} commands (a la Kile/Texmate et al.), if this is
not considered as a too advanced feature. (I've always found this to be
extremely helpful.)

Original issue reported on code.google.com by [email protected] on 12 Aug 2008 at 11:40

wish-list: create own keyboard shortcuts

It would be nice to be able to create keyboard shortcuts either for the
commands of the program or for personnal macros (for example to create a
LaTeX structure,...). And possibility to create macros would be a plus.

Using a French Belgian keyboard, the AltGr combinations do not work and so
the existing shortcuts (like comment/uncomment,...) neither.

Alain Delmotte

Original issue reported on code.google.com by [email protected] on 9 Aug 2008 at 3:02

• Blocking: #432, #434

Feat request: New documents

For new documents, consider a user interface à la Pages (from Mac OS X).
The user should be able to choose between the various possibilities by type 
(article, memoir, 
letter...) but also by visual appearance. As a consequence, a template for a 
new document must 
contain a sample pdf file which may or may not be the output of the text file.

Original issue reported on code.google.com by [email protected] on 31 Aug 2008 at 5:31

Feature request: project design

As texworks will definitely end with some kind of project design, please do not 
stick to TeXShop 
project design. Also consider how AucTeX, iTeXMac2, TeXnicenter and other 
editors manage 
projects.

Original issue reported on code.google.com by [email protected] on 31 Aug 2008 at 5:17

spell-checking in preferences

It would be nice, if there were a default value for the spell-checking in
the preferences as well.

Bye
Martin

Original issue reported on code.google.com by [email protected] on 6 Aug 2008 at 1:04

Feature request: anticipate plug in support

As plug in support will be necessary on the longer term, the internal design 
should anticipate a 
plug in design

Original issue reported on code.google.com by [email protected] on 31 Aug 2008 at 5:11

Feature Request: parse latex log output

What steps will reproduce the problem?
1. Typeset any tex document (preferably with many packages, errors&warnings)

What is the expected output? What do you see instead?
It would be nice to have a concise list of errors and warnings rather than
the long log which includes font tables, package calls etc. Ideally the
errors, warnings, and (over|under)full boxes should be color coded or
displayed next to an icon so the user can quickly identify the severity
(optionally the list may be sortable by severity). Clicking on an error
message should let the user jump to the line producing the error/warning.
Additionally it would be nice if the "Rerun LaTeX" message was displayed on
top of any warnings (if any) so the user knows if he has to rerun it.

Side note: the full log should not be discarded, it could still be
displayed in a separate tab or the user could switch between full log and
parsed log by a context menu or icon. I'd prefer tabs as this would make
new tabs possible in the future.

What version of the product are you using? On what operating system?
SVN r174. Ubuntu 8.04 Hardy Heron

Please provide any additional information below.
There is a gawk script latex error filter provided together a vim plugin
(http://www.vim.org/scripts/script.php?script_id=2325). It is based on
regexps and probably is a good starting point.

Original issue reported on code.google.com by st.loeffler on 30 Sep 2008 at 7:14

texworks crashes on corrupt pdf file

What steps will reproduce the problem?
1. Create an arbitrary tex file an typeset it into a pdf file
2. Corrupt the pdf file (I used `sed -i~ 'l' test.pdf` to line-wrap the file)
3. Open texworks and the original tex file

What is the expected output? What do you see instead?
The expected output is a warning message stating that the pdf file is
corrupt and cannot be used. Instead no message is shown in the gui and the
program crashes. On the command line the same errors are given as by the
system-default pdf viewer if the corrupt pdf file is opened there, followed
by a "segmentation fault".

What version of the product are you using? On what operating system?
texworks: SVN rev 168
OS: Ubuntu 8.04 Hardy Heron (with QT 4.4.0 backport)

Please provide any additional information below.
I noticed the same problem once when I accidentally introduced an error in
a rather large LaTeX project and tried to recompile it. Apparently the
pdflatex process corrupted the pdf file somehow without actually failing. I
couldn't reproduce this error in a simple test case, however.

Original issue reported on code.google.com by st.loeffler on 29 Sep 2008 at 6:37

Feature request: Drag-drop onto window to open

It would be very nice to be able to drag the icon of file (from
Finder/Explorer/Nautilus/whatever) onto an existing TeXworks window, and
have it open in a new window of its own.

Original issue reported on code.google.com by [email protected] on 24 Sep 2008 at 4:39

Versioning in help menu

Even though there is no real version 0.1 right now, the "help-About
TeXworks" could give some information like "pre-release rev 111" or
"0.0.0.111" as Jonathan suggested.

Bye
Martin

Original issue reported on code.google.com by [email protected] on 6 Aug 2008 at 1:07

Adobe Arabic etc fails to display on Windows

PDFs from xetex/xdvipdfmx containing fonts like Adobe Arabic fail to display on 
Windows; the 
glyphs don't appear, although the Fonts dock lists the embedded fonts as 
expected.

The same PDFs display OK on OS X and Linux, so it seems to be a problem with my 
poppler library 
build on Windows.

Original issue reported on code.google.com by [email protected] on 18 Aug 2008 at 10:28

command + arrow keys not working on Mac

When navigating the source in the Mac version, the usual combination 
command + arrow keys
to move to the beginning or end of a line 
is not working

Original issue reported on code.google.com by [email protected] on 17 Jul 2008 at 5:48

Feature request: Kill lines

A short cut for killing lines would be nice: this is handy to get rid of
blank spaces and also when removing large blocks.  Ctrl-K is often used for
this. 

Original issue reported on code.google.com by [email protected] on 24 Sep 2008 at 4:42

parens matching

This feature is quite limited in TeXShop, where you only have parens match
blinking confirmation when you actually type in the closing bracket. In
other editors (like Winedt) it is enough to move the cursor over any
bracket to see the match blink. Another possibility (jEdit) is to have also
a stretchable vertical line appear along a narrow margin, extending as many
lines as the piece of code inside the brackets.
The possibility to run a parens-match test for an entire file would also be
of great help anywhere in the menus (probably Edit menu).  

Original issue reported on code.google.com by [email protected] on 7 Aug 2008 at 6:13

Keyboard shortcuts: CTRL-= should zoom in in PDF viewer.

The shortcut key for zooming in is CTRL-+.  This requires one to either use
the + on the numeric keypad (which is not present on most laptops), or use
CTRL-SHIFT-= on a US English keyboard.

Most other programs which use CTRL-+ foor zooming will also accept CTRL-=
(tried it with Firefox, Adobe Reader, Safari browser).  The TeXworks viewer
should also accept the CTRL-= shortcut.

Potential problems:

I am not sure how this would work on non-English keyboard layouts.  I have
an English keyboard, but regularly use 3 different layouts.  On all 3 I can
use the key that types =/+ on the Enligsh layout for zooming in Firefox,
regardless of the function of that key in the active layout.

Original issue reported on code.google.com by [email protected] on 12 Sep 2008 at 9:31

BiDi issues

What steps will reproduce the problem?
1. Install Arabic translation (with the corresponding Qt translation)
2. Switch the interface to Arabic
3. All the interface is mirrored (RTL) including the text editing and
console areas with no obvious way to switch between RTL and LTR.

What is the expected output? What do you see instead?
Mirroring the UI is required, but since any TeX document will have lots of
LTR text, there should be better handling of the text area.

I suggest that we have auto BiDi detection (detecting paragraph direction
according the first strong BiDi character, as done in GTK+2 applications)
which is ON by default, and provide a UI to switch the whole page to RTL
all LTR as it becomes handy when editing sources with lots of markup like
TeX documents.

Original issue reported on code.google.com by [email protected] on 1 Oct 2008 at 5:17

Attachments:

• TeXworks_ar.png