Difference between revisions of "Wiki:Wishlist (old)"
Jump to navigation
Jump to search
(some more requests/ideas with minor importance) |
(downloading attachments, communication with google) |
||
| Line 6: | Line 6: | ||
=== wiki === | === wiki === | ||
| − | |||
* Are the <code><context></code> images rendered using gs? In that case, could [http://www.cs.wisc.edu/~ghost/doc/cvs/Devices.htm#PNG <code>-sDEVICE=pngalpha</code>] be used to get transparent images? | * Are the <code><context></code> images rendered using gs? In that case, could [http://www.cs.wisc.edu/~ghost/doc/cvs/Devices.htm#PNG <code>-sDEVICE=pngalpha</code>] be used to get transparent images? | ||
* adding <code><latex></code> counterpart to <code><context></code>; mostly in order to be able to compare LaTeX and ConTeXt results or to be able to describe the desired result in [[:Category:From LaTeX]] | * adding <code><latex></code> counterpart to <code><context></code>; mostly in order to be able to compare LaTeX and ConTeXt results or to be able to describe the desired result in [[:Category:From LaTeX]] | ||
| + | |||
=== archive === | === archive === | ||
| + | * Is it possible to download attachments? | ||
| + | |||
=== articles === | === articles === | ||
| + | |||
=== live === | === live === | ||
| + | |||
=== modules === | === modules === | ||
| + | |||
=== source === | === source === | ||
* displaying <code>*.hyp</code> and <code>*.pat</code> files as plain text instead of <code>"sorry, I don't know how to display the file"</code> | * displaying <code>*.hyp</code> and <code>*.pat</code> files as plain text instead of <code>"sorry, I don't know how to display the file"</code> | ||
* adding <code><a name="line xxx"></code> at the beginning of every line in the source code as to be able to reference to a certain line in hyperlinks (on the other hand: it may be a bad idea to be able to point to a certain line since the files are a subject to change) | * adding <code><a name="line xxx"></code> at the beginning of every line in the source code as to be able to reference to a certain line in hyperlinks (on the other hand: it may be a bad idea to be able to point to a certain line since the files are a subject to change) | ||
* perhaps adding <code><a name="ccedilla"></code> to places where <code>\definecharacter</code> stands in a similar way as the ''alt name='' are added in front of <code>\def\somecommand</code> (on the other hand: a bad idea since there may be more than two definitions of a single named character in one file) | * perhaps adding <code><a name="ccedilla"></code> to places where <code>\definecharacter</code> stands in a similar way as the ''alt name='' are added in front of <code>\def\somecommand</code> (on the other hand: a bad idea since there may be more than two definitions of a single named character in one file) | ||
| + | * serching/highlighting more that one word | ||
| + | * if the user comes from google, parse the URL for <code>&q=somequery</code> and add <code>?search=somequery</code> at the end of the new URL | ||
| + | |||
=== dl === | === dl === | ||
| + | |||
| + | === general === | ||
| + | |||
[[Category:Requests]] | [[Category:Requests]] | ||
Revision as of 13:09, 27 August 2005
Here's a wish list for the gardner :)
Contents
Ideas
... a place to collect ideas to make the garden even better ...
wiki
- Are the
<context>images rendered using gs? In that case, could-sDEVICE=pngalphabe used to get transparent images? - adding
<latex>counterpart to<context>; mostly in order to be able to compare LaTeX and ConTeXt results or to be able to describe the desired result in Category:From LaTeX
archive
- Is it possible to download attachments?
articles
live
modules
source
- displaying
*.hypand*.patfiles as plain text instead of"sorry, I don't know how to display the file" - adding
<a name="line xxx">at the beginning of every line in the source code as to be able to reference to a certain line in hyperlinks (on the other hand: it may be a bad idea to be able to point to a certain line since the files are a subject to change) - perhaps adding
<a name="ccedilla">to places where\definecharacterstands in a similar way as the alt name= are added in front of\def\somecommand(on the other hand: a bad idea since there may be more than two definitions of a single named character in one file) - serching/highlighting more that one word
- if the user comes from google, parse the URL for
&q=somequeryand add?search=somequeryat the end of the new URL
