You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(29) |
Dec
(101) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(90) |
Feb
(101) |
Mar
(173) |
Apr
(141) |
May
(38) |
Jun
(28) |
Jul
(14) |
Aug
(7) |
Sep
(3) |
Oct
(7) |
Nov
(15) |
Dec
(9) |
2002 |
Jan
(2) |
Feb
(5) |
Mar
(11) |
Apr
|
May
(4) |
Jun
(6) |
Jul
(7) |
Aug
(12) |
Sep
(8) |
Oct
(1) |
Nov
(4) |
Dec
(7) |
2003 |
Jan
(7) |
Feb
(1) |
Mar
(9) |
Apr
(2) |
May
(3) |
Jun
(4) |
Jul
(19) |
Aug
(4) |
Sep
(8) |
Oct
(30) |
Nov
(25) |
Dec
(22) |
2004 |
Jan
(6) |
Feb
(12) |
Mar
|
Apr
(2) |
May
|
Jun
(10) |
Jul
(18) |
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
2005 |
Jan
(8) |
Feb
(4) |
Mar
(6) |
Apr
(5) |
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(4) |
Nov
(3) |
Dec
|
2006 |
Jan
(9) |
Feb
(6) |
Mar
(11) |
Apr
|
May
(2) |
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(1) |
Dec
(1) |
2007 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Shane <sh...@lo...> - 2004-11-15 17:07:50
|
I agree, something like that would be sweet. I had been thinking about doing LVS http://www.linuxvirtualserver.org/ . When I had a really good student employee two years ago I was able to have him setup a mock environment with an entire LVS and webfarm via multiple webheads and FS shared from an NFS server. But then he left, and I had no time to deal with it. So when I saw this "Pound" thing it caught my eye. Same thing, however. No time to deal with it nor test it etc etc. But it sounds sweet. Shane On Nov 15, 2004, at 11:46 AM, William Scott Lockwood III wrote: > I need something like that. Have you tried setting it up? With multiple > sites? > > -- > Regards, > Scott > > ---==== [ Shane ] ===--- >> Anyone tried front-ending a slashcode-based site with Pound? >> >> http://www.apsis.ch/pound/ >> >> Shane >> > |
From: Shane <sh...@lo...> - 2004-11-14 13:09:50
|
Anyone tried front-ending a slashcode-based site with Pound? http://www.apsis.ch/pound/ Shane |
From: Shane <sh...@lo...> - 2004-10-22 11:18:39
|
Why use 6 month old code? Are you trying to use 6/30/2004 code, ie immediately before the section-topics changes? Why not just go with current-cvs? What version, exactly, is your sc installation that you are wanting to upgrade? Beware that "Display Link Domains" is a user-pref. I'd check that filtering, first, if I were you. Shane On Oct 22, 2004, at 6:02 AM, al...@ow... wrote: > -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% > [score: 0.0000] > X-Scan-Signature: e55f8aef11f945ad03c2b853ce09fcaa > > Folks, > > I am trying to upgrade my slashcode installations from about two year > old > code to about 6 month old code :-) (or eventually latest CVS :-) > > Can someone give me some hints as to what filters get done on the > submitted story. I am trying to trace through the code I do have to see > why hrefs are being dropped. > > It seems to me that the code for identifying urls and turning them into > html anchors is broken on my site, but more importantly anchors > written in > to the submitted articles are having their href's chopped off. > > > Alex Mc > > > > -- > > Alex McLintock > Openweb Analysts Ltd > Software for Complex Websites > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on > ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give > us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out > more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-development > |
From: <al...@ow...> - 2004-10-22 09:55:15
|
Folks, I am trying to upgrade my slashcode installations from about two year old code to about 6 month old code :-) (or eventually latest CVS :-) Can someone give me some hints as to what filters get done on the submitted story. I am trying to trace through the code I do have to see why hrefs are being dropped. It seems to me that the code for identifying urls and turning them into html anchors is broken on my site, but more importantly anchors written in to the submitted articles are having their href's chopped off. Alex Mc -- Alex McLintock Openweb Analysts Ltd Software for Complex Websites |
From: Alessio B. <al...@se...> - 2004-10-02 09:15:45
|
On Fri, 2004-10-01 at 19:37, Peter Winnberg wrote: > The attached patch changes 'CHECKED' the source to use a var, that way > it's possible to use XHTML without code changes and still easy to switch > between HTML and XHTML. > > Any comments? Seems to me that checked="checked" would we perfectly valid HTML too, so IMHO the patch could just be applied in any case. -- Alessio Bragadini <al...@se...> Sevenseas.org Hacking Community |
From: Peter W. <pe...@op...> - 2004-10-01 17:47:08
|
In a couple of places Slash have 'CHECKED' hardcoded. This is then used on markup like this: <input type="checkbox" name="reparent" CHECKED> This is not a problem as long as you are using HTML, but if you are using XHTML the above markup have to look like this: <input type="checkbox" name="reparent" checked="checked" /> The attached patch changes 'CHECKED' the source to use a var, that way it's possible to use XHTML without code changes and still easy to switch between HTML and XHTML. Any comments? -- Peter Winnberg <pe...@op...> Openflows Networks Ltd. |
From: Shane <sh...@lo...> - 2004-09-28 13:46:38
|
this'll easily uninstall a slash-site http://www.lottadot.com/files/uninstallslashsite.plx and this'll reset your topic_draw variables (useful when you're trying to get the newer Slash::Admin installed w/ the topic pop up and the TTF fonts on a non-debian machine) http://www.lottadot.com/files/cleartopicdraw.plx I've been using the uninstall for a few days while modding Slash::Install a bit. So I think it's safe. As always, comments welcome. Shane |
From: Shane <sh...@lo...> - 2004-09-09 12:13:08
|
I've been messing with converting all my slashsites to section-topics. I thought I'd point out a few differences that caused me a bit of pain yesterday: 1. When you are converting a site, do _not_ forget about the upgrades file. Infact, you may, depending on how you are doing the conversion, need to split the upgrades file up in pieces because in the middle of it is some perl code that is dependant on some of the updates in that file. So be careful. If you are not convertDBto200406_render will die in mid-conversion. 2. The schema for the stories table has majorly changed. Gone is 'writestatus' and 'displaystatus'. Now stories.primaryskid <1 == 'never display' and stories.in_trash... well, pretty obvious there. 3. [13:54] <tf23> there may be a problem with the upgrades file with this line [13:54] <tf23> ALTER TABLE skins ADD COLUMN submittable ENUM('no', 'yes') DEFAULT 'yes' NOT NULL AFTER issue; [13:55] <tf23> i'm seeing that submittable column already exists [13:58] <jamie> where was it created? [14:01] <tf23> good question. give me a bit, i'll find it [14:03] <tf23> it's created when convertDBto200406 is run I don't know that that's a bug, for sure. I haven't had time to mess with it and rinse-and-repeat. If I find that it's not my own mistake then I'll file a sf.bug for it. 4. typical/example code for judging which skin/section your code is being run under: my $skin_name = $form->{section}; my $skid = $skin_name ? $slashdb->getSkidFromName($skin_name) : determineCurrentSkin(); setCurrentSkin($skid); my $gSkin = getCurrentSkin(); $skin_name = $gSkin->{name}; $form->{section} = $skin_name; $form->{skin_name} = $skin_name; $form->{skid} = $skid; That's it for now. Shane |
From: Shane <sh...@lo...> - 2004-09-07 10:26:27
|
On Sep 5, 2004, at 5:59 PM, Ian Kluft wrote: > Slashcode developers - > > I'd like to port and contribute the patches for mod_perl 2 and > PostgreSQL > compatibility for Slash. I've done some analysis to scope out the > problem. > But I realize that it wouldn't be useful to proceed beyond this point > without contacting you. Smart man :) > > Here's a page describing what I've done so far and my initial idea of > how to proceed. > > "SlashCode compatibility with mod_perl 2 and PostgreSQL: Scoping the > Problem" > http://www.kluft.com/~ikluft/opensource/slash/ > > Whether or not to continue on this really depends on determining if > you're > interested, and gaining your support. It's a lot of work but this > analysis > shows what needs to be done. It would only be worthwhile if I know > that > the effort has a reasonable chance (pending your usual code submission > procedures, of course) of going into the code base. Understandable. > > As others have pointed out before, one of the big things for PostgreSQL > support is to split up Slash/DB/MySQL/MySQL.pm. 80% of the functions > are not MySQL specific at all, and can be moved to a common parent > class. > Another 16% of the functions will need some database-specific code > moved > to new database-specific functions before the rest of that code can > also > go to the common parent class. (Some would have worked in PostgreSQL > but not in Oracle, so I included them here too.) Only 8 functions are > completely MySQL specific in there. Then some documentation will be > needed to show how to make future code portable among supported > databases. I've always wondered about that. Even though there is Slash::DB::* most everything seems to be Slash::DB::MySQL. > Should I proceed? While I'm no official slash-dev, I vote hell yeah do it. It seems to make sense to me to separate as much generic db-code out and create the unique db code in each. The more db's slash will work with out of the box, the more users of the software. And the more users, the more add-ons developed. At-least, that's how it'd work in my fairy-tale world... :) Shane PS - There's another benefit of this. Once it'd happen, it would be far easier to release plugins that'll work with add'l sql backends. Yes, you'd think that'd be obvious, but the idea just popped into my head :) |
From: Ian K. <ik-...@th...> - 2004-09-05 21:59:47
|
[I'm re-sending this from the correct address that I'm subscribed to the list. The moderators can discard the earlier copy from a day and a half ago which was held by Mailman. Or if that one winds up on the list too, sorry for the duplication.] Slashcode developers - I'd like to port and contribute the patches for mod_perl 2 and PostgreSQL compatibility for Slash. I've done some analysis to scope out the problem. But I realize that it wouldn't be useful to proceed beyond this point without contacting you. Here's a page describing what I've done so far and my initial idea of how to proceed. "SlashCode compatibility with mod_perl 2 and PostgreSQL: Scoping the Problem" http://www.kluft.com/~ikluft/opensource/slash/ Whether or not to continue on this really depends on determining if you're interested, and gaining your support. It's a lot of work but this analysis shows what needs to be done. It would only be worthwhile if I know that the effort has a reasonable chance (pending your usual code submission procedures, of course) of going into the code base. As others have pointed out before, one of the big things for PostgreSQL support is to split up Slash/DB/MySQL/MySQL.pm. 80% of the functions are not MySQL specific at all, and can be moved to a common parent class. Another 16% of the functions will need some database-specific code moved to new database-specific functions before the rest of that code can also go to the common parent class. (Some would have worked in PostgreSQL but not in Oracle, so I included them here too.) Only 8 functions are completely MySQL specific in there. Then some documentation will be needed to show how to make future code portable among supported databases. Should I proceed? Obviously only if the Slash developers are interested, and would be willing to go along with portability after it's in. For example, once the split is done, we can't have new non-MySQL stuff going into MySQL.pm again. While I think that's something you'd readily go along with, I still have to ask because it's entirely up to you. |
From: Malcolm L. <ma...@to...> - 2004-08-20 05:51:06
|
So are there any slash developers on this list paying attention to this = exchange or is everyone on vacation still? Malcolm Lawrence Editor-in-Chief Babel: The multilingual, multicultural online journal and community of arts and ideas. http://www.towerofbabel.com ------------------------------------------------------------ Babel wonders: Are you addicted to moderation? ------------------------------------------------------------ ----- Original Message -----=20 From: i18n=20 To: Malcolm Lawrence=20 Cc: sla...@li...=20 Sent: Thursday, July 29, 2004 10:28 PM Subject: Re: [Slashcode-development] towerofbabel.com I was on vacation right after I wrote that but am back now. I am = interested. I think it would be a fine addition for slash. Other CMS's I = have looked at (only a small subset of what is out there, but still) do = support Unicode. After all, XML is by definition to be in Unicode. How difficult this would be is hard to say without doing a code = analysis, talking with the developers to understand plans for the = future, and so forth. I'd be interested to hear from the developers if = this is the sort of big bang feature that they can see being part of = Slash going forward. Best, Barry Malcolm Lawrence wrote: "Slash doesn't need to deal with any character set, it only needs to = deal with one - Unicode. The modern browser should/will make conversions = to/from Unicode for both inbound and outbound data. If slash is rewritten to = support Unicode instead of whatever it is now (ISO-8859-1 probably?), then that = is all there is to it as far as the database is concerned. Even templates could then be in many languages, even within a template if so desired." So who wants to help thread Slash with Unicode? How difficult would it = be and how long would it take? Malcolm Lawrence Editor-in-Chief Babel: The multilingual, multicultural online journal and community of arts and ideas. http://www.towerofbabel.com ------------------------------------------------------------ Babel knows: It is not unpatriotic to exercise your rights and it is un-American to suggest otherwise. ------------------------------------------------------------ ----- Original Message -----=20 From: "Malcolm Lawrence" <ma...@to...> To: <sla...@li...>; "Barry Caplan" <bc...@i1...> Sent: Thursday, July 01, 2004 7:17 PM Subject: Re: [Slashcode-development] towerofbabel.com "Slash doesn't need to deal with any character set, it only needs to = deal with one - Unicode. The modern browser should/will make conversions to/from Unicode for both inbound and outbound data. If slash is rewritten to support Unicode instead of whatever it is now (ISO-8859-1 probably?), then = that is all there is to it as far as the database is concerned. Even templates could then be in many languages, even within a template if so desired." Rightio. Any other voices like to chime in about slash and Unicode? Malcolm Lawrence Editor-in-Chief Babel: The multilingual, multicultural online journal and community of arts and ideas. http://www.towerofbabel.com ------------------------------------------------------------ Babel knows: People who don't work with their hands are parasites. ------------------------------------------------------------ ----- Original Message -----=20 From: "Barry Caplan" <bc...@i1...> To: "Malcolm Lawrence" <ma...@to...>; <sla...@li...> Sent: Thursday, July 01, 2004 7:06 PM Subject: Re: [Slashcode-development] towerofbabel.com At 06:23 PM 7/1/2004, Malcolm Lawrence wrote: "I can say quite comfortably that using flags as a ui device to indicate language or any other locale issue is a bad bad idea." True enough. I've been building the site for 8 years and am well aware of all the arguments against. But until a more suitable design element = can be implemented (not to mention appropriate icons for topics) they'll = have to do. They're pretty, too. Hmm. I guess I wasn't clear enough on this point. There is not one single professional localizer on the face of the earth that would recommend flags as an UI element indicating locale. I hope that is plain enough. If not, at least it will turn up in = google for someone someday who will read why and decide to not use flags. = ) The reasons, as I enumerated some of them, fall in the general = category of "They don't have a one to one relationship with what is being = described" and "users have visceral, political feelings about them, usually = rightfully so". Example: I am an English speaker in the US. I sometimes see a UK Union Jack flag which is meant to indicate English text. But does it? Or = is it something more specifically about the UK that lurks in that site? What about people in other countries? Do I have to know their flags too? = Australia's first language is English - what flag should they use on their sites to indicate English localization? Example: I live in Silicon Valley where > 30% of people do not speak English as a first language at home (maybe > 50%! I forget so I = will go with the conservative value for now). So if I have content that is US = locale based, but localized into various languages such as Chinese, Spanish, Vietnamese, etc., what flags shall I use? If not US, then what one to = use again falls into the problem just mentioned - e.g. Spanish is spoken = many places, and is not the same Spanish everywhere anymore then English is universal. And even if I somehow choose a flag, then what if the same language = is used in a different place on the site? I surely won't be using the = Taiwan flag everywhere there is Chinese, nor the PRC flag. Except in those 2 countries, it is hard to see which would be appropriate without = offending. Finally, take a look at Canada. With 2 official languages (English = and French), what does a Maple Leaf flag say about the language of = the material behind it? Nothing at all! But it might say something very serious = about political issues you don't mean to say! The reason there are no generally accepted icons to represent locale = is, quite frankly, because there are none to be had. It is not as though people have not put a lot of thought and hard = earned experience into this, looking for a good way. They have. A lot of = people and a lot of time. If it is pretty you want, then make whatever you do pretty, whatever that means to you. You can do that and have plain text too. Photoshop works wonders for that :) For an example of a pretty good effort, look at how yahoo.com = indicates locales on their pages. That basic technical approach, coupled = with whatever UI beautification is needed for your site, is a pretty good way to go. As for if slashcode supports Unicode, I don't know as it has been = well over a year since I looked at it. How complicated that would be to = do is a matter of conjecture - there are technical, testing, and management = issues to consider. I have done just that with closed source code that was far more complex then slashcode, so I am confident it could be done. That it = hasn't been done until now (if it hasn't been done) strikes me a a combination = of all three factors. AFIK Unicode support is de rigeur for any new project that hopes to scale. For any existing project that hopes to stick around with a worldwide = user base, then the switch is going to need to be made. I think I may be volunteering to work with the developers to understand what the effort level and tasks should be, so that people can sign onto them in a coherent fashion. But my experience is that this sort of conversion does need to = be coordinated very closely with any other ongoing development, otherwise = it is just a fork in the code and no one wants that. Managing the codelines = so they don't fork (or they do but they merge back together at a defined point more likely) is something I can definitely bring to the table. "In a perfect world, the browser would accept HTML in Unicode and display properly from there. For folks whose users all have modern browsers, that is possible. The browser will make the conversion to the right = character encoding locally, or it will have Unicode fonts enabled. When there are Unicode fonts available, then you get the advantage of displaying multiple languages on a single page, which, frankly, is what I would expect = of a site called "towerofbabel.com", slashcode or not :)" Well, the browser isn't the problem. It's the ability of slash to be able to deal with any character set when a story is submitted or a comment posted. Would those problems go away as soon as slash were dealing with all internal processing in Unicode? Slash doesn't need to deal with any character set, it only needs = to deal with one - Unicode. The modern browser should/will make = conversions to/from Unicode for both inbound and outbound data. If slash is rewritten to support Unicode instead of whatever it is = now (ISO-8859-1 probably?), then that is all there is to it as far as = the database is concerned. Even templates could then be in many languages, even within a template if so desired. In your case, you probably would not need to go to subdomains unless = you wanted to - you could just have slash sections for each language. = And if someone posted Chinese on the French page, so what? slash won't care so neither should you. Trust me you don't want a case statement for every codeset dependent feature in the code. Your domain name pretty much sums up the reason why that is the case :) Best, Barry =20 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Slashcode-development mailing list Sla...@li... https://lists.sourceforge.net/lists/listinfo/slashcode-development =20 ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Slashcode-development mailing list Sla...@li... https://lists.sourceforge.net/lists/listinfo/slashcode-development =20 |
From: Malcolm L. <ma...@to...> - 2004-08-12 08:48:59
|
I keep getting asked 'Who are you guys?,' so to help unload some of that = extra mail from my inbox I have now provided this nice little page with = a summary of the active Authors, Editors and Managers here, along with = the number of articles that they have posted. http://towerofbabel.com/map/authors.pl Babel is currently expanding to be able to offer content and threaded = discussions in over 400 languages on the site, which means building 400 = brand new sections, each one which will be hosted by Authors, Editors = and Managers in their own native language for our progressive academic = journal and eventual online university. The main idea is to simply take = the English-language prototype of Babel) and have different language = versions of the site with the same goals and aspirations as the original = English-speaking version.=20 The Babel foreign language sections currently built (but not yet visible = online) are for: English -- http://en.towerofbabel.com =20 Spanish =96 http://es.towerofbabel.com =20 French =96 http://fr.towerofbabel.com =20 German =96 http://de.towerofbabel.com =20 Italian =96 http://it.towerofbabel.com =20 Estonian =96 http://et.towerofbabel.com =20 Dutch =96 http://nl.towerofbabel.com =20 Japanese =96 http://ja.towerofbabel.com =20 Russian =96 http://ru.towerofbabel.com =20 and Arabic =96 http://ar.towerofbabel.com =20 Soon another 400 language sections will also be built, with the most = popular languages continuing the subdomain style of having two character = designations for their sections and the more obscure languages having = three character designations for their sections. = (http://www.w3.org/WAI/ER/IG/ert/iso639.htm)=20 (What Babel is attempting to do with Slash is not something which has = been tried before, so it could be a bit of a slow process getting all = 400 language section versions up and going on the site. So please = understand if it takes a while for me to answer your queries right now. = I thank you all in advance for your patience.) What this means for languages spoken in more than one country is that in = the, say, Spanish Babel section there will be Authors, Editors and = Managers who are native Spanish speakers, but hopefully not from the = same country. It would be ideal if there were Authors, Editors and = Managers from Argentina, Mexico, Spain etc. so you will all be able to = post stories submitted in Spanish about issues particular to your = specific country or your specific artistic passion so visitors to the = site can comment in Spanish about what is posted in that language=92s = section. The main thing I need to clarify before we go any further is what the = terms =93Authors=94 =93Editors=94 and =93Managers=94 mean because they = may not mean what you=92re used to them meaning because they=92re terms = which apply to how they=92re designated in Slash. If you=92re not = familiar with Slash or Slashdot I recommend that you go to = http://slashdot.org, which is the site which developed Slash = specifically for the Slashdot site. For a short and concise explanation = about what Slashdot is, go here: http://en.wikipedia.org/wiki/Slashdot. The way Slash is set up there are simply users and Authors, but for the = purposes of Babel I=92ve decided to expand the designations to = =93Authors=94 =93Editors=94 and =93Managers=94 because this way it's = easier to tell the difference between the three different levels of = security access which will provide you with access to the various = administrative parts of the site. The term =93author=94 is actually a = bit of a misnomer as used in Slash because as you can see from my status = as an author further down this page I=92m the =93author=94 of over 700 = stories even though I=92ve only written a few (Neal Robbins is currently = responsible for most of them). It=92s better to think of an author as = =93one who authorizes stories to be displayed, whether they=92ve been = submitted by others or posted by oneself=94 when dealing with Slash.=20 While site users only see the front end of Slash, the Authors, Editors = and Managers have a special interface called backSlash, which controls = everything from posting Stories to managing Authors.=20 Any logged-in Author, Editor or Manager will see a special row of links = below the main title banner of any page. This is the Admin menu. If the = heart of Slash administration is the backSlash interface, its nerve = center is the Admin menu. It holds the keys to unlock the remote = administration features provided by the admin.pl applet.=20 A Slash Author, Editor, or Manager is simply a user account that has = been granted additional privileges. Each user account within Slash has = an assigned security level or =93seclev.=94 This is an integer between 0 = and 10,000. Regular users start with a seclev of 1, and the Anonymous = User has a seclev of 0. Authors must have a seclev of at least 100. Specific author abilities kick in at the following Security Levels:=20 100 =96 the =93Author=94 level View Admin menu View Stories list Edit Stories Use block editor Post new Stories Create and edit polls Unlimited moderation=20 Delete posted comments 500 -- the =93Editor=94 level View and approve submissions Edit templates Edit site colors 1,000 =96 the =93Manager=94 level=20 Manage Sections Manage comment filters 10,000 =96 =93God=94 Manage Authors Edit variables Edit Topics Ban user Edit IP block list Expire user Session Set default user comment score Set user read-only flags One day, hopefully soon, Slash will be threaded with Unicode so anyone = can post stories and/or post comments in any character set they wish to = type. But for now I=92ve decided that the easiest way to make Slash = multilingual is to create 400 new =93sections=94 of Babel, which will be = designated by language. What this means is that each language=92s = section will be needing Authors, Editors and Managers so each section = can be its own version of Babel.=20 As far as the graduated positions are concerned, a Manager is also able = to be an Editor and an Author. An Editor can also be an Author, but not = a Manager. And an Author can only be an Author, not an Editor or a = Manager. Unless of course Authors and Editors do such a stellar job that = we decide to promote them. I'd like those who are interested in being assigned to the section of = your native language version of the site to write and explain which = position you=92d like and why so we can measure how much time, energy, = enthusiasm and creativity you=92re planning on bringing to Babel. The = security levels for Editors will provide opportunities for creativity = and enable you to customize your section as you wish. I like the idea of = Editors being able to design their own section of Babel as they see fit, = perhaps taking a completely different approach to a design of the tower = of Babel. One of the main responsibilities of the section Managers is to spearhead = the initiative to have the content of the user interface pages as well = as the inner workings of the administrative pages of Slash translated = into their own section=92s native language so you can be free to deal = with the code on an administrative level in your own native language. = This will also be of great benefit for the Slash developers community so = that website owners wishing to add Slash to their code will be able to = deal with it in their own language straight out of the box. This does = not need to be accomplished by the section manager alone, and I = recommend getting a hold of other webmasters utilizing Slash in their = own non-English speaking websites to see how much of their sites have = been translated so unnecessary work can be avoided. This list of other sites which are either using Slash in other languages = or else building sites similar in spirit to Slash will give you some = ideas as to how much customization can be done with the code, as well as = see all of the various parts which will need to be translated so each = section can be as independent from the English language as possible.=20 http://www.nlroei.nl =96 A Dutch-speaking site using Slash http://www.minut.ee =96 An Estonian-speaking site using Slash=20 http://www.symlink.ch -- A German-speaking site using Slash http://www.accordo.it -- An Italian-speaking site using Slash http://www.citinv.it =96 An Italian-speaking site using Slash http://www.dsmodena.it =96 An Italian-speaking site using Slash http://www.inRoma.it =96 An Italian-speaking site using Slash http://slashdot.ne.jp =96 A Japanese-speaking site using Slash http://gildot.org -- A Portuguese-speaking site using Slash=20 http://nou.surse.ro =96 A Romanian-speaking site using Slash http://slashzone.ru =96 A Russian-speaking site using Slash http://puntbarra.com -- A Catalan-speaking site in the spirit of = Slashdot http://linuxfr.org/pub -- A French-speaking site in the spirit of = Slashdot=20 http://barrapunto.com -- A Spanish-speaking site in the spirit of = Slashdot Babel is also an online translation laboratory with currently over 300 = translators in 75 languages offering their services to help translate = the site. We are a non-profit organization, the translators are = voluntary and work on the site because they enjoy it (kind of like = Linux). Those translators who work on the site get their resume featured = on the site. Potential translators and journal editors submit their = resume or CV before being allowed to begin helping with the site so = their education, skills, experience and knowledge base with translating = can first be evaluated in order to ensure that Babel=92s standards of = excellence are maintained. If you=92re interested in being a voluntary foreign language journal = author, editor or manager for Babel, send us an email with your current = resume or CV attached as a Microsoft Word attached document so we can = see what your education, skills and knowledge base are. If you=92re interested in being a voluntary translator for Babel, send = us an email with your current resume or CV attached as a Microsoft Word = attached document so we can see what your education, skills and = knowledge base are. =20 706 malcolm=20 Generated on Thursday August 12, @01:19AM. Malcolm Lawrence Editor-in-Chief Babel: The multilingual, multicultural online journal and community of arts and ideas. http://www.towerofbabel.com ------------------------------------------------------------ Babel reminds you: Man is distinguished, not only by his reason, but by = this singular passion from other animals, which is a lust of the mind, = that by a perseverance of delight in the continual and indefatigable = generation of knowledge, exceeds the short vehemence of any carnal = pleasure. -- Thomas Hobbes's Leviathan, Part I, Chapter VI. ------------------------------------------------------------ |
From: i18n <i1...@ya...> - 2004-07-30 05:27:33
|
I was on vacation right after I wrote that but am back now. I am interested. I think it would be a fine addition for slash. Other CMS's I have looked at (only a small subset of what is out there, but still) do support Unicode. After all, XML is by definition to be in Unicode. How difficult this would be is hard to say without doing a code analysis, talking with the developers to understand plans for the future, and so forth. I'd be interested to hear from the developers if this is the sort of big bang feature that they can see being part of Slash going forward. Best, Barry Malcolm Lawrence wrote: >"Slash doesn't need to deal with any character set, it only needs to deal >with one - Unicode. The modern browser should/will make conversions to/from >Unicode for both inbound and outbound data. If slash is rewritten to support >Unicode instead of whatever it is now (ISO-8859-1 probably?), then that is >all there is to it as far as the database is concerned. Even templates >could then be in many languages, even within a template if so desired." > >So who wants to help thread Slash with Unicode? How difficult would it be >and how long would it take? > > >Malcolm Lawrence >Editor-in-Chief >Babel: The multilingual, multicultural >online journal and community of arts and ideas. >http://www.towerofbabel.com >------------------------------------------------------------ >Babel knows: It is not unpatriotic to exercise your rights and it is >un-American to suggest otherwise. >------------------------------------------------------------ > >----- Original Message ----- >From: "Malcolm Lawrence" <ma...@to...> >To: <sla...@li...>; "Barry Caplan" ><bc...@i1...> >Sent: Thursday, July 01, 2004 7:17 PM >Subject: Re: [Slashcode-development] towerofbabel.com > > > > >>"Slash doesn't need to deal with any character set, it only needs to deal >>with one - Unicode. The modern browser should/will make conversions >> >> >to/from > > >>Unicode for both inbound and outbound data. If slash is rewritten to >> >> >support > > >>Unicode instead of whatever it is now (ISO-8859-1 probably?), then that is >>all there is to it as far as the database is concerned. Even templates >>could then be in many languages, even within a template if so desired." >> >>Rightio. Any other voices like to chime in about slash and Unicode? >> >> >>Malcolm Lawrence >>Editor-in-Chief >>Babel: The multilingual, multicultural >>online journal and community of arts and ideas. >>http://www.towerofbabel.com >>------------------------------------------------------------ >>Babel knows: People who don't work with their hands are parasites. >>------------------------------------------------------------ >> >>----- Original Message ----- >>From: "Barry Caplan" <bc...@i1...> >>To: "Malcolm Lawrence" <ma...@to...>; >><sla...@li...> >>Sent: Thursday, July 01, 2004 7:06 PM >>Subject: Re: [Slashcode-development] towerofbabel.com >> >> >> >> >>>At 06:23 PM 7/1/2004, Malcolm Lawrence wrote: >>> >>> >>> >>>>"I can say quite comfortably that using flags as a ui device to >>>> >>>> >indicate > > >>>>language or any other locale issue is a bad bad idea." >>>> >>>>True enough. I've been building the site for 8 years and am well aware >>>> >>>> >of > > >>>>all the arguments against. But until a more suitable design element can >>>> >>>> >>be >> >> >>>>implemented (not to mention appropriate icons for topics) they'll have >>>> >>>> >to > > >>>>do. They're pretty, too. >>>> >>>> >>>Hmm. I guess I wasn't clear enough on this point. >>> >>>There is not one single professional localizer on the face of the earth >>> >>> >>that would recommend flags as an UI element indicating locale. >> >> >>>I hope that is plain enough. If not, at least it will turn up in google >>> >>> >>for someone someday who will read why and decide to not use flags. ) >> >> >>>The reasons, as I enumerated some of them, fall in the general category >>> >>> >of > > >>"They don't have a one to one relationship with what is being described" >> >> >and > > >>"users have visceral, political feelings about them, usually rightfully >> >> >so". > > >>>Example: I am an English speaker in the US. I sometimes see a UK Union >>> >>> >>Jack flag which is meant to indicate English text. But does it? Or is it >>something more specifically about the UK that lurks in that site? What >> >> >about > > >>people in other countries? Do I have to know their flags too? Australia's >>first language is English - what flag should they use on their sites to >>indicate English localization? >> >> >>>Example: I live in Silicon Valley where > 30% of people do not speak >>> >>> >>English as a first language at home (maybe > 50%! I forget so I will go >> >> >with > > >>the conservative value for now). So if I have content that is US locale >>based, but localized into various languages such as Chinese, Spanish, >>Vietnamese, etc., what flags shall I use? If not US, then what one to use >>again falls into the problem just mentioned - e.g. Spanish is spoken many >>places, and is not the same Spanish everywhere anymore then English is >>universal. >> >> >>>And even if I somehow choose a flag, then what if the same language is >>> >>> >>used in a different place on the site? I surely won't be using the Taiwan >>flag everywhere there is Chinese, nor the PRC flag. Except in those 2 >>countries, it is hard to see which would be appropriate without offending. >> >> >>>Finally, take a look at Canada. With 2 official languages (English and >>> >>> >>French), what does a Maple Leaf flag say about the language of the >> >> >material > > >>behind it? Nothing at all! But it might say something very serious about >>political issues you don't mean to say! >> >> >>>The reason there are no generally accepted icons to represent locale is, >>> >>> >>quite frankly, because there are none to be had. >> >> >>>It is not as though people have not put a lot of thought and hard earned >>> >>> >>experience into this, looking for a good way. They have. A lot of people >> >> >and > > >>a lot of time. >> >> >>>If it is pretty you want, then make whatever you do pretty, whatever >>> >>> >that > > >>means to you. You can do that and have plain text too. Photoshop works >>wonders for that :) >> >> >>>For an example of a pretty good effort, look at how yahoo.com indicates >>> >>> >>locales on their pages. That basic technical approach, coupled with >> >> >whatever > > >>UI beautification is needed for your site, is a pretty good way to go. >> >> >>>As for if slashcode supports Unicode, I don't know as it has been well >>> >>> >>over a year since I looked at it. How complicated that would be to do is a >>matter of conjecture - there are technical, testing, and management issues >>to consider. I have done just that with closed source code that was far >> >> >more > > >>complex then slashcode, so I am confident it could be done. That it hasn't >>been done until now (if it hasn't been done) strikes me a a combination of >>all three factors. >> >> >>>AFIK Unicode support is de rigeur for any new project that hopes to >>> >>> >scale. > > >>For any existing project that hopes to stick around with a worldwide user >>base, then the switch is going to need to be made. I think I may be >>volunteering to work with the developers to understand what the effort >> >> >level > > >>and tasks should be, so that people can sign onto them in a coherent >>fashion. But my experience is that this sort of conversion does need to be >>coordinated very closely with any other ongoing development, otherwise it >> >> >is > > >>just a fork in the code and no one wants that. Managing the codelines so >>they don't fork (or they do but they merge back together at a defined >> >> >point > > >>more likely) is something I can definitely bring to the table. >> >> >>>>"In a perfect world, the browser would accept HTML in Unicode and >>>> >>>> >display > > >>>>properly from there. For folks whose users all have modern browsers, >>>> >>>> >that > > >>is >> >> >>>>possible. The browser will make the conversion to the right character >>>>encoding locally, or it will have Unicode fonts enabled. When there are >>>>Unicode fonts available, then you get the advantage of displaying >>>> >>>> >>multiple >> >> >>>>languages on a single page, which, frankly, is what I would expect of a >>>> >>>> >>site >> >> >>>>called "towerofbabel.com", slashcode or not :)" >>>> >>>>Well, the browser isn't the problem. It's the ability of slash to be >>>> >>>> >able > > >>to >> >> >>>>deal with any character set when a story is submitted or a comment >>>> >>>> >>posted. >> >> >>>>Would those problems go away as soon as slash were dealing with all >>>> >>>> >>internal >> >> >>>>processing in Unicode? >>>> >>>> >>>Slash doesn't need to deal with any character set, it only needs to deal >>> >>> >>with one - Unicode. The modern browser should/will make conversions >> >> >to/from > > >>Unicode for both inbound and outbound data. >> >> >>>If slash is rewritten to support Unicode instead of whatever it is now >>> >>> >>(ISO-8859-1 probably?), then that is all there is to it as far as the >>database is concerned. Even templates could then be in many languages, >> >> >even > > >>within a template if so desired. >> >> >>>In your case, you probably would not need to go to subdomains unless you >>> >>> >>wanted to - you could just have slash sections for each language. And if >>someone posted Chinese on the French page, so what? slash won't care so >>neither should you. Trust me you don't want a case statement for every >>codeset dependent feature in the code. Your domain name pretty much sums >> >> >up > > >>the reason why that is the case :) >> >> >>>Best, >>> >>>Barry >>> >>> >>> >>> >> >>------------------------------------------------------- >>This SF.Net email sponsored by Black Hat Briefings & Training. >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>digital self defense, top technical experts, no vendor pitches, >>unmatched networking opportunities. Visit www.blackhat.com >>_______________________________________________ >>Slashcode-development mailing list >>Sla...@li... >>https://lists.sourceforge.net/lists/listinfo/slashcode-development >> >> >> > > > >------------------------------------------------------- >This SF.Net email is sponsored by OSTG. Have you noticed the changes on >Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, >one more big change to announce. We are now OSTG- Open Source Technology >Group. Come see the changes on the new OSTG site. www.ostg.com >_______________________________________________ >Slashcode-development mailing list >Sla...@li... >https://lists.sourceforge.net/lists/listinfo/slashcode-development > > > |
From: Malcolm L. <ma...@to...> - 2004-07-29 21:53:42
|
"Slash doesn't need to deal with any character set, it only needs to deal with one - Unicode. The modern browser should/will make conversions to/from Unicode for both inbound and outbound data. If slash is rewritten to support Unicode instead of whatever it is now (ISO-8859-1 probably?), then that is all there is to it as far as the database is concerned. Even templates could then be in many languages, even within a template if so desired." So who wants to help thread Slash with Unicode? How difficult would it be and how long would it take? Malcolm Lawrence Editor-in-Chief Babel: The multilingual, multicultural online journal and community of arts and ideas. http://www.towerofbabel.com ------------------------------------------------------------ Babel knows: It is not unpatriotic to exercise your rights and it is un-American to suggest otherwise. ------------------------------------------------------------ ----- Original Message ----- From: "Malcolm Lawrence" <ma...@to...> To: <sla...@li...>; "Barry Caplan" <bc...@i1...> Sent: Thursday, July 01, 2004 7:17 PM Subject: Re: [Slashcode-development] towerofbabel.com > "Slash doesn't need to deal with any character set, it only needs to deal > with one - Unicode. The modern browser should/will make conversions to/from > Unicode for both inbound and outbound data. If slash is rewritten to support > Unicode instead of whatever it is now (ISO-8859-1 probably?), then that is > all there is to it as far as the database is concerned. Even templates > could then be in many languages, even within a template if so desired." > > Rightio. Any other voices like to chime in about slash and Unicode? > > > Malcolm Lawrence > Editor-in-Chief > Babel: The multilingual, multicultural > online journal and community of arts and ideas. > http://www.towerofbabel.com > ------------------------------------------------------------ > Babel knows: People who don't work with their hands are parasites. > ------------------------------------------------------------ > > ----- Original Message ----- > From: "Barry Caplan" <bc...@i1...> > To: "Malcolm Lawrence" <ma...@to...>; > <sla...@li...> > Sent: Thursday, July 01, 2004 7:06 PM > Subject: Re: [Slashcode-development] towerofbabel.com > > > > At 06:23 PM 7/1/2004, Malcolm Lawrence wrote: > > > > >"I can say quite comfortably that using flags as a ui device to indicate > > >language or any other locale issue is a bad bad idea." > > > > > >True enough. I've been building the site for 8 years and am well aware of > > >all the arguments against. But until a more suitable design element can > be > > >implemented (not to mention appropriate icons for topics) they'll have to > > >do. They're pretty, too. > > > > > > Hmm. I guess I wasn't clear enough on this point. > > > > There is not one single professional localizer on the face of the earth > that would recommend flags as an UI element indicating locale. > > > > I hope that is plain enough. If not, at least it will turn up in google > for someone someday who will read why and decide to not use flags. ) > > > > The reasons, as I enumerated some of them, fall in the general category of > "They don't have a one to one relationship with what is being described" and > "users have visceral, political feelings about them, usually rightfully so". > > > > Example: I am an English speaker in the US. I sometimes see a UK Union > Jack flag which is meant to indicate English text. But does it? Or is it > something more specifically about the UK that lurks in that site? What about > people in other countries? Do I have to know their flags too? Australia's > first language is English - what flag should they use on their sites to > indicate English localization? > > > > Example: I live in Silicon Valley where > 30% of people do not speak > English as a first language at home (maybe > 50%! I forget so I will go with > the conservative value for now). So if I have content that is US locale > based, but localized into various languages such as Chinese, Spanish, > Vietnamese, etc., what flags shall I use? If not US, then what one to use > again falls into the problem just mentioned - e.g. Spanish is spoken many > places, and is not the same Spanish everywhere anymore then English is > universal. > > > > And even if I somehow choose a flag, then what if the same language is > used in a different place on the site? I surely won't be using the Taiwan > flag everywhere there is Chinese, nor the PRC flag. Except in those 2 > countries, it is hard to see which would be appropriate without offending. > > > > Finally, take a look at Canada. With 2 official languages (English and > French), what does a Maple Leaf flag say about the language of the material > behind it? Nothing at all! But it might say something very serious about > political issues you don't mean to say! > > > > The reason there are no generally accepted icons to represent locale is, > quite frankly, because there are none to be had. > > > > It is not as though people have not put a lot of thought and hard earned > experience into this, looking for a good way. They have. A lot of people and > a lot of time. > > > > If it is pretty you want, then make whatever you do pretty, whatever that > means to you. You can do that and have plain text too. Photoshop works > wonders for that :) > > > > For an example of a pretty good effort, look at how yahoo.com indicates > locales on their pages. That basic technical approach, coupled with whatever > UI beautification is needed for your site, is a pretty good way to go. > > > > As for if slashcode supports Unicode, I don't know as it has been well > over a year since I looked at it. How complicated that would be to do is a > matter of conjecture - there are technical, testing, and management issues > to consider. I have done just that with closed source code that was far more > complex then slashcode, so I am confident it could be done. That it hasn't > been done until now (if it hasn't been done) strikes me a a combination of > all three factors. > > > > AFIK Unicode support is de rigeur for any new project that hopes to scale. > For any existing project that hopes to stick around with a worldwide user > base, then the switch is going to need to be made. I think I may be > volunteering to work with the developers to understand what the effort level > and tasks should be, so that people can sign onto them in a coherent > fashion. But my experience is that this sort of conversion does need to be > coordinated very closely with any other ongoing development, otherwise it is > just a fork in the code and no one wants that. Managing the codelines so > they don't fork (or they do but they merge back together at a defined point > more likely) is something I can definitely bring to the table. > > > > >"In a perfect world, the browser would accept HTML in Unicode and display > > >properly from there. For folks whose users all have modern browsers, that > is > > >possible. The browser will make the conversion to the right character > > >encoding locally, or it will have Unicode fonts enabled. When there are > > >Unicode fonts available, then you get the advantage of displaying > multiple > > >languages on a single page, which, frankly, is what I would expect of a > site > > >called "towerofbabel.com", slashcode or not :)" > > > > > >Well, the browser isn't the problem. It's the ability of slash to be able > to > > >deal with any character set when a story is submitted or a comment > posted. > > >Would those problems go away as soon as slash were dealing with all > internal > > >processing in Unicode? > > > > Slash doesn't need to deal with any character set, it only needs to deal > with one - Unicode. The modern browser should/will make conversions to/from > Unicode for both inbound and outbound data. > > > > If slash is rewritten to support Unicode instead of whatever it is now > (ISO-8859-1 probably?), then that is all there is to it as far as the > database is concerned. Even templates could then be in many languages, even > within a template if so desired. > > > > In your case, you probably would not need to go to subdomains unless you > wanted to - you could just have slash sections for each language. And if > someone posted Chinese on the French page, so what? slash won't care so > neither should you. Trust me you don't want a case statement for every > codeset dependent feature in the code. Your domain name pretty much sums up > the reason why that is the case :) > > > > Best, > > > > Barry > > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-development > |
From: Shane <sh...@lo...> - 2004-07-26 20:35:40
|
I haven't switched - yet. The one thing that's really holding me back - ok, 2 things: 1) there still seem to be changes committed for the new code. mostly it=20= seems like it's tweaking now, but I've not had time enough to follow=20 each commit and the sf.bugs list to know exactly what's going on. 2) all my plugins need to be re-coded (some much more then others) to=20 handle this new code. This is my major hinderance, mostly because I've=20= not had time to figure out exactly how things need to be changed, nor=20 why, in each plugin's own unique situation. this is going to be time=20 consuming for me, so I'm slightly dragging me feet on it ;) But if you're going to just test a new installation, I'd say go for it,=20= and just be prepared to cvs update -dP && make install && symlink-tool -u slash -U &&=20 template-tool -u slash -U often :) Shane On Jul 24, 2004, at 3:34 PM, Alexandre Leroux wrote: > Hi - > > I read the stories about the section-topics overhaul. Planning to=20 > install (first time) & customize slashcode in the coming weeks, I'm=20 > wondering if as of today, the CVS is ready to use (the section-topics=20= > manifest is 5+ weeks old). > > Thanks ! > > A/ex :-) > > > Le 04-07-13, =E0 2:29 pm, Shane a =E9crit : >> I'm considering converting lottadot sometime this week. Any of you >> that have done the conversion, did you run into any problems/issues=20= >> that >> aren't mentioned in the upgrades file? >> >> And, just incase you don't know what I'm referring to by=20 >> "section-topics" see >> >> http://www.slashcode.com/article.pl?sid=3D04/06/11/1239258&tid=3D4 >> >> and >> >> http://slash.lottadot.com/slash/04/06/18/001233.shtml >> >> Thanks, >> Shane > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_idG21&alloc_id=10040&op=CCk > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-development > > -- One gadget to catch them all, and in digital darkness bind them. |
From: Shane <sh...@lo...> - 2004-07-26 20:29:48
|
On Jul 22, 2004, at 12:54 PM, James Marca wrote: > At approximately Wed, Jul 21, 2004 at 06:58:52AM -0400, Shane wrote: > ... >> >> One of the PITA things about Slash, for me (IMHO), has always been the >> language inside the stock theme's templates. >> > ... >> If more text/language was only shown through the getData command, it >> might have the added benefit of making internationalizing a slash >> site's text easier. Because instead of changing a ton of templates, >> you're changing the language in the data* templates (I think there may >> be error* template(s) too, I may be wrong). >> >> Any thoughts? >> > Seems like a good idea. I can think of two areas of concern. One is > performance---if you look up each bit of text, how much extra > processing has to be done? I guess that depends on whether caching is turned on our not. Probably, too, whether or not memcached and a read-only db-slave is used. > Second, modularization is always good in > theory, but it takes a lot of work. That's a big up front cost for > the Slashcode team to pay for not much benefit for them, as they don't > change the language of their templates. True. But they do a) change the code and b) want the slash-addons community to expand and increase involement. Yes, it'd be a lot of work. Painful, and ugly and not fun like creating something entirely new. (IMHO) But it'd make it easier for others try and help support the code as well. > > As to implementation, I have another suggestion. Instead of calling > the get data template with > >> Slash.getData('loginform_err2') > > Could there be one text template per one layout template, that defined > variables filled with text? Hmm, make that two. So at the top of > each (layout) template, there is one line that loads "stock" language > template, and a second one that loads "custom" language template, like > > foo is [% foo %] is undefined? > > [% PROCESS "language_$template_stock" %] > foo is [% foo %], defined in stock > > [% PROCESS "language_$template_custom" %] > foo is [% foo %], if defined in custom it overrides stock > > Custom language is empty by default, but is where you would put your > text bits that override the default. Hmmm. That seems like it'd work. I wonder what the performance difference would be. I'm guessing that if template-caching is on, there is no performance difference between either method. But if it's not on, there could be a big difference between what I was throwing out and what you're suggesting. Any comments from the OSDN guys? You guys have the most experience dealing with performance-related issues due to /. so you all could probably shed some light on this... ??? Shane |
From: James M. <jm...@tr...> - 2004-07-26 18:21:44
|
Hi all, To close the loop on my past email about images in the blob database---the problem was operator error, as usual. I've upgraded MySQL, moved to Linux 2.6, and fixed some other things. Indeed, using the INNODB engine for the blob table works (it helps if you have a version of MySQL that includes InnoDB...). One caveat is that you have to make sure that you've set up the table space properly in the my.cnf file, as noted by Eric Dannewitz below. Specifically, in my case I have 8G or so of images, so far, so I've commited three 4000M files, plus one more autoexpanding file to the InnoDB table space. I figure that should cover my needs for the next two years of digital pics (unless I get a new camera with larger data files). So if you're a nutter like I am and happen to be using Slash as a back end engine for organizing your digital pics, add an InnoDB tablespace management step to your configuration process, and then keep an eye on the InnoDB autoexpanding file to be able to add more space when it bumps up against your filesystem limit. As to serving images, I see no perceptible speed differences between fetching a filename and serving that versus fetching and serving the blob. And for processing images, I think it is a touch faster, since ImageMagick can access the binary immediately rather than having to read the file in, but again, the difference is unnoticeable. James At approximately Thu, Jun 10, 2004 at 11:20:34AM -0700, Eric Dannewitz wrote: > > So wouldn't creating a couple more datafiles solve the problem then? > > Shane wrote: > > > > > On Jun 10, 2004, at 1:40 AM, Eric Dannewitz wrote: > > > >> Wouldn't putting them into Innodb files solve the problem? > > > > > > The schema for slash::blob uses TYPE = InnoDB by default... > > > > http://cvs.sourceforge.net/viewcvs.py/slashcode/slash/plugins/Blob/ > > mysql_schema?rev=1.8&view=auto |
From: Alexandre L. <ale...@le...> - 2004-07-24 19:33:56
|
Hi - I read the stories about the section-topics overhaul. Planning to=20 install (first time) & customize slashcode in the coming weeks, I'm=20 wondering if as of today, the CVS is ready to use (the section-topics=20 manifest is 5+ weeks old). Thanks ! A/ex :-) Le 04-07-13, =E0 2:29 pm, Shane a =E9crit : > I'm considering converting lottadot sometime this week. Any of you > that have done the conversion, did you run into any problems/issues=20 > that > aren't mentioned in the upgrades file? > > And, just incase you don't know what I'm referring to by=20 > "section-topics" see > > http://www.slashcode.com/article.pl?sid=3D04/06/11/1239258&tid=3D4 > > and > > http://slash.lottadot.com/slash/04/06/18/001233.shtml > > Thanks, > Shane |
From: James M. <jm...@tr...> - 2004-07-22 16:54:30
|
At approximately Wed, Jul 21, 2004 at 06:58:52AM -0400, Shane wrote: ... > > One of the PITA things about Slash, for me (IMHO), has always been the > language inside the stock theme's templates. > ... > If more text/language was only shown through the getData command, it > might have the added benefit of making internationalizing a slash > site's text easier. Because instead of changing a ton of templates, > you're changing the language in the data* templates (I think there may > be error* template(s) too, I may be wrong). > > Any thoughts? > Seems like a good idea. I can think of two areas of concern. One is performance---if you look up each bit of text, how much extra processing has to be done? Second, modularization is always good in theory, but it takes a lot of work. That's a big up front cost for the Slashcode team to pay for not much benefit for them, as they don't change the language of their templates. As to implementation, I have another suggestion. Instead of calling the get data template with > Slash.getData('loginform_err2') Could there be one text template per one layout template, that defined variables filled with text? Hmm, make that two. So at the top of each (layout) template, there is one line that loads "stock" language template, and a second one that loads "custom" language template, like foo is [% foo %] is undefined? [% PROCESS "language_$template_stock" %] foo is [% foo %], defined in stock [% PROCESS "language_$template_custom" %] foo is [% foo %], if defined in custom it overrides stock Custom language is empty by default, but is where you would put your text bits that override the default. james |
From: Shane <sh...@lo...> - 2004-07-21 11:00:10
|
One of the PITA things about Slash, for me (IMHO), has always been the language inside the stock theme's templates. It's a problem for me when: 1. trying to keep up with the changes in CVS and keep a non-stock-theme up-to-date with the code 2. it's also been a problem when setting up sites for clients, they see some of the language and baulk at it And once you change the language, then when you diff your theme's templates against the stock-templates (to find code changes) your language changes always make the template show as changed, so you must go have a look at it. Over time this process becomes, well, painful. On to the reason for sending this... I would be interested to know how many of you have run into this as being an issue for you. Also, I was thinking that one solution would be to move as much language out of the general templates, and into the data\;*\;default template(s). An example of where this could be beneficial is the new Slash::Login plugin's template loginForm: http://cvs.sourceforge.net/viewcvs.py/slashcode/slash/plugins/Login/ templates/ Instead of [% ELSE %] Danger, Will Robinson! you'd do something like [% ELSE; Slash.getData('loginform_err2') If more text/language was only shown through the getData command, it might have the added benefit of making internationalizing a slash site's text easier. Because instead of changing a ton of templates, you're changing the language in the data* templates (I think there may be error* template(s) too, I may be wrong). Any thoughts? Shane PS - It's funny, I remember discussions over the past few years about getting the language out of the src and into the templates... :) -- One gadget to catch them all, and in digital darkness bind them. |
From: Shane <sh...@lo...> - 2004-07-17 15:58:38
|
Dunno, I've never used any of that "wiki stuff" :) I was thinking of throwing either a slash::hook into admin.pl in sub updatestory before the write to db or a call for a story::diff plugin's installed constant then just diff the introtext and bodytext from what's in the db to what's going to be written to the db. I don't think it'd be that hard to write. I think I'm going to need something like this to keep a client happy. So I was hoping someone had already written it. That doesn't seem to be the case, so if it stays rainy this weekend here maybe I'll get it done. Shane On Jul 17, 2004, at 6:57 AM, Peter Winnberg wrote: > Not me, but wasn't there a Slash wiki plugin that had revision history? > > On fre, 2004-07-16 at 17:13 -0400, Shane wrote: >> Have any of you written any mods to save either previous version(s) of >> editted stories, or something that'd do a diff of the story on_save >> and >> save the diff(s)? >> >> If so, can you share that code? >> >> Thanks, >> Shane >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by BEA Weblogic Workshop >> FREE Java Enterprise J2EE developer tools! >> Get your free copy of BEA WebLogic Workshop 8.1 today. >> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click >> _______________________________________________ >> Slashcode-development mailing list >> Sla...@li... >> https://lists.sourceforge.net/lists/listinfo/slashcode-development > -- > Peter Winnberg <pe...@op...> > Openflows Networks Ltd. > > |
From: Peter W. <pe...@op...> - 2004-07-17 10:57:35
|
Not me, but wasn't there a Slash wiki plugin that had revision history? On fre, 2004-07-16 at 17:13 -0400, Shane wrote: > Have any of you written any mods to save either previous version(s) of > editted stories, or something that'd do a diff of the story on_save and > save the diff(s)? > > If so, can you share that code? > > Thanks, > Shane > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-development -- Peter Winnberg <pe...@op...> Openflows Networks Ltd. |
From: Shane <sh...@lo...> - 2004-07-16 21:15:00
|
Have any of you written any mods to save either previous version(s) of editted stories, or something that'd do a diff of the story on_save and save the diff(s)? If so, can you share that code? Thanks, Shane |
From: Eric D. <eri...@ja...> - 2004-07-13 19:44:53
|
Thou art brave..... Please please document what you did and how it went. I would love to convert to the new code, but.......I'm scared....... Also, hopefully your wonderful CSS slash is going to work with it as well right? Shane wrote: > > I'm considering converting lottadot sometime this week. Any of you > that have done the conversion, did you run into any problems/issues that > aren't mentioned in the upgrades file? > > And, just incase you don't know what I'm referring to by > "section-topics" see > > http://www.slashcode.com/article.pl?sid=04/06/11/1239258&tid=4 > > and > > http://slash.lottadot.com/slash/04/06/18/001233.shtml > > Thanks, > Shane |
From: Shane <sh...@lo...> - 2004-07-13 18:30:35
|
I'm considering converting lottadot sometime this week. Any of you that have done the conversion, did you run into any problems/issues that aren't mentioned in the upgrades file? And, just incase you don't know what I'm referring to by "section-topics" see http://www.slashcode.com/article.pl?sid=04/06/11/1239258&tid=4 and http://slash.lottadot.com/slash/04/06/18/001233.shtml Thanks, Shane |