On 20 Feb 2008, at 10:55 AM, Rolf Schmolling wrote:
Am 19.02.2008 um 23:43 schrieb Adam R. Maxwell:
In article [EMAIL PROTECTED],
Alexander H. Montgomery [EMAIL PROTECTED] wrote:
On 2008-02-19, at 2:24 PM, [EMAIL PROTECTED] wrote:
Would it reduce the confusion to just save as UTF-8 by
Am 20.02.2008 um 11:09 schrieb Christiaan Hofman:
Hello!
in addition while testdriving I get the following:
Title: {{\glqq}test'' } I did put in “ (smart curly quote up)
greetings,
Rolf
--
Rolf Schmolling M.A. Historian, [EMAIL PROTECTED]
http://rolf_schmolling.macbay.de/
On 20 Feb 2008, at 1:18 PM, Rolf Schmolling wrote:
Am 20.02.2008 um 11:09 schrieb Christiaan Hofman:
…You could turn on TeX conversion in the Files prefs, add custom 2-
way
conversions for {\glqq} and {\grqq}, and use those forms (including
the braces). BibDesk will display the quotes,
On 20 Feb 2008, at 1:20 PM, Rolf Schmolling wrote:
Am 20.02.2008 um 11:09 schrieb Christiaan Hofman:
Hello!
in addition while testdriving I get the following:
Title: {{\glqq}test'' } I did put in “ (smart curly quote up)
greetings,
Rolf
You mean in the bibtex file? This is precisely
On 20 Feb 2008, at 2:28 PM, Rolf Schmolling wrote:
Hi Christiaan,
Am 20.02.2008 um 13:50 schrieb Christiaan Hofman:
On 20 Feb 2008, at 1:20 PM, Rolf Schmolling wrote:
Am 20.02.2008 um 11:09 schrieb Christiaan Hofman:
Hello!
in addition while testdriving I get the following:
Title:
Hi Christiaan,
Am 20.02.2008 um 13:50 schrieb Christiaan Hofman:
On 20 Feb 2008, at 1:20 PM, Rolf Schmolling wrote:
Am 20.02.2008 um 11:09 schrieb Christiaan Hofman:
Hello!
in addition while testdriving I get the following:
Title: {{\glqq}test'' } I did put in “ (smart curly quote up)
In article [EMAIL PROTECTED],
Rolf Schmolling [EMAIL PROTECTED] wrote:
this was a very welcome hint. I've been pondering for a while what to
do about UTF8 or not and comments and abstracts. That Bibdesk is
handling this in the background was something I didn't know and I'm
very happy
Thanks to everyone for their responses.
I guess the bigger question is where is BibDesk going? Is the intent to
make it a research tool for IT developers and programmers, or is it
intended to become an application widely used by all scholars/researchers
instead of that other commercial product?
Am 20.02.2008 um 18:22 schrieb [EMAIL PROTECTED]:
Thanks to everyone for their responses.
I guess the bigger question is where is BibDesk going? Is the
intent to
make it a research tool for IT developers and programmers, or is it
intended to become an application widely used by all
We're certainly not going to automatically delete data, if that's what
you're proposing. That's simply not an option.
Christiaan
On 19 Feb 2008, at 4:55 PM, [EMAIL PROTECTED] wrote:
I raised this issue several months ago, but don't think I made
myself clear.
A problem I've run into is
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
I raised this issue several months ago, but don't think I made myself clear.
A problem I've run into is that if I import a reference with
non-plain-text (Unicode?) character (an en-dash, an em-dash, an open or
closed quote) in the
Christiaan,
If you deleted all the data, think how much quicker everything would run!
:-)
Actually, I was thinking something more along the lines of a setting in
the preferences that says, Replace non-printing characters with ~ or
something similar to what BBEdit does to clean-up troublesome
On 2008-02-19, at 2:24 PM, [EMAIL PROTECTED] wrote:
Would it reduce the confusion to just save as UTF-8 by default? As
long
as TeX conversion is enabled, that should (usually) be fine for TeX
users who work with ASCII exclusively. I save my files as UTF-8
just to
avoid this problem,
Would it reduce the confusion to just save as UTF-8 by default? As long
as TeX conversion is enabled, that should (usually) be fine for TeX
users who work with ASCII exclusively. I save my files as UTF-8 just to
avoid this problem, since the odd characters are almost exclusively in
In article [EMAIL PROTECTED],
Alexander H. Montgomery [EMAIL PROTECTED] wrote:
On 2008-02-19, at 2:24 PM, [EMAIL PROTECTED] wrote:
Would it reduce the confusion to just save as UTF-8 by default? As
long
as TeX conversion is enabled, that should (usually) be fine for TeX
users who
15 matches
Mail list logo
