From f6d66d46845534da1b7677922193f24363f44003 Mon Sep 17 00:00:00 2001 From: "http://kerravonsen.dreamwidth.org/" Date: Thu, 3 Nov 2011 22:50:00 -0400 Subject: comment on the difficulty of trails --- doc/todo/Pagination_next_prev_links.mdwn | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/todo/Pagination_next_prev_links.mdwn b/doc/todo/Pagination_next_prev_links.mdwn index 8b3114340..f1c12d33f 100644 --- a/doc/todo/Pagination_next_prev_links.mdwn +++ b/doc/todo/Pagination_next_prev_links.mdwn @@ -27,4 +27,7 @@ Thank you > reduces the generic usefulness of typed links, though - in particular > you can no longer use "is part of trail A" in a PageSpec. --[[smcv]] +>>> Indeed, I know the problem; I ran into the same kind of thing with my [[plugins/contrib/report]] plugin and its `trail` concept. +>>> I simply had to declare that one couldn't use "trail" and "maketrail" options within the same report. That way, "maketrail" will add links in the "scan" pass, and "trail" will test for links in the "build" pass. That usually works. --[[KathrynAndersen]] + >> Do you have an example? --[[hendry]] -- cgit v1.2.3 From f2d322efee7f098eac9b38a0844995255a008df2 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmKvEhLuOASwaGDP803twCdJYPyXe6JQHY" Date: Fri, 4 Nov 2011 06:31:35 -0400 Subject: add comment. --- doc/bugs/UTF-16_and_UTF-32_are_unhandled.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/bugs/UTF-16_and_UTF-32_are_unhandled.mdwn b/doc/bugs/UTF-16_and_UTF-32_are_unhandled.mdwn index 21df334a8..9e8fba4b9 100644 --- a/doc/bugs/UTF-16_and_UTF-32_are_unhandled.mdwn +++ b/doc/bugs/UTF-16_and_UTF-32_are_unhandled.mdwn @@ -18,3 +18,12 @@ BOMless LE and BE input is probably a lost cause. Optimally, UTF-16 (which is ubiquitous in the Windows world) and UTF-32 should be fully supported, probably by converting to mostly-UTF-8 and using `&#xXXXX;` or `&#DDDDD;` XML escapes where necessary. Suboptimally, UTF-16 and UTF-32 should be converted to UTF-8 where cleanly possible and a warning printed where impossible. + +---- +Reading the wikipedia pages about [[!wikipedia UTF-8]] and [[!wikipedia UTF-16]], all valid Unicode characters are representable in UTF-8, UTF-16 and UTF-32, and the only errors possible with UTF-16/32 -> UTF-8 translation are when there are encoding errors in the original document. + +Of course, it's entirely possible that not all browsers support utf-8 correctly, and we might need to support the option of encoding into [[!wikipedia CESU-8]] instead, which has the side-effect of allowing the transcription of UTF-16 or UTF-32 encoding errors into the output byte-stream, rather than pedantically removing those bytes. + +An interesting question would be how to determine the character set of an arbitrary new file added to the repository, unless the repository itself handles character-encoding, in which case, we can just ask the repository to hand us a UTF-8 encoded version of the file. + +-- [[Martin Rudat|http://www.toraboka.com/~mrudat]] -- cgit v1.2.3 From d95dc2f8d175f5055d02dfb4009260cc9be22b6a Mon Sep 17 00:00:00 2001 From: "http://smcv.pseudorandom.co.uk/" Date: Fri, 4 Nov 2011 11:11:13 -0400 Subject: rename peteg.mdwn to users/peteg.mdwn --- doc/peteg.mdwn | 7 ------- doc/users/peteg.mdwn | 7 +++++++ 2 files changed, 7 insertions(+), 7 deletions(-) delete mode 100644 doc/peteg.mdwn create mode 100644 doc/users/peteg.mdwn diff --git a/doc/peteg.mdwn b/doc/peteg.mdwn deleted file mode 100644 index 4e2face0e..000000000 --- a/doc/peteg.mdwn +++ /dev/null @@ -1,7 +0,0 @@ -I'm adding some plugins to Ikiwiki to support a bioacoustic wiki. See here: - - - -Personal home page: - - diff --git a/doc/users/peteg.mdwn b/doc/users/peteg.mdwn new file mode 100644 index 000000000..4e2face0e --- /dev/null +++ b/doc/users/peteg.mdwn @@ -0,0 +1,7 @@ +I'm adding some plugins to Ikiwiki to support a bioacoustic wiki. See here: + + + +Personal home page: + + -- cgit v1.2.3 From b37ae9d604f68cce17bb274ae769ac7134ba2cf2 Mon Sep 17 00:00:00 2001 From: "http://smcv.pseudorandom.co.uk/" Date: Fri, 4 Nov 2011 11:11:14 -0400 Subject: update for rename of peteg.mdwn to users/peteg.mdwn --- doc/git.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/git.mdwn b/doc/git.mdwn index f4ed2c85b..eb3cc439b 100644 --- a/doc/git.mdwn +++ b/doc/git.mdwn @@ -59,7 +59,7 @@ think about merging them. This is recommended. :-) * [[davrieb|David_Riebenbauer]] `git://git.liegesta.at/git/ikiwiki` ([browse](http://git.liegesta.at/?p=ikiwiki.git;a=summary)) * [[GustafThorslund]] `http://gustaf.thorslund.org/src/ikiwiki.git` -* [[peteg]] `git://git.hcoop.net/git/peteg/ikiwiki.git` +* [[users/peteg]] `git://git.hcoop.net/git/peteg/ikiwiki.git` * [[privat]] `git://github.com/privat/ikiwiki.git` * [[blipvert]] `git://github.com/blipvert/ikiwiki.git` * [[bzed|BerndZeimetz]] `git://git.recluse.de/users/bzed/ikiwiki.git` -- cgit v1.2.3 From 06f5382faadad254c2387dd2a57ddfed0482ebaa Mon Sep 17 00:00:00 2001 From: "http://smcv.pseudorandom.co.uk/" Date: Fri, 4 Nov 2011 11:11:14 -0400 Subject: update for rename of peteg.mdwn to users/peteg.mdwn --- doc/todo/web_reversion.mdwn | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/todo/web_reversion.mdwn b/doc/todo/web_reversion.mdwn index 736d674fe..841fc3703 100644 --- a/doc/todo/web_reversion.mdwn +++ b/doc/todo/web_reversion.mdwn @@ -24,16 +24,16 @@ Implementation plan: and refresh site. Peter Gammie has done an initial implementation of the above. -[[!template id=gitbranch branch=peteg/revert author="[[peteg]]"]] +[[!template id=gitbranch branch=peteg/revert author="[[users/peteg]]"]] ->> It is on a separate branch now. --[[peteg]] +>> It is on a separate branch now. --[[users/peteg]] > Review: --[[Joey]] > > The revert commit will not currently say what web user did the revert. > This could be fixed by doing a --no-commit revert first and then using > rcs_commit_staged. ->> Fixed, I think. --[[peteg]] +>> Fixed, I think. --[[users/peteg]] > > So I see one thing I completly forgot about is `check_canedit`. Avoiding users > using reverting to make changes they would normally not be allowed to do is @@ -45,12 +45,12 @@ Peter Gammie has done an initial implementation of the above. > structure that `rcs_recieve` does. This could be done by using `git revert > --no-commit`, and then examining the changes, and then `git reset` to drop > them. ->> We can use the existing `git_commit_info` with the patch ID - no need to touch the working directory. -- [[peteg]] +>> We can use the existing `git_commit_info` with the patch ID - no need to touch the working directory. -- [[users/peteg]] > > Then the code that is currently in IkiWiki/Receive.pm, that calls > `check_canedit` and `check_canremove` to test the change, can be > straightforwardly refactored out, and used for checking reverts too. ->> Wow, that was easy. :-) -- [[peteg]] +>> Wow, that was easy. :-) -- [[users/peteg]] > > (The data from `rcs_preprevert` could also be used for a confirmation > prompt -- it doesn't currently include enough info for diffs, but at @@ -65,7 +65,7 @@ Peter Gammie has done an initial implementation of the above. >>> I agree, but have not figured out a way to make a hook work yet. >>> --[[Joey]] >> ->> Please look it over and tell me what else needs fixing... -- [[peteg]] +>> Please look it over and tell me what else needs fixing... -- [[users/peteg]] >>> I have made my own revert branch and put a few^Wseveral fixes in there. >>> All merged to master now! --[[Joey]] -- cgit v1.2.3 From 0d650d281059ed5b62a7f7bd3fb76db0e21eba6e Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawk_MMtLPS7osC5MjX00q2ATjvvXPWqm0ik" Date: Sat, 5 Nov 2011 05:35:41 -0400 Subject: Added a comment --- .../comment_1_332d32850c3dc0d45f5cc50434205f39._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/how_to_get_nice_pdf_from_ikiwiki_pages__63__/comment_1_332d32850c3dc0d45f5cc50434205f39._comment diff --git a/doc/forum/how_to_get_nice_pdf_from_ikiwiki_pages__63__/comment_1_332d32850c3dc0d45f5cc50434205f39._comment b/doc/forum/how_to_get_nice_pdf_from_ikiwiki_pages__63__/comment_1_332d32850c3dc0d45f5cc50434205f39._comment new file mode 100644 index 000000000..54f9f396b --- /dev/null +++ b/doc/forum/how_to_get_nice_pdf_from_ikiwiki_pages__63__/comment_1_332d32850c3dc0d45f5cc50434205f39._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawk_MMtLPS7osC5MjX00q2ATjvvXPWqm0ik" + nickname="micheal" + subject="comment 1" + date="2011-11-05T09:35:40Z" + content=""" +I have the same question. Any ideas? +"""]] -- cgit v1.2.3 From 7b324e8092359575a0c93626edcad373a883cdda Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawk_MMtLPS7osC5MjX00q2ATjvvXPWqm0ik" Date: Sat, 5 Nov 2011 05:39:44 -0400 Subject: pdf --- doc/todo/pdf_output.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/todo/pdf_output.mdwn diff --git a/doc/todo/pdf_output.mdwn b/doc/todo/pdf_output.mdwn new file mode 100644 index 000000000..7264d768b --- /dev/null +++ b/doc/todo/pdf_output.mdwn @@ -0,0 +1,3 @@ +Some time ago there was a [[question|http://ikiwiki.info/forum/how_to_get_nice_pdf_from_ikiwiki_pages__63__/?updated#comment-05381634f89629ad26298a1af4b1d5f9]] in the forum how to get a nice pdf output from an ikiwiki page. However there were no answers. So I put it on the todo list, because I think this would be a nice feature. + +Note that for example dokuwiki has a nice plugin which converts the wiki page to latex and then to pdf and you can customize the latex-preamble. -- cgit v1.2.3 From f808388c0b893584ebd8c7f4c035a2ca990d43fe Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawk_MMtLPS7osC5MjX00q2ATjvvXPWqm0ik" Date: Sat, 5 Nov 2011 05:45:39 -0400 Subject: --- doc/todo/pdf_output.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/todo/pdf_output.mdwn b/doc/todo/pdf_output.mdwn index 7264d768b..55a14d845 100644 --- a/doc/todo/pdf_output.mdwn +++ b/doc/todo/pdf_output.mdwn @@ -1,3 +1,3 @@ Some time ago there was a [[question|http://ikiwiki.info/forum/how_to_get_nice_pdf_from_ikiwiki_pages__63__/?updated#comment-05381634f89629ad26298a1af4b1d5f9]] in the forum how to get a nice pdf output from an ikiwiki page. However there were no answers. So I put it on the todo list, because I think this would be a nice feature. -Note that for example dokuwiki has a nice plugin which converts the wiki page to latex and then to pdf and you can customize the latex-preamble. +Note that for example dokuwiki has a [[nice plugin|http://danjer.doudouke.org/tech/dokutexit?do=backlink]] which converts the wiki page to latex and then to pdf and you can customize the latex-preamble. -- cgit v1.2.3 From f7d642421144388130ecd4ecd51e892ae8b3e1f6 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawk_MMtLPS7osC5MjX00q2ATjvvXPWqm0ik" Date: Sat, 5 Nov 2011 05:46:28 -0400 Subject: link --- doc/todo/pdf_output.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/todo/pdf_output.mdwn b/doc/todo/pdf_output.mdwn index 55a14d845..894c714ba 100644 --- a/doc/todo/pdf_output.mdwn +++ b/doc/todo/pdf_output.mdwn @@ -1,3 +1,3 @@ Some time ago there was a [[question|http://ikiwiki.info/forum/how_to_get_nice_pdf_from_ikiwiki_pages__63__/?updated#comment-05381634f89629ad26298a1af4b1d5f9]] in the forum how to get a nice pdf output from an ikiwiki page. However there were no answers. So I put it on the todo list, because I think this would be a nice feature. -Note that for example dokuwiki has a [[nice plugin|http://danjer.doudouke.org/tech/dokutexit?do=backlink]] which converts the wiki page to latex and then to pdf and you can customize the latex-preamble. +Note that for example dokuwiki has a [[nice plugin|http://danjer.doudouke.org/tech/dokutexit]] which converts the wiki page to latex and then to pdf and you can customize the latex-preamble. -- cgit v1.2.3