Igor Spectorsky | 6 Feb 20:29 2016
Picon

Translation tables: using#<code>

Hello,

Working in Winedt5, I translated my tex-files, typed in cp866 
(precisely, in cp866nav), into cp1251, using read and write translation 
tables. It was convenient to prepare such tables using #<code> syntax. 
For example, #128 -> #192 instructed Winedt5 to read Cyrillic "А". 
However, in Winedt9.1, because of Unicode, it it now necessary to write 
code > 255 after #, and it is not supported.

So, is it possible in Winedt9.1 to use #<code> (or something like that) 
for code >255?

Thanks in advance,
Igor

Ulrich Diez | 6 Feb 00:09 2016
Picon

WinEdt 5.5 - How to disable any paragraph wrapping while keeping wrapping of that line where one is currently typing/inserting text?

Hello!

WinEdt-Release in use:
Build: 20071003  (v. 5.5)

OS in use:
Windows 98 SE in virtual machine run under Windows 7 Professional.

I would like the wrapping-behavior of WinEdt 5.5 as follows:

a) While typing text, in case a word doesn't fit into the current line any
   more without the line becoming longer than indicated by the
   "right margin", that word shall be wrapped into a new line.

   In case this happens in the middle of an already typed paragraph while
   inserting something, the paragraph shall _not_ be re-wrapped but a new
   line shall be inserted beginning with the word that caused breaking the
   line.

b) In case I hit "return/enter" on the keyboard while typeing/inserting text 
   into a line, I'd like to have a linebreak at the place where the cursor was blinking
   leading to material that before hitting "return/enter" in the line in question 
   trailed the cursor-position after hitting "return/enter" occuring on a line
   of its own, not affecting the wrapping of previous or subsequent lines.

I'd like this as hard-wrapping, i.e., linebreaks in the WinEdt-editing-
window shall lead to return-characters being inserted in the text-file.

In other words: I would like to have some hard wrapping of that line
where one is currently typing/inserting text but no paragraph-wrapping
(Continue reading)

Matthias Studer | 3 Feb 12:44 2016
Picon
Picon

WinEdt and Druide Antidote

Dear All,

 

Druide antidote is an excellent spell and grammar checking program for French and recently English (http://www.antidote.info/antidote/). It supports LaTeX. I was wondering if someone knows a way to make it work from within WinEdt. It is already possible to do it in many programs.

 

Thanks,

Matthias

 

 

Leonard Maximon | 1 Feb 19:18 2016
Picon

WinEdt 8.2

I have WinEdt 8.2.2014.613  Is this compatible with Windows 10?

Per Ting | 29 Jan 00:58 2016
Picon

"Miktex update wizard" grayed out

Recently the "Miktex update wizard" selection on Winedt 9.1 shows as grayed out. I am using windows 10.

Thanks for the help,

Per
Whitten, Blake | 14 Jan 15:43 2016
Picon

Problem with Toolbar Button

Hi. I customized the toolbar in Version 9.1 (with Windows 7 and Miktex 2.9) and would like to add a button to close all files, in other words, the menu function

 

Windows à Close All

 

The button I tried is

 

BUTTON="Close All"

 

but this doesn’t appear to work. Do I need a different spelling than “Close All” to get the button to work?

 

Thanks!

 

Blake Whitten

University of Iowa

 

 

 

From: WinEdt Team [mailto:support <at> winedt.ca]
Sent: Tuesday, January 05, 2016 12:04 PM
To: winedt+list <at> wsg.net
Subject: Re: [WinEdt] Problems with Directory settings

 

Norbert,

 

> but when I "save" it is saved under W://chapter_b/master.tex and
> NOT under W://master.tex (whether it is \ or // ... I am not sure
> ...) if I opened file_b.tex last.

 

Are you talking about Save As (with Windows common Dialog) or just
plain Save? (there is a difference)

 

> I would like to have all files to be saved automatically to where
> they were opened from, not to another directory.

 

Save does not change the filename or directory. Save As might start
in a different folder (depending on how it is configured).

 

> p.s. Also the .bak-files are not created anymore. How can I invoke
> them again?

 

Again, no idea other than possibly something that you might have
done. Reloading your customizations might save all your problems.

 

Did you previously customize the main menu and placed your custom
ini file in some non-standard directory (other than the default)?

 

Did your local folder %b change recently (for whatever reason)?

 

Your menu customizations could be overwritten with defaults when
you install DocZoom package if it cannot find your custom
MainMenu.ini file. Reloading your customization (wherever you might
have placed it) will restore the previous behavior. By default Save
As menu item is defined as:

 

  ITEM="Save_As"
    CAPTION="Save &As..."
    IMAGE="SaveAs"
    // Change start folder to %p if you want the dialog in the same folder!
    START_FOLDER="%!P"
    MACRO="SaveDocAs;"
    REQ_DOCUMENT=1

 

You might have changed the startup folder to %p but this got lost
if your MainMenu.ini file is not where it should be when you
installed DocZoom (which adds two extra shortcuts to the menu).

 

The same probably explains the backup "problem" (it can be
configured in the Preferences Dialog) but I cannot guess when and
how it changed. Preferences Dialog also contains an option "Change
Folder on Open" which may have changed and you are puzzled by it.
If you customized some settings through Preferences Dialog and then
later modify and load their "native" ini scripts there could be
some conflict in settings for Preferences Dialog. I don't have
enough info and guessing is all I can do. Reload your modifications
and then Start Preferences Dialog and press OK to update those
settings with your changes.

 

Anyway, you should know what you customized and how you did it...

 

best regards,

 

alex

 

ps. If all you wanted to do is to make the font larger you could
have used the Preferences Dialog to change the font size once and
forever.

 

Karl Koeller | 4 Jan 21:16 2016

Re: << using my own compilation sequence >>

Il 04/01/2016 20:51, I. Camps ha scritto:
> Hello,
>
> I am trying to compile a latex book using the "The Legrand Orange 
> Book" template downloaded from LatexTemplates.com 
> (http://www.latextemplates.com/template/the-legrand-orange-book).
>
> The running command to get the full stylized book is:
>
> 1) pdflatex main
> 2) makeindex main.idx -s StyleInd.ist
> 3) biber main
> 4) pdflatex main x 2
>
> I would like to know how to create a button that do all these steps. 
> Something like PDFTeXify.
>
> Best regards,
>
> Camps

Hi Camps.

In your local copy of MainMenu.ini add the lines (in the place you want it)

     ITEM="Legrand"
       CAPTION="Legrand Orange Book"
       IMAGE="BookLaTeX"
       SAVE_INPUT=1
MACRO=`Assign("Old-BibTeX-Executable","%$('BibTeX-Executable');");`+
             `Assign("BibTeX-Executable","biber.exe");`+
`Assign("Old-MakeIndex-Switches","%$('MakeIndex-Switches');");`+
             `Assign("MakeIndex-Switches","-s StyleInd.ist");`+
             `Exe('%b\Exec\TeX\PDFTeXify.edt');`+
`Assign("BibTeX-Executable","%$('Old-BibTeX-Executable');");`+
             `Release("Old-BibTeX-Executable");`
`Assign("MakeIndex-Switches","%$('Old-MakeIndex-Switches');");`+
             `Release("Old-MakeIndex-Switches");`
       REQ_FILTER=:"%!M=TeX"|"%!M=TeX:STY"|"%!M=TeX:AUX"

and in your local copy of Toolbar.ini (in the place you want it) simply

   BUTTON="Legrand"

Best regards,

Karl

I. Camps | 4 Jan 20:51 2016
Picon
Gravatar

<< using my own compilation sequence >>

Hello,

I am trying to compile a latex book using the "The Legrand Orange Book" template downloaded from LatexTemplates.com (http://www.latextemplates.com/template/the-legrand-orange-book).

The running command to get the full stylized book is:

1) pdflatex main
2) makeindex main.idx -s StyleInd.ist
3) biber main
4) pdflatex main x 2

I would like to know how to create a button that do all these steps. Something like PDFTeXify.

Best regards,

Camps
Lemenn | 4 Jan 18:49 2016
Picon

Debugging macros / Appending to file

Hello Alex ! Happy New Year !

I'm writing a macro like this :

Exe('Debug.edt','%b\Macros', 111, "%X", "<message>");

that will append to a .log file, say:    Debug.log
something like:

YYYY-MM-DD_HH:NN:SS %X   (date + full path of macro file)
<message>

"<message>" is something i export to Debug.log, usually the contents
of some string registers.

This way, when something goes bad with a macro, I can look
at the contents of  Debug.log

Is it possible to append some text to an existing file ?
(OpenOutput resets the file to 0 byte and WriteFile does the same)

Thanks by advance.

Wermes Norbert | 4 Jan 13:15 2016
Picon

Problems with Directory settings

Alex,
I have problems both in WinEdt 7.1 and 9.1 regarding the directory structures of a project.
It worked fine so far but was changed "beyond my understanding" by trying to install Karl's DocZoom.

My setup is on a MAC under Parallels, but this should not matter in principle.
I am using Build: 20150731  (v. 9.1) - 32-bit on a MAC under Parallels 9.
I switched to WinEdt 9.1 6 weeks ago and registered last week. WinEdt 7.1 I also still have installed.

I uninstalled DocZoom and deleted everything. The problem persists, though. It is the same in WinEdt 7 and 9.

Here is the problem. I am writing a book with 20 chapters, each in a directory included in Latex via \include from master.tex
The files are collected in a WinEdt "project".

i.e.
w://master/masterproject.prj  (contains master.tex, file_a.tex, file_b.tex)

ALL files are always saved under the directory tree of the last opened file. 
For example for master.tex: at the top of the WinEdt 9.1 window is written: WinEdt 9.1 - [W:\master.tex]

but when I "save" it is saved under
W://chapter_b/master.tex and NOT under W://master.tex (whether it is \ or // ... I am not sure ...)
if I opened file_b.tex last.

I would like to have all files to be saved automatically to where they were opened from, not to another directory.

thanks for any advice
Norbert

p.s.
Also the .bak-files are not created anymore. How can I invoke them again?
Arkady Kitover | 3 Jan 00:53 2016
Picon

Magnifying glass.

Is it possible to increase the visible size of font in winedt. Would be very convenient for people with bad vision like myself.

Thank you for possible answers!

Arkady


Gmane