summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Minimal documentation of all the new paper backend \cfg{} directives.Jacob Nevins2004-06-20
| | | | | | | | | Contains many FIXMEs, both for incomplete documentation and incomplete code. Couple of other minor tweaks elsewhere. [originally from svn r4304]
* We seem to have ended up with duplicate documentation of --man. Gone.Jacob Nevins2004-06-19
| | | | [originally from svn r4303]
* Ensure that every \cfg{} directive documented so far has appropriate \IMJacob Nevins2004-06-19
| | | | | | directives. [originally from svn r4302]
* Fairly wholesale reorganisation of the \cfg{} documentation for the text,Jacob Nevins2004-06-19
| | | | | | | | WinHelp, man, and info backends, and organisation into sections (now that we have rather more directives documented). I've not changed the actual text much if at all. [originally from svn r4301]
* In the text backend, multiple characters can now be used for underlining.Jacob Nevins2004-06-19
| | | | [originally from svn r4300]
* The Unicode OVERLINE in the text backend documentation was probably supposedJacob Nevins2004-06-19
| | | | | | to be quoted. [originally from svn r4299]
* Note that \cfg{quotes} and friends apply to the output in its entirety andJacob Nevins2004-06-19
| | | | | | can't be changed partway through. Also, add a cross-reference from \q{}. [originally from svn r4298]
* Note that no index is generated by the text backend.Jacob Nevins2004-06-19
| | | | [originally from svn r4297]
* Minor correction to --ps and --pdf descriptions.Jacob Nevins2004-06-19
| | | | [originally from svn r4296]
* Initial rough documentation of some of the newer \cfg{} directives, namely:Jacob Nevins2004-06-19
| | | | | | | | | | | | - \cfg{quotes} - text, info, man, and winhelp backends: - charset - quotes and bullets - various WinHelp miscellanea Could stand some rearrangement and expansion, plus I've yet to address the paper or HTML backends. [originally from svn r4295]
* Moderately nasty workaround for the fact that Windows Help's indexSimon Tatham2004-06-19
| | | | | | | | | mechanism is case-insensitive with respect to sorting the list of index entries. We now append nonbreaking spaces to the ends of some index terms to ensure they are considered distinct. (Nasty, but it seems to work.) [originally from svn r4294]
* Add a batch of assertions to ensure no more index terms fail to haveSimon Tatham2004-06-19
| | | | | | | | | their anchors generated. Index bugs of this type can be terribly subtle and go unnoticed for ages; I'm lucky Jacob spotted the first one of the type, but I'm now going to be careful to avoid any further ones. [originally from svn r4293]
* I had somehow managed to leave index entry anchors out of sectionSimon Tatham2004-06-19
| | | | | | titles. Ahem. [originally from svn r4292]
* Add a clash-checking mechanism to ensure we never generate the sameSimon Tatham2004-06-19
| | | | | | fragment name twice for any reason. [originally from svn r4291]
* Support \I\c, \I\cw. (Haven't bothered with \I\e since the emphasis may asJacob Nevins2004-06-19
| | | | | | well outweigh the "invisibility".) [originally from svn r4290]
* s/text-quotes/man-quotes/. Damn cut and paste. Thanks Jacob.Simon Tatham2004-06-16
| | | | [originally from svn r4288]
* The Halibut manual contained at least one instance of two indexSimon Tatham2004-06-13
| | | | | | | | | | | | | | terms (intentionally) differing only in case, which were being silently folded into one by the case-insensitive index tag comparison. Halibut now warns in this situation (but then folds them anyway, which I think is better than silently generating an index containing many case-distinct forms of the same word - I imagine it's very easy to do that by mistake). The manual has been fixed to explicitly define distinct keywords (in the case I spotted and in five other cases picked up by the new warning!), and also documents this issue and how to work with it. [originally from svn r4279]
* Er, don't forget to document the disallowing of \q within \c. Ahem.Simon Tatham2004-06-12
| | | | [originally from svn r4278]
* Enforce that \q may not be used anywhere within \c. It shouldn't beSimon Tatham2004-06-12
| | | | | | | | | | | | | necessary since the whole point of \c should be that the user wants to exercise exact control over the glyphs used, and forbidding it has the useful effect of relieving some backends of having to make difficult decisions: it means the text backend doesn't have to nest two pairs of identical quotes, and the paper backends don't have to downgrade their quote characters if (as is perfectly plausible) the fixed-pitch font doesn't support the same range as the body text fonts. [originally from svn r4277]
* Switch the memory allocation macros from the Halibut onesSimon Tatham2004-06-12
| | | | | | | | | | | | | (mknew/mknewa/resize) to the PuTTY ones (snew/snewn/sresize). snewn and mknewa have their arguments opposite ways round; this may make the change initially painful but in the long term will free me of a nasty context switch every time I move between codebases. Also sresize takes an explicit type operand which is used to cast the return value from realloc, thus enforcing that it must be correct, and arranging that if anyone tries to compile Halibut with a C++ compiler there should be a lot less pain. [originally from svn r4276]
* Initial checkin of the shiny new rewritten-from-scratch HTML backSimon Tatham2004-06-12
| | | | | | | | | | | | | | | | | | end. There's a lot more _potentiality_ for new features than there are actual new features just yet, but future highlights include: configurable flavour of HTML (3.2, 4, XHTML Transitional or Strict), proper character set support (this is half way there already), and more flexible allocation of sections between multiple HTML files. Meanwhile, immediate benefits include correct handling of special characters within `author' and `description' strings, omission of the filename part in hyperlinks within the same HTML file (in particular, this means a single output file is now totally independent of its filename), and hyperlinks to the index from the top-level contents page (I'm amazed nobody has complained at the lack of this yet!). There are no doubt some shiny new bugs as well, but I'll never find them unless people start using the thing... [originally from svn r4275]
* Preferred MIME name for ASCII is "US-ASCII", not "ANSI_X3.4-1968". Oops.Simon Tatham2004-06-03
| | | | | [originally from svn r4269] [this svn revision also touched charset,filter,timber]
* rjk's `make install' patch.Simon Tatham2004-06-02
| | | | [originally from svn r4267]
* Stop the PDF backend from crashing if no outline elements appear. ItSimon Tatham2004-05-23
| | | | | | | still doesn't _work_ properly if there aren't any contents entries, but it's a start. [originally from svn r4250]
* All measurements in the paper backend are now configurable, as areSimon Tatham2004-05-23
| | | | | | bullet and quote characters. [originally from svn r4249]
* Character-set-isation and configurability in the WinHelp backend.Simon Tatham2004-05-23
| | | | | | | | | Newly configurable things are: bullet and quote characters as usual, the ": " that goes between a section number and its title, the "." coming after numbered-list item numbers, and the text "Title page" that appears at the top of the .cnt file. [originally from svn r4248]
* Configurable bullet and quote characters for the man backend.Simon Tatham2004-05-23
| | | | [originally from svn r4247]
* Kurt Jung points out that nav menus ought to be WHLP_PARA_SCROLL,Simon Tatham2004-05-16
| | | | | | not _NONSCROLL. [originally from svn r4228]
* para_Title was confusing the XHTML backend and preventing it fromSimon Tatham2004-05-04
| | | | | | printing preambles. Not quite sure how I missed that one! [originally from svn r4201]
* Windows Help backend was only accepting \cfg{winhelp-filename} if itSimon Tatham2004-05-03
| | | | | | | | | had a parent pointer (owing to putting the test inside the wrong if block). This meant that the fake config directive added by --winhelp=foo.hlp worked fine, but the one at the top of PuTTY's first doc file didn't. Fixed. [originally from svn r4190]
* Handle paragraph comments with no space (e.g. "\#waffle"), since these seemJacob Nevins2004-04-28
| | | | | | to be permitted (and are used in the PuTTY manual) [originally from svn r4164]
* General configurability upgrade for the info back end.Simon Tatham2004-04-23
| | | | [originally from svn r4131]
* Ahem; that only didn't cause a segfault by sheer luck.Simon Tatham2004-04-23
| | | | [originally from svn r4130]
* Oh, and now the text backend warns about too-long code lines, I'dSimon Tatham2004-04-23
| | | | | | better remove the one too-long code line in the manual :-) [originally from svn r4129]
* Enhance the text backend to support configurable quote characters,Simon Tatham2004-04-23
| | | | | | | | | | | configurable emphasis characters, various other configurable bits which have been marked FIXME in the code for a while, and also to warn when a code paragraph line is too long (because that was the only other thing labelled FIXME). Fallback options are implemented, and defaults set accordingly. A UTF-8 text output file now looks like proper UTF-8. [originally from svn r4128]
* Rewrite ustrftime(), so that (a) it uses wcsftime() where available,Simon Tatham2004-04-22
| | | | | | | and (b) it doesn't trip over strange Unicode characters in the format string. [originally from svn r4120]
* Use wcscoll(), if available, when sorting index terms. (In aSimon Tatham2004-04-22
| | | | | | | | somewhat roundabout and arse-backwards sort of way, due to some other properties of the sort that I rather wanted to maintain. But I hope it should still do some good.) [originally from svn r4119]
* Use iswalpha and towlower if they're available.Simon Tatham2004-04-22
| | | | [originally from svn r4118]
* Instead of traversing a list of paragraphs, mark_attr_ends() nowSimon Tatham2004-04-22
| | | | | | | | | merely traverses a list of words, and main() takes responsibility for applying it to each paragraph in the document. This is so that it can _also_ be applied to the display form of each index entry, which Jacob spotted wasn't previously being done. [originally from svn r4117]
* bk_text and bk_info both need to know the on-screen width ofSimon Tatham2004-04-22
| | | | | | | | | | | | characters in order to wrap and align them properly. Therefore, they should be using wcwidth(). So here are a couple of wrappers on wcwidth(), one which filters out the Unicode characters not representable in the target charset, and one which converts _from_ a charset to Unicode before calling wcwidth(). bk_text and bk_info should now align correctly even in the face of unsupported characters and Japanese. [originally from svn r4116]
* Add charset_from_locale(), a best-effort attempt to return theSimon Tatham2004-04-22
| | | | | | | | libcharset CS_* identifier for the character set indicated by the active locale. Uses code from Markus Kuhn's website. [originally from svn r4115] [this svn revision also touched charset,timber]
* Support the locale-supplied character set where appropriate. It'sSimon Tatham2004-04-22
| | | | | | | | | | used for converting command-line -C directives into Unicode; it's used for outputting Unicode strings to stderr in error messages; and it's used as the default character set for input files (although I'd be inclined to recommend everyone use \cfg{input-charset} in all their source files to ensure their portability). [originally from svn r4114]
* Charset support for the man page backend (\cfg{man-charset}).Simon Tatham2004-04-21
| | | | [originally from svn r4112]
* Charset support for the info backend (\cfg{info-charset}). (ThisSimon Tatham2004-04-21
| | | | | | | checkin touches other files because a function in bk_text.c turned out to be of more general use so I moved it out into ustring.c.) [originally from svn r4111]
* I typed `Win1252' today and libcharset didn't recognise it. Fixed.Simon Tatham2004-04-20
| | | | | [originally from svn r4107] [this svn revision also touched charset,timber]
* Don't forget to mention the default setting for \cfg{input-charset}.Simon Tatham2004-04-20
| | | | [originally from svn r4106]
* Acroread's PDF cut and paste appears to depend on the order in whichSimon Tatham2004-04-20
| | | | | | | | text fragments appear in the page graphics stream. Therefore, I should take care to display the leaders _before_ the page number in each contents entry. [originally from svn r4105]
* Add some tests of Unicode in the PDF document outline.Simon Tatham2004-04-20
| | | | [originally from svn r4104]
* Ahem. Fix stupid string handling error in new command-line configSimon Tatham2004-04-20
| | | | | | mechanism. [originally from svn r4103]
* The Windows Help backend now uses libcharset to the maximum extentSimon Tatham2004-04-20
| | | | | | | | | | it can. (Which isn't much, since I currently don't know how to indicate that a help file is encoded in anything other than Win1252, and so the only use I found for libcharset was to replace the previous pathetic 8859-1 conversion so that extra things like the trademark sign are supported.) [originally from svn r4102]
generated by cgit v1.1 at 2026-04-26 14:26:12 +0000