gmane.editors.winedt

Re[2]: [BULK] A bug in jabref 2.4.

Hongsheng Zhao — 2008-09-07T15:16:11

Options ->> Preferences -> File -> "Store the following fields with Thanks a lot, you let me finally sort this issue out! Sincerely yours,

Re: [BULK] A bug in jabref 2.4.

Joseph Wright — 2008-09-07T12:56:56

Options -> Preferences -> File -> "Store the following fields with braces around capital letters", which takes a semi-colon separated list. Just that JabRef might do things you don't quite expect: Bekir {\c{C}}etinkaya gives cCetinkaya for example. Just keep an eye on the system!

Re[2]: [BULK] A bug in jabref 2.4.

Hongsheng Zhao — 2008-09-07T11:41:14

Do you mean the JabRef can do this for automatically? If so, how can I make JabRef to add braces around them automatically? In fact, I cann't find any options of JabRef to do the above things automatically. Why in this case ( the first character of a name is accented) some trouble can arise? What's the trouble? How to solve it? Sincerely yours,

Re: [BULK] A bug in jabref 2.4.

Joseph Wright — 2008-09-07T11:11:41

This is dependent on your BibTeX style. The point of BibTeX is that the formatting can be varied while using the same database. Hence JabRef expects to find author data in a known layout. You are only supposed to use {...} around specific items to be left alone by BibTeX. I think you will be very unlucky to find a BibTeX style that alters capitalisation of names, and in any case you can get JabRef to add braces around them "behind the scenes" when saving. Taking a complex example: author = {Bj{\o}rn Anders and A. N. T{\ae}rs and {A and B}}, where "A and B" is a company name, and so the "and" is part of the name itself. JabRef will understand that type of entry just fine (some trouble can arise if the first character of a name is accented, but this is usually a relatively low number of entries).

Re[2]: [BULK] A bug in jabref 2.4.

Hongsheng Zhao — 2008-09-07T09:22:16

If I use the and as the delimiter, then the ultimate compiled results would be: ----------------- M. D. Segall, P. J. D. Lindan, M. J. Probert, C. J. Pickard, P. J. Hasnip, S. J. Clark, and M. C. Payne. ----------------- In fact, I just want the authors look like this in the ultimate compiled result files: --------------------- Segall M D, Lindan P J D, Probert M J, Pickard C J, Hasnip P J, Clark S J and Payne M C --------------------- Furthermore, I also use a pare of redundant "{}" to include all of the authors in it in order to keep the override the BibTeX's capitalization conventions and keep some special latex command sequence, such as \ae correct in the the ultimate compiled result file, but this will also confuse the jabref 2.4, I mean, in this case, the jabref 2.4 will treat all the authors in the inner "{}" added by me as the only one author, this is just the reason of my issue posted by my last mail. Sincerely yours,

RE: Access violation when trying to build tree or set main file

Jan-Henrik Horstmann — 2008-09-07T07:05:02

I'm a mechanical/system engineer and not a computer guru, but your explaination sounds reasonable. :-) I'm looking forward to it. So far all is working well, no problems whatsoever. Hence, I will stick to the status quo of my "running system" and not play around. I'll keep on giving feedback though in case I can come up with a reproducable version of the problem - when I have time to look at it in October/November... I was aware of that and thus used Emacs for some time. Finally switched back to WinEdt when I realized it was working fine... And I'm happy if I can help improving it despite the fact that I'm unfortunately not so much into software programming. Anyway, thank you for the "support" and keep up the great work. Kind regrads, Jan-Henrik _________________________________________________________________ MSN Video: Coole Beats und krasse Actionen! Kostenlos anschauen! http://video.msn.com/?mkt=de-de

Re: [BULK] A bug in jabref 2.4.

Joseph Wright — 2008-09-07T06:39:21

Each author name should be separated by "and": author = {Segall, M. D. and Lindan, P. J. D. and Probert, M. J. and Pickard, C. J. and Hasnip, P. J. and Clark, S. J. and Payne, M. C.}, You'll also confuse the bibtex with the field as you gave.

[BULK] A bug in jabref 2.4.

Hongsheng Zhao — 2008-09-07T06:21:35

Dear Winedt+list, I find a the bug in the recently released jabref 2.4, I know I should post this to the list of jabref, but I cann't find the corresponding list of it. The jabref 2.4's bibtexkey generator pattern has the following bug: the [auth][year] doesn't work correctly, it will do the following wrong thing like this: ---------------------- author = {{Segall M D, Lindan P J D, Probert M J, Pickard C J, Hasnip P J, Clark S J and Payne M C}}, will be translated to: SegallMDLindanPJDProbertMJPickardCJHasnipPJClarkSJandPayneMC ---------------------- Sincerely yours,

Re: Greek Dictionary and final sigma

WinEdt Team — 2008-09-06T16:38:58

Zach: your server did not allow alex's reply through: message has been deleted by the SPAM filter on our server so here it is via the List You should specify Upper and Lower Sigma as a pair and then finalsigma twice: Óò óó There is nothing I can fix for the default settings since WinEdt asks Windows which characters are a part of the (language-sensitive) alphabet and what are their lower and upper case equivalents. Details depend on a language and they are different for Western, Greek, CE, Cyrillic, etc... Some characters may not have lower-case equivalents. Whatever you do make sure that you don't have any character in custom alphabet repeated in more than one line. Òò Óó óò or Óò óò would cause problems! While: Óò óó or Óó òò is OK (as long as these characters are not anywhere else in the custom alphabet specification!). I don't speak Greek so I don't know which of the above is correct as far as capital letters go... You must decide which of the three (p

Re[2]: calling JabRef from WinEdt

Hongsheng Zhao — 2008-09-06T08:53:31

That doesn't has matter with your Operating system, the JabRef itself has some form of releases, including exe for win32, tar for all platforms and etc., you should choose the file that best matches your architecture or operating system from the list of files contained in its release: http://sourceforge.net/project/showfiles.php?group_id=92314&package_id=97632&release_id=623522 Furthermore, even you use the exe file as the setup program of JabRef, the actual program is still a tar ball at the the following default location: C:\Program Files\JabRef\JabRef-a.b.c.tar. In fact, after the installation has been completed with the exe, you will only rely on the the above tar file to run the jabref, all of the other files in the C:\Program Files\JabRef can be removed from there. Sincerely yours, -- Hongsheng Zhao yahoo.com.cn> Xinjiang Technical Institute of Physics and Chemistry Chinese Academy of Sciences GnuPG DSA: 0xD108493 2008-9-6

Re: calling JabRef from WinEdt

Yogeshwarsing Calleecharan — 2008-09-06T08:20:45

Grammar checker?

Howard Brill — 2008-09-05T16:42:25

About the only thing I like about Word versus the WinEdt/LaTeX/PDF stack for technical documents is the availability of grammar checking. Does anyone know of a grammar checker that could be callable from WinEdt? Howard Brill, Ph. D. Director of Health Informatics Monroe Plan for Medical Care 2700 Elmwood Ave Rochester, NY 14534 (585) 256-8424 hbrill< at >monroeplan.com _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ This electronic message transmission is intended to be for the use of the individual or entity to whom it is addressed, and may contain information from the Monroe Plan which may be confidential. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this electronic message in error, please notify us immediately by calling collect at (585) 256-8419 or by electronic mail at postmaster< at >monroeplan.com and delete or destr

Re: calling JabRef from WinEdt

Evaristo Arroyo F. — 2008-09-05T14:31:03

En Fri, 05 Sep 2008 03:29:36 -0430, Yogeshwarsing Calleecharan ltu.se> escribió:

Re: calling JabRef from WinEdt

Nicolas Vaughan — 2008-09-05T12:25:01

Its simply a macro called by a menu item or a toolbar button. Follow these instructions: 1.Enter Menu Setup -> Shortcuts 2. Insert -> Macro 3. Label it 'JabRef' (or whatever you like) 4. In the Macro space paste the command you found. Be careful with the path. In my case I use the following: [IfisMode('BibTeX', '%!m', 'LetReg(0,"%p\%n%t");', 'LetReg(0,"");'); Run('"javaw" -jar "d:\Tex\Jabref\JabRef-2.4.jar" "%!0"', '%p');] (Note I'm using JabRef version 2.4, so I chose this jar file and added it to the command). 5. Check 'Requieres open document'. 6. Add a shortcut if you wish. 7. If you wish to create a toolbar button, choose both a couple of images and a hint text (I chose the Java icon). 8. Close the Menu Setup dialog (by clicking 'ok'). 9. Enter the Tool Bar Setup. 10. Choose the button which corresponds to the very same image you selected for the macro. 11. Add it to the toolbar by drag-and-dropping it. Cheers, Nicolas Vaughan On Fri, Sep 5, 2008 at 2:59 AM, Yogeshwarsing Calleecharan < yoge

calling JabRef from WinEdt

Yogeshwarsing Calleecharan — 2008-09-05T07:59:36

Greek Dictionary and final sigma

Zach Agioutantis — 2008-09-05T05:53:48

When the Greek dictionary is loaded some words that have a final Greek sigma are highlighted as incorrect. It looks like that if the word (minus the final sigma) is present in the dictionary, then the whole word appears correct. If not, all the letters except the last (final sigma) are highlighted as incorrect. The final sigma is not highlighted. Settings->Language has custom enabled, but final sigma does not show there. I am not attaching any images but if need be I can send some. Thanks.

Re: Define text colours within winedt

WinEdt Team — 2008-09-04T20:03:46

No, you cannot change the size. Highlighting allows you to change color, background and font attributes (bold, italic, strikethrough and underlined). That's all you can do inside switches. Best regards, alex

Re: Access violation when trying to build tree or set main file

WinEdt Team — 2008-09-04T19:49:46

Although I was not able to reproduce the crash I did some investigating (focusing on a UTF-8 format and absence of BOM). As it turns out WinEdt moved 1-byte too many when loading a UTF-8 document for purpose of building a tree AND a document did not contain a BOM AND the document was actually ASCII (it contained no multi-byte characters). Usually 1-byte in a large memory segment should not cause an Access Violation because Windows tends to round-up memory allocations. However, an access violation could arise under certain circumstances (this would explain why it was not always reproducible)... Anyway, if I am correct then the problem is fixed for the next version. There was also a discrepancy with freeing memory after converting a UTF-8 document. This one would result in small memory leaks. This, too, has now been fixed. WinEdt's (limited) UTF-8 capabilities have not been extensively tested by many users. That's why your problem is not widely experienced by others. It was worth taking a second look at the

Re: Define text colours within winedt

2008-09-04T19:30:40

I know that the original question was for something that didn't affect the output text, only the look in winedt, but I have found the fixme package very useful in the past. Cheers, Kris. Sent from my BlackBerry® wireless device -----Original Message----- From: "Nicolas Vaughan" gmail.com> Date: Thu, 4 Sep 2008 14:26:19 To: wsg.net> Subject: Re: [WinEdt] Define text colours within winedt Hi, Can such a filter be used to change the size of the text, and not only its color? (I'm thinking in something as AUCTeX does.) Regards Nicolas Vaughan On Thu, Sep 4, 2008 at 9:08 AM, David Huffer csosa.gov> wrote:

Re: Define text colours within winedt

Nicolas Vaughan — 2008-09-04T19:26:19

Hi, Can such a filter be used to change the size of the text, and not only its color? (I'm thinking in something as AUCTeX does.) Regards Nicolas Vaughan On Thu, Sep 4, 2008 at 9:08 AM, David Huffer csosa.gov> wrote:

Re: Define text colours within winedt

Charles Cresswell — 2008-09-04T14:25:59

Dear Dr Huffer, Thanks for your help, I'll try to set that up. Best Regards Charles