Next | Query returned 137 messages, browsing 131 to 140 | previous

History of commit frequency

CVS Commit History:


   2012-09-15 12:07:21 by OBATA Akio | Files touched by this commit (1789) | Package updated
Log message:
recursive bump from libffi shlib major bump
(additionaly, reset PKGREVISION of qt4-* sub packages from base qt4 update)
   2012-09-14 14:26:19 by Matthias Drochner | Files touched by this commit (3) | Package updated
Log message:
revbump for poppler update
   2012-09-07 21:17:56 by Adam Ciarcinski | Files touched by this commit (1263)
Log message:
Revbump after updating graphics/cairo
   2012-08-13 14:18:37 by Matthias Drochner | Files touched by this commit (6)
Log message:
PKGREV bump for poppler shlib major change
   2012-07-01 21:05:29 by David A. Holland | Files touched by this commit (118)
Log message:
Add desktopdb.mk and bump PKGREVISION for 118 packages as reported by
pkglint. If any of these are wrong for some reason, please revert/adjust.
   2012-03-22 00:35:04 by Thomas Klausner | Files touched by this commit (1)
Log message:
Fix encodingo.
   2012-03-21 23:44:20 by Mark Davies | Files touched by this commit (6) | Imported package
Log message:
Import texworks 0.4.3

The TeXworks project is an effort to build a simple TeX front-end program
(working environment) that will be available for all todays major desktop
operating systems-in particular, MS Windows (XP/Vista/7), typical GNU/Linux
distros and other X11-based systems, as well as Mac OS X. It is deliberately
modeled on Dick Koch?s award-winning TeXShop for Mac OS X, which is credited
with a resurgence of TeX usage on the Mac platform.

To provide a similar experience across all systems, TeXworks is based on
cross-platform, open source tools and libraries. The Qt toolkit was chosen
for the quality of its cross-platform user interface capabilities, with
native "look and feel" on each platform being a realistic target. Qt also
provides a rich application framework, facilitating the relatively rapid
development of a usable product.

The normal TeXworks workflow is PDF-centric, using pdfTeX and XeTeX as
typesetting engines and generating PDF documents as the default formatted
output. Although it is possible to configure a processing path based on DVI,
newcomers to the TeX world need not be concerned with DVI at all, but can
generally treat TeX as a system that goes directly from marked-up text files
to ready-to-use PDF documents.


Next | Query returned 137 messages, browsing 131 to 140 | previous