phpwebsite-developers

[Phpwebsite-developers] phpws Internationalisation

[Ulf H. <U1...@ul...>]

Good morning,

I finally made it on this list. To those of you who might have expecting 
me much earlier: Please excuse - I hope the birth of a daughter is 
reason enough to postpone a couple of hacking activities. ;) To those of 
you who have no idea of what I am talking about, please let me explain.

My basic motivation is that I am running a bunch of web sites based on 
phpws and that I would like to get my custom code supported. Well - you 
might say: That's what we all want. I do think though, that I am talking 
about a feature that is relatively easy to support while being the 
number one reason of large / professional web site not being efficiently 
upgradeable after once being successfully deployed. Guess what I am 
talking about...?

*Multi-Language-Capability.*

Hold on. Doesn't phpws provide that with the language module? Yes, it 
does. But, despite the great documentation of this module, I think it is 
far too complicated for the regular user to integrate some important 
core modules (such as pagemaster). This is because it is not only about 
registering related modules with the lang mod. There are lots of traps 
where the regular user will tap into if he doesn't watch out. If he 
watches out, though, he will end up with a bunch of custom code that 
will be a pain in the neck to re-apply once new phpws versions get released.

*So what can be done?*

First, I think that things like

http://sourceforge.net/tracker/?func=detail&aid=958502&group_id=15539&atid=315539
http://sourceforge.net/tracker/?func=detail&aid=942393&group_id=15539&atid=315539
http://sourceforge.net/tracker/?func=detail&aid=942365&group_id=15539&atid=315539

should make it into the supported code of related core mods. Secondly, I 
think that there should be a recommendation that phpws mods should be 
tested regarding their lang mod integratability, ideally related code 
would be already shipped with the mods and could be activated by a flag. 
I am offering to help coordinating this effort and to provide sort of 
I18N feedback to mod developers. If I knew who they are ....

... - which brings me to the third activity I'd like to initiate: A more 
structured family of web sites where information like this can easily be 
found by the regular user. I think I am an experienced web user, but I 
often found myself lost in the large world of phpws-support-sites.

I have been talking to Kenneth Poulsen about this (so far with no 
success - maybe my baby break is the reason). A key benefit is that this 
effort can leverage the multi-language activities that I described 
above: By providing one multi-lingual core site that uses great phpws 
features like branches etc. (1) to integrate other supported sites and 
(2) to show everybody out there the great things that can be done with a 
system that deserves to be the number one php framework in the world.

I promise that this was my first and last long email ito this list. If 
you think that what I am saying makes sense and if you have an idea 
about how to proceed - please contact me.

Cheers, and greetings from Munich

Ulf


http://www.ulftopia.com/vita_e.html

[Phpwebsite-developers] Re: phpws Internationalisation

[Mike N. <mh...@us...>]

On Wed, 2004-06-30 at 10:05, Ulf Hallmann wrote:
> My basic motivation is that I am running a bunch of web sites based on
> phpws and that I would like to get my custom code supported. Well -
> you might say: That's what we all want.

Ulf,
This is why the phpwebsite-comm project was started. It provides a place
for community members to work on their ideas. It also provides a place
for the ASU team to review content for inclusion in phpwebsite releases.


> Multi-Language-Capability.

Most of the current functionality in phpwebsite is l10n. The underlying
support for i18n isn't implemented yet. i18n requires underlying
structure support from database, web server, php code, xhtml, and css to
function properly.

> 
> First, I think that things like 
> http://sourceforge.net/tracker/?func=detail&aid=958502&group_id=15539&atid=315539
> http://sourceforge.net/tracker/?func=detail&aid=942393&group_id=15539&atid=315539
> http://sourceforge.net/tracker/?func=detail&aid=942365&group_id=15539&atid=315539
> should make it into the supported code of related core mods. Secondly,
> I think that there should be a recommendation that phpws mods should
> be tested regarding their lang mod integratability, ideally related
> code would be already shipped with the mods and could be activated by
> a flag. I am offering to help coordinating this effort and to provide
> sort of I18N feedback to mod developers. If I knew who they are ....
> 
> ... - which brings me to the third activity I'd like to initiate: A
> more structured family of web sites where information like this can
> easily be found by the regular user. I think I am an experienced web
> user, but I often found myself lost in the large world of
> phpws-support-sites.

I'm going to setup a wiki (mediawiki) for phpwebsite-comm. I hope
everyone can contribute to the knowledge base.
> 
> I have been talking to Kenneth Poulsen about this (so far with no
> success - maybe my baby break is the reason). A key benefit is that
> this effort can leverage the multi-language activities that I
> described above: By providing one multi-lingual core site that uses
> great phpws features like branches etc. (1) to integrate other
> supported sites and (2) to show everybody out there the great things
> that can be done with a system that deserves to be the number one php
> framework in the world.

With your assistance we can work on this goal at phpwebsite-comm.

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

[Phpwebsite-developers] Re: phpws Internationalisation

[Matthew M. <ma...@tu...>]

> To those of you who might have expecting me much earlier: Please
> excuse - I hope the birth of a daughter is reason enough to postpone a
> couple of hacking activities. ;)

We'll let it slide.

> My basic motivation is that I am running a bunch of web sites based on
> phpws and that I would like to get my custom code supported.

That's what you all want!

>  Well - you might say: That's what we all want.

oh... nevermind.

> Multi-Language-Capability.
> 
> Hold on. Doesn't phpws provide that with the language module? Yes, it
> does. But, despite the great documentation of this module, I think it
> is far too complicated for the regular user to integrate some
> important core modules (such as pagemaster).

You are being far too kind. The language support stinks.

> So what can be done?

Here is what _will_ be done in 0.9.4.

1) Language will not be handled by a module. It will be handled by PO
files: http://www.gnu.org/software/gettext/gettext.html
PO files are widely used and there are several editors for them.

2) A i18n push. Before 0.9.4 comes out officially, we will ask
translators to try and use the po file format. Once the volunteers sign
off on it, we will work on creating a depository of translation files.

3) We will try and make sure that anglo-oriented functions like date()
are replaced with i18n friendly functions (like strftime() ).

> Secondly, I think that there should be a recommendation that phpws
> mods should be tested regarding their lang mod integratability,
> ideally related code would be already shipped with the mods and could
> be activated by a flag. I am offering to help coordinating this effort
> and to provide sort of I18N feedback to mod developers. If I knew who
> they are ....

I think that is sound. Once 0.9.4 comes out, I suggest a module page
that includes information on what version it is running, when the last
update was, and what languages it supports. 

> ... - which brings me to the third activity I'd like to initiate: A
> more structured family of web sites where information like this can
> easily be found by the regular user. I think I am an experienced web
> user, but I often found myself lost in the large world of
> phpws-support-sites.

I would like to see that as well. However, and this is not to slight you
Ulf, but there have been MANY people who have offered their help only to
quietly fade away. Some stick around (Mike, Kenneth, Don, Shaun, and
others I am leaving out) but most get busy with other things.

So, while I would welcome this level of support, it really is dependent
on the community. We help when we can, but we have to concentrate on
programming and, more importantly, our duty to the university (who pay
us). 

Welcome to the community, and we hope to hear more from you in the
future. I would also ask that you stay tuned for the 0.9.4 release so we
can make a smooth translation transition.

Best regards,
Matt

-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
http://phpwebsite.appstate.edu
http://ess.appstate.edu

[Phpwebsite-developers] textSettings.php for multiple branches?

[Tony M. <cl...@us...>]

I have an interesting dilemma.  I have multiple sites as branch sites off 
of my hub code.  They are sharing the same textSettings.php it seems.  So 
there doesn't appear to be a way to customize the "censoring" and allowed 
tags for each branch.

I have one site: http://www.manlymen.org which has a little more "lenient" 
language restriction than http://www.bsacjc.org :))  I'd like to be able 
to customize these a little better.

Thanks for any input you can offer.

-Tony  

-- 
Hometown Enterprises Internet Services
Professional, affordable web design and hosting.
http://www.hteis.com/

Re: [Phpwebsite-developers] textSettings.php for multiple branches?

[Shaun M. <sh...@ae...>]

On 30 Jun 2004, at 21:24, Tony Miller wrote:

> I have an interesting dilemma.  I have multiple sites as branch sites 
> off
> of my hub code.  They are sharing the same textSettings.php it seems.  
> So
> there doesn't appear to be a way to customize the "censoring" and 
> allowed
> tags for each branch.

That's the case currently. Also, datesettings, imagetypes, thumbnail 
sizes, image sizes and a bunch of other things are all global instead 
of local to the branches as many are either picked up from the /conf/ 
directory in the main branch or from /mod/xxx/conf/ for each module. 
There's a long standing RFE for at least some of those to be changed.

conf files that can not be overridden by settings configured by a web 
config are evil, IMHO. They are often overlooked, unknown and easily 
overwritten when upgrading a module.

Shaun
aegis design - http://www.aegisdesign.co.uk

[Phpwebsite-developers] Re: phpws Internationalisation

[Fabio E. <nfe...@so...>]

> 1) Language will not be handled by a module. It will be handled by PO
> files: http://www.gnu.org/software/gettext/gettext.html
> PO files are widely used and there are several editors for them.
>
> 2) A i18n push. Before 0.9.4 comes out officially, we will ask
> translators to try and use the po file format. Once the volunteers sign
> off on it, we will work on creating a depository of translation files.
>

Hi all, thanks Ulf you have been a great help to me lately.

With respect to 0.9.4 how will it then handel the dynamic content?  This
is a very import issue for me and my leave me behind at 0.9.3-3 for ever.

Just as background to what I'm up to.  I'm trying to get phpws used at my
work (Government of Canada) for several projects.  We've offer by law all
services to public servents and the public in both official languages. No
mixing of languages.

Thanks to the University and all of you for phpwebsite.

Fabio