You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(103) |
Jul
(105) |
Aug
(16) |
Sep
(16) |
Oct
(78) |
Nov
(36) |
Dec
(58) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(100) |
Feb
(155) |
Mar
(84) |
Apr
(33) |
May
(22) |
Jun
(77) |
Jul
(36) |
Aug
(37) |
Sep
(183) |
Oct
(74) |
Nov
(235) |
Dec
(165) |
2002 |
Jan
(187) |
Feb
(183) |
Mar
(52) |
Apr
(10) |
May
(15) |
Jun
(19) |
Jul
(43) |
Aug
(90) |
Sep
(144) |
Oct
(144) |
Nov
(171) |
Dec
(78) |
2003 |
Jan
(113) |
Feb
(99) |
Mar
(80) |
Apr
(44) |
May
(35) |
Jun
(32) |
Jul
(34) |
Aug
(34) |
Sep
(30) |
Oct
(57) |
Nov
(97) |
Dec
(139) |
2004 |
Jan
(132) |
Feb
(223) |
Mar
(300) |
Apr
(221) |
May
(171) |
Jun
(286) |
Jul
(188) |
Aug
(107) |
Sep
(97) |
Oct
(106) |
Nov
(139) |
Dec
(125) |
2005 |
Jan
(200) |
Feb
(116) |
Mar
(68) |
Apr
(158) |
May
(70) |
Jun
(80) |
Jul
(55) |
Aug
(52) |
Sep
(92) |
Oct
(141) |
Nov
(86) |
Dec
(41) |
2006 |
Jan
(35) |
Feb
(62) |
Mar
(59) |
Apr
(52) |
May
(51) |
Jun
(61) |
Jul
(30) |
Aug
(36) |
Sep
(12) |
Oct
(4) |
Nov
(22) |
Dec
(34) |
2007 |
Jan
(49) |
Feb
(19) |
Mar
(37) |
Apr
(16) |
May
(9) |
Jun
(38) |
Jul
(17) |
Aug
(31) |
Sep
(16) |
Oct
(34) |
Nov
(4) |
Dec
(8) |
2008 |
Jan
(8) |
Feb
(16) |
Mar
(14) |
Apr
(6) |
May
(4) |
Jun
(5) |
Jul
(9) |
Aug
(36) |
Sep
(6) |
Oct
(3) |
Nov
(3) |
Dec
(3) |
2009 |
Jan
(14) |
Feb
(2) |
Mar
(7) |
Apr
(16) |
May
(2) |
Jun
(10) |
Jul
(1) |
Aug
(10) |
Sep
(11) |
Oct
(4) |
Nov
(2) |
Dec
|
2010 |
Jan
(1) |
Feb
|
Mar
(13) |
Apr
(11) |
May
(18) |
Jun
(44) |
Jul
(7) |
Aug
(2) |
Sep
(14) |
Oct
|
Nov
(6) |
Dec
|
2011 |
Jan
(2) |
Feb
(6) |
Mar
(3) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(11) |
Feb
(3) |
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(8) |
Dec
(1) |
2015 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2016 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
(11) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
(3) |
2024 |
Jan
(7) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Steve W. <sw...@pa...> - 2001-12-12 21:23:24
|
Looks good: http://phpwiki.sourceforge.net/alpha/index.php/RecentChanges?format=rss --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: <ph...@de...> - 2001-12-11 18:27:28
|
On Tue, 11 Dec 2001 11:19:33 -0500 (EST), Steve Wainstead <sw...@pa...> wrote: => On Tue, 11 Dec 2001, Jeff Dairiki wrote: => > Other than having three French translations under way, are we currently => > having coordination problems? => Just me remembering who is doing what :-) And the rest of us, non-developers, chomping at the bit while awaiting a stable or released 1.3.x version ... <grin> Thanks for all your efforts, it's a great package! Cheers, - Don |
From: Steve W. <sw...@pa...> - 2001-12-11 16:37:33
|
thx! ~swain On Tue, 11 Dec 2001, Jeff Dairiki wrote: > On Tue, 11 Dec 2001 02:21:10 -0500 (EST) > "Steve Wainstead" <sw...@pa...> wrote: > > > Could you email me with the things you are currently working on > > See http://phpwiki.sf.net/wiki/JeffsToDoList for a list of things I'm (at > least thinking about) working on. > > Also, I've just visited the SF bugs and tasks lists and have (un-)signed > up for those bugs/tasks that I plan on working on... > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Jeff D. <da...@da...> - 2001-12-11 16:33:22
|
On Tue, 11 Dec 2001 02:21:10 -0500 (EST) "Steve Wainstead" <sw...@pa...> wrote: > Could you email me with the things you are currently working on See http://phpwiki.sf.net/wiki/JeffsToDoList for a list of things I'm (at least thinking about) working on. Also, I've just visited the SF bugs and tasks lists and have (un-)signed up for those bugs/tasks that I plan on working on... |
From: Steve W. <sw...@pa...> - 2001-12-11 16:20:35
|
On Tue, 11 Dec 2001, Jeff Dairiki wrote: > Other than having three French translations under way, are we currently > having coordination problems? Just me remembering who is doing what :-) ~swain --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Jeff D. <da...@da...> - 2001-12-11 15:07:51
|
On Tue, 11 Dec 2001 02:21:10 -0500 (EST) "Steve Wainstead" <sw...@pa...> wrote: > > Could you email me with the things you are currently working on, so I can > update the task list? I don't want any duplication of effort, and you can > check to see if something you want/need is being worked on. > > ~swain Maybe we should start a ProjectsUnderway (bad name, but can't think of a better one right now --- maybe ActiveProjects) page on the wiki where people could give brief listings of things they are currently working on (along with requests for things like "don't touch the CVS for a couple hours while I refactor the file names"...) The SF tasklist is good for a more permanent record, but it's hard to keep track of on a daily (or hourly) basis. Other than having three French translations under way, are we currently having coordination problems? |
From: Lawrence A. <la...@us...> - 2001-12-11 10:47:27
|
Reply-all sends a copy to the sender, and a copy to the list. The result is that the sender gets two copies of each message. If you can set it to reply to list, the sender (who is presumably subscribed) will receive just one copy - as Nature intended. Also, is there a way to search the archive? Lawrence At 07:17 11/12/2001, Steve Wainstead wrote: >Gagh. Still trying to keep up with the list volume... so...: > >On Thu, 22 Nov 2001, Reini Urban wrote: > > > BTW: Steve, cannot this list be managed to reply to list per default > > and not reply to poster. seems to be mailman. > >I set it to the recommended default, which is reply to user, and in Pine I >always get the question "Reply to all?" and I just choose that. Have you >accidentally replied only to the sender? > >~swain |
From: Steve W. <sw...@pa...> - 2001-12-11 07:21:14
|
Could you email me with the things you are currently working on, so I can update the task list? I don't want any duplication of effort, and you can check to see if something you want/need is being worked on. ~swain --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Steve W. <sw...@pa...> - 2001-12-11 07:17:43
|
Gagh. Still trying to keep up with the list volume... so...: On Thu, 22 Nov 2001, Reini Urban wrote: > BTW: Steve, cannot this list be managed to reply to list per default > and not reply to poster. seems to be mailman. I set it to the recommended default, which is reply to user, and in Pine I always get the question "Reply to all?" and I just choose that. Have you accidentally replied only to the sender? ~swain --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Steve W. <sw...@pa...> - 2001-12-11 07:13:54
|
On Mon, 10 Dec 2001, Jeb Bateman wrote: > I had some ideas on supporting different patterns for wiki, based on > experience I had long ago creating something called the 'patterns > plugin' for a web authoring enviornment I don't use anymore... > http://ocha.net/plugins/patterns/ > > Anyway, the idea of that code was very similar to wiki, in that you > use simple shorthand markup to write html. The main difference was > that users had the ability to create their own patterns, based on the > needs of their specific page or website. > > I was thinking something similar could be done for wiki, to support > multiple "sets" of patterns, via a popup menu in the EditText page, or > individual patterns via checkboxes. Of course, the drawback to this > type of flexability is the possibility that pages could be broken by a > change in pattern selection, for example. There might also be ways to > work around that problem. Anyway, just a thought I've been meaning to > share, and I might have time to work on in the future... > Hmm. I guess in an ideal world, the default markup the user sees is the one we feel is easiest to understand; but in user options, they could choose any markup scheme they like (those of other wikis, or limited html, or roll their own.) This would, again, require storing the page content in some intermediate format, like xml, and converting to the user-chosen markup whenever they decide to edit a page. Just thinking out loud. ~swain > > On Fri, Dec 07, 2001 at 12:14:53AM -0500, Steve Wainstead wrote: > > > > I'd like to move (again) to a syntax like the NBTSC Wiki, which is in line > > with suggestions by many users over the last two years. Ali went for > > syntax that is a lot like how people do things in plain text elsewhere: > > > > *bold* > > /italic/ > > > > I think are two examples. Ali's reasoning was the marked up page language > > should be as easy to read/understand as the rendered page. > > > > Now, the one thing that has troubled me about both the plugin syntax and > > the proposed plain text tags is they are not consistent with the markup to > > date... and inconsistency is not good for the user. As PhpWiki grows in > > features, though, I understand it gets harder to maintain consistency. > > > > I'd like to see some proposals that are consistent with our current > > syntax, or some way that would be compatible with NBTSC syntax. > > > > ~swain > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Steve W. <sw...@pa...> - 2001-12-11 06:48:55
|
On a side note, Sourceforge is apparently going to move away from Geocrawler, which IMO is an awful mail archiver anyway. PhpWiki could do it better, given infinite programmer time, hardware resources and caffeine ;-) ~swain On Sat, 8 Dec 2001, Jeff Dairiki wrote: > On Sat, 8 Dec 2001 15:38:41 -0000 > "Lawrence Akka" <Law...@th...> wrote: > > > Could we add phpwiki-talk: > > http://www.geocrawler.com/archives/3/4037/2001/ > > > > to the interwiki map, to allow quick references to this list > > > > eg http://www.geocrawler.com/archives/3/4037/2001/12/0/7271426/ > > Interestingly, when referring to a specific post, only the last of those > numbers in the URL seems to matter. > > e.g. http://www.geocrawler.com/archives/1/1/1/1/1/7271426 works fine. > > So adding > phpwiki-talk http://www.geocrawler.com/archives/1/1/1/1/1/ > to interwiki.map would allow phpwiki-talk:7271426. (However, perhaps a > better moniker would be 'Geocrawler'.) > > I'm not sure that's a good idea though. Most "InterWiki" links make sense > on their own. Consider 'Wiki:RecentChanges' and 'RFC:822'. The text > itself makes a good title for the link --- one can tell from the text > alone what the link (is supposed to) points to. The number in > phpwiki-talk:7271426 is pretty much an arbitrary quasi-random number. I > guess I don't see the advantage of making it an interwiki link over just > > See [this post| http://www.geocrawler.com/...] on phpwiki-talk. > > Interwiki link makes for less typing, but it seems you pretty much have to > cut-and-paste to get that message number, you might as well cut-and-paste > the whole URL. > > On a related note, I also suspect the Geocrawler reindexes their archives > periodically (thus breaking all these links.) I'm pretty sure I remember > this having happened in the past. > > That's my two cents worth, at least. > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Steve W. <sw...@pa...> - 2001-12-11 06:45:35
|
No objection from me... ~swain On Mon, 10 Dec 2001, Carsten Klapp wrote: > Hi, > > Does anyone mind if I move this from phpwiki.css into phpwiki-heavy.css? > It doesn't render properly in my primary browser (OmniWeb 4), it looks > pretty ugly in Nescape 4 too. > > /* This renders the ? invisible in OW4 */ > .wikiunknown A, .named-wikiunknown > { color: white; background-color: #600; } > > Carsten > > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > --- http://www.panix.com/~swain/ "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." -- Frank Zappa |
From: Carsten K. <car...@ma...> - 2001-12-11 04:59:08
|
Hi, Does anyone mind if I move this from phpwiki.css into phpwiki-heavy.css? It doesn't render properly in my primary browser (OmniWeb 4), it looks pretty ugly in Nescape 4 too. /* This renders the ? invisible in OW4 */ .wikiunknown A, .named-wikiunknown { color: white; background-color: #600; } Carsten |
From: Jeb B. <je...@oc...> - 2001-12-10 18:09:30
|
I had some ideas on supporting different patterns for wiki, based on experience I had long ago creating something called the 'patterns plugin' for a web authoring enviornment I don't use anymore... http://ocha.net/plugins/patterns/ Anyway, the idea of that code was very similar to wiki, in that you use simple shorthand markup to write html. The main difference was that users had the ability to create their own patterns, based on the needs of their specific page or website. I was thinking something similar could be done for wiki, to support multiple "sets" of patterns, via a popup menu in the EditText page, or individual patterns via checkboxes. Of course, the drawback to this type of flexability is the possibility that pages could be broken by a change in pattern selection, for example. There might also be ways to work around that problem. Anyway, just a thought I've been meaning to share, and I might have time to work on in the future... -jeb On Fri, Dec 07, 2001 at 12:14:53AM -0500, Steve Wainstead wrote: > > I'd like to move (again) to a syntax like the NBTSC Wiki, which is in line > with suggestions by many users over the last two years. Ali went for > syntax that is a lot like how people do things in plain text elsewhere: > > *bold* > /italic/ > > I think are two examples. Ali's reasoning was the marked up page language > should be as easy to read/understand as the rendered page. > > Now, the one thing that has troubled me about both the plugin syntax and > the proposed plain text tags is they are not consistent with the markup to > date... and inconsistency is not good for the user. As PhpWiki grows in > features, though, I understand it gets harder to maintain consistency. > > I'd like to see some proposals that are consistent with our current > syntax, or some way that would be compatible with NBTSC syntax. > > ~swain |
From: Jan N. <ja...@gn...> - 2001-12-09 20:42:43
|
Laurent Rathle <la...@pa...> writes: > I'm doing a french translation of phpwiki and I would like to test it. That's nice. Have you checked with the phpwiki folks so that you're not duplicating this effort? > I've tried to change "C" into "de" or "nl" in lib/config.php to see > PhpWiki in other languages, I always fall on english. I've got the > goos repertories (locale/de, ...) and they are accessible for the > web server (good permissions). I've certainly forgot something, but > what ? There are some problems with certain versions of php and phpwiki. What versions do you have? > Could you help me ? First, you should try to get gettext to work in a simple page. Try: <? # setlocale(LC_ALL, "nl_NL"); bindtextdomain ("libc", "/usr/share/locale"); textdomain ("libc"); print (gettext ("cannot open")); print ("\n"); bindtextdomain ("phpwiki", "/var/www/wiki/locale"); textdomain ("phpwiki"); print (gettext ("None")); print ("\n"); ?> save this as gettext.php, and run: 21:37:52 fred@appel:~/public_html$ php4 gettext.php X-Powered-By: PHP/4.1.0 Content-type: text/html kan niet openen Geen The first string, `cannot open' should always work; then try to get the phpwiki to work. > If you are interested, I can send you the translation when it's finished. Better send it to the phpwiki list directly. Greetings, Jan. -- Jan Nieuwenhuizen <ja...@gn...> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org |
From: Adam S. <ad...@pe...> - 2001-12-09 20:13:40
|
> The map entries would probably be cached (maybe in the page > meta-data), so that the whole map page doesn't have to be scanned for > entries on every page view. i like this idea, especially the idea of a community edited map file, though it's been repeatedly shot down on meatball. there are some interesting ideas popping up recently though here: http://www.usemod.com/cgi-bin/mb.pl?FileReplacement adam. |
From: Jeff D. <da...@da...> - 2001-12-09 17:23:41
|
On Sat, 8 Dec 2001 19:14:43 -0500 "Carsten Klapp" <car...@ma...> wrote: > How about using a file name like "shortcuts.map"? (Keep the real Wikis in > interwiki.map). I've been thinking they should be moved into (locked) wiki pages. I'm not sure what the format should be, but it should include provisions to include short blurbs about each entry. Something like (in page InterWikiMap): --- Here is a list of InterWiki prefixes supported on this wiki. ; PhpWiki : http://phpwiki.sf.net/wiki/ This is the home-wiki of PhpWiki... ; Wiki: http://c2.com/cgi/wiki? The original wiki... --- The map entries would probably be cached (maybe in the page meta-data), so that the whole map page doesn't have to be scanned for entries on every page view. Good idea? Suggestions for format? |
From: Reini U. <ru...@x-...> - 2001-12-09 16:44:54
|
Carsten Klapp schrieb: > <?php > // language codes are comma delimited > $lang = strtok ( $HTTP_ACCEPT_LANGUAGE, "," ); > while ( $lang ) { > //if there is "en" in it > if ( strstr ( $lang, "en" ) ) { > header ( "Location: http://localhost/english/" ); > exit; ... better is to check the first 2 chars only. if ( substr($lang, 0,2) == "en" ) otherwise we might get a match on the secondary specification. (de_at) -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
From: Carsten K. <car...@ma...> - 2001-12-09 07:20:10
|
My Wiki 1.3 is working in postgresql with the database created in = unicode! !!!! but still needs some work. You can see a screen snapshot of KOREAN text in Wiki 1.3 on my web site: <http://homepage.mac.com/carstenklapp/phpwiki/> No I don't speak Korean :-) initdb -E 'UNICODE' /usr/local/pgsql/data createdb -E 'UNICODE' wiki psql wiki < schemas/psql.sql (instead of psql wiki -f schemas/psql.sql) index.php 'dsn' =3D> 'pgsql://postgres@localhost/wiki', browse.html, editpage.html, message.html: <?php echo "<?xml version=3D'1.0' encoding=3D'UTF-8'?>\n"; ?> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-8" = /> Carsten On Saturday, December 8, 2001, at 08:42 pm, Carsten Klapp wrote: > > Hi, > > I'm trying to set up wiki 1.3 for use with pgsql. Is the DB backend = for=20 > postgresql still in the works? I get this error when loading the home=20= > page. > pgsql is running, wiki database created with the schema. > > lib/WikiDB/backend/PearDB.php:28: Fatal[256]: Can't connect to = database:=20 > wikidb_backend_pgsql: fatal database error > > =95 DB Error: connect failed > =95 (pgsql://postgres@localhost/wiki) > =95 > > Fatal error: Call to a member function on a non-object in=20 > /Library/WebServer/Documents/phpwiki-1.3/lib/ErrorManager.php on line = 191 > > index.php: > 'dsn' =3D> 'pgsql://postgres@localhost/wiki', > > MySQL doesn't seem to support UTF-8 or unicode yet. For Wiki to = support=20 > UTF-8, non-ascii characters would have to be encoded into hex strings=20= > before storing in the database. This might be ugly in the database but=20= > the %hex%hex codes can be dumped straight into the html. > > pgSQL does support multibyte unicode characters and utf-8 encoded = unicode. > > Carsten |
From: Carsten K. <car...@ma...> - 2001-12-09 01:42:59
|
Hi, I'm trying to set up wiki 1.3 for use with pgsql. Is the DB backend for=20= postgresql still in the works? I get this error when loading the home = page. pgsql is running, wiki database created with the schema. lib/WikiDB/backend/PearDB.php:28: Fatal[256]: Can't connect to database:=20= wikidb_backend_pgsql: fatal database error =95 DB Error: connect failed =95 (pgsql://postgres@localhost/wiki) =95 Fatal error: Call to a member function on a non-object in=20 /Library/WebServer/Documents/phpwiki-1.3/lib/ErrorManager.php on line = 191 index.php: 'dsn' =3D> 'pgsql://postgres@localhost/wiki', MySQL doesn't seem to support UTF-8 or unicode yet. For Wiki to support=20= UTF-8, non-ascii characters would have to be encoded into hex strings=20 before storing in the database. This might be ugly in the database but = the=20 %hex%hex codes can be dumped straight into the html. pgSQL does support multibyte unicode characters and utf-8 encoded = unicode. Carsten |
From: Carsten K. <car...@ma...> - 2001-12-09 00:16:49
|
Normalizing the headings sounds awesome! My vote goes to the second variation. Carsten On Saturday, December 8, 2001, at 09:55 am, Gary Benson wrote: > > On Fri, 7 Dec 2001, Carsten Klapp wrote: > >> One limitation I've run into is only 3 levels of headings. While >> heading levels 4, 5 and 6 are not frequently used outside of >> documentation or other published material, they are supported by html. >> Is anyone else here interested in seeing 4 (or more) heading levels? > > A nice way to do this is without breaking everything is to `normalise' the > headings during parsing. The biggest heading (ie the most !'s) you use > should be h1, the next biggest h2 and so on; if you use more than 6 > different sizes then the smallest ones all get set to h6. > > A variation would have the biggest heading set to h2, since h1 would > generally be used in the template for the page's title... > > Cheers, > Gary > > [ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ] > |
From: Carsten K. <car...@ma...> - 2001-12-09 00:14:48
|
Also, I'd like to see two map lists, one for REAL Wiki & WikiClones, the other for any "URL shortcuts" like RFC, ISBN etc. For one thing the link-icons for Inter-Wiki isn't appropriate for Internet shorcuts, those should just use the regular http icon. (The code for interpreting the URLs in the map files obviously is still the same.) How about using a file name like "shortcuts.map"? (Keep the real Wikis in interwiki.map). Carsten On Saturday, December 8, 2001, at 12:14 pm, Jeff Dairiki wrote: > On Sat, 8 Dec 2001 15:38:41 -0000 > "Lawrence Akka" <Law...@th...> wrote: > >> Could we add phpwiki-talk: >> http://www.geocrawler.com/archives/3/4037/2001/ >> >> to the interwiki map, to allow quick references to this list >> >> eg http://www.geocrawler.com/archives/3/4037/2001/12/0/7271426/ > > Interestingly, when referring to a specific post, only the last of those > numbers in the URL seems to matter. > > e.g. http://www.geocrawler.com/archives/1/1/1/1/1/7271426 works fine. > > So adding > phpwiki-talk http://www.geocrawler.com/archives/1/1/1/1/1/ > to interwiki.map would allow phpwiki-talk:7271426. (However, perhaps a > better moniker would be 'Geocrawler'.) > > I'm not sure that's a good idea though. Most "InterWiki" links make sense > on their own. Consider 'Wiki:RecentChanges' and 'RFC:822'. The text > itself makes a good title for the link --- one can tell from the text > alone what the link (is supposed to) points to. The number in > phpwiki-talk:7271426 is pretty much an arbitrary quasi-random number. I > guess I don't see the advantage of making it an interwiki link over just > > See [this post| http://www.geocrawler.com/...] on phpwiki-talk. > > Interwiki link makes for less typing, but it seems you pretty much have to > cut-and-paste to get that message number, you might as well cut-and-paste > the whole URL. > > On a related note, I also suspect the Geocrawler reindexes their archives > periodically (thus breaking all these links.) I'm pretty sure I remember > this having happened in the past. > > That's my two cents worth, at least. > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > |
From: Jeff D. <da...@da...> - 2001-12-08 17:14:49
|
On Sat, 8 Dec 2001 15:38:41 -0000 "Lawrence Akka" <Law...@th...> wrote: > Could we add phpwiki-talk: > http://www.geocrawler.com/archives/3/4037/2001/ > > to the interwiki map, to allow quick references to this list > > eg http://www.geocrawler.com/archives/3/4037/2001/12/0/7271426/ Interestingly, when referring to a specific post, only the last of those numbers in the URL seems to matter. e.g. http://www.geocrawler.com/archives/1/1/1/1/1/7271426 works fine. So adding phpwiki-talk http://www.geocrawler.com/archives/1/1/1/1/1/ to interwiki.map would allow phpwiki-talk:7271426. (However, perhaps a better moniker would be 'Geocrawler'.) I'm not sure that's a good idea though. Most "InterWiki" links make sense on their own. Consider 'Wiki:RecentChanges' and 'RFC:822'. The text itself makes a good title for the link --- one can tell from the text alone what the link (is supposed to) points to. The number in phpwiki-talk:7271426 is pretty much an arbitrary quasi-random number. I guess I don't see the advantage of making it an interwiki link over just See [this post| http://www.geocrawler.com/...] on phpwiki-talk. Interwiki link makes for less typing, but it seems you pretty much have to cut-and-paste to get that message number, you might as well cut-and-paste the whole URL. On a related note, I also suspect the Geocrawler reindexes their archives periodically (thus breaking all these links.) I'm pretty sure I remember this having happened in the past. That's my two cents worth, at least. |
From: Lawrence A. <Law...@th...> - 2001-12-08 15:34:06
|
Could we add phpwiki-talk: http://www.geocrawler.com/archives/3/4037/2001/ to the interwiki map, to allow quick references to this list eg http://www.geocrawler.com/archives/3/4037/2001/12/0/7271426/ Lawrence |
From: Gary B. <ga...@in...> - 2001-12-08 14:56:56
|
On Fri, 7 Dec 2001, Carsten Klapp wrote: > One limitation I've run into is only 3 levels of headings. While > heading levels 4, 5 and 6 are not frequently used outside of > documentation or other published material, they are supported by html. > Is anyone else here interested in seeing 4 (or more) heading levels? A nice way to do this is without breaking everything is to `normalise' the headings during parsing. The biggest heading (ie the most !'s) you use should be h1, the next biggest h2 and so on; if you use more than 6 different sizes then the smallest ones all get set to h6. A variation would have the biggest heading set to h2, since h1 would generally be used in the template for the page's title... Cheers, Gary [ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ] |