Hi all,
if you use para indentation=none looseness=1Something.../para you
are not using XML properly. The purpose of XML is to describe the structure
of a document, not its appearance. Generally you will print the information
from the XML file in a different order or you will print just a part of
Dear Shivashankar,
I'm moving the answer to the mailing list where other people will be
able to help you better than I can (please CC him).
On Mon, Apr 27, 2015 at 11:49 AM, Shiva Shankar wrote:
Hi Mojca,
My name is Shivashankar and I am from Srirangapatna, Karnataka, India. I
wanted to
Joseph Wright wrote:
On 27/04/2015 07:35, Philip Taylor wrote:
Going even further off-topic, but pursuing this one aspect of the
thread, is there not only real one problem : the need to educate users
to cease marking up their documents in raw (La)TeX syntax, and instead
to express them in
2015-04-27 16:40 GMT+02:00 Apostolos Syropoulos asyropou...@yahoo.com:
Many consider that JSON will eventually replace XML.
Only if JSON gets schemes.
http://json-schema.org/ exists, but is not widely used.
Best
Martin
--
Subscriptions,
Joseph Wright wrote:
Somewhat away from the original topic, but it strikes me that building a
tagged PDF is going to be much more problematic at the macro layer than
at the engine level: is that fair? Deciding what elements of a document
are 'structure' is hard, and in 'real' documents it's
On 27/04/2015 00:22, Ross Moore wrote:
But of course that doesn't address the problem for LaTeXt users until
someone writes a suitable/comparable package (maybe someone did
already, I didn't try to follow).
I have coding for much of what is needed, using the modified pdfTeX.
But there is a
On 27/04/2015 08:43, Ross Moore wrote:
Hi Joseph,
On 27/04/2015, at 4:19 PM, Joseph Wright wrote:
On 27/04/2015 00:22, Ross Moore wrote:
But of course that doesn't address the problem for LaTeXt users until
someone writes a suitable/comparable package (maybe someone did
already, I didn't
On 27/04/2015 07:35, Philip Taylor wrote:
Going even further off-topic, but pursuing this one aspect of the
thread, is there not only real one problem : the need to educate users
to cease marking up their documents in raw (La)TeX syntax, and instead
to express them in well-formed XML ? I
Hi Simon,
On Mon, Apr 27, 2015 at 5:57 AM, Simon Cozens si...@simon-cozens.org wrote:
On 26/04/2015 23:18, Zdenek Wagner wrote:
I pushed a fix in r37053, both ITF Devanagari and Kohinoor Devanagari
works for me now.
I'm still seeing problems with Kohinoor Devanagari, even after the two
Hi Joseph,
On 27/04/2015, at 4:19 PM, Joseph Wright wrote:
On 27/04/2015 00:22, Ross Moore wrote:
But of course that doesn't address the problem for LaTeXt users until
someone writes a suitable/comparable package (maybe someone did
already, I didn't try to follow).
I have coding for much
On 27/04/2015 01:05, Douglas McKenna wrote:
Joseph Wright wrote:
\def\{0}\expandafter\def\csname^00022\endcsname{1}
\ifnum\=0 \message{tex82}\else\message{newstuff}\fi
When I implemented a Unicode escape sequence extension using double-caret
notation in the JSBox TeX-language
Hello Simon,
Thanks very much for this detailed information. Obviously (for now) there
is plenty there that I don’t get, terminology-wise, but no surprise. I’ll
keep this handy and work on it as I can.
I never really worked with C (I was a B programmer back in the day) and am
now working on
On 27/04/2015 19:39, Philip Taylor wrote:
As to whether XML is a particularly good format not only here or for
anything, all I can say is that in my experience we (humanity, that is)
have not yet come up with anything better; LaTeX 2e, by explicitly
permitting the conflation of form and
Zdenek Wagner wrote:
If you want to describe the page layout in a structured way, the page
... /page markup might cause other mark up not well formed. Of course,
if the XML is for your own purpose, you can do anything. Even if it is
not suggested by XML experts, it may be helpful. And if
2015-04-27 15:00 GMT+02:00 Philip Taylor p.tay...@rhul.ac.uk:
Zdenek Wagner wrote:
If you want to describe the page layout in a structured way, the page
... /page markup might cause other mark up not well formed. Of course,
if the XML is for your own purpose, you can do anything. Even
Zdenek Wagner wrote:
Formatting advices should better be present in processing instructions.
You can type ?TeX something? ?HTML something else ? etc.
Why do you write better, Zdeněk ? They /can/ be expressed as
processing instructions, but that would require an augmented parser;
they can
2015-04-27 13:57 GMT+02:00 Philip Taylor p.tay...@rhul.ac.uk:
Zdenek Wagner wrote:
Formatting advices should better be present in processing instructions.
You can type ?TeX something? ?HTML something else ? etc.
Why do you write better, Zdeněk ? They /can/ be expressed as
processing
Zdenek Wagner wrote:
if you use para indentation=none looseness=1Something.../para
you are not using XML properly. The purpose of XML is to describe the
structure of a document, not its appearance.
Yes, the element describes the structure; attributes such as those
you quote in the example
2015-04-27 13:27 GMT+02:00 Philip Taylor p.tay...@rhul.ac.uk:
Zdenek Wagner wrote:
if you use para indentation=none looseness=1Something.../para
you are not using XML properly. The purpose of XML is to describe the
structure of a document, not its appearance.
Yes, the element
Dear Shivashankar,
I do not know Kannada, I even do not know other scripts, I know only
Devanagari and I think that the problems will be similar. Hyphenation in
Unicode aware engines is quite simple, if you have the patterns. TeX
hyphenates words and a word is defined as a sequence of characters
As to whether XML is a particularly good format not only here or for
anything, all I can say is that in my experience we (humanity, that is)
have not yet come up with anything better; LaTeX 2e, by explicitly
permitting the conflation of form and content, fails abysmally in this
respect
Ross Moore wrote -
On 27/04/2015, at 10:05 AM, Douglas McKenna wrote:
Given that the number of TeX input files using ^^u is likely miniscule, and
the number of those that follow the ^^u or ^^U with four or six hex digits
is even smaller, it seemed like a worthwhile benefit vs. cost,
On 27 April 2015 at 01:05, Douglas McKenna d...@mathemaesthetics.com
wrote:
Joseph Wright wrote:
\def\{0}\expandafter\def\csname^00022\endcsname{1}
\ifnum\=0 \message{tex82}\else\message{newstuff}\fi
When I implemented a Unicode escape sequence extension using double-caret
notation
Thank you sir.
Now I will start working on that.
Thanks a lot once again.
On Mon, Apr 27, 2015 at 5:02 PM, Zdenek Wagner zdenek.wag...@gmail.com
wrote:
Dear Shivashankar,
I do not know Kannada, I even do not know other scripts, I know only
Devanagari and I think that the problems will be
David Carlisle wrote -
Introducing incompatible syntax for functionality shared across Unicode TeX
extensions
is a major headache for package authors. Please don't use this syntax!
Understood.
That isn't at all clear, I don't see any evidence that the equivalent #;
notation in XML
On 27 April 2015 at 23:41, Douglas McKenna d...@mathemaesthetics.com
wrote:
Ross Moore wrote -
On 27/04/2015, at 10:05 AM, Douglas McKenna wrote:
Given that the number of TeX input files using ^^u is likely miniscule,
and the number of those that follow the ^^u or ^^U with four or six
Hi all,
On 28/04/2015, at 0:40, Apostolos Syropoulos asyropou...@yahoo.com wrote:
As to whether XML is a particularly good format not only here or for
anything, all I can say is that in my experience we (humanity, that is)
have not yet come up with anything better; LaTeX 2e, by explicitly
27 matches
Mail list logo
