Menu
▾
▴
phpwiki-talk
|
From: Jan N. <ja...@gn...> - 2000-10-01 21:49:25
|
On Sunday, 1 October 2000, Steve Wainstead writes:
> The patch files were over 40K, which made the listserv hold them for
> approval. I upped the msg size limit to 100K.
Ok, didn't know/check it was so big already.
> I'm siding with Arno on the ease of installation issue, which has been a
> major concern of mine since version 0.01 back in December. It should be as
> easy as tar -xzvf <phpwiki tarball> and it runs on any GNU/Linux or BSD
> system.
Sure, if you think that's needed. Arno had a simple (=good) idea that
I stole so that my last patch will allow this, although only php4 user
get the ``better'' implementation. The legacy php3 support can later
be dropped at any time.
> When we say "users" of PhpWiki we usually mean "the people who install and
> maintain the Wiki," i.e. the sysadmins and programmers. It's my belief
> that the easier it is to use (install) the more readily accepted it is;
Ok. Wouldn't it help if we made wiki_config.php3 a lot smaller,
and make type of database selectable by a single variable, something
like:
<?php3
$DataBase = "dbm"; # "mysql", "pgsql", "msql"
$DatabaseDir = "/tmp"; # only used by DBM
$DatabaseName = "wiki"; # only used by
$DatabaseUser = "wiki";
$DatabasePass = "";
$LANG = "C";
// you probably don't need to change these
$DatabaseServer = "localhost";
$DatabasePort = "5432"; # only used by pgsql
...
?>
This gets included by index.php3, which also includes the relevant
db config.
Also, why don't we make RedHat and debian packages. That should make
install both easy, and OK for no-messing-with-my-package-system people.
apt-get install phpwiki
is a lot simpler than surfing the internet for a wiki's most recent
tarball, handconfigure it, etc.
Greetings,
Jan.
--
Jan Nieuwenhuizen <ja...@gn...> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
|
|
From: Jan N. <ja...@gn...> - 2000-10-01 22:02:33
|
On Sunday, 1 October 2000, Arno Hollosi writes:
> So I installed the gettext package and your script runs ok now.
> Ok, maybe we should use gettext to automatically produce files
> for the translators. But I would still use hash-tables for phpwiki
> (generated automatically from those .po files if you like).
>
> Apart from avoiding duplicate information (.mo and .php3 files) and being
Ok, that's a valid reason. A reason to use gettext tools would be
that you could have them translated by the GNU translation project.
However, maybe that's all a bit overdone, because there are so few
strings in php code...
> How can you have per-visitor localization?
[snip -- would be real cool]
> Or is this feature too far off the mark?
Yes, I pondered about that too, esp. wrt to the RecentChanges page.
I don't think it would be worth the effor: you'd get 'EditText'
instead of 'VeranderText' when you visit a dutch wiki, but all
pages would still be in dutch. I think localisation on a per-wiki
basis would be ok.
> On a side note: I think all files for translators should be moved into
> a "translator" directory: currently that is translate.sh and the files in the
+
> po directory. That way one can easily delete stuff unnecessary for running
> the wiki.
Otoh, it's non standard, so people might wonder how it all works.
> And I don't understand why we need wiki_linguas.php3. Either the pagename
Duh. I think that I goofed on that one. It's probably that I kept
seeing things like EditText, before I translated the templates.
It would be good if the templates were gettextised too, so that there'd
only be the .po's and the pgsrc's.
Greetings,
Jan.
--
Jan Nieuwenhuizen <ja...@gn...> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
|
|
From: Arno H. <aho...@in...> - 2000-10-02 05:14:44
|
>Ok, that's a valid reason. A reason to use gettext tools would be >that you could have them translated by the GNU translation project. >However, maybe that's all a bit overdone, because there are so few >strings in php code... Hm, yes. I'm still not 100% convinced but could accept it in its dual form (mo + php3). Btw, you didn't localize all strings yet. E.g. wiki_search is missing. >> On a side note: I think all files for translators should be moved into >> a "translator" directory: currently that is translate.sh and the files in >> the po directory. That way one can easily delete stuff unnecessary for >> running the wiki. > >Otoh, it's non standard, so people might wonder how it all works. I think you misunderstood. It would still be in the tarball, but users could then more easily delete files not necessary for a running wiki. >It would be good if the templates were gettextised too, so that there'd >only be the .po's and the pgsrc's. Hm, that would mean making php files out of the templates? The nice thing right now is that GeneratePage() produces the entire page in one string. php-templates would make this more complicated. Or is there a way around this? /Arno p.s. I'm again gone for some days - so don't expect immediate replies to further emails. |
|
From: Jan N. <ja...@gn...> - 2000-10-02 07:27:21
|
On Monday, 2 October 2000, Arno Hollosi writes:
> Hm, yes. I'm still not 100% convinced but could accept it in its dual form
> (mo + php3). Btw, you didn't localize all strings yet. E.g. wiki_search is
> missing.
Yes, I wanted to see first if this got in. I'll see to the remaining
strings and pages.
> Hm, that would mean making php files out of the templates?
Yes, it's a trade-off. Maybe just do a gettext () on the template
$page = gettext (join('', file($templates[$template])));
(doesn't make sense on a per line basis, I guess? Then we'd have
only the pgrsrc as extra, which would be quite accepteble.
Greetings,
Jan.
--
Jan Nieuwenhuizen <ja...@gn...> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
|
|
From: Jan N. <ja...@gn...> - 2000-10-02 07:33:16
|
On Sunday, 1 October 2000, Steve Wainstead writes: > Yes, it's been on my mind for a while but haven't gotten around to it. The > section the admin edits could be shortened and made a lot clearer. Ok. > Do you volunteer? ;-) Maybe I'll make a debian package, but I don't have the time to adopt packages for debian. If you want a redhat package you'll have to ask me real nice, because I don't have use for that myself :-) Jan. -- Jan Nieuwenhuizen <ja...@gn...> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org |
|
From: Steve W. <sw...@wc...> - 2000-10-01 22:41:38
|
On Sun, 1 Oct 2000, Jan Nieuwenhuizen wrote: > Ok. Wouldn't it help if we made wiki_config.php3 a lot smaller, > and make type of database selectable by a single variable, something > like: > > <?php3 > > $DataBase = "dbm"; # "mysql", "pgsql", "msql" > > $DatabaseDir = "/tmp"; # only used by DBM > $DatabaseName = "wiki"; # only used by > $DatabaseUser = "wiki"; > $DatabasePass = ""; > $LANG = "C"; > > > // you probably don't need to change these > $DatabaseServer = "localhost"; > $DatabasePort = "5432"; # only used by pgsql > ... > > ?> > > This gets included by index.php3, which also includes the relevant > db config. Yes, it's been on my mind for a while but haven't gotten around to it. The section the admin edits could be shortened and made a lot clearer. > Also, why don't we make RedHat and debian packages. That should make > install both easy, and OK for no-messing-with-my-package-system people. > > apt-get install phpwiki > > is a lot simpler than surfing the internet for a wiki's most recent > tarball, handconfigure it, etc. Do you volunteer? ;-) sw ...............................ooo0000ooo................................. Hear FM quality freeform radio through the Internet: http://wcsb.org/ home page: www.wcsb.org/~swain |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X