headers
David Denton | 2 Jan 13:31

WinEdt and Unicode

Hello WinEdt users,

Happy New Year!

I am working on documents that are primarily in English but contain
words or phrases written in Cree syllabics, for which there exist only
limited Latex font support. However, there are several TrueType
Unicode and 8-bit fonts for this script.

I waited patiently until Miktex 2.7 was released and then tried Xetex.
With a bit of fiddling I was able to compile my documents using the
Unicode version of the font, but not using WinEdt. I read the WinEdt
help concerning the limited UTF-8 support, and do not see how this
could help. I eventually used a Unicode editor (Texmaker) and
everything seemed to work very well.

My problem is I am loath to put WinEdt aside for a vastly inferior
editor, but I am not sure what choice I have. I tried compiling the
document with Xetex using WinEdt and the 8-bit version of the font
which uses the upper ASCII codes. This was not a success, and I later
learned that Tex or Latex uses some of these as control codes. Does
anyone have any ideas on how this could be done? This could solve my
problem in the short term.

So this is where things stand. Xetex works very well with the Unicode
version of the font when I use a Unicode aware editor, but not with
WinEdt. Is there any convenient work-around that will allow me to
continue to use WinEdt? Or, are there any new developments re: Delphi
and when we might see a Unicode version of WinEdt? (I have read the
various postings of Alex on this issue).
(Continue reading)

Permalink | Reply | 3 comments |
headers
Evan Cooch | 2 Jan 13:55
Picon
Favicon

Re: WinEdt and Unicode

Try LEd (LaTeX Editor) - http://www.latexeditor.org/

I seem to recall that it has UNICODE support - either native (latest 
build), or as an add-on. I'm loathe to recommend something other than 
WinEdt (which I prefer for the sort of work I do), but there are some 
features in LEd which might be of use to some users.

David Denton wrote:
> Hello WinEdt users,
>
> Happy New Year!
>
> I am working on documents that are primarily in English but contain
> words or phrases written in Cree syllabics, for which there exist only
> limited Latex font support. However, there are several TrueType
> Unicode and 8-bit fonts for this script.
>
> I waited patiently until Miktex 2.7 was released and then tried Xetex.
> With a bit of fiddling I was able to compile my documents using the
> Unicode version of the font, but not using WinEdt. I read the WinEdt
> help concerning the limited UTF-8 support, and do not see how this
> could help. I eventually used a Unicode editor (Texmaker) and
> everything seemed to work very well.
>
> My problem is I am loath to put WinEdt aside for a vastly inferior
> editor, but I am not sure what choice I have. I tried compiling the
> document with Xetex using WinEdt and the 8-bit version of the font
> which uses the upper ASCII codes. This was not a success, and I later
> learned that Tex or Latex uses some of these as control codes. Does
> anyone have any ideas on how this could be done? This could solve my
(Continue reading)

Permalink | Reply | 2 comments |
headers
Evan Cooch | 2 Jan 14:00
Picon
Favicon

Re: WinEdt and Unicode


Evan Cooch wrote:
> Try LEd (LaTeX Editor) - http://www.latexeditor.org/
>
> I seem to recall that it has UNICODE support - either native (latest 
> build), or as an add-on. I'm loathe to recommend something other than 
> WinEdt (which I prefer for the sort of work I do), but there are some 
> features in LEd which might be of use to some users.
>

The one feature LEd has which would be *really* helpful to me if in 
WinEdt is code folding (wherein parts of the source text can be 
collapsed to one line. This feature lets you temporarily hide fragments 
that you do not wish to see at the moment. You can also see the folded 
part in a  hint.) For those of us working with ginormous files, where 
only small sections are changing at any one time (e.g., books, where 
you're tweaking only a few paragraphs in a chapter), this feature would 
save us/me *tons* of time spent scrolling.
Permalink | Reply | 1 comment |
headers
Ulrich Dirr | 2 Jan 14:12
Picon
Favicon

RE: WinEdt and Unicode

I would like to strongly second unicode support for WinEdt ...

On Wednesday, January 02, 2008 2:00 PM Evan Cooch wrote:
> The one feature LEd has which would be *really* helpful to me if in
> WinEdt is code folding (wherein parts of the source text can be
> collapsed to one line. This feature lets you temporarily hide
> fragments that you do not wish to see at the moment. You can also see
> the folded part in a  hint.) For those of us working with ginormous
files, 
> where only small sections are changing at any one time (e.g., books,
where
> you're tweaking only a few paragraphs in a chapter), this feature
would
> save us/me *tons* of time spent scrolling.

and not only folded to one line but to a special marker -- just think of
a document with a bunch of index entries, folding these would make your
source document much more readable ;-)

Ulrich
Permalink | Reply | 0 comments |
headers
WinEdt.org | 2 Jan 17:33

Mailing List Guidelines


     .°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.°.

               HAPPY NEW YEAR TO THE WinEdt COMMUNITY!

     ^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^.^

      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
      <http://www.winedt.org/Doc/FAQ>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Justin Zhu | 3 Jan 04:49
Picon
Picon
Favicon

eps figures in dvi

Hi,

I use \includegraphics* to display my .eps figures. I 
'latex' the file first and view it use dvi. Why sometime 
the figure appears, other time the figure does not? All 
figures appear when I convert to pdf. Only in div some 
appears, others don't.

Justin
Permalink | Reply | 2 comments |
headers
Paolo Radaelli | 3 Jan 09:59
Picon
Favicon

Re: eps figures in dvi

In order to corretctly display your .eps figures you have to convert the dvi 
into ps.
Dvi is not a correct previewer when you include eps (or pdf) figures.
Paolo

----- Original Message ----- 
From: "Justin Zhu" <j.zhu <at> imb.uq.edu.au>
To: <winedt+list <at> wsg.net>
Sent: Thursday, January 03, 2008 4:49 AM
Subject: [WinEdt] eps figures in dvi

> Hi,
>
> I use \includegraphics* to display my .eps figures. I 'latex' the file 
> first and view it use dvi. Why sometime the figure appears, other time the 
> figure does not? All figures appear when I convert to pdf. Only in div 
> some appears, others don't.
>
> Justin
>
Permalink | Reply | 1 comment |
headers
Evan Cooch | 3 Jan 13:04
Picon
Favicon

Re: eps figures in dvi

Depends on which DVI previewer you use. If you use yap (which comes 
bundled with MikTeX), then .eps figures are viewable in the dvi if the 
selected render method is appropriate - newest version of yap defaults 
to auto, and should show .eps figures automatically.

To say that you *have* to convert the dvi to ps (or to pdf) is incorrect.

Paolo Radaelli wrote:
> In order to corretctly display your .eps figures you have to convert 
> the dvi into ps.
> Dvi is not a correct previewer when you include eps (or pdf) figures.
> Paolo
>
> ----- Original Message ----- From: "Justin Zhu" <j.zhu <at> imb.uq.edu.au>
> To: <winedt+list <at> wsg.net>
> Sent: Thursday, January 03, 2008 4:49 AM
> Subject: [WinEdt] eps figures in dvi
>
>
>> Hi,
>>
>> I use \includegraphics* to display my .eps figures. I 'latex' the 
>> file first and view it use dvi. Why sometime the figure appears, 
>> other time the figure does not? All figures appear when I convert to 
>> pdf. Only in div some appears, others don't.
>>
>> Justin
>>
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Claudio Beccari | 4 Jan 11:08
Picon
Favicon

I fear WinEdt should make a quantum leap...

Dear all,
I suppose everybody noticed that the engine that drives all the workings 
of the TeX system is not anymore TeX the program, but it is pdfetex! 
This is true with all distributions of the TeX system, in particular 
with MiKTeX and TeXlive, the two distributions for which WinEdt is 
particularly suited as "the" editor front end.

May be not all users are aware that pdfetex can work in eight modes 
according to three different settings that are set by default during 
initialization of the system, but can be changed by the shell editor 
and/or by the user.

One is given by the value of the system counter \pdfoutpout; when its 
value is zero, pdfetex produces the traditional DVI ouput, when its 
value is greater than zero the ouput is in the  PDF format. Some 
implementations of the executable pdfetex require the setting of an 
option, some others accept the setting of the value in the command line 
used by the shell editor macro.

The second setting is the ability of activating the \write18 internal 
command; if this command is not activated, the engine behaves as a 
standalone executable, while if it is activated the engine can shell to 
other programs that can perform intermediate tasks hopefully on behalf 
of the engine itself. "Hopefully" means that malicious code can be 
activated, so that it is important that the \write 18 capability be 
activated only in protected platform environments.

The third setting allows to use the engine in extended mode, that is to 
exploit the new features of etex; the number of boxes or registers is no 
more limited to 256, and a new bunch of new commands are available that
(Continue reading)

Permalink | Reply | 0 comments |
headers
RS | 5 Jan 03:30
Picon

Re: I fear WinEdt should make a quantum leap...

Hi Claudio,

a long message ... ;-)

I think you are raising some interesting issues, however, I don't agree
with all you say.

On 04.01.2008 11:08, Claudio Beccari wrote:
> I suppose everybody noticed that the engine that drives all the
> workings of the TeX system is not anymore TeX the program, but it is
> pdfetex! This is true with all distributions of the TeX system, in
> particular with MiKTeX and TeXlive, the two distributions for which
> WinEdt is particularly suited as "the" editor front end.

The fact that pdfetex is the default engine even for dvi output is
transparent to the users, ie. it doesn't make a difference for them
whether the dvi file is generated with etex+latex.fmt or with
pdfetex+latex.fmt+\pdfoutput=0. Therefore I think the following points
are irrelevant as far as WinEdt is concerned. Which engine to use is,
and should be, configurable in the TeX system (miktex's options dialog,
texlive's texmf.cnf), and should not be the front end's business.

> May be not all users are aware that pdfetex can work in eight modes 
> according to three different settings that are set by default during 
> initialization of the system, but can be changed by the shell editor 
> and/or by the user.
> 
> One is given by the value of the system counter \pdfoutpout; when its
>  value is zero, pdfetex produces the traditional DVI ouput, when its 
> value is greater than zero the ouput is in the  PDF format. Some
(Continue reading)

Permalink | Reply | 0 comments |

Gmane