Hi Phillip,
You are missing a point here. Or points.
Does a font have the glyph?
How to access the glyph?
What is the easiest way to input the glyph?
Readability of the input source.
Even though we have unicode not a
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 Khaled,
I did not intend to say anybody was insulting an another,
but the debate was getting there.
The question would be is what is a UI inconsistency.
Windows has conventions which are roughly followed.
Apple has HIG which one is supposed (has to) adh
I do not think there should be any specific editor prposed.
Instead a chapter about entering unicode and a few of the
most popular editors and viewers should be listed with a short
run down of the ups and downs.
regards
Keith.
Am 28.09.2010 um 16:20 schrieb Tobias Schoel:
> Hi
I am neither a beginner nor a "dumb user" (which do not exist)
but I will not touch Emacs with a ten foot pole.
As far as short cuts and scripts are concerned I have the in
TeXShop. Emacs is even intimidating to the intermediate
developer. Do not get me wrong, it is very powerful and
extendable.
Hi,
Tobias bist du des Wahnsinns!! (Sorry, Tobias way over-board here)
I hate to say this nobody actually needs TeX&Co Nowadays. (See my next post)
Not to say that they are the better system for doing things.
TeX et al is for typesetting, layout and publishing that is its sole
purpose! It was de
Hi All,
I chime in here again. First, I give you some of my background.
I have been around computer for 30 years, since the advent of the PC
Apple IIe (my first) and the IBM PC( The 386 my second).
I have work with Wordstar, Word, and (La)Tex when they were in their
infancy.
I have studied Physic
I do not get it. A text document is per say structured one way or the other.
Tex-documents do not add anymore structure to the text than any other
WYSIWYG-Program.
With WYSIWYG the structure of the document is not visible in the form of
command codes, but are represented directly on your screen.
of
typing and commands are no longer need. This is especially, true for languages
other than english.
regards
Keith.
Am 30.09.2010 um 19:11 schrieb Gerrit Glabbart:
>
> Am 30.09.2010 um 16:01 schrieb Keith J. Schultz:
>
>
>> If you take the
>> time to lo
I have set lshort for german in xetex and use some system fonts.
But the code is old and it does not use unicode or the math styles for
xetex. so alot of work to do. I not planing on converting it just use for
experimenting.
regards
Keith.
Am 30.09.2010 um 18:47 schrieb Michiel Kamerman
Hi Elliot,
Welcome aboard.
First , if your on a Mac take a look at TeXShop, if not look at TeXWorks,
it might be more familiar to you. It might be eaier that learning E-macs. (your
call).
As far a documentation is concerned look at the LaTeX Companion for packages.
Forget about anything you fi
Hi Tobias,
I see where you are coming from.
But, your basic point are here OT. I will mail you off list as
this discussion though interesting is of mcuh interest to this
list that education of students.
regards
Keith.
Am 01.10.2010 um 08:2
Am 02.10.2010 um 20:41 schrieb Philipp Stephani:
> Am 30.09.2010 um 12:27 schrieb Keith J. Schultz:
>
>> The same should be true of xelshort. It should:
>
> I find your list very useful, but it seems to focus more on the differences
> between XeLaTeX and pdfLaTeX. Wha
HI Mike,
This problem is not "Tex" specific.
It is not easy to get large amounts of information onto a single page
or several.
The problem is more of getting it in a form that is informative and
precise without
leaving something out.
I agree that
Hi Elliot,
There is nothing like a fool question.
As to ConTeXt and LuaTeX. When ConTeXt came out i thought that is
what I was waiting for, but when I went to the manuals I went UGHH!
How was this suppose to be easier than LaTeX. Since I did have the time
Hi All,
I chime in here.
This is all OT.
At the risk of being mark as a TROLL, here goes.
Evidently, the participants of this discussion come from varying
backgrounds and the terminology is getting all messed up.
1) structure of a document
Hi Everybody,
I am very sorry for starting this discussion of on OT route.
Whether to use Word or "TeX" for one purpose the other is very
philosophical.
Each has their strengths and deficiencies. A discussion that does not
belong here
and there is no real
O.K. I am can not remember where I got the part where TeX was based on
SGML. Maybe, I have the context wrong maybe it was LaTeX. It was somewhere
in the depths of CTAN, though.
regards
Keith
Am 04.10.2010 um 19:13 schrieb maxwell:
> 10...@googlemail.com> <099c5363-8fa4-43bd-bc2e-f981c1d
Hi Adam,
Yes, there is a reason for TexWorks not working with the MacOSX
character palette. TeXWorks is a multi-platform application and is not
designed
to work with all input methods provided by an OS. In other words it
does not
have the API in order to work with
Hi Alexandros,
Though I sympathize with your goal and always thought that LaTex&Co
would be better off if it had its commands in different languages.
But, Xe(La)TeX is a macro language and as such "predefined".
Though you can rename the command names it would make
Am 12.10.2010 um 10:26 schrieb Philip Taylor (Webmaster, Ret'd):
> If I may address a couple of Ulrike's questions :
>
> Ulrike Fischer wrote:
>
>> Also: How will a user of a fully localized format be able to get
>> help from the XeTeX-community?
>
> Such a user will be able to get help from h
Am 12.10.2010 um 11:25 schrieb Philip Taylor (Webmaster, Ret'd):
> There are, of course, potential : one is colour names, where
> the cardinality of the colour-name set varies with language.
> But just because there are problems does not mean that the idea
> /in general/ is not feasible. I genui
Am 12.10.2010 um 13:22 schrieb Apostolos Syropoulos:
>>As I have stated before, it should be possible to internationalize the
> use
>>of LaTeX and Xe(La)TeX. We just need to develop a standardized way of
>>defining these translations, similarly as is done in GUIs.
>>All we ha
Am 12.10.2010 um 18:18 schrieb Tobias Schoel:
>
> Hi,
>
>
> Am 12.10.2010 15:03, schrieb Fr. Michael Gilmary:
>> Philip Taylor (Webmaster, Ret'd) wrote:
>>
>>
>>
>>> I genuinely believe that we should
>>> be moving towards a more inclusive society, in which each can
>>> express his or her i
Am 12.10.2010 um 20:24 schrieb Khaled Hosny:
> On Tue, Oct 12, 2010 at 07:54:26PM +0200, Keith J. Schultz wrote:
>> Personally, whether it is called \section, \abschnitt, or \ghaefjkh123
>> does not matter, as long as I can learn
>> which command name to use
Am 13.10.2010 um 01:27 schrieb Andrew Cunningham:
> maybe one way forward is to define the commands in Greek, but also
> develop a script to covert to/from Greek localised XeLaTeX and
> standard XeLaTeX?
>
This is definitely is a way to go.
Another question is is their a wide-sp
Am 13.10.2010 um 19:27 schrieb Mojca Miklavec:
> On Wed, Oct 13, 2010 at 12:57, Keith J. Schultz wrote:
>>
>>If Yes, then the question would be how easy would it be to modify
>> Xe(La)TeX
>>to be localizable.
> [snip, snip
> ]
> But of cours
Am 14.10.2010 um 12:59 schrieb Peter Dyballa:
>
> Am 14.10.2010 um 12:39 schrieb Keith J. Schultz:
>
>> This would be a good idea, but the original thought was also
>> for using localized units and such.
>
> I don't think there are so many "local
Hi Again,
Like I saiud the best point to confront the problem is in the parser at
a low level directly in the xetex engine. so that the "normal" is
distinguished
from the markup.
There seems to be a consensus that it would be a good idea to have the
marku
tant.
I think I can safely assume that the tex code is somewhat archaic and not easy
to patch.
Though I have not look at the sources since the 80s.
regards
Keith.
Am 15.10.2010 um 11:53 schrieb Philip Taylor (Webmaster, Ret'd):
>
>
> Keith J. Schultz wrote:
>
>>
Nice examples.
Am 15.10.2010 um 15:29 schrieb Philip Taylor (Webmaster, Ret'd):
>
> Keith, I don't see enough in your answer to enable me to understand
> how you propose to resolve what seem to me to be very serious
> problems of semantic ambiguity. Let me give a simple example,
> using a fictit
Well since the xetex engine/binary is modified one can
allow it to accept an optional line before \documentclass
for setting the "language".
If it is there change "language" if not assume "normal".
regards
Keith.
Am 15.10.2010 um 15:45 schrieb Philip Taylor (Webmaster, Ret'd):
>
>
> A
Hi Will,
Do not worry about it. These things do happen and all is work in
progress.
Also, it it was that easy we would not need you, and appreciate your
hard work so much!!
regards
Keith.
Am 17.10.2010 um 07:40 schrieb Will Robertson:
>
> Well, we try
Hi Rodney,
Look into the unicode-math package and the
unicode math fonts.
regards
Keith.
Am 18.10.2010 um 08:41 schrieb Rodney Polkinghorne:
> Dear list
>
> Has anyone used lcm with XeTeX? If so, how do you map greek letters
> in the XeTeX source to th
What is your preamble?
regards
Keith.
Am 14.12.2010 um 05:58 schrieb Alan Jones:
>
> Hi:
>
> I get this error compiling my thesis. I have TexLive 2008 on Debian Lenny.
>
> ! Package ifpdf Error: Name clash, \ifpdf is already defined.
>
> See the ifpdf package documentation for expl
Hi David,
Are You joking?
Seriously!
All I can say is HAL == IBM!
Now == Opx!!
Please do not be offended. But, it does seem more than
a coincidence! A shift of one!
Sorry, no help.
regards
Keith
HI,
I am on 10.6.7 and do not have any problems with fonts and printing!
I believe their is a simple fix. Delete the font caches.
I can not remeber the the source, but deleting the font cache seems to
fix the problem!
regards
Keith.
Am 01.04.2011 um 21:00 schrieb Mojca Miklavec:
> Hel
Hi All,
Have anybody with problems have the 64-bit kernal running!
I am as I prepare for the transition to Lion! So far I do not have any problems
with any of the programs i use! So it just not be apples fault! then again!
regards
Keith.
---
Hi Phil,
I can not much about Persian, Farsi, but
the Americans use to speak acedenmically
"American English", which in colloquial American
was referred to as English. Today, American is the widespread
term in Acedemica. Québécois is definitely is not French.
regards
Keith.
Am 10.06.2011
Hi Everybody,
The problem is not the OS or "filing system". It is the programs.
1) If you have a remote server mounted all you need
is the mount point plus the path to the file. Standard
on all OSes I know.
2) A program can open any/retrieve any file on a
Am 22.06.2011 um 10:36 schrieb Philip TAYLOR (Webmaster, Ret'd):
>
>
> Keith J. Schultz wrote:
>
>> The problem is not the OS or "filing system". It is the programs.
>> 1) If you have a remote server mounted all you need
>> is the mo
22.06.2011 um 15:27 schrieb msk...@ansuz.sooke.bc.ca:
> On Wed, 22 Jun 2011, Keith J. Schultz wrote:
>> 2) A program can open any/retrieve any file on a server
>> using http. all it needs to do is speak http!
>
> While we're at it, let's add a spellin
Hi Nicolas,
Normally, XeTeX does not take that long to start up or run!
It would seem to me that your system and web-server is set-up
wrong. There are other possibilities for the problems you are experiencing.
Either way, I believe you problem has nothing to do with XeTeX.
Sorry.
regards
Hi All,
Although this is ended.
There is another interpretation of the use of "quick reply"
quick can, also, mean brief/short !! That is how I read it.
On the other side, Heba said a quick reply would be "highly appreciated".
Which is very polite,
even I he needed a response very fast!
La
Hi Herbert,
You are right their is font library that is deprecated and only allows xe(l)tex
to be built 32-bit!
This will have to change as the Mac world has going 64-bit. Yes, you can run
32-bit programs
under Lion, but it also comes at a performance price.
Anyone know exactly which library an
ewrite the needed
libraries.
If this is the wrong place to discuss this, please point me in the
right direction.
regards
Keith.
Am 30.08.2011 um 02:57 schrieb George N. White III:
> On Mon, Aug 29, 2011 at 2:32 PM, Keith J. Schultz
> wrote:
>> Hi Herbert,
>>
&g
can comment.
regards
Keith
Am 30.08.2011 um 11:15 schrieb Peter Dyballa:
>
> Am 30.08.2011 um 09:53 schrieb Keith J. Schultz:
>
>> The question is if there is an actual need to still support ATSU at all?
>
> This question could probably be answered
Keith.
Am 30.08.2011 um 18:47 schrieb George N. White III:
> On Tue, Aug 30, 2011 at 4:53 AM, Keith J. Schultz
> wrote:
>
>> Hi George,
>>
>>The Macports version of xetex is built 64-bit, but it does not have
>> ATSU features.
>>
Hi Peter,
Am 30.08.2011 um 23:30 schrieb Peter Dyballa:
>
> Am 30.08.2011 um 16:43 schrieb Keith J. Schultz:
>
>> ATSU is deprecated and replaced by Core Text for handling unicode as of
>> Leopard.
>>
>> So, xetex has to be refractured or rewritten to us
Excuse ME! Peter.
What is you problem
The call to Core text offer the same results as ATSUI!!!
So no instability is introduced!
Am 31.08.2011 um 15:30 schrieb Peter Dyballa:
>
> Am 31.08.2011 um 12:02 schrieb Keith J. Schultz:
>
>> Nothing is considered stable just yet.
Am 31.08.2011 um 20:12 schrieb George N. White III:
> On Wed, Aug 31, 2011 at 12:47 PM, Richard Koch wrote:
>> Folks,
>>
>>
[snip, snip]
>> Having said all of that, it would be wonderful if someone would take on the
>> task of converting the Macintosh portions of XeTeX from ATSUI to Core Text,
Thanx Dicl for your sober response.
Basically, that was the intension of my message here.
The problem is that I am not a texnician, not do I know much,
to say anything, about electronic typography.
I was hoping to get pointers, before I just download the the xetex source and
work through before
Am 01.09.2011 um 20:42 schrieb Peter Dyballa:
>
> Am 01.09.2011 um 20:13 schrieb Keith J. Schultz:
>
>> Furthermore I do not know which compilers are used over at MacTeX as this
>> does matter
>> in ways which are far to complicates to discuss here.
>
> It&#
Am 01.09.2011 um 22:01 schrieb Peter Dyballa:
>
> Am 01.09.2011 um 21:12 schrieb Keith J. Schultz:
>
>> Are you sure you know what you are talking- er- writing about!!
>
> Yes.
>
> The problem is with libgcc (or libstdc++ or libobjc). You don't nee
t know this) I have had Apples since the FIRST
Apple IIe came out and developed
on them.
regards
Keith.
Am 02.09.2011 um 15:03 schrieb Martin Schröder:
> 2011/9/1 Keith J. Schultz :
>>Are you sure you know what you are talking- er- writing about!!
>
> Yes.
>
Hi Nathan, Vafa,
TeX, LaTeX, Xe(La)TeX, Lua(La)Tex, etc come with a very steep learning
curve.
It was one of the reasons I stopped using LaTeX some 20 years ago.
Also, back then the packages were not stable and conflicted with each
other so if
really ne
Hi Vafa,
I kind of figured as much.
The only, I can do for you is to ask.
Can anybody. please help him. I assume many problems is that the
packages either do not support unicode
of are not designed to work with RTL. I am sure if the packages are
fixed other pro
Hi Mathew,
I think you are being a bit unfair towards Vafa!
LaTeX, et al are highly complex. The advent of unicode has not made things
easier.
The problem is not that bidi or the other package is "faulty", but in the way it
is done, so that when then two are used together the result is not what
Hi All,
For what it is worth I see two roads to follow.
1) create a glossary for swiss-french
2) modify the french glossary to accommodate swiss-spacing.
Following 1 has the advantage that it keeps the french glossary clean. Yet, to
follow this road
causes a problem with mainta
O.K. I will jump in here.
Intellectual property rights are often a great big gray zone.
Maybe, it is time the author of the package speaks up himself
what is meant.
Also, it does seem clear if the code being used or parts thereof are from a
different party, who may or may not have rights which t
examples!
Mike should chime in here and clarify. He should also change his license to
be more specific.
regards
Keith.
Am 25.10.2011 um 17:32 schrieb Tobias Schoel:
>
>
> Am 25.10.2011 10:30, schrieb Keith J. Schultz:
>> O.K. I will jump in here.
>
schrieb Philip TAYLOR (Webmaster, Ret'd):
>
>
> Keith J. Schultz wrote:
>
>> 2) Intellectual Property Rights
>> This controls modification of code and use thereof.
>>In our case, the author discourages this, and basically
>>
Hi Tobias,
Polyglossia works fine for german! I believed you missed a error message.
You have to change one line, you need:
\defaultfontfeatures{Ligatures=TeX}
regards
Keith.
Am 28.10.2011 um 16:53 schrieb Tobias Schoel:
> As a simple user (very simple: none of my work gets published,
Hi Everybody,
Slow down a bit. Sorry if I sound high headed here!
There seems to be a misunderstanding what exactly a
PLAIN TEXT FILE is.
Computing has evolved since I started using computers.
When I started out a plain text file was a file just holding
7-bit ASCII or EBCDIC, or the like witho
Hi Phillip,
Am 14.11.2011 um 09:36 schrieb Philip TAYLOR:
>
>
> Keith J. Schultz wrote:
>
>> So, Unicode needs an editor to be displayed correctly.
>
> Why ? Not meant to sound aggressive, but seems a very
> odd assertion, IMHO. Editors are for changing thi
responses to Phillip and Zdenek for more insight.
regards
Keith.
Am 14.11.2011 um 11:10 schrieb Peter Dyballa:
>
> Am 14.11.2011 um 09:21 schrieb Keith J. Schultz:
>
>> So, Unicode needs an editor to be displayed correctly.
>
Hi Zdenek, all,
I was to lazy to list all those encodings.
I will be more precise know for those not reading carefully.
There is a difference between what is considered plain text in the
computer
world and what its content is.
Basically, plain te
Hi there,
Am 14.11.2011 um 11:20 schrieb Chris Travers:
> My $0.02
>
> In general, I think we are going to get the most mileage by sticking
> with the TeX way of doing things by default. The nice thing is that ~
> can be turned into a non-active character, and one can set other
> thing
Well, XeTeX users are already restricted in their choice of editors. The
must/should support
minimalistically unicode. Of course you can enter the characters/glyphs in a
cryptic manner.
Have fun reading a text with true unicode!
Also, remember when you had to use ALT-XXX for entering characters
Well, Zdenek,
I guess that is where TeXWorks comes to mind. It could give a unified
GUI for TeX with unicode.
regards
Keith.
Am 14.11.2011 um 11:38 schrieb Zdenek Wagner:
> You live in a perfect world where you can do everything with a single
> editor using nice GUI. The world is not y
Hi Chris,
I agree with you that one should be able to see the differences in an editor,
but this feature should be feature to turn off and on.
The question is what is an ordinary editor.
Also, most prefer to use their pet editors.
regards
Keith.
> I get worried when reserved character
Hi Humpty Dumpty,
Go read the standards and cry without kissing the girls.
Evidently, you are trained in computer science or you would
know what a real plain text file is.
Also, in computer science we do not use the definitions of lay persons nor
common language use.
I assume you know all ab
Hi Herbert,
You are absolutely right in your assessment. True plain text files are/where
traditionally 7-bits.
Though, I have to tell you that nowadays even 8-bit files are considered plain
text.
The verdict is still out in how far unicode text files are plain text files, as
unicode is well u
:
> 2011/11/14 Keith J. Schultz :
>> Well, Zdenek,
>>
>> I guess that is where TeXWorks comes to mind. It could give a unified
>> GUI for TeX with unicode.
>>
> Does it mean I will be forced to use TeXWorks and nothing else? And
> will it work over telnet or ssh
Hi Tobias,
Am 14.11.2011 um 18:42 schrieb Tobias Schoel:
>
>
> Am 14.11.2011 18:30, schrieb msk...@ansuz.sooke.bc.ca:
[snip, snip]
> Now we come to the trouble of Unicode specifying a line-breaking algorithm (
> http://www.unicode.org/reports/tr14/tr14-26.html ), which probably isn't
Hi all,
I agree that XeTeX should support all printable characters.
A non.breaking space is to me a printable character, in so far that
it is important and must be used to distinguish between word space, et all.
To go back in history, one of my pet peeves in LaTeX was that I had to
enter the Ge
there are conventions that one has to follow concerning the
wrapping of words. Most
prominent Names.
As an example I will use my name Keith J. Schultz. (Yes, this is not the best
example and (Xe)Tex has ways
of getting around this) Names should not be wrap or should there not be
unnecessary space
Am 17.11.2011 um 11:26 schrieb Keith J. Schultz:
> O.K.
>
> You mention in a later post that you do consider a space as a printable
> character.
This line should read as:
You mention in a later post that you consider a space as a
non-printable character.
> I
is in (Xe)TeX's parsing algorithm. I never liked it
and personally I have many problems it.
regards
Keith.
Am 17.11.2011 um 13:53 schrieb Philip TAYLOR:
>
>
> Keith J. Schultz wrote:
>>
>> Am 17.11.2011 um 11:26 schrieb Keith J. Schultz:
>>
>>>
Hi Pihilip,
Thoughout, my programming life and experience I have learned
that internal structure means nothing, as long as the result is correct
when it comes out.
As you rightfully point out the problem lies inside how TeX internally
handles space characters when adding them to its internal str
to be completely revamped.
Am 17.11.2011 um 20:36 schrieb Ross Moore:
> Hi Phil,
>
> On 17/11/2011, at 23:53, Philip TAYLOR wrote:
>
>> Keith J. Schultz wrote:
>>>>
>>>> You mention in a later post that you do consider a space as a printable
>&
TAYLOR:
>
>
> Keith J. Schultz wrote:
>
>> The crux of of the problem is in (Xe)TeX's parsing algorithm. I never liked
>> it
>> and personally I have many problems it.
>
> Is this XeTeX-specific, Keith, or do you also dislike
> TeX's parsing al
Keith.
P.S. Want a signed version.
regards
Keith.
Am 18.11.2011 um 14:57 schrieb Arthur Reutenauer:
> On Fri, Nov 18, 2011 at 10:16:31AM +0100, Keith J. Schultz wrote in
> reply to Ross Moore:
>> You are probably a little young to know this, but TeX'
Hi Zdenek,
I do not think anybody disputes the fact that characters are not glyphs.
The confusion arises that a character in CS is well defined and has a
history.
To be more exact it is just one byte in size so that there can be only
256 characters.
Unic
:
>
>
> Keith J. Schultz wrote:
>
>> I do not think anybody disputes the fact that characters are not glyphs.
>>
>> The confusion arises that a character in CS is well defined and has a
>> history.
>> To be more exact it is just one byte
Am 19.11.2011 um 13:51 schrieb Zdenek Wagner:
> 2011/11/19 Keith J. Schultz :
>
>>As for getting junk when copying unicode, just copy between to text
>> using different fonts, where one font does
>>not contain the glyph.
>>
> When performing co
>
>
>
> On 19 November 2011 09:27, Philip TAYLOR wrote:
>
>
> Keith J. Schultz wrote:
>
>Me I am almost 50 and have been around computers since the 80s.
>First was a Apple IIe, at the university we used a main frame.
>
> My first computer was a
Hi Everybody,
I have been loosely following this thread.
>From my lay point of view. Using two different colors can
work unicode for composing the output in (Xe)Tex.
>From my simplistic view, it would be just a having a two color
"T" where the top cross should be red and the rest black.
(Xe)Te
Hi All,
I jump back in. I will cite anybody because what has been said is correct.
But,
1) trying to compare a browser, XeTex engine and LuaTeX will not help
as they have different methods of composing their output.
That is how they compose and position their gly
composed glyphs whether you realize it or not.
regards
Keith.
Am 30.11.2011 um 13:56 schrieb Khaled Hosny:
> On Wed, Nov 30, 2011 at 11:10:11AM +0100, Keith J. Schultz wrote:
>> Hi All,
>>
>> I jump back in. I will cite anybody because what has been said i
Hi Dan,
Though, you problem is interesting, but I can believe you have this
problem.
You do realize that a footnote in general is not intend to contain this kind of
information. Even though it may be possible in TeX, et al.
Most writers show poor style by stuffing all kinds of information in the
course, you should create a
command
like \myrefernce for easy typing or even \myfootnote.
regards
Keith.
Am 04.12.2011 um 12:51 schrieb Daniel Greenhoe:
> Hi Keith,
>
> On Sun, Dec 4, 2011 at 6:01 PM, Keith J. Schultz wrote:
>> Most writers show poor style by stuffi
Hi John,
The philosophers can think, but have poor writing habits and style IMHO!
Yet, that is a tradition. ;-))
regards
Keith.
Am 04.12.2011 um 13:40 schrieb John Was:
> Hello
>
> I use plain XeTeX, and thanks to scholars of ancient philosophy who like to
> have huge footnotes (some
Hi,
I am no expert, but
1) using XeTeX et al. you normally should not be using the fontenc
package!
2) In the example below you are using \usepackage with \makeatletter
I assume this will cause problems.
3) I would use polyglossia instead of babe
I missed that! thought it was just font stuff.
Anyway, after that he loads babel! I am almost sure first load font spec,
polyglossia and then babel is
likely to cause some weird side effects.
regards
Keith.
Am 05.12.2011 um 08:58 schrieb Andy Lin:
> Actually, he does load polyglossia.
Hi Wolfgang,
Eventhough you have things working now,
I would still clean up you code or even templates!
For example if you are using polyglossia you do not need babel.
To my knowledge, babel is sufficient for german.
regards
Keith.
Am 05.12.2011 um 12:11 schrieb Wolfgang Keller:
> Hel
C'mon Phil, no problem.
There must be a purpose in this madness.
regards
Keith.
Am 13.12.2011 um 12:39 schrieb Philip TAYLOR:
> Sorry, list : this was meant to go to Dominik, not everyone ...
> ** Phil.
>
> Philip TAYLOR wrote:
>
>> Ah, Dominik, you mad mad "early adopter" : I
Hi,
I would suggest putting a newline after the therorem title. Could right your
own command
for that.
Though it is a matter of style and taste.
regards
Keith.
Am 16.12.2011 um 02:55 schrieb Daniel Greenhoe:
> I have a rather long document involving mathematics that sometimes has
> t
Hi Kiddies,
I am getting a good laugh with this thread!
Yes, there are caveats to the arguments.
The important thing is that there is someone/ a team that is willing
to improve the behavior of Babel and maybe teaching it some new tricks
while not breaking it! The benefits may only be for a few o
1 - 100 of 131 matches
Mail list logo
