> juanfrancisc...@gmail.com>* wrote:
>
>
> From: Juan Francisco Fraile Vicente
> Subject: Re: [XeTeX] Em-dash
> To: "Unicode-based TeX for Mac OS X and other platforms"
> Date: Tuesday, 4 May, 2010, 6:42 PM
>
>
> Yes, it exists that keyboard as John has shown.
le Vicente
wrote:
From: Juan Francisco Fraile Vicente
Subject: Re: [XeTeX] Em-dash
To: "Unicode-based TeX for Mac OS X and other platforms"
Date: Tuesday, 4 May, 2010, 6:42 PM
Yes, it exists that keyboard as John has shown.
But I think that the next step is different. I think the most
Yes, it exists that keyboard as John has shown.
But I think that the next step is different. I think the most useful thing
would be that the keyboard be another screen, but a "tactil"-digital one. I
think that this option would develope all the possibilities of Unicode.
I am not talking of a keyboa
On Tue, May 4, 2010 at 1:11 AM, Wilfred van Rooijen
wrote:
> Hi all,
>
> This seems to be precisely the issue. Xetex can read and understand all
> unicode characters, but at this time, the only way to communicate with the
> computer is through the keyboard and the mouse. Thus, there will always be
On 5/4/2010 1:11 AM, Wilfred van Rooijen wrote:
Hi all,
This seems to be precisely the issue. Xetex can read and understand
all unicode characters, but at this time, the only way to communicate
with the computer is through the keyboard and the mouse. Thus, there
will always be issues with "sp
ubject: Re: [XeTeX] Em-dash
But is this keyboard so expensive because of the technology or because
of the "design" (which, by the way, I find to be fairly conservative :-)) )
Wilfred
--- On Tue, 4/5/10, John Was wrote:
From: John Was
Sub
But is this keyboard so expensive because of the technology or because of the
"design" (which, by the way, I find to be fairly conservative :-)) )
Wilfred
--- On Tue, 4/5/10, John Was wrote:
From: John Was
Subject: Re: [XeTeX] Em-dash
To: "Unicode-based TeX for Mac OS X and
On my computer, compose is Shift+RightControl (see
http://en.wikipedia.org/wiki/Compose_key). This approach is best for staying
within one script. For example, typing accented Latin characters (for
various western European languages for example) on a US English keyboard and
the compose key approach
UT.
John
- Original Message -
From: Wilfred van Rooijen
To: Unicode-based TeX for Mac OS X and other platforms
Sent: Tuesday, May 04, 2010 9:11 AM
Subject: Re: [XeTeX] Em-dash
Hi all,
This seems to be precisely the issue. Xetex can read and understand al
does not treat it as a regular space
(rather, treats it like ~, I suppose).
Cheers,
Wilfred
--- On Tue, 4/5/10, Juan Francisco Fraile Vicente
wrote:
From: Juan Francisco Fraile Vicente
Subject: Re: [XeTeX] Em-dash
To: "Unicode-based TeX for Mac OS X and other platforms"
Date: Tues
Which is that compose key on Linux?
I think all of you have a part of reason, but we have to remember that one
of the best things of the world of TeX is the multiple options that offers.
Erasing that conventions would be a loss.
Although I agree (it's difficult to see --- sometimes and the source
On Linux, there is the compose key, on Mac, there is the option/alt key, and
both are very convenient. On Windows, there are the alt key codes but these
are very inconvenient, instead you can use the program AllChars (
allchars.zwolnet.com) which imitates the behaviour of the compose key. I use
the
Hi all,
> This is the same kind of issue as one
> of the earlier ones: the whole point of XeTeX is that one
> simply types what one wants into a Unicode editor (i.e., if
> you want an em-dash, you simply type an em-dash, and there
> is no need any more for TeX conventions like ---, \"a, etc.
> etc
This is the same kind of issue as one of the earlier ones: the whole
point of XeTeX is that one simply types what one wants into a Unicode
editor (i.e., if you want an em-dash, you simply type an em-dash, and
there is no need any more for TeX conventions like ---, \"a, etc. etc.).
Even if ther
On Mon, May 03, 2010 at 11:43:30AM +0900, Cyril Niklaus wrote:
>
> On 3 mai 10, at 10:26, David Purton wrote:
>
>> Hi all,
>>
>> Can someone test if the the below example works with the 12pt article
>> option?
>>
>> i.e., \documentclass[12pt]{article}
>>
>> I'm just left with blankspaces for em an
On 3 mai 10, at 10:26, David Purton wrote:
Hi all,
Can someone test if the the below example works with the 12pt article
option?
i.e., \documentclass[12pt]{article}
I'm just left with blankspaces for em and en dashes with 12pt and the
default fonts.
\documentclass[12pt]{art
Hi all,
Can someone test if the the below example works with the 12pt article
option?
i.e., \documentclass[12pt]{article}
I'm just left with blankspaces for em and en dashes with 12pt and the
default fonts.
Any thoughts on making it work?
On Fri, Apr 30, 2010 at 03:16:34PM +0100, José Carlos S
Am Fri, 30 Apr 2010 10:40:30 -0400 schrieb Mike Axiak:
> I'm actually having the same problem with CMBright. Specifically, I
> have the following code:
>
> \usepackage{cmbright}
> \usepackage{fontspec}
> \usepackage{xltxtra}
> \usepackage{xunicode}
> \newfontface\chinesefont{AR PL UKai
Am 30.04.2010 um 16:40 schrieb Mike Axiak:
I'm actually having the same problem with CMBright.
CMBright is not a Unicode encoded font.
--
Greetings
Pete
There's no sense in being precise when you don't even know what you're
talking about.
– John von Neu
I'm actually having the same problem with CMBright. Specifically, I
have the following code:
\usepackage{cmbright}
\usepackage{fontspec}
\usepackage{xltxtra}
\usepackage{xunicode}
\newfontface\chinesefont{AR PL UKai HK}
\defaultfontfeatures{Scale=MatchLowercase,Mapping=tex-text}
And t
Hi,
Try
\setmainfont[Mapping=tex-text]{Arial}
Best regards,
António Fernandes
On Apr 30, 2010, at 3:16 PM, José Carlos Santos wrote:
> Hi all (yes, it's me again!):
>
> If I compile this file:
>
> \documentclass{article}
> \pagestyle{empty}
> \usepackage{fontspec}
> \usepackage{xunicode}
>
On 30-04-2010 15:29, Alan Munn wrote:
If I compile this file:
\documentclass{article}
\pagestyle{empty}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
---
\end{document}
with XeLaTeX, then I get a PDF file which contains a single character,
namely an em-dash.
On Apr 30, 2010, at 9:16 AM, José Carlos Santos wrote:
> Hi all (yes, it's me again!):
>
> If I compile this file:
>
> \documentclass{article}
> \pagestyle{empty}
> \usepackage{fontspec}
> \usepackage{xunicode}
> \usepackage{xltxtra}
> \begin{document}
> ---
> \end{document}
>
> with XeLaTeX,
On 4/30/2010 7:29 AM, Alan Munn wrote:
On Apr 30, 2010, at 10:16 AM, José Carlos Santos wrote:
Hi all (yes, it's me again!):
If I compile this file:
\documentclass{article}
\pagestyle{empty}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
---
\end{document}
On Apr 30, 2010, at 10:16 AM, José Carlos Santos wrote:
Hi all (yes, it's me again!):
If I compile this file:
\documentclass{article}
\pagestyle{empty}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
---
\end{document}
with XeLaTeX, then I get a PDF file whi
Hi all (yes, it's me again!):
If I compile this file:
\documentclass{article}
\pagestyle{empty}
\usepackage{fontspec}
\usepackage{xunicode}
\usepackage{xltxtra}
\begin{document}
---
\end{document}
with XeLaTeX, then I get a PDF file which contains a single character,
namely an em-dash. But if
26 matches
Mail list logo
