\NC 04 \NC \currentdate[mm] \NC\NR
\NC jj \NC 11 \NC \currentdate[jj] \NC\NR
\NC yy \NC 11 \NC \currentdate[yy] \NC\NR
\NC weekday \NC Monday \NC \currentdate[weekday] \NC\NR
\NC referral \NC 20110404 \NC \currentdate[referral] \NC\NR
I am writing a booklet for use by junior doctors at the hospital where
I work. It will contain random bits of data that is available from
various online sources such as phone numbers, dosages of exotic drugs,
referral routes and assorted things better written down than
remembered. Much of it is in
ommand
# \processcommalist
# \processfirstactioninset
\processpage[names][yes|no]
# \processXMLbuffer
# \processXMLelement
# \processXMLfile
# \processXMLfilegrouped
# \product
\program[name]
# \project
# \protect
\publication[reference]
\quotation{text}
\quote{text}
\ran{text}
# \readfile
\ref[t|p|r|
hem
img_src=img.attributes['src'].reverse.sub(/\w+\./,"").reverse
# puts img_src
# see if position of figure is indicated
img_pos="force"
img_attrs.each do |arr|
img_pos=arr.gsub("position=","") if arr.match("position=&
we replace it with a ConTeXt reference
(@article/"a").each do |a|
a.swap("\\in[#{a.inner_html}]")
end
# remove 'alt' attribute inside element
# replace by equivalent command in context
(@article/"p/img").each do |img|
img_attrs=img.attributes['a
(on which we develop context) provides different link
systems i seldom use them; also, the server has just a copy of my local
stuff and not more;
> That way and as long as the archive files are available, a precise version of
> Context could be fetched from pragma-ade's server without
server without maintaining a local
versioned archive of cont.tmf.zip etc. Referral to a specific version of
Context would be a lot easier, and documenting the tools used for a project
would be a lot simpler. A common understanding of a Context version, reflected
in its package file name, would re
