<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.editors.winedt">
    <title>gmane.editors.winedt</title>
    <link>http://blog.gmane.org/gmane.editors.winedt</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3743"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3739"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3731"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3719"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3701"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3689"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3686"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3682"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3677"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3673"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3670"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3657"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3653"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3649"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3648"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3645"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3642"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3637"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3636"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.editors.winedt/3635"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3743">
    <title>Saving text file in ASCII mode for the first time</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3743</link>
    <description>Hi All,

I am sorry this problem is probably easy to fix but I wasn't able to
solve it after reading help and performing some experimentation.  The
problem has to do with saving a file in text mode for the first time,
I ended up losing all spacing information.  I felt that this must be
related to the "keep all spaces" option under document properties, but
even if that's checked, when I save the file, the problem persists.
Is there something that I am missing?

Version: 5.5 running on WinXP.

Many thanks!

Regards,
- Sam

</description>
    <dc:creator>Samuel Ieong</dc:creator>
    <dc:date>2008-05-13T00:09:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3739">
    <title>Winedt 5.6 console</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3739</link>
    <description>Dear Alex,

I have found the new console very nice, especially because you can
change from console to log file with a click. I wonder if it would
also be included the gather window in this behaviour, i.e. one can
open either the gather window from the console or open the console/log
file window within the gather window. For the rest, it seems it runs
very fine.

Best regards,

Agustin


</description>
    <dc:creator>=?iso-8859-15?Q?Agustin_E._Bolz=E1n?=</dc:creator>
    <dc:date>2008-05-12T12:42:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3731">
    <title>bug in Vista</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3731</link>
    <description>
</description>
    <dc:creator>Evaristo Arroyo F.</dc:creator>
    <dc:date>2008-05-11T02:25:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3719">
    <title>winedt+ list</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3719</link>
    <description>Please take my name off the list of the persons receiving emails about
winedir.

Sincerely

Stratis Kounias




</description>
    <dc:creator>Stratis Kounias</dc:creator>
    <dc:date>2008-05-08T17:29:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3701">
    <title>Setting location of bib file</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3701</link>
    <description>Hi,

I keep not being able to solve a problem, no matter which version of 
WinEdit or MiKTeX I use. I want BibTeX to assume MY bib files are in a 
particular folder on my USB flash drive (so that it's available on both 
my home/office/laptop computers). HOW do I achieve that?

ANY help greatly appreciated,

Best,
JP

</description>
    <dc:creator>Jean-Pierre Koenig</dc:creator>
    <dc:date>2008-05-05T14:47:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3689">
    <title>Mailing List Guidelines</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3689</link>
    <description>
      WinEdt Mailing List Guidelines
      ==============================


   These guidelines are sent to the WinEdt Mailing List once a month.
   Please keep them in mind when posting to the list.

   ---------------------------------------------------------------------

* What To Post

   The WinEdt Mailing List is for questions about the WinEdt editor. You
   should  not post questions concerning LaTeX, MiKTeX, BibTeX et al. to
   the mailing list. WinEdt is a shell/editor for  LaTeX  etc.  and  the
   list  is  intended  to  answer questions concerning WinEdt, not LaTeX
   etc.
   (Sometimes it might be difficult  to  decide  whether  a  problem  is
   related to WinEdt or to MiKTeX, LaTeX etc. A rule of thumb is: If you
   are having the same  problems  when  running  the  program  from  the
   command line, it is NOT related to WinEdt.)

   A lot of questions are being asked over and over  again.  Check  that
   your question isn't already answered in the WinEdt FAQ at
      &lt;http://www.winedt.org/Doc/FAQ&gt;
   or in the mailing list archives at
      &lt;http://groups.yahoo.com/group/WinEdt&gt;.

   When sending a question to the mailing list, try to be specific.
   Include (at least)
     + the Build number of your WinEdt (see "Help | About WinEdt...")
     + your operating system (e.g.: "Windows 2000, Service Pack 2")
     + a detailed description of the problem and how to reproduce it.

   If you have received one or more answers that  solved  your  problem,
   you  can  give  something  back  to the WinEdt community by writing a
   summary that can be integrated in the WinEdt FAQ. You can either send
   it to the list, or directly to the maintainer of the FAQ.

   Do NEVER post your registration key. Nobody needs to know it.


* How To Post

   Use plain-text format. Not everybody can (or wants to) read HTML.

   Use a meaningful subject line that will  make  sense  to  the  people
   whose help you are trying to get.

   Do not quote entire messages just to add a few lines at the beginning
   or  end.  Instead, quote the parts to which you are directly replying
   or quote enough to establish the context.
   Everybody on the list has already received the message that  you  are
   quoting,  and anyone searching the archive will find your message and
   the previous message listed under the same thread.

   Do not start a new thread by replying to  an  unrelated  message  and
   just  changing  the  subject  line.  For people who group messages by
   threading in their mailer, your  mail  will  appear  as  one  of  the
   replies  to the original message. It is better to start a new message
   for a new thread.

   The preferred language on the WinEdt Mailing List  is  English.  This
   does  not  imply disrespect to other languages, but simply guarantees
   the best possible communication as English is the language  that  the
   largest number of subscribers are able to understand.

   Since the WinEdt list has been used for unwittingly spreading viruses
   in  e-mail  attachments  in the past, all attachments will be removed
   from your mails. All relevant  documents  (if  any)  are  text  files
   anyway, which you can include in the body of your message.

   Do not request return receipts.

   If you are "out of office" and you want to set up  an  auto-responder
   for  your  e-mail  account,  please   unsubscribe   from   the   list
   temporarily!


* Unsubscribing + More

   To unsubscribe from the WinEdt Mailing List, send an empty  mail  to:
   &lt;winedt+list-unsubscribe&lt; at &gt;wsg.net&gt;  from  the  account  that  you  are
   subscribed with.

   DO NOT send a mail to the list! This will have no effect  apart  from
   annoying the subscribers.

   The complete list of administrative commands for the  WinEdt  Mailing
   List can be found here: &lt;http://www.winedt.org/Doc/listinstr.php&gt;


* Links

   + The WinEdt home page
     &lt;http://www.winedt.com/&gt;

   + WinEdt community's home page
     &lt;http://www.winedt.org/&gt;

     WinEdt.org is a place for users of WinEdt to share configuration
     components, macros, plug-ins etc.

     It also hosts a list of frequently asked questions:
     &lt;http://www.winedt.org/Doc/FAQ/&gt;

   + The WinEdt Mailing List messages are archived at
     &lt;http://groups.yahoo.com/group/WinEdt&gt;

   + Links for LaTeX and friends:
     - the UK TUG TeX FAQ: &lt;http://www.tex.ac.uk/faq&gt;
     - the international TeX newsgroup &lt;news:comp.text.tex&gt;, offering
       quick and knowledgeable help
     - its archive can be found at
       &lt;http://groups.google.com/groups?group=comp.text.tex&gt;
     - the MiKTeX mailing lists (see &lt;http://www.miktex.org/lists.html&gt;)

   + If you have any suggestions for these guidelines, please contact me
     at &lt;robert&lt; at &gt;winedt.org&gt;

   ---------------------------------------------------------------------

   Happy WinEdt'ing!

   For the WinEdt.org team,
    robert&lt; at &gt;winedt.org


Last changed on: $Date: 2003-04-26 16:41:23+02 $





</description>
    <dc:creator>WinEdt.org</dc:creator>
    <dc:date>2008-05-01T12:27:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3686">
    <title>ANN: WinEdt 5.6</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3686</link>
    <description>Beta version of WinEdt 5.6 is now available for testing.

Read the instructions carefully and proceed accordingly. You
should also read the What's New section for description of all
the changes, bug fixes, etc...

This version may not be for everyone: Macros in Exec folder
have been rewritten and the Accessories Menu for MiKTeX and TeX
Live has been changed to call the new (common) macros that can
execute console applications in WinEdt's Console. Restoring the
old macros in Exec folder or the old Accessories Menu will not
(can not!) work properly with the new Execution Modes...

Documentation is yet to be updated: reading the What's New
file is the only way to get familiar with the new
functionality.

Have fun.

Best regards,

alex

</description>
    <dc:creator>WinEdt Team</dc:creator>
    <dc:date>2008-04-30T17:27:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3682">
    <title>Who can put word DRAFT on all pages in a latex doc?</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3682</link>
    <description> 

Tusiime Swaleh
Physics Department
Makerere university
Box 7062 Kampala
Uganda
Mob. +256 0752 520159
Email:stusiime&lt; at &gt;physics.mak.ac.ug
    tsmswlh&lt; at &gt;yahoo.com
Hope you are all fine, 

problem: You know in microsoft word you can print a document with some 
wording like 'DRAFT' to appear on all pages of your document, 

fancyhdr package (for moving headers and footers)seem not to be able to do 
it. 

How is it done in latex? who knows? any help? 

yours tusiime s

</description>
    <dc:creator>stusiime&lt; at &gt;physics.mak.ac.ug</dc:creator>
    <dc:date>2008-04-29T17:10:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3677">
    <title>F3 ?</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3677</link>
    <description>Dear Colleagues -- Working hard to identify a problem
with a Perl program edited using WinEDT, I am being
driven to distraction by the latter's out-of-the-box
treatment of "F3" after "Ctrl-F".  "Ctrl-F" launches
a "Find" dialogue box, as a Windows user would
expect, but "F3" does /not/ perform a "Find next",
unlike most (every ?) other Windows program.
Is this intentional, if so what is the reason,
and can it be fixed by the user ?

Philip TAYLOR

</description>
    <dc:creator>Philip TAYLOR (Ret'd</dc:creator>
    <dc:date>2008-04-29T16:47:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3673">
    <title>CE character</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3673</link>
    <description>Hi!
I have for me serious troubles with use of CE character set.

I don't know, how to permanently convince WinEdt to use CE. Now every 
time when start WinEdt, regardless that i select in Preferences for 
fonts Curier New with CE scripts, it show document in Default windows 
character sets (i see \`{c} insead of \v{c}, presented in LaTeX 
notation). This I can every time fix manuely by selection in 
options/fonts CE character set. This is only annoying, but when i try to 
use find--replace function, WinEdt some character which i like to 
replace with \v{c} replace with just c ...

Described problem I didn't observe at \v{s} and \v{z} character.

Please help mi fix this problem.

Regards, Zarko

</description>
    <dc:creator>Zarko Cucej</dc:creator>
    <dc:date>2008-04-25T12:26:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3670">
    <title>Help with parsing bracketed parameters (non WinEdt related question)</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3670</link>
    <description>Hi,
This is a non-WinEdt related question...  but elsewhere I've found no help
with it!

I'm writing a class style for LaTeX. But I want my commands to parse
optional commands enclosed in [ ].

I know I must use something like \&lt; at &gt;ifnextchar[ , but I haven't been able to
understand the examples I've looked up in the net. I found out, though, that
the syntax of such a command is:

\&lt; at &gt;ifnextchar&lt;char&gt;{truecase}{falsecase}

My problem is how to incorporate it in the command.

Note that I don't want to parse optional parameters with the LaTeX 2e
command-definition syntax (\newcommand{\name}[1][1]...), since this doesn't
allow me to use bracketed optionals.

Any tips?

Thanks in advance.

Nicolas Vaughan
</description>
    <dc:creator>Nicolas Vaughan</dc:creator>
    <dc:date>2008-04-16T16:50:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3657">
    <title>Log examination</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3657</link>
    <description>I'm using Winedt build 20071003 (v. 5.5). The minimal input is the file 
showing my problem is

--------------------------------------------
\documentclass[12pt]{article}
\begin{document}
Hello world!
\end{document}
-------------------------------------------

I run this file through pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7). 
Next, I hit the log button in Winedt. That causes a pop up warning (and 
no log display at screen bottom). The warning says

  ")" Expected
  [FindError(1,1,0,1,0,0 ^^^,0,4);]

I have no idea what this means or what to do about it. BTW, all was 
working but I haven't done any tex-ing for a while and now this - no 
updates since installation. Any ideas what is going on and what to do 
about it. The log file is included below. Thanks for any help.

</description>
    <dc:creator>Bernice Barnett</dc:creator>
    <dc:date>2008-04-14T05:41:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3653">
    <title>Problem with Dictionary manager</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3653</link>
    <description>Hi,
I've been having some problems with WinEdt's (5.5 b. 20071003) Dictionary
manager:

   1. I currently use mainly three dictionaries (apart from WinEdt's and
   LaTeX's): English, Spanish and Latin. I usually need to add words to any of
   these, but WinEdt doesn't ask me to which one. It adds them to the first
   dictionary on the list (English, in my case). All the options of the three
   dictionaries are the same (modified, load on start, add new words, and
   compounded words are all checked) .
   2. As a result, I've had to manually add words to these dictionaries.
   But when I ask the Dictionary manager to sort the dictionaries, these remain
   unchanged.

Any tips?

Thanks a lot!

Nicolas Vaughan
</description>
    <dc:creator>Nicolas Vaughan</dc:creator>
    <dc:date>2008-04-13T18:20:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3649">
    <title>Hyperref</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3649</link>
    <description>Hi there,

I have a LaTex file that makes use of the hyperref package. When I generate
the dvi in my desktop using WinEdt the hyper links work perfectly, but when
I do the same thing in my laptop id doesn't. I believe both WinEdt and Yap
versions are the same. Apparently, there is some configuration that is
different but I just can't recall changing anything or find any different
configuration.

Any ideas on how to make my Laptop's Texify (using WinEdt) to insert the
hyperlinks in the generated dvi?

Cheers,
Marcel

********************************************
Dr. Marcel Oliveira
Research Fellow
Department of Computer Science and Applied Mathematics
Universidade Federal do Rio Grande do Norte
Brazil
********************************************  


</description>
    <dc:creator>Marcel Oliveira</dc:creator>
    <dc:date>2008-04-12T11:09:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3648">
    <title>Problem with the mouse</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3648</link>
    <description>This is my problem: when I edit any text in WindEdt,
the focus of the mouse is moving all the time.
If I click the mouse in a position in an open text,
the blinking cursor indicating the WinEdt current position 
is placed correctly there but, if I click again without
moving at all the mouse, the cursor appears in a different
place (a few lines above). 
This is very annoying. In particular, I can't do double-clicking.
It does not depend on the mouse. The touchpad of the laptop
or an external USB mouse do the same.

This behavior only happens when editing  WinEdt texts,
not in other applications (including WinEdt Help).

Has anybody experienced a similar problem?

Thanks,

Paco Lopez

My configuration:
Dell Inspiron 94000, Windows Vista Ultimate


********************************
Francisco J. Lopez Fraguas
Dep. Sistemas Informaticos y Computacion
Fac. Informatica U. Complutense Madrid
Prof. Jose Garcia Santesmases s/n
28040 Madrid
Spain

fraguas&lt; at &gt;sip.ucm.es
Tel: +34 91 3947630
Fax: +34 91 3947529
********************************



</description>
    <dc:creator>FRANCISCO JAVIER LOPEZ FRAGUAS</dc:creator>
    <dc:date>2008-04-12T05:19:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3645">
    <title>External execution macro + log support</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3645</link>
    <description>Hello,

I use WinEdt for quite a while now, but I am not very familiar
with the Macro language.

I have a java program I would like to execute and capture the
results in a log file. What I had in mind was to execute a bat
file such as

java -jar myjar.jar %1 &gt;&gt; %2

where %1 would be a set of parameters sent by winedt,
say the current file name or something like it, and %2
would be some log file name that I would like to integrate
within find errors window (usually docked underneath the
editor window itself).

I looked into the manuals, and the Texify.edt, Latex.edt,
but it sounded quite a task to understand it all. And I
wondered if somebody had already done something similar,
or could give me some hints/tips on how to achieve that, please.

Many thanks :-)

Best,
Leo

</description>
    <dc:creator>Leonardo Freitas</dc:creator>
    <dc:date>2008-04-11T07:32:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3642">
    <title>REQ:  Are you interested in doing some WinEdt support and customisation?</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3642</link>
    <description>Hello

Here at The Open Univerity, we use TeX to produces Mathematics and
upper-level Physics courses, and I'm hired as the resident TeX expert.
For this year and next I'm working two days a week on another project,
and so we're looking for someone to help us out with WinEdt.  

We're looking for someone to answer support questions, help with
configuration and do some menu customisation.  If you're familiar with
WinEdt and its documentation, and have good electronic communication
skills, then you're well placed to do this paid work.

If you're interested, please send me an email.  (And in case you're
wondering, I already asked Alex, and he said he was too busy.)


Jonathan
</description>
    <dc:creator>J.Fine</dc:creator>
    <dc:date>2008-04-10T14:56:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3637">
    <title>what happened with eps2pdf?</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3637</link>
    <description>After a long time without using it, I need now to convert eps graphics
to pdf. In the past I used the eps2pdf tool that I installed with the
old MUI interface. But now it seems that the old MUI does not work
anymore (maybe because it was replaced inside winedt.exe?) and each
time I try to run the epstopdf.edt macro, nothing happens. Any clue?

Thanks  a lot in advance!

Best regards,

Agustín


</description>
    <dc:creator>=?iso-8859-15?Q?Agustin_E._Bolz=E1n?=</dc:creator>
    <dc:date>2008-04-04T15:14:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3636">
    <title>Question about project tree</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3636</link>
    <description>Hi,

For many LaTeX projects I use the \input command to retrieve files from 
various directories. If the path information appears explicitly in the 
\input command (for example \input{path/filename}), this appears 
correctly in the project tree as "path/filename" (without quotes) and 
clicking on it opens the corresponding input file. However, if the path 
information is stored in a LaTeX variable (say, \mypath), then 
\input{\mypath/filename} produces "? filename" and clicking on it will 
result in a 'file not found' error message.

My question, therefore, is there a way of transmitting the path 
information in \mypath to the project tree macro? I presume this would 
have to involve retrieving this information from some file header which 
would be okay. (And if it should be possible, I would like the project 
tree to show only "filename" and suppress the path information.) I am 
perfectly willing doing some programming myself if I get pointed to the 
right files to get started.

Thank you.
--hh

PS: I use WinEdt build: 20071003  (v. 5.5).

</description>
    <dc:creator>Helmut Haberzettl</dc:creator>
    <dc:date>2008-04-03T15:21:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3635">
    <title>New version of WinEdt?</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3635</link>
    <description>Hi,
When is the new version of WinEdt due? What are the new goodies in it?
Thanks!
José Romero
</description>
    <dc:creator>Pepe Romero</dc:creator>
    <dc:date>2008-04-02T19:42:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.editors.winedt/3632">
    <title>Mailing List Guidelines</title>
    <link>http://comments.gmane.org/gmane.editors.winedt/3632</link>
    <description>
      WinEdt Mailing List Guidelines
      ==============================


   These guidelines are sent to the WinEdt Mailing List once a month.
   Please keep them in mind when posting to the list.

   ---------------------------------------------------------------------

* What To Post

   The WinEdt Mailing List is for questions about the WinEdt editor. You
   should  not post questions concerning LaTeX, MiKTeX, BibTeX et al. to
   the mailing list. WinEdt is a shell/editor for  LaTeX  etc.  and  the
   list  is  intended  to  answer questions concerning WinEdt, not LaTeX
   etc.
   (Sometimes it might be difficult  to  decide  whether  a  problem  is
   related to WinEdt or to MiKTeX, LaTeX etc. A rule of thumb is: If you
   are having the same  problems  when  running  the  program  from  the
   command line, it is NOT related to WinEdt.)

   A lot of questions are being asked over and over  again.  Check  that
   your question isn't already answered in the WinEdt FAQ at
      &lt;http://www.winedt.org/Doc/FAQ&gt;
   or in the mailing list archives at
      &lt;http://groups.yahoo.com/group/WinEdt&gt;.

   When sending a question to the mailing list, try to be specific.
   Include (at least)
     + the Build number of your WinEdt (see "Help | About WinEdt...")
     + your operating system (e.g.: "Windows 2000, Service Pack 2")
     + a detailed description of the problem and how to reproduce it.

   If you have received one or more answers that  solved  your  problem,
   you  can  give  something  back  to the WinEdt community by writing a
   summary that can be integrated in the WinEdt FAQ. You can either send
   it to the list, or directly to the maintainer of the FAQ.

   Do NEVER post your registration key. Nobody needs to know it.


* How To Post

   Use plain-text format. Not everybody can (or wants to) read HTML.

   Use a meaningful subject line that will  make  sense  to  the  people
   whose help you are trying to get.

   Do not quote entire messages just to add a few lines at the beginning
   or  end.  Instead, quote the parts to which you are directly replying
   or quote enough to establish the context.
   Everybody on the list has already received the message that  you  are
   quoting,  and anyone searching the archive will find your message and
   the previous message listed under the same thread.

   Do not start a new thread by replying to  an  unrelated  message  and
   just  changing  the  subject  line.  For people who group messages by
   threading in their mailer, your  mail  will  appear  as  one  of  the
   replies  to the original message. It is better to start a new message
   for a new thread.

   The preferred language on the WinEdt Mailing List  is  English.  This
   does  not  imply disrespect to other languages, but simply guarantees
   the best possible communication as English is the language  that  the
   largest number of subscribers are able to understand.

   Since the WinEdt list has been used for unwittingly spreading viruses
   in  e-mail  attachments  in the past, all attachments will be removed
   from your mails. All relevant  documents  (if  any)  are  text  files
   anyway, which you can include in the body of your message.

   Do not request return receipts.

   If you are "out of office" and you want to set up  an  auto-responder
   for  your  e-mail  account,  please   unsubscribe   from   the   list
   temporarily!


* Unsubscribing + More

   To unsubscribe from the WinEdt Mailing List, send an empty  mail  to:
   &lt;winedt+list-unsubscribe&lt; at &gt;wsg.net&gt;  from  the  account  that  you  are
   subscribed with.

   DO NOT send a mail to the list! This will have no effect  apart  from
   annoying the subscribers.

   The complete list of administrative commands for the  WinEdt  Mailing
   List can be found here: &lt;http://www.winedt.org/Doc/listinstr.php&gt;


* Links

   + The WinEdt home page
     &lt;http://www.winedt.com/&gt;

   + WinEdt community's home page
     &lt;http://www.winedt.org/&gt;

     WinEdt.org is a place for users of WinEdt to share configuration
     components, macros, plug-ins etc.

     It also hosts a list of frequently asked questions:
     &lt;http://www.winedt.org/Doc/FAQ/&gt;

   + The WinEdt Mailing List messages are archived at
     &lt;http://groups.yahoo.com/group/WinEdt&gt;

   + Links for LaTeX and friends:
     - the UK TUG TeX FAQ: &lt;http://www.tex.ac.uk/faq&gt;
     - the international TeX newsgroup &lt;news:comp.text.tex&gt;, offering
       quick and knowledgeable help
     - its archive can be found at
       &lt;http://groups.google.com/groups?group=comp.text.tex&gt;
     - the MiKTeX mailing lists (see &lt;http://www.miktex.org/lists.html&gt;)

   + If you have any suggestions for these guidelines, please contact me
     at &lt;robert&lt; at &gt;winedt.org&gt;

   ---------------------------------------------------------------------

   Happy WinEdt'ing!

   For the WinEdt.org team,
    robert&lt; at &gt;winedt.org


Last changed on: $Date: 2003-04-26 16:41:23+02 $





</description>
    <dc:creator>WinEdt.org</dc:creator>
    <dc:date>2008-04-01T07:25:07</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.editors.winedt">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.editors.winedt</link>
  </textinput>
</rdf:RDF>
