Am 28.09.2010 um 07:42 schrieb Michiel Kamermans:
> On 9/27/2010 8:53 PM, Khaled Hosny wrote:
>>
>> You know, because Windows has the most consistent user interface an OS
>> ever had.
>>
>> (From some one who is yet to see two "native" Windows applications that
>> behave the same)
>>
>
Heh, Michiel and Khaled,
Slow a minute take a deep breath.
No need to get nasty!
TeX and the use thereof is quite intimidated at first.
Their is a big learning curve. That goes also using editors
that work with the TeX-System. One has to learn to use
each properly. This is the biggest reason tha
Hi!
Le 28/09/2010 7:42, Michiel Kamermans a écrit :
On 9/27/2010 8:53 PM, Khaled Hosny wrote:
You know, because Windows has the most consistent user
interface an OS
ever had.
(From some one who is yet to see two "native" Windows
applications that
behave the same)
Yeah, yeah, look, my name is
Am 28.09.2010 um 02:20 schrieb David J. Perry:
> As a relative newcomer to Xe(La)TeX, and proponent of Unicode and
> multilingual computing for 15+ years, I was very surprised by the lack of
> Unicode support in the TeX world. I think what lshort and other tutorials
> need is a very clear and
On Tue, Sep 28, 2010 at 09:50:53AM +0200, Keith J. Schultz wrote:
> Heh, Michiel and Khaled,
>
> Slow a minute take a deep breath.
> No need to get nasty!
Sorry if I offended any one, non was intended. I just wanted to point
that no one really cares about UI inconsistency (except UI nazis,
of cou
Hi,
this discussion does indeed seem to get hot. (Wrong adjective?)
The arguments concerning user expectance and user experience of windows
UI have been exchanged, (The simples solution -- porting kile to windoof
and using a pdf viewer which doesn't grab&hold its file -- is of course
out of r
This was posted to c.t.t on 14 September but drew no responses.
I have been using Memoir with XeLaTeX and Bidi (brought in by
Polyglossia to support RTL languages). Two footnote problems have
arisen.
The first is that memoir's \multfootsep does not get inserted between
consecutive \footnote comma
Am 28.09.2010 um 16:20 schrieb Tobias Schoel:
Can we now come back to the beginning problem:
Which way of creating unicode-encoded .tex-documents to propose in
lshort?
Using GNU Emacs 23.x – the Unicode Emacs (and any of its variants) –
with its AUCTeX extension. One can either set all TE
On Tue, 28 Sep 2010 Peter Dyballa wrote:
> Am 28.09.2010 um 16:20 schrieb Tobias Schoel:
>
>> Can we now come back to the beginning problem:
>> Which way of creating unicode-encoded .tex-documents to propose in
>> lshort?
>
> Using GNU Emacs 23.x √ the Unicode Emacs (and any of its variants) √
Am 28.09.2010 um 21:16 schrieb Peter Dyballa:
>
> Am 28.09.2010 um 16:20 schrieb Tobias Schoel:
>
>> Can we now come back to the beginning problem:
>> Which way of creating unicode-encoded .tex-documents to propose in lshort?
>
> Using GNU Emacs 23.x – the Unicode Emacs (and any of its variants
On 28-09-2010 21:44, Philipp Stephani wrote:
Can we now come back to the beginning problem:
Which way of creating unicode-encoded .tex-documents to propose in lshort?
Using GNU Emacs 23.x – the Unicode Emacs (and any of its variants) – with its
AUCTeX extension.
I use the same technology, b
Am 28.09.2010 um 22:44 schrieb Philipp Stephani:
Am 28.09.2010 um 21:16 schrieb Peter Dyballa:
Am 28.09.2010 um 16:20 schrieb Tobias Schoel:
Can we now come back to the beginning problem:
Which way of creating unicode-encoded .tex-documents to propose in
lshort?
Using GNU Emacs 23.x –
Windoof user have to be hardened by ugly UI.
What about "losedos"?
I am (mostly) a Windows user but am neither stupid nor a loser. All OSs
have their imperfections, people have different reasons for what they use,
so let's stay on task here without insults.
David
--
On Sep 28, 2010, at 4:42 PM, Peter Dyballa wrote:
>
> Am 28.09.2010 um 22:44 schrieb Philipp Stephani:
>
>> Am 28.09.2010 um 21:16 schrieb Peter Dyballa:
>>
>>>
>>> Am 28.09.2010 um 16:20 schrieb Tobias Schoel:
>>>
Can we now come back to the beginning problem:
Which way of creatin
Am 29.09.2010 um 00:02 schrieb David J. Perry:
Windoof user have to be hardened by ugly UI.
What about "losedos"?
I am (mostly) a Windows user but am neither stupid nor a loser. All
OSs have their imperfections, people have different reasons for what
they use, so let's stay on task he
Does this happen with ordinary book class? if not, then this is not my issue
and you should direct it to memoir's authors.
--
به نام خداوند جان و خرد کزین برتر اندیشه برنگذرد
--
Subscriptions, Archive, and List information, etc.:
http:
On Sep 28, 2010, at 5:42 PM, Peter Dyballa wrote:
Am 28.09.2010 um 22:44 schrieb Philipp Stephani:
Am 28.09.2010 um 21:16 schrieb Peter Dyballa:
Am 28.09.2010 um 16:20 schrieb Tobias Schoel:
Can we now come back to the beginning problem:
Which way of creating unicode-encoded .tex-documen
On 9/28/2010 5:42 PM, Peter Dyballa wrote:
By learning to use accelerating keyboard shortcuts one gains more time
Where I *really* gain time is by defining the control+alpha
keys for cursor control, because cursor control is what I do most (other
than type text). That way I never have to mo
I'd like to use the commercial font "Pro Typewriter Underwood," from
http://www.vintagetype.com/, with XeLaTeX, to produce a close
approximation of old-style typewriter output. But I can't get it to
correctly recognize that the font is a monospace font for the purposes of
inter-sentence spacing.
Hi all,
It seems setting Numbers=OldStyle breaks \scshape. This example uses Sabon,
but it happens with other fonts too. My fontspec version is 2.1a.
Andrew
\documentclass{article}
\usepackage{fontspec}
\setmainfont{Sabon LT Std}
\begin{document}
Some text {\scshape in small caps}? Yes.
\ad
20 matches
Mail list logo
