From f5d5dc04a3a9336da726ed2dcf9bcb741f8dad4b Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Tue, 11 Oct 2011 22:54:02 +0000 Subject: morehype (11oct11) git-svn-id: svn://tug.org/texlive/trunk@24269 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/tex/latex/morehype/blog.sty | 287 +++++++++++++--------- Master/texmf-dist/tex/latex/morehype/blogdot.css | 41 ++++ Master/texmf-dist/tex/latex/morehype/blogdot.sty | 200 +++++++++++++++ Master/texmf-dist/tex/latex/morehype/lang-de.fdf | 4 +- Master/texmf-dist/tex/latex/morehype/lnavicol.sty | 141 +++++++++-- Master/texmf-dist/tex/latex/morehype/texblog.fdf | 283 +++++++++++++++++++++ Master/texmf-dist/tex/latex/morehype/texlinks.sty | 39 ++- 7 files changed, 849 insertions(+), 146 deletions(-) create mode 100644 Master/texmf-dist/tex/latex/morehype/blogdot.css create mode 100644 Master/texmf-dist/tex/latex/morehype/blogdot.sty create mode 100644 Master/texmf-dist/tex/latex/morehype/texblog.fdf (limited to 'Master/texmf-dist/tex') diff --git a/Master/texmf-dist/tex/latex/morehype/blog.sty b/Master/texmf-dist/tex/latex/morehype/blog.sty index 6ff50a8ab58..5ff71be95e2 100644 --- a/Master/texmf-dist/tex/latex/morehype/blog.sty +++ b/Master/texmf-dist/tex/latex/morehype/blog.sty @@ -1,5 +1,5 @@ \NeedsTeXFormat{LaTeX2e}[1994/12/01] %% \newcommand* etc. -\ProvidesPackage{blog}[2011/08/31 v0.5 simple fast HTML (UL)] +\ProvidesPackage{blog}[2011/10/10 v0.5 simple fast HTML (UL)] %% copyright (C) 2010 2011 Uwe Lueck, %% http://www.contact-ednotes.sty.de.vu %% -- author-maintained in the sense of LPPL below. @@ -21,12 +21,17 @@ %% |\CLBrk| is a \emph{code line break} %% (also saving subsequent comment mark): \newcommand*{\CLBrk}{^^J} +%% |\htmakeext| is the extension of the generated file. +%% Typically it should be `.html', as set here, +%% but my Atari emulator needs `.htm' +%% (see `texblog.fdf'): +\newcommand*{\htmakeext}{.html} %% |\BlogCopyFile[]{}| %% ``copies" the \TeX\ source file %% into the file specified by `\ResultFile'. %% As in \TeX\ an empty line starts a new paragraph, %% we ``interpret" an empty source line as -%% \acro{HTML} tag \xmltagcode{p} for starting a new paragraph. +%% \HTML\ tag \xmltagcode{p} for starting a new paragraph. %% Empty source lines following some first empty source %% line immediately are ignored %% (``compression" of empty lines).---However, @@ -43,6 +48,8 @@ \ProcessOptions \MakeOther\< \MakeOther\> %% TODO ... \newcommand*{\BlogCopyFile}[2][]{% + \typeout{^^J\screenqtd{blog.sty} generating %% 2011/10/05 + \screenqtd{\htmljob\htmakeext}}% \ProcessFileWith[\BlogCodes \let\ProvidesFile\BlogProvidesFile %% 2011/02/24 \let\protect\@empty %% 2011/03/24 @@ -61,15 +68,15 @@ \newcommand*{\BlogCodes}{% %% 2010/09/07 \endlinechar`\ \catcode`\~\active \BasicNormalCatCodes} %% The tilde is active as in Plain~TeX too, it is so natural to -%% use it for abbreviating \acro{HTML}'s ` '! +%% use it for abbreviating \HTML's ` '! %% %% %% v0.42: %% |\ProvidesFile{.tex}[]| \ is supported %% for use with the \CtanPkgRef{morehype}{myfilist} %% package %% TODO \urlpkgfoot!? 2011/02/22 %% to get a list of source file infos. -%% In generating the \acro{HTML} file, the file infos are transformed -%% into an \acro{HTML} comment. Actually it is +%% In generating the \HTML\ file, the file infos are transformed +%% into an \HTML\ comment. Actually it is %% |\BlogProvidesFile| (for the time being, 2011/02/22): \@ifdefinable\BlogProvidesFile{% \def\BlogProvidesFile#1[#2]{% @@ -87,19 +94,20 @@ %% \[`\let\ProvidesFile\BlogProvidesFile'\] %% somewhere, e.g., in `\BlogCopyFile'. %% -%% \pagebreak[3] %% 2011/05/11 -%% == General \acro{HTML} Matters == +%% \pagebreak %% 2011/10/10 +%% == General \HTML\ Matters == %% The following stuff is required for any web page %% (or hardly evitable). %% === General Tagging === -%% $$|\TagSurr{}{}{}|$$ +%% %% $$ -> \[ ... 2011/10/10: +%% \[|\TagSurr{}{}{}|\] %% (I hoped this way code would be more readable %% than with `\TagSurround' ...) -%% and $$|\SimpleTagSurr{}{}|$$ +%% and \[|\SimpleTagSurr{}{}|\] %% are used to avoid repeating element names in %% definitions of \TeX\ macros that refer to ``entire" %% elements---as opposed to elements whose content often -%% spans lines (as readable \acro{HTML} code). +%% spans lines (as readable \HTML\ code). %% We will handle the latter kind of elements %% using \LaTeX's idea of ``environments." %% `\TagSurr' also inserts specifications of element @@ -116,10 +124,10 @@ %% === Attributes === %%% (General) %%% %% Inspired by the common way to use `@' for referring %% to element attributes---i.e., `@' refers to attribute -%% `'---in \acro{HTML}/\acro{XML} documentation, we often use -%% $$`\@{}' \qquad -%% \mbox{to ``abbreviate"}\qquad `=""'$$ -%% within the starting tag of an \acro{HTML} element. +%% `'---in \HTML/\acro{XML} documentation, we often use +%% \[`\@{}' \qquad +%% \mbox{to ``abbreviate"}\qquad `=""'\] +%% within the starting tag of an \HTML\ element. %% This does not really %% make typing easier or improve readability, %% it rather saves \TeX's memory by using a single token @@ -130,24 +138,32 @@ \newcommand*{\declareHTMLattrib}[1]{% \def\reserved@a{@#1}% \@ifundefined{@#1}% -% {\@namedef{@#1}##1{ #1="##1"}}% {\@namedef{@#1}##1{#1="##1"}}% \@notdefinable} %% So after `\declareHTMLattrib{}', `\@' is a %% \TeX\ macro expecting one parameter for the specification. %% %% A few frequent attributes are declared this way here. +%% %% 2011/09/27: +%% |@class|, |@id|, |@style|, |@title|, |@lang|, and |@dir| +%% are the ones named on +%% \wikienref{HTML\#Attributes}{\meta{Wikipedia}}: +\let\@class\relax %% for tab/arr in latex.ltx +\declareHTMLattrib{class} +\declareHTMLattrib{id} +\declareHTMLattrib{style} +\let\@title\relax %% for \title in latex.ltx +\declareHTMLattrib{title} %% 2011/04/26 +\declareHTMLattrib{lang} +\declareHTMLattrib{dir} +%% |@type| is quite frequent too: %% doc. 2011/09/27 +\declareHTMLattrib{type} %% |@href| is most important for that ``hyper-text:" \declareHTMLattrib{href} %% ... and |@name| (among other uses) is needed for %% |@name| for %% 2011/04/26 %% hyper-text anchors: \declareHTMLattrib{name} %% 2010/11/06 -%% Many elements have the |@type| attribute: %% 2011/08/01 -\declareHTMLattrib{type} -%% |@title| for tooltips: %% 2011/04/26 -\let\@title\relax -\declareHTMLattrib{title} %% 2011/04/26 %% |@bgcolor| is used in tables as well as %% for the appearance of the entire page: \declareHTMLattrib{bgcolor} @@ -180,7 +196,6 @@ %% Some other uses of `\declareHTMLattrib' essential for %% \emph{tables:} %% emph 2011/04/24 \declareHTMLattrib{border} %% 2011/04/24 -\declareHTMLattrib{class} %% 2011/04/24 \declareHTMLattrib{cellpadding} %% 2010/07/18 \declareHTMLattrib{cellspacing} %% 2010/07/18 \declareHTMLattrib{colspan} %% 2010/07/17 @@ -193,28 +208,28 @@ %% well, not so bad, as the main purpose of this namespace %% is saving tokens \emph{in macros.} %% -%% === \acro{HTML}'s Special Symbols === -%% |#| is needed for numerical specifications in \acro{HTML}, +%% === \HTML's Special Symbols === +%% |#| is needed for numerical specifications in \HTML, %% especially colors and Unicode symbols, %% while it plays a different (essential) role in our %% definitions of \TeX\ macros here. %% We redefine \LaTeX's |\#| %% for a kind of ``quoting" `#' in macro definitions -%% in order to refer to their \acro{HTML} meaning.---I \textbf{wonder} +%% in order to refer to their \HTML\ meaning.---I \textbf{wonder} %% what I had in mind with the |&| things here. %% I cannot find any use of |\AmpMark| in my code %% (including my web pages). There is no real problem -%% with calling special \acro{HTML} symbols, `&' is simply +%% with calling special \HTML\ symbols, `&' is simply %% made `other' already here for macros calling those symbols %% (below), and in processing source files, it is as well %% `other' by default. The symbols section, however, redefines |\&| -%% for calling \acro{HTML}'s ampersand symbol. +%% for calling \HTML's ampersand symbol. {\catcode`\&=12 \catcode`\#=12 \gdef\AmpMark{&} \gdef\#{#}} %% ... `\CompWordMark' etc.? %% %% === Head === -%% |\head| produces the first two tags that an \acro{HTML} file must start: +%% |\head| produces the first two tags that an \HTML\ file must start: \newcommand*{\head}{} %% ^^J rm 2010/10/10 %% |\MetaTag{}| and |\ContentAtt{}| %% are internal shortcuts: @@ -224,14 +239,14 @@ \newcommand*{\charset}[1]{% \MetaTag{http-equiv="Content-Type" \ContentAtt{text/html; #1}}} %% |\description{}| for web searches (I think): -\newcommand*{\description}[1]{% - \MetaTag{\@name{description} \ContentAtt{#1}}} -%% ... an outright \textbf{mistake!} TODO %% todo 2011/07/25 +% \newcommand*{\description}[1]{% +% \MetaTag{\@name{description} \ContentAtt{#1}}} +%% ... an outright \textbf{mistake!} %% commented out 2011/10/05 %% The definition is overridden -%% to get the \acro{HTML} equivalent to \LaTeX's `description' environment. +%% to get the \HTML\ equivalent to \LaTeX's `description' environment. %% `\newcommand' did not warn here because we don't load any \LaTeX\ %% class for text-processing macros and code generation.---And so -%% some |\MetaDescr| should be defined---and used finally! +%% some |\MetaDescr| should be defined---and used finally! TODO %% %% |\robots{}|: \newcommand*{\robots}[1]{%% juergenf: index, follow, noarchive @@ -242,7 +257,16 @@ %% `media=""': \newcommand*{\stylesheet}[2]{% \space\space %% 2010/09/10 - } + } +%% %% 2011/10/05: +%% Alternatively, style declarations may occur in the +%% \xmltagcode{style} element. It can be accessed by the +%% |{style}| environment (cf. Sec.~\ref{sec:env}): +\newenvironment*{style}[1] + {} %% With |\title{}|, heads %% grammar? TODO 2010/04/08 %% the browser window: \renewcommand*{\title}[1]{\space\space#1} @@ -270,9 +294,9 @@ %% %% We ``re-use" some \LaTeX\ commands for specifying font attributes, %% rather than (re)defining macros `\i', `\b', `\tt', ... -%% $$|\textit{}| \qquad +%% \[|\textit{}| \qquad %% \mbox{just expands to}\qquad -%% \xmltagcode{i}\xmltagcode{/i}$$ +%% \xmltagcode{i}\xmltagcode{/i}\] \renewcommand*{\textit}{\SimpleTagSurr i} %% etc. for |\textbf|, |\texttt| ...: \renewcommand*{\textbf}{\SimpleTagSurr b} @@ -280,7 +304,7 @@ %% |\textsf{}| TODO (see some `makehtml.tex') %% 2011/05/11 %% %% |\textcolor| is from \LaTeX's 'color' package -%% that we won't load for generating \acro{HTML}, +%% that we won't load for generating \HTML, %% so it is ``new" here, it is just natural to use it %% for colored text (2010/05/15): \newcommand*{\textcolor}[1]{\TagSurr{font}{color="#1"}} @@ -289,21 +313,26 @@ %% |\code{}| marks as ``code," %% just accessing te \xmltagcode{code} element, %% while standard \LaTeX\ does not provide a `\code' command: -\newcommand*{\code} {\SimpleTagSurr{code}} %% 2010/04/27 +\newcommand*{\code}{\SimpleTagSurr{code}} %% 2010/04/27 %% |\emph{}| is \LaTeX's command again, but somewhat abused, %% expanding to \lq\xmltagcode{em}\xmltagcode{/em}\rq: \renewcommand*{\emph} {\SimpleTagSurr{em}} %% ... Note that \LaTeX's `\emph' feature of switching to `up' %% when `\emph' appears in an italic context doesn't work here ... %% -%% |\strong{}| again just calls an \acro{HTML} element. +%% |\strong{}| again just calls an \HTML\ element. %% It may behave like `\textbf{}', or ... I don't know ... -\newcommand*{\strong} {\SimpleTagSurr{strong}} +\newcommand*{\strong}{\SimpleTagSurr{strong}} %% %% 2011/03/09: %% |\var{}| accesses the \xmltagcode{var} element: \newcommand*{\var}{\SimpleTagSurr{var}} +%% |\acronym{}| ... there is `\acro' in the TUGboat +%% macros, while \HTML\ provides an \xmltagcode{acronym} +%% environment ... %% 2011/09/21 +\newcommand*{\acronym}{\SimpleTagSurr{acronym}} %% %% == Environments == +%% \label{sec:env} %% We reduce \LaTeX's |\begin| and |\end| to their most primitive %% core. %% \begin{description} @@ -317,81 +346,81 @@ %% does not allow any assignments while ``copying" %% the \TeX\ source into the `.htm'. %% There even is no check for proper nesting. -%% `\begin' and `\end' just represent \acro{HTML} elements +%% `\begin' and `\end' just represent \HTML\ elements %% (their starting/ending tags) %% that typically have ``long" content. %% (We might ``intercept" `\begin' and `\end' before %% copying for executing some assignments in a future version.) \let\begin\@nameuse \def\end#1{\csname end#1\endcsname} -%% |{center}|---TODO cf. \xmltagcode{center} 2010/07/18: -\renewenvironment*{center}{

}{

} %% ... moving |{english}| to `xmlprint.cfg' %% 2010/05/22 ...%% doc 2010/11/06 %% %% As formerly with ``fonts," we have \emph{two} policies for %% \textbf{choosing macro names}: -%% (i)~using an \emph{existing} \acro{HTML} element name, +%% (i)~using an \emph{existing} \HTML\ element name, %% (ii)~using a \LaTeX\ command name for accessing a somewhat -%% similar \acro{HTML} element having a \emph{different} name. -%% -%% |\declareHTMLelement{}| creates a \emph{new} -%% ``environment" according to policy~(i): -\newcommand*{\declareHTMLelement}[1]{% - \newenvironment*{#1}{<#1>}{}} -%% |\renderHTMLelement{}{}| \emph{redefines} -%% \LaTeX's environment to use \acro{HTML}'s element -%% according to policy~(ii): -\newcommand*{\renderHTMLelement}[2]{% - \renewenvironment*{#1}{<#2>}{}} -%% Applying former auxiliaries: -%% -%% `\small' is a \LaTeX\ command from a \emph{class}---that -%% we won't load, therefore we can create a \emph{new} -%% |{small}| environment using \xmltagcode{small} according to -%% policy~(i): -\declareHTMLelement{small} +%% similar \HTML\ element having a \emph{different} name. +%% [\,2011/10/05: so what? TODO\,] +%% +%% New 2011/10/05: +%% With |\useHTMLelement{}{}|, +%% you can access the \xmltagcode{} element +%% by the `' environment. +%% The ``starred" form is for ``list" environments +%% where I observed around 2011/10/01 that certain links +%% (with Mozilla Firefox) need \xmltagcode{/li}: +\newcommand*{\useHTMLelement}{% + \@ifstar{\@useHTMLelement[]}{\@useHTMLelement}} +\newcommand*{\@useHTMLelement}[3][]{% + \@namedef{#2}{<#3>}% + \@namedef{end#2}{#1}} +%% Applications: +%% +%% \acro{CARE:} |{small}| is an environment here, +%% it is not in \LaTeX: +\useHTMLelement{small}{small} +%% |{center}|: %% TODO von 2010/07/18, weiter oben +% \renewenvironment*{center}{

}{

} +% \renewenvironment*{center}{

}{

} +\useHTMLelement{center}{center} %% The next definitions for |{enumerate}|, |{itemize}|, %% `{verbatim}' follow policy~(ii): -\renderHTMLelement{enumerate}{ol} -\renderHTMLelement{itemize} {ul} +\useHTMLelement*{enumerate}{ol} +\useHTMLelement*{itemize} {ul} %% %% 2010/11/16: %% With 'blog.sty', |{verbatim}| really doesn't work much %% like its original \LaTeX\ variant. \TeX\ macros inside %% still are expanded, and you must care yourself for %% wanted \dqtd{quoting}: -\renderHTMLelement{verbatim} {pre} %% 2010/09/10 -%% -%% |{quote}| is defined in \LaTeX\ classes only again. -%% To use it for policy~(ii), we give it a dummy definition -%% so `\render'... won't complain: -\let\quote\empty -\renderHTMLelement{quote}{blockquote} -%% For list |\item|s, I tried to get readable \acro{HTML} code +\useHTMLelement{verbatim} {pre} +%% |{quote}|: +\useHTMLelement{quote}{blockquote} +%% For list |\item|s, I tried to get readable \HTML\ code %% using `\indenti'. This fails with nested lists. %% The indent could be increased for nested lists %% if we supported assignments with `\begin' and `\end'. +%% 2011/10/04 including \xmltagcode{}, +%% repairs more links in \acro{DANTE} talk: \renewcommand*{\item}{\indenti
  • } -%% <- 2010/05/23, 2010/06/10 -> -% \renewcommand*{\item}{
  • } %% \LaTeX's |{description}| environment redefines the %% label format for the optional argument of `\item'. %% Again, \emph{we} cannot do this here %% (we even cannot use optional arguments, %% at least not easily). %% Instead we define a different |\ditem{}| -%% having a \emph{mandatory} argument. -%% %% 2010/07/05: -\renderHTMLelement{description}{dl} +%% having a \emph{mandatory} argument +%% (TODO star?). %% 2011/10/05 +\useHTMLelement{description}{dl} \newcommand*{\ditem}[1]{\indenti
    \strong{#1}
    } %% %% == Links == %% === Basic Link Macros === %% |\hanc{}{}| makes an anchor with -%% \acro{HTML} label (like 'hyperref''s `\hypertarget'): +%% \HTML\ label (like 'hyperref''s `\hypertarget'): \newcommand*{\hanc}[1]{\TagSurr a{\@name{#1}}} %% |\hancref{}{}{}| makes an anchor with -%% \acro{HTML} label and at the same time a link to : +%% \HTML\ label and at the same time a link to : \newcommand*{\hancref}[2]{\TagSurr a{\@name{#1} \@href{#2}}} %% |\href{}{}| makes a link to : \newcommand*{\href}[1]{\TagSurr a{\@href{#1}}} @@ -426,7 +455,7 @@ %% %% === Built Macros for Links to Local Files === %% Originally, I wanted to refer to my web pages only, -%% using $$|\fileref{}|.$$ I have used +%% using \[|\fileref{}|.\] I have used %% extension `.htm' to avoid disturbing my Atari %% editor 'xEDIT' or the the Atari emulator (Hatari). %% %% rm. 2011/08/18: @@ -439,6 +468,7 @@ %% general `\FileRef{}|', overlooking %% that it was the same as |\href|. % \newcommand*{\FileRef}[1]{\TagSurr a{\@href{#1}}} +\newcommand*{\htext}{.htm} %% 2011/10/05 \newcommand*{\fileref}[1]{\href{#1\htext}} % \newcommand*{\emfileref}[2]{\fileref{#1}{\emph{#2}}} \newcommand*{\itfileref}[2]{\fileref{#1}{\textit{#2}}} @@ -477,9 +507,9 @@ \TagSurr a{\@href{https://#1" target="_blank}}} %% %% -%% == Symbols == %% ordering 2011/02/25 +%% == Characters/Symbols == %% `Symbols' until 2011/09/25 %% === Basic Preliminaries === -%% |&| is made `other' for using it to call \acro{HTML}'s +%% |&| is made `other' for using it to call \HTML's %% ``character entities." %% dot inside 2011/02/25 \@makeother\& %% Again we have the two policies about choosing macro names @@ -498,6 +528,7 @@ \renderHTMLsymbol{\&}{amp} \let\%\PercentChar %% +%% \pagebreak %% output routine problem 2011/10/05 %% === Diacritics === %% changed 2011/03/04 %% For the difference between \dqtd{diacritic} and %% \dqtd{accent,} see \wikienref{Diacritic}{Wikipedia}. @@ -505,7 +536,7 @@ %% |\ccedil|: %%%, |\eacute|, |\ocirc| (``r\^ole") \declareHTMLsymbol{ccedil} %% %% 2011/03/04: -%% \acro{HTML} entities |é|, |ô| etc. can be accessed +%% \HTML\ entities |é|, |ô| etc. can be accessed %% by \TeX's accent commands |\'|, |\^|, |\`|, |\"|: % \declareHTMLsymbol{eacute} % \declareHTMLsymbol{ocirc} @@ -581,7 +612,7 @@ %% %% === Dashes === %% The ligatures `--' and `---' for en~dash and em~dash -%% don't work in our expanding mode. Now, \acro{HTML}'s policy +%% don't work in our expanding mode. Now, \HTML's policy %% for choosing names often prefers shorter names than %% are recommended for (La)\TeX, so here I adopt a \emph{third} %% police besides (i) and (ii) earlier; cf. \LaTeX's @@ -599,7 +630,7 @@ \renewcommand* {\qquad} {\quad\quad} %% 2011/07/22: ` ' allows line breaks, %% so we introduce |\thinsp| to access ` ', -%% while |\thinspace| and |\,| use Unicode "Narrow No-Break Space" +%% while |\thinspace| and |\,| use Unicode ``Narrow No-Break Space" %% (`U+202F', see \meta{Wikipedia \Wikienref{Space (punctuation)}}; %% browser support?): % \renderHTMLsymbol{\thinspace}{thinsp} @@ -607,13 +638,15 @@ \declareHTMLsymbol{thinsp} \renderHTMLsymbol{\thinspace}{\#8239} \renderHTMLsymbol{\,} {\#8239} +%% |\figurespace| %% 2011/09/25 +%% (U+2007, cf.~\wikienref{Figure space}{\meta{Wikipedia}}): +\newcommand*{\figurespace}{&\#8199;} %% %% === Quotes, Apostrophe, Prime === %% |\lq|, |\rq| \renderHTMLsymbol{\lq} {lsquo} -% \newcommand* {\rsquo} {’} %% removed 2010/04/26 \renderHTMLsymbol{\rq} {rsquo} -%% In order to use the right single quote for the \acro{HTML} apostrophe, +%% In order to use the right single quote for the \HTML\ apostrophe, %% we must save other uses before. %% |\screentqtd{}| is used for screen messages, %% and |\urlapostr| is the version of the right single quote @@ -627,7 +660,8 @@ %% save `\screenqtd'! Tilde likwise!? %% ... TODO change `\catcode`\`'!? 2010/04/26 %% -%% |\ldquo|, |\rdquo|, |\sbquo|, |\prime|, |\Prime| ... +%% |\bdquo|, |\ldquo|, |\rdquo|, |\sbquo|, |\prime|, |\Prime| ... +\declareHTMLsymbol{bdquo} %% 2011/09/23 \declareHTMLsymbol{ldquo} \declareHTMLsymbol{rdquo} \declareHTMLsymbol{sbquo} %% 2010/07/01 @@ -637,15 +671,15 @@ %% |\endqtd{}| quotes in the English style using double quote %% marks, |\enqtd{}| uses single quote marks instead, and %% |\dedqtd{}| quotes in German style: -\def\endqtd#1{\ldquo#1\rdquo} %% \newcommand: "\end" +\def\endqtd#1{\ldquo#1\rdquo} %% \newcommand: ``\end" \newcommand*\enqtd[1]{\lq#1\rq} %% 2010/09/08, \new... 2010/11/08 -\newcommand*{\dedqtd}[1]{„#1\ldquo} +\newcommand*{\dedqtd}[1]{\bdquo#1\ldquo} \newcommand*{\deqtd}[1]{‚#1‘} %% corr. 2011/05/14 -%% ... TODO `\bdquo'!? %% 2010/11/08 +%% TODO `\glqq' from 'german.sty' etc. %% 2011/09/22 %% %% === Math === %% %% doc. extended 2011/05/08: -%% Because \verb+<+ and \verb+>+ are used for \acro{HTML}'s +%% Because \verb+<+ and \verb+>+ are used for \HTML's %% element notation, we provide aliases |\gt|, |\lt| %% for mathematical $\lt$ and $\gt$: \declareHTMLsymbol{gt} @@ -675,12 +709,12 @@ \renderHTMLsymbol{\ast}{lowast} %% 2011/03/29 %% Besides \TeX's |\subset| and |\subseteq|, %% we provide short versions |\sub| and |\sube| %% 2011/05/08 -%% inspired by \acro{HTML}: +%% inspired by \HTML: \declareHTMLsymbol{sub} %% 2011/04/04 \let\subset\sub %% 2011/05/08 \declareHTMLsymbol{sube} %% 2011/03/29 \let\subseteq\sube %% 2011/05/08 -%% \TeX\ and \acro{HTML} agree on |\cap|, |\cup|, %% 2011/05/08 +%% \TeX\ and \HTML\ agree on |\cap|, |\cup|, %% 2011/05/08 %% and |\times|: \declareHTMLsymbol{cap} %% 2011/04/04 \declareHTMLsymbol{cup} %% 2011/04/04 @@ -690,7 +724,8 @@ %% We need |\minus| since math mode switching is %% not supported by 'blog': %% 2011/05/08 \declareHTMLsymbol{minus} %% 2011/03/31 -%% We override \acro{HTML}'s `ˆ' to get \TeX's \cs{circ} +%% We override \HTML's \lq`ˆ'\rq\ %% \lq\rq 2011/09/08 +%% to get \TeX's \cs{circ} %% (i.e., $\circ$; %% 2011/05/08: %% \textcolor{red}{but I cannot see it %% on my own pages!?}): @@ -698,8 +733,14 @@ \renderHTMLsymbol{\cdot}{middot} %% 2011/05/07 %% |\sdot| generates `&sdot,', a variant of of `·' %% reserved for the \Wikienref{dot product} according to -%% the \wikideref{Malzeichen\#Skalarprodukt}: +%% the \wikideref{Malzeichen\#Skalarprodukt} +%% {German \meta{Wikipedia}} %% 2011/09/08! \declareHTMLsymbol{sdot} %% 2011/05/08 +%% I provide |\degrees| for the degree symbol. +%% \LaTeX\ already has `\deg' as an operator, +%% therefore I do not want to use `\declareHTMLsymbol' +%% here. +\newcommand*{\degrees}{°} %% %% === Other === %% The tilde |~| is used for its wonderful purpose, @@ -723,12 +764,15 @@ %% |\euro|: %% 2011/05/09 \declareHTMLsymbol{euro} %% \LaTeX's |\S| prints the \dqtd{\Wikienref{section sign}} -%% \qtd{\S}. In \acro{HTML}, the latter accessed by `§', +%% \qtd{\S}. In \HTML, the latter accessed by `§', %% we \dqtd{redirect} `\S' to this: %% 2011/05/18 \renderHTMLsymbol{\S}{sect} +%% |\dagger|, |\ddagger|: %% 2011/10/01 +\renderHTMLsymbol{\dagger}{dagger} +\renderHTMLsymbol{\ddagger}{Dagger} %% %% -%% == \TeX-related == %% 2010/08/24 +%% == \TeX-related == %% 2010/08/24 %% Somebody actually using 'blog.sty' must have a need to put down %% notes about \TeX\ for her own private purposes at least---I expect. %% === Logos === @@ -750,23 +794,25 @@ \newcommand*{\XeTeX}{\prg{XeTeX}} %% 2010/10/09 \newcommand*{\TeXbook}{TeXbook} %% 2010/09/13 %% -%% === Else === +%% === Describing Macros === %% With v0.4, \TeX-related \emph{links} are moved to 'texlinks.sty'. %% %% |\texcs{\}| or `\texcs\' %% (care for spacing yourself): -\newcommand*{\texcs}[1]{\code{\string#1}} %% 2010/11/13 +\newcommand*{\texcs}[1]{\code{\string#1}} %% 2010/11/13 %% Good old |\cs{}| may be preferable: -\def\cs#1{\code{\BackslashChar#1}} %% 2011/03/06 +\def\cs#1{\code{\BackslashChar#1}} %% 2011/03/06 +%% |\metavar{}|: %% 2011/09/22 +\newcommand*{\metavar}[1]{\angled{\meta{#1}}} %% %% == Tables == %% %% 2011/04/24: rm. remark on doubtful stability, ordered %% === Indenting === %% There are three levels of indenting: -%% $$|\indenti|, \quad +%% \[|\indenti|, \quad %% |\indentii|,\quad \mbox{and}\quad -%% |\indentiii|.$$ -%% The intention for these was to get readable \acro{HTML} code. Not sure ... +%% |\indentiii|.\] +%% The intention for these was to get readable \HTML\ code. Not sure ... {\catcode`\ =12%% 2010/05/19 \gdef\indenti{ }\gdef\indentii{ }\gdef\indentiii{ }} %% @@ -783,7 +829,7 @@ {\indenti\CLBrk\endTable} %% === Rows === %% I first thought it would be good for readability if -%% some \acro{HTML} comments explain nesting or briefly describe +%% some \HTML\ comments explain nesting or briefly describe %% the content of some column, row, or cell. %% But this is troublesome when you want to comment out %% an entire table ... @@ -795,7 +841,7 @@ \newenvironment{tablecoloredrow}[2] {\TableRow{#1}{\@bgcolor{#2}}} {\endTableRow} -%% "top" 2010/05/18: +%% ``top" 2010/05/18: \newenvironment{tablerow}[1]{\TableRow{#1}{\@valign@t}} {\endTableRow} %% 2010/07/18: @@ -830,6 +876,7 @@ %% 2010/07/18: \newcommand*{\startTd}[1]{} \def\endTd{} +\newcommand*{\emptycell}{} %% 2011/10/07 %% %% === Filling a Row with Dummy Cells === %% Generalization 2010/06/28: @@ -841,11 +888,12 @@ \newcommand*{\fillrowcolor}[2]{\FillRow{#1}{\@bgcolor{#2}}} %% %% == Misc == -%% |\comment{}| produces a one-line \acro{HTML} comment. +%% |\comment{}| produces a one-line \HTML\ comment. %% By contrast, there is an environment %% |{commentlines}{}| -%% for mult-line comments. It is convenient for ``commenting out" -%% code (unless the latter contains other \acro{HTML} comments ...) +%% for multi-line comments. %% was mult-l... 2011/09/08 +%% It is convenient for ``commenting out" +%% code (unless the latter contains other \HTML\ comments ...) %% where is a \emph{comment} for explaining what is %% commented out. %% 2010/11/14 \newcommand*{\comment}[1]{} @@ -855,10 +903,10 @@ {} %% \TeX's |\hrule| (rather deprecated in \LaTeX) is redefined -%% to produce an \acro{HTML} horizontal line: +%% to produce an \HTML\ horizontal line: \renewcommand*{\hrule}{
    } %% Redefining |\ | to be the same as `\space' may be helpful -%% for manual indenting or spacing of \acro{HTML} code. +%% for manual indenting or spacing of \HTML\ code. %% Or better (just now remembering): I used it for making %% ``ASCII trees" with the \xmltagcode{pre} element %% (redefined `verbatim'). @@ -920,7 +968,7 @@ v0.3 2010/11/10 removed ^^J from \head v0.4 2011/01/24 moving links to texlinks.sty v0.41 2011/02/07 \NormalHTTPref 2011/02/10 refined call of `texlinks' - PART OF CTAN RELEASE r0.3 +part of MOREHYPE RELEASE r0.3 v0.5 2011/02/22 \BlogProvidesFile 2011/02/24 ... in \BlogCopyFile 2011/02/25 ordering symbols @@ -956,3 +1004,20 @@ v0.5 2011/02/22 \BlogProvidesFile 2011/07/25 "todo" on \description 2011/08/18f.removing \FileRef, 0.42-> 0.5 2011/08/31 clarified use of \urlapostr +part of MOREHYPE RELEASE r0.4 +v0.6 2011/09/08 doc. uses \HTML, \lq/\rq with ˆ, + doc. fix `mult-'; \degrees + 2011/09/21 \acronym + 2011/09/22 \metavar; TODO \glqq... + 2011/09/23 \bdquo + 2011/09/25 doc. `Characters/Symbols'; \figurespace + 2011/09/27 "universal" attributes completed, reworked doc. + 2011/09/30 end lists with
  • + 2011/10/01 \dagger, \ddagger + 2011/10/04 \item includes + 2011/10/05 {style}; doc. \acronym -> \acro, \pagebreak, + rm. \description; {center} accesses
    , + \useHTMLenvironment replaces \declareHTMLelement + and \renderHTMLelement, message "generating" + 2011/10/07 \emptycell + 2011/10/10 doc.: page breaks, $$->\[/\] diff --git a/Master/texmf-dist/tex/latex/morehype/blogdot.css b/Master/texmf-dist/tex/latex/morehype/blogdot.css new file mode 100644 index 00000000000..31f8e9ddeed --- /dev/null +++ b/Master/texmf-dist/tex/latex/morehype/blogdot.css @@ -0,0 +1,41 @@ +/* blogdot.css for blogdot.sty (morehype bundle) 2011/10/05 */ +/* (C) 2011 Uwe Lueck www.contact.uwe.lueck.de.vu */ +/* 2011/09/21 aus blog/plain.css, 2011/09/26 gekürzt, Versuche, Umbau */ +/* +b, h1, h2, h3, h4, div, p, td, th, body, span, table, ol, li, a, ul { +font-family:Arial,Verdana,"Lucinda Sans",sans-serif; +color:#000000; +font-size:21px; +} +*/ + +h1 { font-size: 42px; margin-bottom: 21px } +h2 { font-size: 30px; margin-bottom: 21px } +h3 { font-size: 24px; } +h4 { font-size: 21px; } + +/* body, td, th, div, p, ul, li, em, strong */ +td { +font-family:Arial,Verdana,"Lucinda Sans",sans-serif; +color:#000000; +font-size: 21px +} + +p { margin-bottom:0px } +dl, ol, ul { +/* padding-left: 18px; */ +padding-left: 1em; +margin-left: 1em; margin-top: 18px; margin-bottom: 18px; +vertical-align: middle; +} +dt { margin: 0px; margin-top: 18px; margin-bottom: 9px; padding: 0px } +li { margin: 0px; margin-top: 9px; margin-bottom: 9px; padding: 0px } +blockquote { margin-left: 2em } +pre { margin-left:2em; margin-top:0px } + +/* table { margin: 0px; margin-top: 9px; margin-bottom: 18px; padding: 0px} */ + +a:link { color:#0000d0; text-decoration:none; } +a:visited { color:purple; text-decoration:none; } +a:hover { color:blue; text-decoration:underline; } +a:active { color:blue; text-decoration:underline; } diff --git a/Master/texmf-dist/tex/latex/morehype/blogdot.sty b/Master/texmf-dist/tex/latex/morehype/blogdot.sty new file mode 100644 index 00000000000..08f4779a099 --- /dev/null +++ b/Master/texmf-dist/tex/latex/morehype/blogdot.sty @@ -0,0 +1,200 @@ +\NeedsTeXFormat{LaTeX2e}[1994/12/01] %% \newcommand* etc. +\ProvidesPackage{blogdot}[2011/10/10 v0.2 HTML presentations (UL)] +%% copyright (C) 2011 Uwe Lueck, +%% http://www.contact-ednotes.sty.de.vu +%% -- author-maintained in the sense of LPPL below. +%% +%% This file can be redistributed and/or modified under +%% the terms of the LaTeX Project Public License; either +%% version 1.3c of the License, or any later version. +%% The latest version of this license is in +%% http://www.latex-project.org/lppl.txt +%% We did our best to help you, but there is NO WARRANTY. +%% +%% Please report bugs, problems, and suggestions via +%% +%% http://www.contact-ednotes.sty.de.vu +%% +%% == 'blog' Required == +%% 'blogdot' is an extension of 'blog' +%% (but what about options? TODO): +\RequirePackage{blog} +%% == Size Parameters == +%% \label{sec:dot-size} +%% I assume that it is clear what the following +%% six page dimension parameters +%% \begin{quote} +%% |\leftpagemargin|, |\rightpagemargin|, +%% |\upperpagemargin|,\\|\lowerpagemargin|, +%% |\typeareawidth|, |\typeareaheight| +%% \end{quote} +%% mean. +%% The choices are what I thought should work best +%% on my 1024$\times$600 screen; but I had to optimize +%% the left and right margins experimentally +%% (with Mozilla Firefox~3.6.22 for Ubuntu canonical~-~1.0); +%% see `blogdot.cfg': +\newcommand*{\leftpagemargin}{192} +\newcommand*{\rightpagemargin}{\leftpagemargin} +%% So |\rightpagemargin| ultimately is the same as +%% |\leftpagemargin| as long as you don't redefine it, +%% and it suffices to `\renewcommand' `\leftpagemargin' +%% in order to get a horizontically centered type area +%% with user-defined margin widths.---Something analogous +%% applies to |\upperpagemargin| and |\lowerpagemargin|: +\newcommand*{\upperpagemargin}{80} +\newcommand*{\lowerpagemargin}{\upperpagemargin} +%% A difference to the ``horizontal" parameters is +%% (I expect) that the position of the type area on the +%% screen is affected by |\upperpagemargin| only, +%% and you may choose |\lowerpagemargin| just large enough +%% that the next slide won't be visible on any computer screen +%% you can think of. +\newcommand*{\typeareawidth}{640} +\newcommand*{\typeareaheight}{440} +%% Centering with respect to web page body may work better on +%% different screens (2011/10/03), but it doesn't work here +%% (2011/10/04). +% \renewcommand*{\body}{% +% \CLBrk +% } +%% +%% == (Backbone for) Starting a ``Slide" == +%% \label{sec:dot-start} +%% |\startscreenpage{