<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/trackchanges/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/trackchanges/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sat, 03 Mar 2012 15:32:49 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/trackchanges/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Add to CTAN</title><link>https://sourceforge.net/p/trackchanges/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be good to have this in CTAN. The competing (and more complex) package "changes" is in CTAN already, see &lt;a href="http://ctan.org/pkg/changes" rel="nofollow"&gt;http://ctan.org/pkg/changes&lt;/a&gt;&lt;br /&gt;
Having the package in CTAN makes it easier for people, for example users of MiKTeX, to install and update the package.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gustav W Delius</dc:creator><pubDate>Sat, 03 Mar 2012 15:32:49 -0000</pubDate><guid>https://sourceforge.neta25c6f48a94780f5a4ea1e373b371d0bdcc3d9bd</guid></item><item><title>graphical LaTeX diff</title><link>https://sourceforge.net/p/trackchanges/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice if there was some diff tool that&lt;br /&gt;
compares two LaTeX source versions and marks changes&lt;br /&gt;
using \add \remove and \change commands.&lt;/p&gt;
&lt;p&gt;The goal of this tool is that differences between two&lt;br /&gt;
LaTeX files could be highlighted and seen in DVI!&lt;/p&gt;
&lt;p&gt;Maybe, this could be achieved by using UNIX diff but&lt;br /&gt;
I'm not sure whether UNIX diff only works on per-line&lt;br /&gt;
basis which is not sufficient in our case ....&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felix Salfner</dc:creator><pubDate>Mon, 12 Jun 2006 09:47:52 -0000</pubDate><guid>https://sourceforge.net504dec264b996a4b0be12bfd8ce84ff11e26c265</guid></item><item><title>write LaTeX documentation</title><link>https://sourceforge.net/p/trackchanges/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;LaTeX packages are usually equipped with a LaTeX&lt;br /&gt;
documentation document. This is missing ... &lt;/p&gt;
&lt;p&gt;Once available, the package could also be uploaded to&lt;br /&gt;
CTAN ...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felix Salfner</dc:creator><pubDate>Wed, 31 May 2006 21:38:49 -0000</pubDate><guid>https://sourceforge.netb5764b437e22bfcd33e7e2029d4b1734b8abf730</guid></item><item><title>acceptChanges.py: Separate parser from rest</title><link>https://sourceforge.net/p/trackchanges/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;acceptChanges.py contains both: command line processing&lt;br /&gt;
and the parser. If the parser is to be used by other&lt;br /&gt;
programs (e.g., some frontend) it should be made a&lt;br /&gt;
separate python module.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felix Salfner</dc:creator><pubDate>Wed, 31 May 2006 08:29:26 -0000</pubDate><guid>https://sourceforge.net964b96baab6e9c04b6bd8654179172e85e3fff76</guid></item><item><title>acceptChanges frontend: Cross-platform Java frontend</title><link>https://sourceforge.net/p/trackchanges/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;In order to provide cross-platform support, I suggest&lt;br /&gt;
that a Java-based frontend should be developed.&lt;/p&gt;
&lt;p&gt;The core functionality should include:&lt;/p&gt;
&lt;p&gt;- open / save / save as ... file actions&lt;br /&gt;
- filtering of trackchanges:&lt;br /&gt;
o process only commands with certain initials:&lt;br /&gt;
this enables that a user can accept / reject&lt;br /&gt;
changes of himself/herself or of another&lt;br /&gt;
dedicated user&lt;br /&gt;
o process only a selection of commands:&lt;br /&gt;
for example: only \note and \annote commands&lt;br /&gt;
should be processed&lt;br /&gt;
- a button to accept all changes/adds/removes&lt;br /&gt;
- a button to reject all changes/adds/removes&lt;br /&gt;
- a button to accept the selected changes/adds/removes&lt;br /&gt;
- a button to reject the selected changes/adds/removes&lt;br /&gt;
- a button to remove all notes/annotes&lt;br /&gt;
- a button to remove the selected notes/annotes&lt;/p&gt;
&lt;p&gt;In order to select changes quick and easy, the entire&lt;br /&gt;
document has to be presented and changes must be&lt;br /&gt;
highlighted. &lt;/p&gt;
&lt;p&gt;My idea was to add a checkbox to each change command&lt;br /&gt;
such that the user can go over the document and simply&lt;br /&gt;
select the changes with the mouse. &lt;br /&gt;
An alternative to a checkbox would be to present&lt;br /&gt;
changes like links on a webpage: the user can directly&lt;br /&gt;
click on the text to select / deselect it. Once&lt;br /&gt;
selected the text must change color.&lt;/p&gt;
&lt;p&gt;The optimum presentation would be that the frontend&lt;br /&gt;
interacts with a DVI viewer! The user could go over the&lt;br /&gt;
DVI document, click on a marked change and the GUI&lt;br /&gt;
would jump to the appropriate position in the&lt;br /&gt;
source.... but that's maybe too much ...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felix Salfner</dc:creator><pubDate>Wed, 31 May 2006 08:26:46 -0000</pubDate><guid>https://sourceforge.net7675574ff8dc32d3d7fb0492813558da138b0284</guid></item><item><title>acceptChanges backend: export parsed text as XML file</title><link>https://sourceforge.net/p/trackchanges/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice, if the acceptChanges backend would&lt;br /&gt;
create an XML-file such that various frontends could&lt;br /&gt;
easily process it.&lt;/p&gt;
&lt;p&gt;My suggestion is to use something like:&lt;/p&gt;
&lt;p&gt;...&lt;br /&gt;
&amp;lt;document&amp;gt;&lt;br /&gt;
&amp;lt;normalText&amp;gt; ..... &amp;lt;/normalText&amp;gt;&lt;br /&gt;
&amp;lt;addCommand&amp;gt;&lt;br /&gt;
&amp;lt;initials&amp;gt;FS&amp;lt;/initials&amp;gt;&lt;br /&gt;
&amp;lt;newText&amp;gt;new text ...&amp;lt;/newText&amp;gt;&lt;br /&gt;
&amp;lt;/addCommand&amp;gt;&lt;br /&gt;
&amp;lt;normalText&amp;gt; ..... &amp;lt;/normalText&amp;gt;&lt;br /&gt;
&amp;lt;changeCommand&amp;gt;&lt;br /&gt;
&amp;lt;originalText&amp;gt;old text&amp;lt;/originalText&amp;gt;&lt;br /&gt;
&amp;lt;newText&amp;gt;new text&amp;lt;/newText&amp;gt;&lt;br /&gt;
&amp;lt;/changeCommand&amp;gt;&lt;br /&gt;
&amp;lt;normalText&amp;gt;.....&amp;lt;/normalText&amp;gt;&lt;br /&gt;
&amp;lt;/document&amp;gt;&lt;/p&gt;
&lt;p&gt;the XML-schema looks quite easy and the XML-overhead&lt;br /&gt;
seems to be acceptable.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Felix Salfner</dc:creator><pubDate>Wed, 31 May 2006 08:08:00 -0000</pubDate><guid>https://sourceforge.net2d117dfd48faf0a794b797399668c21e3ced8380</guid></item></channel></rss>