Hi alex,

LstGetItem doesn't seem to work correctly -- it always returns the first
item from the list:

LetReg(0,"a|b|c")
LstEnum("%!0","|");
LstGetItem(1,2);
Prompt("%!1");

Secondly, totally unrelated, is it (or rather could it be made) possible
for the user to select more than one item in MUI lists?


Regards,
--
   Robert

Hi all,

when I enter the \cite{} command the usually the "Bibitems" pop up is
opened. If a \ref{} command precedes the \cite{} command in the same
line, I get the "Labels" pop up on typing the closing brace ...

Can anyone confirm this and/or knows how to fix this?

Best regards,
Hanno Dierke

PS: version is 5.5 (20070716)

> LstGetItem doesn't seem to work correctly -- it always returns the first
> item from the list:
>
> LetReg(0,"a|b|c")
> LstEnum("%!0","|");
> LstGetItem(1,2);
> Prompt("%!1");

Correct. This has now been fixed.

> Secondly, totally unrelated, is it (or rather could it be made) possible
> for the user to select more than one item in MUI lists?

This has now been added to MUI ListBox (currently it is not
possible to have multiple selections).

List Box now has extra properties:

   multi select: 0/1
   selected: 0/1 (for each item)
   selected count (readonly)

Example:

MUIReset;
   MUIAdd(5,5,145,60, 'MyListBox','TListBox','','A|B|C|D');
     MUISet("MyListBox",'multi select','1');
     MUISet("MyListBox",'selected','0','-1'); // deselect all
     MUISet("MyListBox",'selected','1','0');  // select the first item
     MUISet("MyListBox",'selected','1','1');  // and the second item
   // etc ...
   MUIShow; // (De)Select what you will ...

   // You must iterate through all the items to see which ones
   // are selected...
   MUIGet("MyListBox",'count',2);
   LetRegNum(1,0);
:Iterate_Selections:: =====
   IfNum(%!1,%!2,'>=',"JMP('Done');");
   MUIGet("MyListBox",'selected','0','%!1');
   IfNum('%!0','0','=','JMP("NOT_Selected");');
   MUIGet("MyListBox",'item','3','%!1');
   // We know that %!1 is selected: do something....
   Prompt('Selected: %!1 "%!3"');
:NOT_Selected:: ====
   LetRegNum(1,'%!1+1');
   JMP('Iterate_Selections');
:Done:: ======
   // etc ...
End;

Also the property "item" has been added for ListBox, ComboBox,
RadioGroup and PageControl to allow direct access to items (by
index) with MUIGet and MUISet (Data is the index of the item):

   item

Example:

GetItem("MyListBox",'item','0','2');
//%!0 Caption of the third item in the list
GetItem("MyListBox",'item','0','-1');
//%!0 Caption of selected item in the list
SetItem("MyListBox",'item','current item!','-1');

Best regards,

alex

> when I enter the \cite{} command the usually the "Bibitems" pop
> up is opened. If a \ref{} command precedes the \cite{} command
> in the same line, I get the "Labels" pop up on typing the
> closing brace ...
>
> Can anyone confirm this and/or knows how to fix this?

I could not confirm this with the default settings. Can you
give a short (one-line) example with instructions on to
reproduce the problem?

In any case it has to do with definitions in Settings -> Active
Strings Dialog.

> PS: version is 5.5 (20070716)

I only tested with the latest build and it is possible that
your older build acts slightly differently although reversing
the order of \?ref{} and \cite?{} in the above dialog should
change this...

Best regards,

alex

WinEdt Team wrote:
>> when I enter the \cite{} command the usually the "Bibitems" pop
>> up is opened. If a \ref{} command precedes the \cite{} command
>> in the same line, I get the "Labels" pop up on typing the
>> closing brace ...
>>
> In any case it has to do with definitions in Settings -> Active
> Strings Dialog.
>
Indeed... For some strange reason my active strings list contained
several \?ref?{} commands instead of \?ref{} etc. in the default
configuration. Missed that the first time.

Problem is solved, thanks.

Best regards, Hanno

On 23.01.2008 01:58, WinEdt Team wrote:
> This has now been fixed.
...
> This has now been added to MUI ListBox

Thanks!

Best,
--
   Robert

Also, I forgot to mention that regular Texify works just fine on the same file
(compiles and opens the DVI), so it seems to be specific to pdf.

Michael.

>Does anyone know what WinEdt uses to decide whether PDFTex created the pdf OK
or if it had >errors?� When I run PDFTexify on one of my projects, it creates
the pdf just fine, but WinEdt acts >like there was an error (it doesn't open the
pdf and opens the log file--which doesn't contain any >errors, just warnings).
�I can open the pdf manually, and it compiled just fine.� Other projects >work
normally (compile and open the pdf), so it seems this is specific to the one Tex
file.� Any >ideas on what to check?
>
>Thanks,
>
>Michael.

>  > ...You are right.  It  turns  out  that  the
>  > caret  is  not properly offset which becomes
>  > obvious  when  extra  line  spacing  exceeds
>  > value  2,  and  becomes really annoying with
>  > larger spacing. I never intended  or  tested
>  > extra  line spacing with values greater than
>  > 2 but now that you have pointed  it  out  it
>  > has been fixed for the next version (for all
>  > three supported shapes of carets)...
>
> Is there something I can alter in the ini file to temporarily
> side-step this issue?

I am afraid not.

>  > ...I have no intention to  introduce  custom
>  > dimensions for caret...
>
> What about custom colors to make the caret more visible?

Caret is a shared resource and it does not provide a custom
color attribute. Thus it cannot be done (with reasonable
effort)...

Best regards,

alex

> Does anyone know what WinEdt uses to decide whether PDFTex
> created the pdf OK or if it had errors?  When I run PDFTexify
> on one of my projects, it creates the pdf just fine, but
> WinEdt acts like there was an error (it doesn�t open the pdf
> and opens the log file--which doesn�t contain any errors,
> just warnings).  I can open the pdf manually, and it compiled
> just fine.  Other projects work normally (compile and open
> the pdf), so it seems this is specific to the one Tex file.
> Any ideas on what to check?

Try looking at the execution mode setting: | Options | Execution Modes... |,
then select PDFTex in the list and look at what's checked in the Process
Flow list.

Cheers,  Phil
  --
  Email.it, the professional e-mail, gratis per te: http://www.email.it/f

  Sponsor:
  Quanti possono essere i tuoi potenziali clienti? Scoprilo subito con il
servizio di Email Marketing di Email.it
  Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=7484&d=20080124

> > Does anyone know what WinEdt uses to decide whether PDFTex
> > created the pdf OK or if it had errors?  When I run PDFTexify
> > on one of my projects, it creates the pdf just fine, but
> > WinEdt acts like there was an error (it doesn't open the pdf
> > and opens the log file--which doesn't contain any errors,
> > just warnings).  I can open the pdf manually, and it compiled
> > just fine.  Other projects work normally (compile and open
> > the pdf), so it seems this is specific to the one Tex file.
> > Any ideas on what to check?
>
> Try looking at the execution mode setting: | Options |
> Execution Modes... |, then select PDFTex in the list and look
> at what's checked in the Process Flow list.

Correct: by disabling error detection in Execution Modes you
may prevent this behavior as Philip pointed out. This will,
however, prevent detection of more serious errors as well...

The source of the problem is that PDFTeX or PDFLaTeX reports
certain font warnings in a format that is otherwise reserved
for errors (not warnings). That's why this happens: the blame
is on the lack of conventions when it comes to reporting errors
and warnings by (PDF)TeX -- log file is quite a mess and hard
to make sense of...

I do, however, suspect that you have an older WinEdt because
the latest build has some special filters to eliminate this
oddity in the log file produced by PDFLaTeX and by default
WinEdt should ignore those messages.

This is from WinEdt's News.txt (Help -> What's New):

[since] WinEdt 5 [Build 20070913 (v. 5.5)]
           ==================================

...

  - A minor correction to the default error detection in
order to filter out more (harmless) warnings produced by
PDFTeX...

...

Best regards,

alex

> I just installed the newest winedt (Build: 20071003 (v. 5.5))
> and I saw a small problem with the document tabs:
>
> If I minimize winedt and then restore it the document tabs
> looks odd: E.g. I can see a second (non working) tab a bit to
> right of the real tab. There are points and lines and parts of
> icons everywhere. If I switch to another application and then
> back to winedt everything is fine again.
>
> I'm using Win XP (on a laptop) and the classical windows look.
> If I change to the Win XP look the effect is no longer there.

You are correct. This one took a while to be properly diagnosed
and fixed:-)

Themed controls act slightly differently from classic ones. In
an effort to reduce unwanted flickering of tabs when themes are
enabled a refresh oddity with classic view was unintentionally
introduced. This has now been fixed and tested with Classic
Appearance. In the meantime you may have to force a refresh by
switching out and back to WinEdt (as indicated above) to fix
the oddity...

Also an unwanted Horizontal scrollbar with Classic Appearance
has been eliminated (for some reason the width of the width of
a vertical scroll bar was not properly initialized when classic
appearance is enabled).

> I also have another question: Is it possible to install the new
> version without admin rights (as power user)? I can't remember
> that the older versions didn't install without admin rights.
> But here it was the case.

This has to do with Vista where admin rights with extra
privileges are absolutely required for proper installation.
Rather than having two install images (one for Vista and one
for XP or earlier) the admin privileges are now required for
installation even on platforms where power user account would
be sufficient...

Best regards,

alex

Ich schaffs nicht, dem WinEdt deutsch NUR fuer files der form

*.de.*

beizubringen.
Eigentlich ist in den Settings das ja so definiert,

:DE|*.de;*.*

Wenn ich im Dictionary Manager DE als submode fuer das deuschsche
Woerterbuch angebe, dann wirds aber bei *.de.txt nicht angewendet.
Was muss ich machen, damit das funktioniert?


--
Erich Neuwirth, University of Vienna
Faculty of Computer Science
Computer Supported Didactics Working Group
Visit our SunSITE at http://sunsite.univie.ac.at
Phone: +43-1-4277-39464 Fax: +43-1-4277-39459

Hi Alex,

Will the patch you describe below be available anytime soon?

--Ryan

----- Original Message ----
From: WinEdt Team <support@...>
To: winedt+list@...
Sent: Friday, October 26, 2007 4:25:16 PM
Subject: Re: [WinEdt] bibMacros 2.1 not finding .bib files after WinEdt5.5
upgrade

> After some more experimenting, I found one such scenario (and
> this is actually a bug in WinEdt): Tree.ini offers the
> possibility to specify additional paths where WinEdt should
> search for files (PATH). Such files are displayed without any
> path specification in the tree, while GetTree will incorrectly
> show them as residing in the current path.

Indeed: a bug. I neglected to correct all references to the full
filenames in the project tree. Thus some functions (like GetTree)
fail to find files that are placed outside the main file's
directory even though WinEdt knows where they are on the extended
PATH. Even FindInFiles (all files in the project) has the same
problem. I didn't think hard enough when introducing the
possibility to specify PATH for input directives. This has now
been fixed and I will upload yet another patch (with this fix) for
5.5 within a week...

Anyway, it is good to see that there are users out there who
understand and use the new extended input directives...

Best regards,

alex





      
________________________________________________________________________________\
____
Never miss a thing.  Make Yahoo your home page.
http://www.yahoo.com/r/hs

> Will the patch you describe below be available anytime soon?

I was hoping to prepare it by the end of November. However, I
haven't been well for weeks and in the meantime I've made too
many changes to upload them as a Patch. I am, however, hoping
to make Beta of 5.6 available in March. This will be an
opportunity to test all the functionality and report any
remaining problems...

> > After some more experimenting, I found one such scenario (and
> > this is actually a bug in WinEdt): Tree.ini offers the
> > possibility to specify additional paths where WinEdt should
> > search for files (PATH). Such files are displayed without any
> > path specification in the tree, while GetTree will incorrectly
> > show them as residing in the current path.

Best regards,

alex

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>
    or in the mailing list archives at
       <http://groups.yahoo.com/group/WinEdt>.

    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:
    <winedt+list-unsubscribe@...>  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: <http://www.winedt.org/Doc/listinstr.php>


* Links

    + The WinEdt home page
      <http://www.winedt.com/>

    + WinEdt community's home page
      <http://www.winedt.org/>

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

    + The WinEdt Mailing List messages are archived at
      <http://groups.yahoo.com/group/WinEdt>

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

    + If you have any suggestions for these guidelines, please contact me
      at <robert@...>

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

    Happy WinEdt'ing!

    For the WinEdt.org team,
     robert@...


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

I'm trying to do some graphical conversions in LaTeX (using dot2texi,
amongst other packages). However, I get error messages when I compile to
the effect that 'Shell escape isn't enabled'.

At one point I thought I knew how to do this, but I don't remember the mechanics
- can
someone remind me of how to flip the switch in WinEdt to allow shell
escapes for LaTeX and PDFeTeX compiles?

Thanks!

Le 03/02/2008 12:22, Evan Cooch a �crit :
> I'm trying to do some graphical conversions in LaTeX (using dot2texi,
> amongst other packages). However, I get error messages when I compile to
> the effect that 'Shell escape isn't enabled'.
>
> At one point I thought I knew how to do this, but I don't remember the
> mechanics - can someone remind me of how to flip the switch in WinEdt to
> allow shell escapes for LaTeX and PDFeTeX compiles?
>
> Thanks!
>
>

If you're using MiKTeX, invoke latex with

-enable-write18

F. P�tiard

Merci - I'll give that a try.

P�tiard Fran�ois wrote:
> Le 03/02/2008 12:22, Evan Cooch a �crit :
>> I'm trying to do some graphical conversions in LaTeX (using dot2texi,
>> amongst other packages). However, I get error messages when I compile
>> to the effect that 'Shell escape isn't enabled'.
>>
>> At one point I thought I knew how to do this, but I don't remember
>> the mechanics - can someone remind me of how to flip the switch in
>> WinEdt to allow shell escapes for LaTeX and PDFeTeX compiles?
>>
>> Thanks!
>>
>>
>
> If you're using MiKTeX, invoke latex with
>
> -enable-write18
>
> F. P�tiard
>

Dear users of WinEdt,

I have installed WinEdt 5.5 + Windows XP and a switch from
English to Russian. This switch is working in Microsoft Word and
not working in WinEdt.

What should I do to be able to switch from English to Russian
in WinEdt?

Thank you in advance,

V. V. Goldberg

> I have installed WinEdt 5.5 + Windows XP and a switch from
> English to Russian. This switch is working in Microsoft Word
> and not working in WinEdt.
>
> What should I do to be able to switch from English to Russian
> in WinEdt?

WinEdt is not a UNICODE application.

However, you have two possibilities to properly display text in
Windows Russian Code Page:

1. Options -> Fonts -> Cyrillic Charset

2. Make sure that the option Language Sensitive Script is
enabled in Options -> Settings.

(1) is probably a better solution...

This advice assumes that you can type Russian in WinEdt (after
switching a Keyboard Layout in WinEdt) but the displayed
characters show 8-bit characters corresponding to the default
code page on your machine (probably Western). Changing the font
charset in WinEdt Options should remedy this. Otherwise you
should explain in detail what you want and what happens.

Best regards,

alex

Dear Alex,

Thanks. Following your advice, I was able to get Russian
on my PC where I still have WinEdt 5.3.

However, on my laptop where I have WinEdt 5.5, I am getting Russian fonts
but with different location of letters. For example, on PC I am getting

qwerty=яверты

and on the laptop I am getting

qwerty=йцукен

I am accustomed to the first one:

qwerty=яверты

Best regards,

Vladislav



WinEdt Team wrote:
>> I have installed WinEdt 5.5 + Windows XP and a switch from
>> English to Russian. This switch is working in Microsoft Word
>> and not working in WinEdt.
>>
>> What should I do to be able to switch from English to Russian
>> in WinEdt?
>
> WinEdt is not a UNICODE application.
>
> However, you have two possibilities to properly display text in
> Windows Russian Code Page:
>
> 1. Options -> Fonts -> Cyrillic Charset
>
> 2. Make sure that the option Language Sensitive Script is
> enabled in Options -> Settings.
>
> (1) is probably a better solution...
>
> This advice assumes that you can type Russian in WinEdt (after
> switching a Keyboard Layout in WinEdt) but the displayed
> characters show 8-bit characters corresponding to the default
> code page on your machine (probably Western). Changing the font
> charset in WinEdt Options should remedy this. Otherwise you
> should explain in detail what you want and what happens.
>
> Best regards,
>
> alex
>

> Thanks. Following your advice, I was able to get Russian
> on my PC where I still have WinEdt 5.3.
>
> However, on my laptop where I have WinEdt 5.5, I am getting Russian fonts
> but with different location of letters. For example, on PC I am getting
>
> qwerty=яверты
>
> and on the laptop I am getting
>
> qwerty=йцукен
>
> I am accustomed to the first one:
>
> qwerty=яверты
>

Create a "qwerty" file, one that contains qwerty in Russian, with
the wrong glyphs in your laptop and transfer it to your PC and see
how it looks there.

You should also start WinEdt's (Tools menu) Character Map on both
machines and see if they display the same characters. Perhaps you
have to choose a different font on your laptop, because it's
possible not all Windows fonts support all Windows' code pages.

There is no difference between 5.3 and 5.5 in this regard.
Comparing with Word doesn't help because Word uses Windows'
Unicode...

Of course it goes without saying you should mention whether on any
of your machines you have enabled Translation Tables (OEM or so)

best regards

alex

Dear Alex,

You wrote:

Create a "qwerty" file, one that contains qwerty in Russian, with
the wrong glyphs in your laptop and transfer it to your PC and see
how it looks there.

The answer: it looks on PC exactly as on the laptop


You should also start WinEdt's (Tools menu) Character Map on both
machines and see if they display the same characters. Perhaps you
have to choose a different font on your laptop, because it's
possible not all Windows fonts support all Windows' code pages.

Character Map is different on 2 computers: on PC it has 6 lines while
on the laptrop only 4 lines.

On PC I have

ACSCII: 252 HEX:  FC

and on the laptop

ACSCII: 237: HEX  ED

Best,

Vladislav
WinEdt Team wrote:
>> Thanks. Following your advice, I was able to get Russian
>> on my PC where I still have WinEdt 5.3.
>>
>> However, on my laptop where I have WinEdt 5.5, I am getting Russian
>> fonts
>> but with different location of letters. For example, on PC I am getting
>>
>> qwerty=яверты
>>
>> and on the laptop I am getting
>>
>> qwerty=йцукен
>>
>> I am accustomed to the first one:
>>
>> qwerty=яверты
>>
>
> Create a "qwerty" file, one that contains qwerty in Russian, with
> the wrong glyphs in your laptop and transfer it to your PC and see
> how it looks there.
>
> You should also start WinEdt's (Tools menu) Character Map on both
> machines and see if they display the same characters. Perhaps you
> have to choose a different font on your laptop, because it's
> possible not all Windows fonts support all Windows' code pages.
>
> There is no difference between 5.3 and 5.5 in this regard.
> Comparing with Word doesn't help because Word uses Windows'
> Unicode...
>
> Of course it goes without saying you should mention whether on any
> of your machines you have enabled Translation Tables (OEM or so)
>
> best regards
>
> alex
>

I have just started Notepad, switched Keybord to Russion and typed querty.
Both Notepad and WinEdt show the same string (the one that you don't like).
Case closed as far as WinEdt is concerned but let us know what you find
out...

alex



----- Original Message -----
From: "Vladislav Goldberg" <vze29sp7@...>
To: <winedt+list@...>
Sent: Friday, February 08, 2008 9:03 PM
Subject: Re: [WinEdt] switch from,English to Russian ин ВинЕдт


> Dear Alex,
>
> You wrote:
>
> Create a "qwerty" file, one that contains qwerty in Russian, with
> the wrong glyphs in your laptop and transfer it to your PC and see
> how it looks there.
>
> The answer: it looks on PC exactly as on the laptop
>
>
> You should also start WinEdt's (Tools menu) Character Map on both
> machines and see if they display the same characters. Perhaps you
> have to choose a different font on your laptop, because it's
> possible not all Windows fonts support all Windows' code pages.
>
> Character Map is different on 2 computers: on PC it has 6 lines while
> on the laptrop only 4 lines.
>
> On PC I have
>
> ACSCII: 252 HEX:  FC
>
> and on the laptop
>
> ACSCII: 237: HEX  ED
>
> Best,
>
> Vladislav
> WinEdt Team wrote:
>>> Thanks. Following your advice, I was able to get Russian
>>> on my PC where I still have WinEdt 5.3.
>>>
>>> However, on my laptop where I have WinEdt 5.5, I am getting Russian
>>> fonts
>>> but with different location of letters. For example, on PC I am getting
>>>
>>> qwerty=яверты
>>>
>>> and on the laptop I am getting
>>>
>>> qwerty=йцукен
>>>
>>> I am accustomed to the first one:
>>>
>>> qwerty=яверты
>>>
>>
>> Create a "qwerty" file, one that contains qwerty in Russian, with
>> the wrong glyphs in your laptop and transfer it to your PC and see
>> how it looks there.
>>
>> You should also start WinEdt's (Tools menu) Character Map on both
>> machines and see if they display the same characters. Perhaps you
>> have to choose a different font on your laptop, because it's
>> possible not all Windows fonts support all Windows' code pages.
>>
>> There is no difference between 5.3 and 5.5 in this regard.
>> Comparing with Word doesn't help because Word uses Windows'
>> Unicode...
>>
>> Of course it goes without saying you should mention whether on any
>> of your machines you have enabled Translation Tables (OEM or so)
>>
>> best regards
>>
>> alex
>>
>

Dear Alex,

You are correct.

However, I still do not understand why on my PC (with WinEdt 5.3 and
MSWord 2003)
I am getting

qwerty=яверты (which I like)

while on my laptop (with WinEdt 5.5 and MSWord 2007) I am getting

qwerty=йцукен (which I do not like)

Note that for WinEdt 5.3 and 5.5 Coversion Maps are different
(see my previous letter).

Best regards,

Vladislav




WinEdt Team wrote:
> I have just started Notepad, switched Keybord to Russion and typed
> querty. Both Notepad and WinEdt show the same string (the one that you
> don't like). Case closed as far as WinEdt is concerned but let us know
> what you find out...
>
> alex
>
>
>
> ----- Original Message ----- From: "Vladislav Goldberg"
> <vze29sp7@...>
> To: <winedt+list@...>
> Sent: Friday, February 08, 2008 9:03 PM
> Subject: Re: [WinEdt] switch from,English to Russian ин ВинЕдт
>
>
>> Dear Alex,
>>
>> You wrote:
>>
>> Create a "qwerty" file, one that contains qwerty in Russian, with
>> the wrong glyphs in your laptop and transfer it to your PC and see
>> how it looks there.
>>
>> The answer: it looks on PC exactly as on the laptop
>>
>>
>> You should also start WinEdt's (Tools menu) Character Map on both
>> machines and see if they display the same characters. Perhaps you
>> have to choose a different font on your laptop, because it's
>> possible not all Windows fonts support all Windows' code pages.
>>
>> Character Map is different on 2 computers: on PC it has 6 lines while
>> on the laptrop only 4 lines.
>>
>> On PC I have
>>
>> ACSCII: 252 HEX:  FC
>>
>> and on the laptop
>>
>> ACSCII: 237: HEX  ED
>>
>> Best,
>>
>> Vladislav
>> WinEdt Team wrote:
>>>> Thanks. Following your advice, I was able to get Russian
>>>> on my PC where I still have WinEdt 5.3.
>>>>
>>>> However, on my laptop where I have WinEdt 5.5, I am getting Russian
>>>> fonts
>>>> but with different location of letters. For example, on PC I am
>>>> getting
>>>>
>>>> qwerty=яверты
>>>>
>>>> and on the laptop I am getting
>>>>
>>>> qwerty=йцукен
>>>>
>>>> I am accustomed to the first one:
>>>>
>>>> qwerty=яверты
>>>>
>>>
>>> Create a "qwerty" file, one that contains qwerty in Russian, with
>>> the wrong glyphs in your laptop and transfer it to your PC and see
>>> how it looks there.
>>>
>>> You should also start WinEdt's (Tools menu) Character Map on both
>>> machines and see if they display the same characters. Perhaps you
>>> have to choose a different font on your laptop, because it's
>>> possible not all Windows fonts support all Windows' code pages.
>>>
>>> There is no difference between 5.3 and 5.5 in this regard.
>>> Comparing with Word doesn't help because Word uses Windows'
>>> Unicode...
>>>
>>> Of course it goes without saying you should mention whether on any
>>> of your machines you have enabled Translation Tables (OEM or so)
>>>
>>> best regards
>>>
>>> alex
>>>
>>
>

> You are correct.
>
> However, I still do not understand why on my PC (with WinEdt
> 5.3 and MSWord 2003) I am getting
>
> qwerty=?????? (which I like)
>
> while on my laptop (with WinEdt 5.5 and MSWord 2007) I am
> getting
>
> qwerty=?????? (which I do not like)
>
> Note that for WinEdt 5.3 and 5.5 Coversion Maps are different
> (see my previous letter).

WinEdt does not have anything to do with it since Notepad acts
the same way. I suspect that you have different keyboard layout
in your language settings. That would explain the situation.

For example on your PC key A results in A and F in FI while on
your Notepad the keys are reversed. They act the same way for
ALL UNICODE and ASCII applications (respectively). Correct?

Even Word should have nothing to do with it (it should act the
same way as Notepad). Try to inspect your language settings and
keyboard layout for RU... Believe it, or not, but I have heard
of problems with Windows keyboards before (eg. on Vista
Romanian keyboard has a few keys that don't get mapped
correctly for non-UNICODE applications). Users often report it
as a WinEdt-problem until they realize that it persists for all
(non-Unicode) applications and in your case for UNICODE as well
(Notepad!)

This what I get in WinEdt or Notepad when switching to Russian
with Russian (Typewriter) Keyboard layout (default for RU on XP
or Vista):

querty -> (you don't like this one)

Now I changed the Keyboard layout to Serbian (Cyrillic):

quarty -> (that's the one you like)

You don't like the first keyboard layout but you are used to
the second one. Now you know what to do...

Best regards,

alex

> You are correct.
>
> However, I still do not understand why on my PC (with WinEdt
> 5.3 and MSWord 2003) I am getting
>
> qwerty=?????? (which I like)
>
> while on my laptop (with WinEdt 5.5 and MSWord 2007) I am
> getting
>
> qwerty=?????? (which I do not like)
>
> Note that for WinEdt 5.3 and 5.5 Coversion Maps are different
> (see my previous letter).

WinEdt does not have anything to do with it since Notepad acts
the same way. I suspect that you have different keyboard layout
in your language settings. That would explain the situation.

For example on your PC key A results in A and F in FI while on
your Notepad the keys are reversed. They act the same way for
ALL UNICODE and ASCII applications (respectively). Correct?

Even Word should have nothing to do with it (it should act the
same way as Notepad). Try to inspect your language settings and
keyboard layout for RU... Believe it, or not, but I have heard
of problems with Windows keyboards before (eg. on Vista
Romanian keyboard has a few keys that don't get mapped
correctly for non-UNICODE applications). Users often report it
as a WinEdt-problem until they realize that it persists for all
(non-Unicode) applications and in your case for UNICODE as well
(Notepad!)

This what I get in WinEdt or Notepad when switching to Russian
with Russian (Typewriter) Keyboard layout (default for RU on XP
or Vista):

querty -> éãóêåí (you don't like this one)

Now I changed the Keyboard layout to Serbian (Cyrillic):

quarty -> šóåðòç (that's the one you like)

Thus you don't like the first keyboard layout but you are used
to the second one. Now you know what to do...

Best regards,

alex

--
Hola

Hi all

I am a curious problem with mi distribution winedt 5.5, miktex 2.6, and
jabref 2.2

All thing were right, but now i cant to do that \cite{} work appropriately
(the "bibliography item" window is not appearing). More, only work in one
project. I try copy all file (of project that is fine) in other directory,
but don't work. In the main file is not the plus symbol in the
bibliography section of project tree.

It is very stranger to me.

Thanks to all in advance.


Atentamente,
Evaristo Arroyo F.