diff options
| -rw-r--r-- | sisu.org | 830 |
1 files changed, 830 insertions, 0 deletions
@@ -930,3 +930,833 @@ footnotes uses marker and endnote, check **** DONE make sure sisu works *** TODO [#C] refactor ruby :ongoing: + +** bugs :bug: + +*** misc, unclassified + +**** TODO [#B] sisu should give warning when part of minimal essential structure is missing :processing:fix: + +work through testing for as many of these as possible + +minimal content/structure requirement: +[metadata] + @title: + @creator: +[levels] + A~ (level A [title]) + 1~ (at least one level 1 [segment/(chapter)]) +test what happens in the absence of each + +structure rules (document heirarchy, heading levels): + + there are two sets of heading levels ABCD (title & parts if any) and 123 (segment & subsegments if any) + sisu has the fllowing levels: + + A~ [title] . required (== 1) followed by B~ or 1~ + B~ [part] * followed by C~ or 1~ + C~ [subpart] * followed by D~ or 1~ + D~ [subsubpart] * followed by 1~ + 1~ [segment (chapter)] + required (>= 1) followed by text or 2~ + text * followed by more text or 1~, 2~ or relevant part *(B~ if none other used; if C~ is last used: C~ or B~; if D~ is used: D~, C~ or B~) + 2~ [subsegment] * followed by text or 3~ + text * followed by more text or 1~, 2~ or 3~ or relevant part, see *() + 3~ [subsubsegment] * followed by text + text * followed by more text or 1~, 2~ or 3~ or relevant part, see *() + + * level A~ is the tile and is mandatory + * there can only be one level A~ + * heading levels BCD, are optional and there may be several of each + (where all three are used corresponding to e.g. Book Part Section) + * sublevels that are used must follow each other sequentially (alphabetically), + * heading levels A~ B~ C~ D~ are followed by other heading levels rather than substantive text + which may be the subsequent sequential (alphabetic) heading part level + or a heading (segment) level 1~ + * there must be at least one heading (segment) level 1~ + (the level on which the text is segmented, in a book would correspond to the Chapter level) + * additional heading levels 1~ 2~ 3~ are optional and there may be several of each + * heading levels 1~ 2~ 3~ are followed by text (which may be followed by the same heading level) + and/or the next lower numeric heading level (followed by text) + or indeed return to the relevant part level + (as a corollary to the rules above substantive text/ content + must be preceded by a level 1~ (2~ or 3~) heading) + +there must be a title, level A +creator field absent: crash, no warnings given +title missing: +level A missing: +no level 1: + +**** TODO [#B] victory chals discussed parsing problem caused by use of open-close markers around url + +**** TODO [#B] exclude heading where possible marker '-#' not distinguished from unnumbered heading '~#' + + * ~# is general & means no ocn (for any object to which it is applied) + * -# is relevant only for 1~ dummy headings & instructs that they should be + removed from output where possible + * where -# is used on any other objects, it is treated the same way as ~# + +**** TODO [#B] collapsed level work out logic where dummy lev1 heading + + * exclude heading where lev1 '-#' + * means subsequent headings & text belong to parent heading (of lev1 -#) 1 level up + * ponder + +*** DBT Outstanding bugs -- Normal bugs; Unclassified (2 bugs) :debian:dbt:normal: + <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=sisu> + +**** TODO [#B] #744360 [n|u] sisu: includes do not work properly :processing:fix: + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744360> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: includes do not work properly +Date: Sun, 13 Apr 2014 12:38:59 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +using this in foo.ssm: + + :A~ foo + + :B~ bar + + << bar/baz.ssi + +and this in baz.ssi: + + 1~ foo bar baz + +then everything works. + +using the more natural foo.ssm: + + :A~ foo + + << bar/baz.ssi + +and baz.ssi: + + :B~ bar + + 1~ foo bar baz + +makes ':B~ bar' being ignored in the output (pdf) entirely. + +Regards, +Daniel + +**** TODO [#B] #744378 [n|u] sisu: --no-manifest not working anymore + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744378> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: --no-manifest not working anymore +Date: Sun, 13 Apr 2014 16:12:13 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +when running sisu-pdf with --no-manifest, the output (pdf) still +contains the sisu manifest at the end of the document. + +Regards, +Daniel + +**** TODO ONGOING #746740 [n|u] manpages incomplete + +Date: Sat, 03 May 2014 08:45:49 +0200 +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +Subject: manpages incomplete +Package: sisu +Version: 5.3.4-1 +Tag: upstream +Severity: normal + +sisu supports options like --verbose or --no-manifest, but they are not +listed in the sisu manpage. + +**** TODO #746742 [n|u] please implement --no-metadata similar to --no-manifest + +Date: Sun, 13 Apr 2014 16:12:13 +0200 +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +Subject: --no-manifest not working anymore +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +when running sisu-pdf with --no-manifest, the output (pdf) still +contains the sisu manifest at the end of the document. + +Regards, +Daniel + +*** DBT Outstanding bugs -- Wishlist items; Unclassified (24 bugs) :debian:dbt:wishlist: + +**** TODO [#D] #744352 [w|u] sisu output: aligning margin numbers when using 'code' + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744352> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: 744352@bugs.debian.org +Subject: Re: sisu output: too many margin numbers +Date: Sun, 13 Apr 2014 17:27:10 +0200 +retitle 744352 sisu output: aligning margin numbers when using 'code' +severity 744352 wishlist +thanks + +sorry, i've looked wrongly at the output, the problem is simply an +aligning issue. it looks like that: + + foo bar. [1] + [2] + baz + + foo bar baz. [3] + +rather than: + + foo bar. [1] + + baz [2] + + foo bar baz. [3] + +Regards, +Daniel + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: too many margin numbers +Date: Sun, 13 Apr 2014 12:28:14 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +when using the following code: + +foo bar. + +code{ + + baz + +}code + +foo bar baz. + +the result in the output (pdf) is: + +foo bar. [1] + [2] +baz [3] + [4] +foo bar baz. [5] + +the '[n]' designates the margin number at the right site of the page. + +the problem is that sisu gives margin numbers to *empty* lines, which is +wrong. margin numbers should only be assigned to actual content. + +Regards, +Daniel + +**** TODO [#D] #744353 [w|u] sisu output: please do not use typewriter for urls + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744353> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: please do not use typewriter for urls +Date: Sun, 13 Apr 2014 12:28:27 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +when using urls in sisu like this: + + http://example.org + +sisu then creates in the output (pdf) links like this: + + <http://example.org> + +where as '<http://example.org>' is written in typewriter font +(monospace). please don't do that automagically since it's desturbing +the visual flow when reading. If the users wants that, he should be able +to configure it. + +Regards, +Daniel + +**** TODO [#C] #744354 [w|u] sisu output: please do not add '<' and '>' around urls + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: please do not add '<' and '>' around links +Date: Sun, 13 Apr 2014 12:28:37 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +when using urls in sisu like this: + + http://example.org + +sisu then creates in the output (pdf) links like this: + + <http://example.org> + +Please do not automagically add a '<' and '>' around urls. If the user +wants them, he would add one. + +Regards, +Daniel + +**** TODO [#C] #744355 [w|u] vim syntaxhighlighting: includes and directories + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744355> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: vim syntaxhighlighting: includes and directories +Date: Sun, 13 Apr 2014 12:28:46 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +When using includes like this: + + << foo.ssi + +then vim correctly displays the line in blue. + +However, when using includes in a subdirectory like this: + + << bar/foo.ssi + +then vim doesn't use any colors at all. + +Regards, +Daniel + +**** TODO [#C] #744356 [w|u] vim syntaxhighlighting: urls and tags + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744356> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: vim syntaxhighlighting: urls and tags +Date: Sun, 13 Apr 2014 12:28:56 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +When using an URL at the end of a sentence like this: + + Foo bar baz http://example.org. + +then vim properly highlights the url in blue. + +this also works properly when a second sentence after it, like: + + Foo bar baz http://example.org. Foo bar baz http://example.org. + +it works with html tag as well, like this: + + Foo bar baz http://example.org. <br />Foo bar baz http://example.org. + +but it doesn't work if there's no space: + + Foo bar baz http://example.org.<br />Foo bar baz http://example.org. + +then, the string 'http://www.gnu.org/licenses/.<' is shown red. + +Regards, +Daniel + +**** TODO [#C] #744357 [w|u] sisu output: please create mailto links automatically + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744357> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: please create mailto links automatically +Date: Sun, 13 Apr 2014 12:29:12 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +When using urls like: + + http://example.org + +in sisu, the output (pdf) contains a hyperlink to http://example.org +automatically, which is nice. + +please also create mailto links when using email adresses like: + + john.doe@example.org + +Regards, +Daniel + +**** TODO [#C] #744358 [w|u] sisu output: please do not add ';' after \:copyright: + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744358> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: please do not add ';' after :copyright: +Date: Sun, 13 Apr 2014 12:29:20 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +When using: + + :copyright: foo bar baz. + +sisu generates the following in the output format (pdf): + + foo bar baz.; + +Please do not automagically add a semicolon (;). If the user wants a +semicolon, he would add one. + +Regards, +Daniel + +**** TODO [#B] #744379 [w|u] sisu: missing includes doesn't give an error + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744379> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: missing includes doesn't give an error +Date: Sun, 13 Apr 2014 16:14:46 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +When using includes (*.ssi) in a sisu master document (*.ssm) like: + + << foo.ssi + +and that to be included file foo.ssi (for whatever reason) doesn't +exist, sisu doesn't error out but include '<< foo.ssi' literally as a +string in the output (pdf). + +Regards, +Daniel + +**** TODO [#D] #744381 [w|u] sisu syntax: inconsistency \:copyright: and \:license: + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744381https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744381> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: inconsistency between :copyright: and :license: +Date: Sun, 13 Apr 2014 16:26:55 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +when using ':copyright: foo', then the output contains 'foo'. + +when using ':license: foo', then the output contains 'License: foo'. + +this is inconsistent. either both should have a 'prefix' in the output, +or neither should have one (i'd prefere the latter). + +Regards, +Daniel + +**** TODO [#B] #744383 [w|u] sisu syntax: :B and :C result in the same formatting + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744383> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu syntax: :B and :C result in the same formatting +Date: Sun, 13 Apr 2014 16:32:07 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +when using :A, :B, and :C in sisu, in the output (pdf) both :B and :C +are formatted identically. + +imho :C should be 'smaller' than :B. + +or, as an analogy with html: i would expect that :A equals <h1>, :B +equals <h2>, and :C equals <h3>. currently, (in that analogy), :B and :C +both equal <h2>. + +Regards, +Daniel + +**** TODO [#C] #744384 [w|u] sisu syntax: relies on empty lines + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744384> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu syntax: relies on empty lines +Date: Sun, 13 Apr 2014 16:34:46 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +the following snipped: + + :C~ foo bar + << foo-bar.ssi + +means that the include is ignored entirely. apparently sisu relies on +having an empty line in between like this: + + :C~ foo bar + + << foo-bar.ssi + +Regards, +Daniel + +**** TODO [#B] #744386 [w|u] sisu syntax: 1~ and 2~ result in the same formatting + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744386> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu syntax: 1~ and 2~ result in the same formatting +Date: Sun, 13 Apr 2014 16:43:51 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +similar as with #744383, the same also applies for 1~ and 2~ - they +should be different in the output format (pdf here). + +Regards, +Daniel + +**** TODO [#B] #744390 [w|u] sisu: empty sections are ignored + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744390> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu: empty sections are ignored +Date: Sun, 13 Apr 2014 17:09:32 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist + +if you have the following sisu syntax: + + :B~ foo + + 1~ foo1 + + foo1. + + 1~ foo2 + + foo2. + + :B~ bar + + 1~ bar1 + + 1~ bar2 + + :B~ baz + + 1~ baz1 + + 1~ baz2 + +then anything (including and) after ':B~ bar' is ignored entirely. + +**** TODO [#C] #744391 [w|u] sisu output: no color on a4 portrait + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744391> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu output: please use (blue) color for links +Date: Sun, 13 Apr 2014 17:23:37 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +it would be nice if links (urls and emails) would be colored blue to +mark them visually as links. this behaviour is somewhat the lowest +common denominator in browsers (if you use html without any css that is). + +Regards, +Daniel + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: 744391@bugs.debian.org +Subject: Re: sisu output: please use (blue) color for links +Date: Sun, 13 Apr 2014 17:35:33 +0200 +retitle 744391 sisu output: no color on a4 portrait +thanks + +now this is strange.. turns out that (yes, i have colors enabled in +sisurc) the portrait a4 pdf has no colors at all, while the landscape a4 +pdf does indeed have colors (red for toc, blue for links). + +Regards, +Daniel + +**** TODO [#D] #744395 [w|u] sisu output: half-page title page in landscape output + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744395> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu output: half-page title page in landscape output +Date: Sun, 13 Apr 2014 17:38:03 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +in a4 landscape output, there's always two pages on one page, which is +nice; except for the title page which spans over the whole page. + +it would be nice if the first page would be consistent to the same +scheme like the rest of the document - spanning only over the half of +the page. + +Regards, +Daniel + +**** TODO [#C] #744396 [w|u] sisu output: "european" toc indenting + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744396> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu output: "european" toc indenting +Date: Sun, 13 Apr 2014 17:40:53 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +by default, latex uses the following indenting in the TOC: + + 1. foo + 1.1 bar1 + 1.1.1 baz + 1.2 bar2 + +there's a latex option that i don't remember off-hand to have the +indenting like it's common in europe: + + 1. foo + 1.1 bar1 + 1.1.1 baz + 1.2 bar2 + +it would be nice if sisu could let the used decide which indenting style +to use for TOCs. + +Regards, +Daniel + +**** TODO [#B] #744399 [w|u] sisu syntax: :A smaller formatted than :B + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744399> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu syntax: :A smaller formatted than :B +Date: Sun, 13 Apr 2014 17:49:26 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +in a document like this: + +:A~ foo + +:B~ bar + +the :A~ 'title' is formated 'smaller' (not bold, smaller font size) than +the :B~ 'title' on the first page of the actual document (means, first +page after TOC). + +Regards, +Daniel + +**** TODO [#C] #744402 [w|u] sisu: support sha512 + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744402> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu: support sha512 +Date: Sun, 13 Apr 2014 18:06:56 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +sisu uses sha256 when using sha as digest, please support sha512. + +it would be even nicer if you could specify the actual digest like +'sha512', 'sha256', etc. rather than just 'sha'. + +Regards, +Daniel + +**** TODO [#C] #744405 [w|u] sisu: set default font size + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744405> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu: set default font size +Date: Sun, 13 Apr 2014 18:29:46 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +in sisurc, one can set the default fonts. it would be nice to be also +able to set the default font size. + +Regards, +Daniel + +**** TODO [#C] #744407 [w|u] sisu: possibility to influence content/formating of the title page + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744407> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu: possibility to influence content/formating of the title page +Date: Sun, 13 Apr 2014 18:32:14 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +by default, the title page (in the pdf output) shows @title and @creator. + +it would be nice if there would be a possibility to influence the +formatting (e.g. to have the title written in bold), and to have +additional possibilities to influence the content on the title page +(like the date or version, an url, or other text strings). + +Regards, +Daniel + +**** TODO [#C] #744408 [w|u] sisu: support more than one level of includes/nested includes + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744408> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu: support more than one level of includes/nested includes +Date: Sun, 13 Apr 2014 18:39:23 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +currently, it's possible to use only one ssm file which itself includes +one or more ssi files. + +it would be nice if the ssm could include an 'intermediate' ssi, which +then includes further ssi files. this is very handy for larger documents. + +Regards, +Daniel + +**** TODO [#C] #744409 [w|u] sisu output: urls in code blocks are not linkified + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744409> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu output: urls in code blocks are not linkified +Date: Sun, 13 Apr 2014 18:41:09 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +it would be nice if urls written withiin code{...}code blocks would also +be automatically transformed into a link within the output (html). + +Regards, +Daniel + +**** TODO [#C] #744541 [w|u] sisu: urls in @creator broken + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744541> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu: urls in @creator broken +Date: Sun, 13 Apr 2014 18:45:35 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +first, if you have an url within @creator, like: + + @creator: foo bar http://example.org + +the generation fails (pdf output). + +as a workaround, i put the url into parenthesis, like: + + @creator: foo bar (http://example.org) + +but then, it would be nice if that url would be automatically +transformed into a link in the output format (pdf). + +Regards, +Daniel + +**** TODO [#C] #744685 [w|u] sisu output: copy&past-able wrapped code blocks + <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744685> + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu output: copy&past-able wrapped code blocks +Date: Sun, 13 Apr 2014 19:04:01 +0200 +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +if a line within a 'code{...}code' block is longer and needs to be +wrapped, sisu indicates the wrapping with an 'arrow' (←) symbol, which +is nice. + +it would be even nicer if the arrow would not 'selectable', so that when +you mark the line spanning over two lines with your mouse, the arrow is +not selected and thus not copy&pasted. + +i don't know how to do this, but it's possible within pdfs, as can be +seen in lots of pdfs in the internet. + +Regards, +Daniel + +**** TODO [#C] #744734 [w|u] sisu output: replace all occurences of (C) rather than the first only + +From: Daniel Baumann <daniel.baumann@progress-technologies.net> +To: Debian Bug Tracking System <submit@bugs.debian.org> +Subject: sisu output: replace all occurences of (C) rather than the first only +Date: Mon, 14 Apr 2014 06:11:13 +0200 + +Package: sisu +Version: 5.3.4-1 +Severity: wishlist +Tags: upstream + +if you have a '(C)' in :copyright:, it is automatically replaced with a +copyright symbol, which is nice, however, it sisu does that with the +first occurence only. + +so if you use: + + :copyright: (C) john doe<br />(C) jane doe + +then the second occurence is not replaced and that combination looks +very ugly. i suggest you replace all occurences of '(C)' to the +copyright symbol automatically. + +Regards, +Daniel |