Hi All,
according to the new reformed rules, the use of ß is dependent on the length of
the preceding
vowel.
So, according to the latest reformed orthography rules wusste is correct.
Some words seem to be still allowed with the older orthography, but the they
are exceptions.
Either way, the
Hi All, Phillip.
Let recap the situation here:
The original post from Scott stated he had a problem going from his wiki
to PDF via Xe(La)TeX! His problem involved texts with mixed directionality.
I did not express myself very well and should have said that in unicode one
can identify
that the unicode
standard
and utf-8 encoding/decoding is inadequate, but in its implementation.
The culprit is not utf-8!
Am 09.12.2013 um 23:51 schrieb Philip Taylor p.tay...@rhul.ac.uk:
Keith J. Schultz wrote:
Hi Phillip,
1) I do not know Vietnamese!
2) If I did uses the proper BMP would give
schrieb Khaled Hosny khaledho...@eglug.org:
On Thu, Dec 05, 2013 at 09:41:04AM +0100, Keith J. Schultz wrote:
Hi Scott,
We are talking Unicode here right! What is there to guess?
And how do you, using Unicode, tell in what language is this line
written
that already has not
identified
the language.
Am 09.12.2013 um 10:38 schrieb Khaled Hosny khaledho...@eglug.org:
On Mon, Dec 09, 2013 at 09:22:10AM +0100, Keith J. Schultz wrote:
Hi Khaled,
your question can not be serious!
No, it is.
It is pretty much in the standard!
No.
True enough
option is probably to treat embedded LTR text in an RTL context as 'exotic'
and not to attempt hyphenation.
I've heard it said that LuaTeX has better bidi support. What does that
mean, exactly? Should I be considering switching?
--scott
On Dec 4, 2013 4:08 AM, Keith J. Schultz schul
Hi,
Another command line tool on the Mac to find files is mdfind. See mdfind.
regards
Keith.
Am 14.11.2013 um 01:16 schrieb NMPOST7 nmpo...@gmail.com:
On 14/11/2013 01:08, Herbert Schulz wrote:
Get the `Find Any File' application! No need to update the locate database,
etc.
Hi All,
There is one possibility which all seem to be all are over-looking!
Direct input!
- = -
-- = –
--- = —
All characters are easily typed directly. (At least on the Mac)
regards
Keith.
--
Hi Zdenek,
Am 07.08.2012 um 10:36 schrieb Zdenek Wagner zdenek.wag...@gmail.com:
Please do not mix engine and format. XeTeX does a few things i a
different way than TeX. In the LaTeX user's eyes the font loading is
different. It was not practical to modify the old LaTeX font loading
Hi Again,
I am now trying to grock LuaTeX otfload, that is ContTexts font loading system.
From what I have understood so far in order get things started is a
GDEF-feature
and GPOS Lookup support in the font.loader and font-otf.lua.
Do you know off hand, if these features are already implemented
um 15:22 schrieb Martin Schröder mar...@oneiros.de:
2012/8/1 Keith J. Schultz keithjschu...@web.de:
As has been mentioned the source and programming rational behind
LuaTeX is not documented, at least not publically. Even if one would
do the programming their is no guarantee that the code
Hi All,
No, Apostolos is right.
Things got a little to OT.
I apologize. I will next time listen to my inner feelings.
regards
Keith.
Am 02.08.2012 um 17:38 schrieb Philip TAYLOR p.tay...@rhul.ac.uk:
Apostolos Syropoulos wrote:
I fully agree with this remark. I suppose there
Hi Adam,
Yes, LuaTeX is a evolving project, especially at the lowest level.
Am 01.08.2012 um 02:54 schrieb Adam Twardoch (List) list.a...@twardoch.com:
On 31.07.2012, at 13:02, Peter Dyballa peter_dyba...@web.de wrote:
it's questionable whether it's worth when XeTeX has reached its end of
Hi Zdenek,
I believe well are pretty much inline with each other.
Am 01.08.2012 um 10:48 schrieb Zdenek Wagner zdenek.wag...@gmail.com:
2012/8/1 Keith J. Schultz keithjschu...@web.de:
Hi Adam,
Yes, LuaTeX is a evolving project, especially at the lowest level.
Am 01.08.2012 um 02
Am 01.08.2012 um 10:31 schrieb Zdenek Wagner zdenek.wag...@gmail.com:
[snip, snip]
XeTeX is not a remedy to TFM deficiencies, it is again the remedy of
encoding deficiencies. It won't be that difficult to extend TFM but
implementation of Unicode and support for comlpex Arabic and Asian
Hi Ulrike,
Am 01.08.2012 um 12:13 schrieb Ulrike Fischer ne...@nililand.de:
Am Wed, 1 Aug 2012 09:32:16 +0200 schrieb Keith J. Schultz:
From the simple user side. LuaTeX is about as easy as it gets. For
most purpose I can teach you all you need to know how to use Lua
for TeX in 2 hours
Hi Zdenek,
Am 01.08.2012 um 13:22 schrieb Zdenek Wagner zdenek.wag...@gmail.com:
2012/8/1 Ulrike Fischer ne...@nililand.de:
Am Wed, 1 Aug 2012 12:30:52 +0200 schrieb Zdenek Wagner:
Well you only confirm my impression: That quite a lot of scripts
never felt the pressure put on us by the
will dawn on you.
regards
Keith.
Am 01.08.2012 um 13:41 schrieb Zdenek Wagner zdenek.wag...@gmail.com:
2012/8/1 William Adams will.ad...@frycomm.com:
On Jul 31, 2012, at 6:02 PM, Keith J. Schultz wrote:
You are only partially correct. Yes, you can create very fine structures
off
Hi Zdenek,
I am perfectly, able to learn what I need to learn. I am perfectly able
to program in almost any programming langauge. TeX is one that I
can directly program in because I simple can grasp its philosophy.
The biggest problem to all this at what is needed is so essential, that
without
Am 01.08.2012 um 18:56 schrieb Zdenek Wagner zdenek.wag...@gmail.com:
2012/8/1 Keith J. Schultz keithjschu...@web.de:
Hi Zdenek,
[snip, snip]
No, microtype does not offer more glyphs, it offers glyph distorted in
many different ratios. Multiple Master Fonts would be able to solve
Hi Joachim,
Am 31.07.2012 um 13:46 schrieb Joachim Trinkwitz j...@uni-bonn.de:
Am 31.07.2012 um 11:06 schrieb Keith J. Schultz keithjschu...@web.de:
One of the reasons why I stopped using LaTeX was its lack of support for
system fonts.
Xe(La)TeX change all that. Yet, when I look
Hi Adrian,
Xe(La)TeX will be around from quite some time. If I see things
right many features are still being developed or expanded.
Will it go away or die? Eventually, maybe. Who knows? I mean TeX
is still around.
regards
Keith.
Am 31.07.2012 um 22:14 schrieb Adrian Burd
how exact could one
get?
regards
Keith.
Am 31.07.2012 um 19:38 schrieb William Adams will.ad...@frycomm.com:
On Jul 31, 2012, at 11:59 AM, Keith J. Schultz wrote:
except micro-type goe sway beyond Gutenbergs resolution!
Sure, if one chooses to use sp to define such, but one
Hi there,
Am 05.06.2012 um 17:44 schrieb proteus:
Apostolos Syropoulos writes:
As far as I know and is not a Greek word!!!
In your opinion! Others, including the designer of biblatex, strongly
disagree!
Just copy the relevant file into your working directory, adjust it
to suit your own
Hi All,
I have a question.
In a style file would say TeX barf if it contained utf-8 characters even if
I have them in a conditional sothat the are not processed by the engine
just parsed?
regards
Keith
Am 14.05.2012 um 01:19 schrieb Ross Moore:
Hi Ulrike, and Bruno,
On
Thanx for the info.
I was just curious because of the discussions about backward/legacy
compatibilties
with UTF.
It would seem to me that them all base packages should be refractured to
the point where the package/style file contains the if(engine) and loads then
the appropriate files for
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
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
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 shall
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:
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
. Of 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 keithjschu...@web.de wrote:
Most writers show poor style by stuffing all
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
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
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 is correct.
But,
1) trying
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)Tex
...@rhul.ac.uk 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 Clary 404, with 8K of magnetic core memory,
a magnetic card reader
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.
:
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 in size so that there can be only
256 characters
Am 19.11.2011 um 13:51 schrieb Zdenek Wagner:
2011/11/19 Keith J. Schultz keithjschu...@web.de:
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 copypaste or text search
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
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 p.tay...@rhul.ac.uk wrote:
Keith J. Schultz wrote:
You mention in a later post that you do consider a space as a printable
character.
This line should read
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's original output
format
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 do disagree
)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:
O.K.
You mention in a later post that you do consider a space
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 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
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 things;
why would you need a program
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.
Use GNU Emacs
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
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
things if
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
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
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
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,
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
denies us the right to do it.
He does /not/ deny
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
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
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 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
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
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 keithjschu...@web.de:
Are you sure you know what you are talking- er- writing about!!
Yes.
Please stop
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.
The same would
Am 31.08.2011 um 20:12 schrieb George N. White III:
On Wed, Aug 31, 2011 at 12:47 PM, Richard Koch k...@math.uoregon.edu 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
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's not only a question of compilers – you also
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 on some fonts or font technologies
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 keithjschu...@web.de
wrote:
Hi George,
The Macports version of xetex is built 64-bit, but it does not have
ATSU features.
so it is not fully functional
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
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!
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
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 spelling checker, SQL database backend
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 mount point plus the path to the file. Standard
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 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 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
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
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
Hi Alexandros,
Though I sympathize with your goal and always thought that LaTexCo
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 it
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 his/her
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 have to do
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 ideas in his or her
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 for getting a section.
So \قسم
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
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
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
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
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:
snip
If you take the
time to look at a Word-file(doc or docx
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
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
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:
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.
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
97 matches
Mail list logo
