Thread: [PHPiCalendar-DEV] 0.8.1

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Want to ship 0.8.1?

-C

We could if you like. I won't be able to work on it tonight because I 
have other things to do so now is as good a time as ever. There are 
quite a few bug fixes, and that's about all that there is. I will make 
sure everything I have done is commited (pretty sure it is, just gotta 
double check), including a 0.8.1 section in the README.

-Jared

On Saturday, November 2, 2002, at 01:02  AM, Chad wrote:

> Want to ship 0.8.1?
>
> -C
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

Well I wanted to get out a maint release since 0.9 will probably be a 
bit. Ive already started the README as you can probably tell. Let me 
know when your ready and I'll package it up.

-C

On Saturday, November 2, 2002, at 08:03  AM, Jared wrote:

> We could if you like. I won't be able to work on it tonight because I 
> have other things to do so now is as good a time as ever. There are 
> quite a few bug fixes, and that's about all that there is. I will make 
> sure everything I have done is commited (pretty sure it is, just gotta 
> double check), including a 0.8.1 section in the README.
>
> -Jared
>
> On Saturday, November 2, 2002, at 01:02  AM, Chad wrote:
>
>> Want to ship 0.8.1?
>>
>> -C
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
>> handheld. Power & Color in a compact size!
>> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
>> _______________________________________________
>> Phpicalendar-devel mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

It's fine. go for it.

-Jared

On Saturday, November 2, 2002, at 11:06  AM, Chad wrote:

> Well I wanted to get out a maint release since 0.9 will probably be a 
> bit. Ive already started the README as you can probably tell. Let me 
> know when your ready and I'll package it up.
>
> -C
>
> On Saturday, November 2, 2002, at 08:03  AM, Jared wrote:
>
>> We could if you like. I won't be able to work on it tonight because I 
>> have other things to do so now is as good a time as ever. There are 
>> quite a few bug fixes, and that's about all that there is. I will 
>> make sure everything I have done is commited (pretty sure it is, just 
>> gotta double check), including a 0.8.1 section in the README.
>>
>> -Jared
>>
>> On Saturday, November 2, 2002, at 01:02  AM, Chad wrote:
>>
>>> Want to ship 0.8.1?
>>>
>>> -C
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
>>> handheld. Power & Color in a compact size!
>>> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
>>> _______________________________________________
>>> Phpicalendar-devel mailing list
>>> Php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
>> handheld. Power & Color in a compact size!
>> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
>> _______________________________________________
>> Phpicalendar-devel mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

Hi ,
Can I propose to make some improvements in phpiCalendar ?

- to move the $week_start_day into the language pack. The reason is, 
only in UK and US the sunday is the first week day. In the rest of the 
world (especially in Europe and Africa) it's monday...

This thing done, the $week_start_day would be $language dependent. If 
in Australia, weeks start on monday (an example) we could imaging a 
australian.inc.php and so on...

And then we could add a Pop Up menu : View this page in "English, 
french, german..." The prefered language will be cookied into the 
visitor browser, so this visitor will be able to see the whole calendar 
without having to change his language again.

$cookie_language (in user's browser) override the $language preference 
set in the config.inc.php  So the language is no more stuck to the 
config.inc.php configuration.

Are you OK with this ? If you are, I can be charged of this.

Small cosmetic bug: can we set the width of the left column in the 
bottom table with this month event (file month_bottom.php lines 343, 
345, 395) to 200 instead of 160 ? In some language set (french, 
swedish, polish, ...) the all-day-event are split in 2 lines... This 
will prevent it.

The problem I see with that is adding even more language files (like 
AUS) for no real reason. Providing all the *most common* configuration 
options in the config file is what I'd like to keep. Having to tell 
someone to look in the language file for their start week time seems to 
be a bit user-unfriendly. I'd like them to only have to touch one file. 
You could perhaps have it in both places, blank in the config but if 
the user sets it there, it overrides whats in the language file. :-)

For 0.9 I've been planning a 'Preferences' page that will solve 
hopefully all these issues.

In it (set by cookie):

Set your default view
Set your default calendar
Set your default start time, start day
Set your language
FTP up new calendars (user, pass required).
Selection box of overlaying of multiple calendars (might be possible, 
don't know about coloring).

Jared and I have been working on PHP iCalendar now for almost 2 months 
straight and need some time to relax. This also gives us time to really 
discuss some of the bigger feature requests people make.

Go ahead and fix the month width if you like.

On Wednesday, November 6, 2002, at 11:34  AM, Michel wrote:

> Hi ,
> Can I propose to make some improvements in phpiCalendar ?
>
> - to move the $week_start_day into the language pack. The reason is, 
> only in UK and US the sunday is the first week day. In the rest of the 
> world (especially in Europe and Africa) it's monday...
>
> This thing done, the $week_start_day would be $language dependent. If 
> in Australia, weeks start on monday (an example) we could imaging a 
> australian.inc.php and so on...
>
> And then we could add a Pop Up menu : View this page in "English, 
> french, german..." The prefered language will be cookied into the 
> visitor browser, so this visitor will be able to see the whole 
> calendar without having to change his language again.
>
> $cookie_language (in user's browser) override the $language preference 
> set in the config.inc.php  So the language is no more stuck to the 
> config.inc.php configuration.
>
> Are you OK with this ? If you are, I can be charged of this.
>
>
> Small cosmetic bug: can we set the width of the left column in the 
> bottom table with this month event (file month_bottom.php lines 343, 
> 345, 395) to 200 instead of 160 ? In some language set (french, 
> swedish, polish, ...) the all-day-event are split in 2 lines... This 
> will prevent it.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

Chad wrote :

> The problem I see with that is adding even more language files (like 
> AUS) for no real reason. Providing all the *most common* configuration 
> options in the config file is what I'd like to keep. Having to tell 
> someone to look in the language file for their start week time seems 
> to be a bit user-unfriendly. I'd like them to only have to touch one 
> file. You could perhaps have it in both places, blank in the config 
> but if the user sets it there, it overrides whats in the language 
> file. :-)

Chad, most of the time, Start day and language are tied together. 
Australian was a really bad example as ALL the english speaking country 
have their week begining with monday. And I don't think there is any 
incompatibility beetween language and start day.

So why including the 24/12 time format in the language pack ? We're 
speaking about the same Week/Time specification linked to the language.

I promised, Chad, this is a good idea. And something less to configure 
installing phpiCal...

Mike.

Most of the time, but not all the time. It would cause more problems 
than it would solve, in my opinion. Any of those languages that 
originate from countries where the start of the week is Monday wouldn't 
work in America, for example. Whether someone wants to view a language 
other than English in America shouldn't affect the importance of Sunday 
being our consistent start day.

This is why, despite localization, Apple has chosen iCal to have a 
separate preference for the week start day. As Chad said, we could put 
a default value in the language file with the option to change it in 
the config file.

It might be best to start doing our language files as en_US or en_UK 
and things like that. After all, the wording and spelling of English 
words will change. As for other languages, I'm not sure how much they 
change, but English has major differences. Maybe we should just do it 
for the few languages where it truly matters, by putting a 
"-COUNTRYCODE" after it. Like "english-us.inc.php". Either that, or the 
config file will become more cryptic for that setting. If there is a 
prefs page to build the file, (or however Chad is thinking of 
implementing prefs), then it wouldn't be such an issue.

-Jared

On Wednesday, November 6, 2002, at 02:15  PM, Michel wrote:

> Chad wrote :
>
>> The problem I see with that is adding even more language files (like 
>> AUS) for no real reason. Providing all the *most common* 
>> configuration options in the config file is what I'd like to keep. 
>> Having to tell someone to look in the language file for their start 
>> week time seems to be a bit user-unfriendly. I'd like them to only 
>> have to touch one file. You could perhaps have it in both places, 
>> blank in the config but if the user sets it there, it overrides whats 
>> in the language file. :-)
>
>
> Chad, most of the time, Start day and language are tied together. 
> Australian was a really bad example as ALL the english speaking 
> country have their week begining with monday. And I don't think there 
> is any incompatibility beetween language and start day.
>
> So why including the 24/12 time format in the language pack ? We're 
> speaking about the same Week/Time specification linked to the > language.
>
> I promised, Chad, this is a good idea. And something less to configure 
> installing phpiCal...
>
> Mike.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

If we do this both ways, it still allows simple configuration changes 
by the end user, plus now most languages won't have to set their option 
-- which is what Mike wants.

So change all the languages to have their own 'default' week start, and 
have an option in config.inc.php to override whatever may be in the 
language file.

True could be said for the time format. I liked the '12' or '24' option 
in the config.

-C

On Wednesday, November 6, 2002, at 12:58  PM, Jared wrote:

> Most of the time, but not all the time. It would cause more problems 
> than it would solve, in my opinion. Any of those languages that 
> originate from countries where the start of the week is Monday 
> wouldn't work in America, for example. Whether someone wants to view a 
> language other than English in America shouldn't affect the importance 
> of Sunday being our consistent start day.
>
> This is why, despite localization, Apple has chosen iCal to have a 
> separate preference for the week start day. As Chad said, we could put 
> a default value in the language file with the option to change it in 
> the config file.
>
> It might be best to start doing our language files as en_US or en_UK 
> and things like that. After all, the wording and spelling of English 
> words will change. As for other languages, I'm not sure how much they 
> change, but English has major differences. Maybe we should just do it 
> for the few languages where it truly matters, by putting a 
> "-COUNTRYCODE" after it. Like "english-us.inc.php". Either that, or 
> the config file will become more cryptic for that setting. If there is 
> a prefs page to build the file, (or however Chad is thinking of 
> implementing prefs), then it wouldn't be such an issue.
>
> -Jared
>
> On Wednesday, November 6, 2002, at 02:15  PM, Michel wrote:
>
>> Chad wrote :
>>
>>> The problem I see with that is adding even more language files (like 
>>> AUS) for no real reason. Providing all the *most common* 
>>> configuration options in the config file is what I'd like to keep. 
>>> Having to tell someone to look in the language file for their start 
>>> week time seems to be a bit user-unfriendly. I'd like them to only 
>>> have to touch one file. You could perhaps have it in both places, 
>>> blank in the config but if the user sets it there, it overrides 
>>> whats in the language file. :-)
>>
>>
>> Chad, most of the time, Start day and language are tied together. 
>> Australian was a really bad example as ALL the english speaking 
>> country have their week begining with monday. And I don't think there 
>> is any incompatibility beetween language and start day.
>>
>> So why including the 24/12 time format in the language pack ? We're 
>> speaking about the same Week/Time specification linked to the > 
>> language.
>>
>> I promised, Chad, this is a good idea. And something less to 
>> configure installing phpiCal...
>>
>> Mike.
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
>> handheld. Power & Color in a compact size!
>> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
>> _______________________________________________
>> Phpicalendar-devel mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

Jared wrote :

> This is why, despite localization, Apple has chosen iCal to have a 
> separate preference for the week start day. As Chad said, we could put 
> a default value in the language file with the option to change it in 
> the config file.

Sorry to insist on that point because it's the only point that remain 
preventing us adding a language view feature in phpiCal.

Apple start day of the week in iCal works in the main window doesn't 
work in the month calendar view on the left side.

But it works very well in phpiCal. ;-)

Maybe because in Apple's iCal, start day of the week is hard coded in 
the mainframe function. The only reason why Apple choose to put start 
day of the week in iCal pref is because nowhere in the main System 
preferences such a feature is present. The reason is because Calendar 
functions or programs were not present in previous system versions and 
iCal has been released after Jaguar. But that preference could have 
been already set in the Language pref. NONE english country have their 
start day of the week other that sunday, NONE french, german or italian 
speaking country have their start day other than monday. It's like 
24/12 format time or metric system: it's stuck to the language. You 
have to know that foreign country with english as primary language 
(like in africa), they adopt the same habits as in US or OK: non metric 
system, 12 time format, and sunday as start day of the week.

So forget my Australian example. That was a bad idea. There is no 
exception, or souldn't be.

But if config.inc.php override the language pref as Chad proposed we 
will lost all the benefit. The best is to invite webmaster to change a 
" custom.inc.php " file in the language directory and set this file as 
prefered language in his conf.inc.php if no language file correspond to 
their need (if ever).  So visitors will have the possibility to change 
their language view. And with their $_cookie_pref_language, phpical 
will be able to display the week days as desired.

Mike. 

On Thursday, November 7, 2002, at 02:29  AM, Michel wrote:

> NONE english country have their start day of the week other that 
> sunday, NONE french, german or italian speaking country have their 
> start day other than monday.

What about Canada? They speak both French and English. There week start 
is on Sunday, isn't it? Even in Quebec?

> It's like 24/12 format time or metric system: it's stuck to the 
> language. You have to know that foreign country with english as 
> primary language (like in africa), they adopt the same habits as in US 
> or OK: non metric system, 12 time format, and sunday as start day of 
> the week.

I disagree. It's not stuck to the language but rather the country. The 
US has the week start on Sunday. If someone in the US prefers their 
calendars to be viewed in French or German, why should the week start 
be on Monday? The calendar is still a US calendar.

It is very common for a language to be stuck to a country as well, but 
they aren't tied as tightly together and bilingual people might want to 
choose.

For me, I'm learning Japanese. Neither of our solutions will affect me 
as Japan has a week start of Sunday too so either way it'll work. I 
want it to work for everyone, though.

Now, your idea to have some other custom.inc.php or something might 
work. However, I'd rather the visitor get to choose which language to 
view it in and the system admin get to choose the week start. If we 
implement a good multi-user system, all this will be solved as each 
user will be able to choose their own settings. Any visitor might be 
able to change the language, but the start week is something fixed to 
the creator of the calendar, as that is the layout of the calendar to 
that person.

I dunno, it's all very confusing, but I do want a good implementation 
when this is all done so we have to come up with something sound.

-Jared

Jared wrote :

> I disagree. It's not stuck to the language but rather the country. The 
> US has the week start on Sunday. If someone in the US prefers their 
> calendars to be viewed in French or German, why should the week start 
> be on Monday? The calendar is still a US calendar.

This is your point of view. But remember: start week of the day doesn't 
affect the calendar results themselves! It's just for VIEWERS' 
convenience, just to fit people's mind. Just like translation or 24/12. 
So why stuck 24/12 in the language file and not week days ? 24h is not 
part of the US calendar and someone watching your calendar with "French 
view" would see 18h30: Japanese. Even if he lives in the US and is used 
to 12h time format. That's the same thing. Week days are just something 
everyone learn at school and are used to. So if you, Jared, come to 
France, you will be a little confused to see a french week view even 
with english day manes on it if you choosed the "US view". Because it's 
not convient for you.

> It is very common for a language to be stuck to a country as well, but 
> they aren't tied as tightly together and bilingual people might want 
> to choose.

For bilingual persons it's another deal. Not a big deal, because 
they're used to see both ways of displaying calendars. When french 
speaking Quebec people, and they're numerous, come to our websites 
hosted in France, they're used to see things the French way: 24, metric 
system, Euro, monday, etc... When they surf on US website they see 
thing differently. Quebec webmaster, will be able to have a custom 
mixed French/12h/sunday calendar with the custom.inc.php file I 
mentioned for the convenience of their Quebec visitors. It's still up 
to the webmaster!

That's a very little thing to change, and that would allow "Prefered 
view language" feature. Without that change, "Prefered view language" 
feature is a nonsense and is useless too.

Mike. 

There isn't any reason these cannot be three tiered.

cookie takes precedence over config and lang file
config takes precedence over lang file
if neither, lang file is used

I don't see why this wouldn't solve all problems. User selects a 
language to view in, it falls to the start day in the file, but if they 
still want they can change it with their cookie. The admin can set what 
they want in the config if they want to override our defaults.

-C

On Thursday, November 7, 2002, at 02:27  AM, Mike wrote:

> Jared wrote :
>
>> I disagree. It's not stuck to the language but rather the country. 
>> The US has the week start on Sunday. If someone in the US prefers 
>> their calendars to be viewed in French or German, why should the week 
>> start be on Monday? The calendar is still a US calendar.
>
> This is your point of view. But remember: start week of the day 
> doesn't affect the calendar results themselves! It's just for VIEWERS' 
> convenience, just to fit people's mind. Just like translation or 
> 24/12. So why stuck 24/12 in the language file and not week days ? 24h 
> is not part of the US calendar and someone watching your calendar with 
> "French view" would see 18h30: Japanese. Even if he lives in the US 
> and is used to 12h time format. That's the same thing. Week days are 
> just something everyone learn at school and are used to. So if you, 
> Jared, come to France, you will be a little confused to see a french 
> week view even with english day manes on it if you choosed the "US 
> view". Because it's not convient for you.
>
>
>
>> It is very common for a language to be stuck to a country as well, 
>> but they aren't tied as tightly together and bilingual people might 
>> want to choose.
>
> For bilingual persons it's another deal. Not a big deal, because 
> they're used to see both ways of displaying calendars. When french 
> speaking Quebec people, and they're numerous, come to our websites 
> hosted in France, they're used to see things the French way: 24, 
> metric system, Euro, monday, etc... When they surf on US website they 
> see thing differently. Quebec webmaster, will be able to have a custom 
> mixed French/12h/sunday calendar with the custom.inc.php file I 
> mentioned for the convenience of their Quebec visitors. It's still up 
> to the webmaster!
>
> That's a very little thing to change, and that would allow "Prefered 
> view language" feature. Without that change, "Prefered view language" 
> feature is a nonsense and is useless too.
>
> Mike.
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

By default $week_start_day could be set to "Same as Language" and then 
it would use the one from the language file. Otherwise, the language 
file wouldn't reset that var.

Would that be acceptable?

-Jared

On Thursday, November 7, 2002, at 10:45  AM, Chad wrote:

> There isn't any reason these cannot be three tiered.
>
> cookie takes precedence over config and lang file
> config takes precedence over lang file
> if neither, lang file is used
>
> I don't see why this wouldn't solve all problems. User selects a 
> language to view in, it falls to the start day in the file, but if 
> they still want they can change it with their cookie. The admin can 
> set what they want in the config if they want to override our > defaults.
>
> -C
>
>
> On Thursday, November 7, 2002, at 02:27  AM, Mike wrote:
>
>> Jared wrote :
>>
>>> I disagree. It's not stuck to the language but rather the country. 
>>> The US has the week start on Sunday. If someone in the US prefers 
>>> their calendars to be viewed in French or German, why should the 
>>> week start be on Monday? The calendar is still a US calendar.
>>
>> This is your point of view. But remember: start week of the day 
>> doesn't affect the calendar results themselves! It's just for 
>> VIEWERS' convenience, just to fit people's mind. Just like 
>> translation or 24/12. So why stuck 24/12 in the language file and not 
>> week days ? 24h is not part of the US calendar and someone watching 
>> your calendar with "French view" would see 18h30: Japanese. Even if 
>> he lives in the US and is used to 12h time format. That's the same 
>> thing. Week days are just something everyone learn at school and are 
>> used to. So if you, Jared, come to France, you will be a little 
>> confused to see a french week view even with english day manes on it 
>> if you choosed the "US view". Because it's not convient for you.
>>
>>
>>
>>> It is very common for a language to be stuck to a country as well, 
>>> but they aren't tied as tightly together and bilingual people might 
>>> want to choose.
>>
>> For bilingual persons it's another deal. Not a big deal, because 
>> they're used to see both ways of displaying calendars. When french 
>> speaking Quebec people, and they're numerous, come to our websites 
>> hosted in France, they're used to see things the French way: 24, 
>> metric system, Euro, monday, etc... When they surf on US website they 
>> see thing differently. Quebec webmaster, will be able to have a 
>> custom mixed French/12h/sunday calendar with the custom.inc.php file 
>> I mentioned for the convenience of their Quebec visitors. It's still 
>> up to the webmaster!
>>
>> That's a very little thing to change, and that would allow "Prefered 
>> view language" feature. Without that change, "Prefered view language" 
>> feature is a nonsense and is useless too.
>>
>> Mike.
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
>> handheld. Power & Color in a compact size!
>> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
>> _______________________________________________
>> Phpicalendar-devel mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
> handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

Everyone can take a look at my version with the "View in..." pop menu...

http://LaShampoo.net/iCal

Basically, the prefered language is the default language set by the=20
webmaster (here it's french). Then if the visitor (you) change the=20
prefered language, the language is set in the visitor cookies. The=20
visitor can then browse the entire calendar with his prefered language.=20=

The $week_start_day is set in the language file (I try to set the=20
proper $week_start_day in every language file).

Chad wrote :

> cookie takes precedence over config and lang file
> config takes precedence over lang file
> if neither, lang file is used

How do you set the "Start week day" cookie ? Is there a pop menu "Start=20=

Day Week" ? We still have to respond to that question.

Jared wrote :

> By default $week_start_day could be set to "Same as Language" and then=20=

> it would use the one from the language file. Otherwise, the language=20=

> file wouldn't reset that var. Would that be acceptable?

Yes. That would be more acceptable. But best is to add an=20
$prefered_start_day in the config file:

=AB $prefered_start_day =3D '' // If the start week day in your language=20=

file don't fit your need, please do change this variable to the desired=20=

day otherwise leave blank. =BB

Explanations: if the visitor use the same language as the webmaster and=20=

the webmaster didn't like the default settings set in the language=20
file, then $prefered_start_day is not blank and phpical will use the=20
$prefered_start_day   Otherwise, if the visitor choose another=20
language, phpical will use $week_start_day set in the language file and=20=

not the $prefered_start_day because is no more the same language. This=20=

is more convenient for FOREIGN people because the $start_week_day is no=20=

more fixed by the webmaster for HIS own language.

Other option (best): to tell webmasters to change the $week_start_day=20
in THEIR language file to their needs. This way, that doesn't affect=20
other languages and they can change the 24/12 format too (some english=20=

country may use 24h format).

This way, visitors with other languages can still benefit the proper=20
settings of the desired language file whatever if the french language=20
file is used in a "Sunday" country for example.

And YES, to respond to Matt Jarjoura, even American country will have=20
the desired settings whatever they're Sunday or Monday and 12h or 24h=20
country...

Mike.=20=

Its on the preferences page that doesn't yet exist, but is scheduled 
for 0.9. Im pretty sure I've gone over this already. I would like to 
use your chlang popup on that upcoming page.

Your basically re-iterating everything I've already said in your email. 
Please add 'list_languages.php' to functions in CVS as well as your 
changes to all the pages. We will move the selection options to the new 
Prefs page I hope to find time to start this weekend.

-C

Chad wrote :

> cookie takes precedence over config and lang file
> config takes precedence over lang file
> if neither, lang file is used

How do you set the "Start week day" cookie ? Is there a pop menu "Start 
Day Week" ? We still have to respond to that question.

If you look at most OS's they give language as one choice and then your
localization as another. This way I can still see dollars but see the
written word in another language, maybe Spanish.

I would suggest not putting the start of the week in the language files
because they are unrelated completely.  Sure most European countries start
on Monday, but most Americans like it to start on Sunday.

Furthermore, what about creating localization settings? If you want to make
it easy for the user what's one more select box?  Select Language as config
#1 and then select localization as default config #2.

On 11/7/02 5:27 AM, "Mike" <mi...@la...> wrote:

> Jared wrote :
> 
>> I disagree. It's not stuck to the language but rather the country. The
>> US has the week start on Sunday. If someone in the US prefers their
>> calendars to be viewed in French or German, why should the week start
>> be on Monday? The calendar is still a US calendar.
> 
> This is your point of view. But remember: start week of the day doesn't
> affect the calendar results themselves! It's just for VIEWERS'
> convenience, just to fit people's mind. Just like translation or 24/12.
> So why stuck 24/12 in the language file and not week days ? 24h is not
> part of the US calendar and someone watching your calendar with "French
> view" would see 18h30: Japanese. Even if he lives in the US and is used
> to 12h time format. That's the same thing. Week days are just something
> everyone learn at school and are used to. So if you, Jared, come to
> France, you will be a little confused to see a french week view even
> with english day manes on it if you choosed the "US view". Because it's
> not convient for you.
> 
> 
> 
>> It is very common for a language to be stuck to a country as well, but
>> they aren't tied as tightly together and bilingual people might want
>> to choose.
> 
> For bilingual persons it's another deal. Not a big deal, because
> they're used to see both ways of displaying calendars. When french
> speaking Quebec people, and they're numerous, come to our websites
> hosted in France, they're used to see things the French way: 24, metric
> system, Euro, monday, etc... When they surf on US website they see
> thing differently. Quebec webmaster, will be able to have a custom
> mixed French/12h/sunday calendar with the custom.inc.php file I
> mentioned for the convenience of their Quebec visitors. It's still up
> to the webmaster!
> 
> That's a very little thing to change, and that would allow "Prefered
> view language" feature. Without that change, "Prefered view language"
> feature is a nonsense and is useless too.
> 
> Mike. 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
> 

==========================
        Matt Jarjoura
==========================
|  UMBC  | Phi-Delta 313 |
==========================

Hello.

i installed phpicalendar-0.8.1 on my windows 2000/iis 5 server.

the url is

http://www.emkdemo.com/phpicalendar-0.8.1/index.php

note that i don't have the default page set to index.php on this
directory, so you have to specify it in the URL.

the only change i made to config.inc.php, or any file for that matter,
was the default path url. 

$default_path                   =
'http://www.emkdemo.com/phpicalendar-0.8.1';

it appears to function fine to me, I really don't believe there is a
need for any special instructions with regards to windows server
installations.

My phpinfo is available at

http://emkdemo.com/phpicalendar-0.8.1/phpinfo.php

I appreciate your comments!

Thanks

Waitman

On Sat, 2002-11-02 at 09:06, Chad wrote:
    Well I wanted to get out a maint release since 0.9 will probably be a 
    bit. Ive already started the README as you can probably tell. Let me 
    know when your ready and I'll package it up.

    -C

    On Saturday, November 2, 2002, at 08:03  AM, Jared wrote:

    > We could if you like. I won't be able to work on it tonight because I 
    > have other things to do so now is as good a time as ever. There are 
    > quite a few bug fixes, and that's about all that there is. I will make 
    > sure everything I have done is commited (pretty sure it is, just gotta 
    > double check), including a 0.8.1 section in the README.
    >
    > -Jared
    >
    > On Saturday, November 2, 2002, at 01:02  AM, Chad wrote:
    >
    >> Want to ship 0.8.1?
    >>
    >> -C
    >>
    >>
    >>
    >> -------------------------------------------------------
    >> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
    >> handheld. Power & Color in a compact size!
    >> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
    >> _______________________________________________
    >> Phpicalendar-devel mailing list
    >> Php...@li...
    >> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
    >
    >
    >
    >
    > -------------------------------------------------------
    > This sf.net email is sponsored by: See the NEW Palm Tungsten T 
    > handheld. Power & Color in a compact size!
    > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
    > _______________________________________________
    > Phpicalendar-devel mailing list
    > Php...@li...
    > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

    -------------------------------------------------------
    This sf.net email is sponsored by: See the NEW Palm 
    Tungsten T handheld. Power & Color in a compact size!
    http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
    _______________________________________________
    Phpicalendar-devel mailing list
    Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

oops, i take that back.

i noticed a problem with 
http://www.emkdemo.com/phpicalendar-0.8.1/rss/index.php

i was getting a "WARNING: failed to include fle ./header.inc.php on line
17" at the top of the page.

changing line 17 from 
include("./header.inc.php");

to 
include ("../header.inc.php"); 

(extra dot prefix)

fixed the problem.

Best,

Waitman Gobble
EMK Design
Buena Park, California
+1.7145222528
http://emkdesign.com

On Tue, 2002-11-05 at 07:52, Waitman C. Gobble wrote:
    Hello.

    i installed phpicalendar-0.8.1 on my windows 2000/iis 5 server.

    the url is

    http://www.emkdemo.com/phpicalendar-0.8.1/index.php

    note that i don't have the default page set to index.php on this
    directory, so you have to specify it in the URL.

    the only change i made to config.inc.php, or any file for that matter,
    was the default path url. 

    $default_path                   =
    'http://www.emkdemo.com/phpicalendar-0.8.1';

    it appears to function fine to me, I really don't believe there is a
    need for any special instructions with regards to windows server
    installations.

    My phpinfo is available at

    http://emkdemo.com/phpicalendar-0.8.1/phpinfo.php

    I appreciate your comments!

    Thanks

    Waitman

    On Sat, 2002-11-02 at 09:06, Chad wrote:
        Well I wanted to get out a maint release since 0.9 will probably be a 
        bit. Ive already started the README as you can probably tell. Let me 
        know when your ready and I'll package it up.

        -C

        On Saturday, November 2, 2002, at 08:03  AM, Jared wrote:

        > We could if you like. I won't be able to work on it tonight because I 
        > have other things to do so now is as good a time as ever. There are 
        > quite a few bug fixes, and that's about all that there is. I will make 
        > sure everything I have done is commited (pretty sure it is, just gotta 
        > double check), including a 0.8.1 section in the README.
        >
        > -Jared
        >
        > On Saturday, November 2, 2002, at 01:02  AM, Chad wrote:
        >
        >> Want to ship 0.8.1?
        >>
        >> -C
        >>
        >>
        >>
        >> -------------------------------------------------------
        >> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
        >> handheld. Power & Color in a compact size!
        >> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
        >> _______________________________________________
        >> Phpicalendar-devel mailing list
        >> Php...@li...
        >> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
        >
        >
        >
        >
        > -------------------------------------------------------
        > This sf.net email is sponsored by: See the NEW Palm Tungsten T 
        > handheld. Power & Color in a compact size!
        > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
        > _______________________________________________
        > Phpicalendar-devel mailing list
        > Php...@li...
        > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

        -------------------------------------------------------
        This sf.net email is sponsored by: See the NEW Palm 
        Tungsten T handheld. Power & Color in a compact size!
        http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
        _______________________________________________
        Phpicalendar-devel mailing list
        Php...@li...
    https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

    -------------------------------------------------------
    This sf.net email is sponsored by: See the NEW Palm 
    Tungsten T handheld. Power & Color in a compact size!
    http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
    _______________________________________________
    Phpicalendar-devel mailing list
    Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

hello,

can we add this to config.inc.php

$allow_html[] = 'no';  // allow html in event descriptions.

(you could default to "yes")

then change event.php - the section that deals with description:

$description = rawurldecode($description);
$description = stripslashes($description);
$description = str_replace('\\', '', $description);
if (strtolower($allow_html)=='no')
{
        $description = htmlspecialchars($description);
        $description = @eregi_replace("&lt;br&gt;","<br>",$description);
}

the reason is i sometimes put code notes in my event entries. if you
think this feature is not important enough to include in the main code,
my feelings won't be hurt ;-)

this is a "quick fix" - with the downside being that IF my code notes
contain a <BR> tag, it doesn't show up as a <br> tag but creates a new
line. 

i thought about simply doing a <pre>$description</pre> but then there
are word wrap and new line issues.

a good alternative that may prove prudent is to look at the phpbb code
and try to emulate the phpbb style codes in the event descriptions????

like
[code] blah blah blech [/code]
[url]http://myfavouritepornsite.com[/url]

whatever...

please let me know you opinions!

thanks and best

Waitman Gobble
EMK Design
Buena Park California
+1.7145222528
http://emkdesign.com

On Sat, 2002-11-02 at 09:06, Chad wrote:
    Well I wanted to get out a maint release since 0.9 will probably be a 
    bit. Ive already started the README as you can probably tell. Let me 
    know when your ready and I'll package it up.

    -C

    On Saturday, November 2, 2002, at 08:03  AM, Jared wrote:

    > We could if you like. I won't be able to work on it tonight because I 
    > have other things to do so now is as good a time as ever. There are 
    > quite a few bug fixes, and that's about all that there is. I will make 
    > sure everything I have done is commited (pretty sure it is, just gotta 
    > double check), including a 0.8.1 section in the README.
    >
    > -Jared
    >
    > On Saturday, November 2, 2002, at 01:02  AM, Chad wrote:
    >
    >> Want to ship 0.8.1?
    >>
    >> -C
    >>
    >>
    >>
    >> -------------------------------------------------------
    >> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
    >> handheld. Power & Color in a compact size!
    >> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
    >> _______________________________________________
    >> Phpicalendar-devel mailing list
    >> Php...@li...
    >> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
    >
    >
    >
    >
    > -------------------------------------------------------
    > This sf.net email is sponsored by: See the NEW Palm Tungsten T 
    > handheld. Power & Color in a compact size!
    > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
    > _______________________________________________
    > Phpicalendar-devel mailing list
    > Php...@li...
    > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

    -------------------------------------------------------
    This sf.net email is sponsored by: See the NEW Palm 
    Tungsten T handheld. Power & Color in a compact size!
    http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
    _______________________________________________
    Phpicalendar-devel mailing list
    Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

oops, my typo. 

the line should be $allow_html = 'no';
(ie it shouldn't be an array!)

take care

waitman

On Tue, 2002-11-05 at 08:46, Waitman C. Gobble wrote:
    hello,

    can we add this to config.inc.php

    $allow_html[] = 'no';  // allow html in event descriptions.

    (you could default to "yes")

    then change event.php - the section that deals with description:

    $description = rawurldecode($description);
    $description = stripslashes($description);
    $description = str_replace('\\', '', $description);
    if (strtolower($allow_html)=='no')
    {
            $description = htmlspecialchars($description);
            $description = @eregi_replace("&lt;br&gt;","<br>",$description);
    }

    the reason is i sometimes put code notes in my event entries. if you
    think this feature is not important enough to include in the main code,
    my feelings won't be hurt ;-)

    this is a "quick fix" - with the downside being that IF my code notes
    contain a <BR> tag, it doesn't show up as a <br> tag but creates a new
    line. 

    i thought about simply doing a <pre>$description</pre> but then there
    are word wrap and new line issues.

    a good alternative that may prove prudent is to look at the phpbb code
    and try to emulate the phpbb style codes in the event descriptions????

    like
    [code] blah blah blech [/code]
    [url]http://myfavouritepornsite.com[/url]

    whatever...

    please let me know you opinions!

    thanks and best

    Waitman Gobble
    EMK Design
    Buena Park California
    +1.7145222528
    http://emkdesign.com

    On Sat, 2002-11-02 at 09:06, Chad wrote:
        Well I wanted to get out a maint release since 0.9 will probably be a 
        bit. Ive already started the README as you can probably tell. Let me 
        know when your ready and I'll package it up.

        -C

        On Saturday, November 2, 2002, at 08:03  AM, Jared wrote:

        > We could if you like. I won't be able to work on it tonight because I 
        > have other things to do so now is as good a time as ever. There are 
        > quite a few bug fixes, and that's about all that there is. I will make 
        > sure everything I have done is commited (pretty sure it is, just gotta 
        > double check), including a 0.8.1 section in the README.
        >
        > -Jared
        >
        > On Saturday, November 2, 2002, at 01:02  AM, Chad wrote:
        >
        >> Want to ship 0.8.1?
        >>
        >> -C
        >>
        >>
        >>
        >> -------------------------------------------------------
        >> This sf.net email is sponsored by: See the NEW Palm Tungsten T 
        >> handheld. Power & Color in a compact size!
        >> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
        >> _______________________________________________
        >> Phpicalendar-devel mailing list
        >> Php...@li...
        >> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
        >
        >
        >
        >
        > -------------------------------------------------------
        > This sf.net email is sponsored by: See the NEW Palm Tungsten T 
        > handheld. Power & Color in a compact size!
        > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
        > _______________________________________________
        > Phpicalendar-devel mailing list
        > Php...@li...
        > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

        -------------------------------------------------------
        This sf.net email is sponsored by: See the NEW Palm 
        Tungsten T handheld. Power & Color in a compact size!
        http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
        _______________________________________________
        Phpicalendar-devel mailing list
        Php...@li...
    https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

    -------------------------------------------------------
    This sf.net email is sponsored by: See the NEW Palm 
    Tungsten T handheld. Power & Color in a compact size!
    http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
    _______________________________________________
    Phpicalendar-devel mailing list
    Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

Waitman said:
>i noticed a problem with 
>http://www.emkdemo.com/phpicalendar-0.8.1/rss/index.php
>
>i was getting a "WARNING: failed to include fle ./header.inc.php on line
>17" at the top of the page.

I changed this to use BASE like the include of the footer.

I also fixed the problem that descriptions weren't being included
in the rss feed.

  Bill

Yeah I saw those. Thanks :-)

I'll be a bit busy with work / life for the next few weeks. Well 
probably the rest of the year, but I'll make more time.

-C

On Wednesday, November 6, 2002, at 11:26  AM, Bill Fenner wrote:

>
> Waitman said:
>> i noticed a problem with
>> http://www.emkdemo.com/phpicalendar-0.8.1/rss/index.php
>>
>> i was getting a "WARNING: failed to include fle ./header.inc.php on 
>> line
>> 17" at the top of the page.
>
> I changed this to use BASE like the include of the footer.
>
> I also fixed the problem that descriptions weren't being included
> in the rss feed.
>
>   Bill
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

great.

what do you think about changing the constant BASE to a variable, and
setting it to getcwd()

?

there was a report of a bug in php 4.2.3 with apache 2.0.43 the messed
up the file_exists call. i have seen this bug in previous versions of
php, not sure why it has apparently resurfaced, but using the full path
with getcwd fixes the problem.

the change would simply prevent future incidence.

the getcwd() should be used in a single place, with a note :

in case some ISP has this function blocked in their php.ini
configuration file, the user can manually place the full path in the
$BASE variable and remove the getcwd() call.

otherwise, perhaps we could check to see if the function is available
and default to the "./" thing.

thanks!

waitman

On Wed, 2002-11-06 at 11:26, Bill Fenner wrote:
    Waitman said:
    >i noticed a problem with 
    >http://www.emkdemo.com/phpicalendar-0.8.1/rss/index.php
    >
    >i was getting a "WARNING: failed to include fle ./header.inc.php on line
    >17" at the top of the page.

    I changed this to use BASE like the include of the footer.

    I also fixed the problem that descriptions weren't being included
    in the rss feed.

      Bill

    -------------------------------------------------------
    This sf.net email is sponsored by: See the NEW Palm 
    Tungsten T handheld. Power & Color in a compact size!
    http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
    _______________________________________________
    Phpicalendar-devel mailing list
    Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel

This issue seems to have come about due to Apache 2.x and PHP4.2.x 
working together and breaking relative paths (ie ../filename instead of 
/my/path/filename). This bug was reported at php.net and can be seen at 
the urls:

http://bugs.php.net/bug.php?id=19323
http://bugs.php.net/bug.php?id=19287

The suggested course of action is to upgrade your version of PHP to 
PHP4-STABLE-200210011500 or higher, or consider changing Apache back to 
the 1.3 branch.

Unfortunately using getcwd breaks certain pages, such as the RSS index.

On Wednesday, November 6, 2002, at 02:14  PM, Waitman C. Gobble wrote:

> great.
>
> what do you think about changing the constant BASE to a variable, and
> setting it to getcwd()
>
> ?
>
> there was a report of a bug in php 4.2.3 with apache 2.0.43 the messed
> up the file_exists call. i have seen this bug in previous versions of
> php, not sure why it has apparently resurfaced, but using the full path
> with getcwd fixes the problem.
>
> the change would simply prevent future incidence.
>
> the getcwd() should be used in a single place, with a note :
>
> in case some ISP has this function blocked in their php.ini
> configuration file, the user can manually place the full path in the
> $BASE variable and remove the getcwd() call.
>
> otherwise, perhaps we could check to see if the function is available
> and default to the "./" thing.
>
> thanks!
>
> waitman
>
>
> On Wed, 2002-11-06 at 11:26, Bill Fenner wrote:
>     Waitman said:
>> i noticed a problem with
>> http://www.emkdemo.com/phpicalendar-0.8.1/rss/index.php
>>
>> i was getting a "WARNING: failed to include fle ./header.inc.php on 
>> line
>> 17" at the top of the page.
>
>     I changed this to use BASE like the include of the footer.
>
>     I also fixed the problem that descriptions weren't being included
>     in the rss feed.
>
>       Bill
>
>
>     -------------------------------------------------------
>     This sf.net email is sponsored by: See the NEW Palm
>     Tungsten T handheld. Power & Color in a compact size!
>     http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
>     _______________________________________________
>     Phpicalendar-devel mailing list
>     Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Phpicalendar-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel