From: Geoff S. <Ge...@Ho...> - 2001-04-01 05:04:00
|
I'm having the problem with the screwed up months in the calendar. Here's the bug report: https://sourceforge.net/tracker/index.php?func=detail&aid=405305&group_id=15 539&atid=115539 I'd like to go ahead and fix it, but, I don't want to step on anyone's toes. It's assigned to Matthew. (So, if you are working on it ...) Anyway, I need it fixed ASAP, so, I'm happy to do it! Geoff Geoff Staples, Founder Action Agenda <http://www.actionagenda.com/> 3883 Turtle Creek Blvd., Suite 1812 Dallas, Texas 75219-4432 214.599.0260 Action Agenda is hosted as a public service by Hostricity Web Hosting <http://www.hostricity.com/> ActionAgenda.com is a Community Center for progressive and liberal activists to stay informed, find allies, and build support. |
From: Alain F. <al...@va...> - 2001-04-01 16:40:02
|
Hi everyone, Today I wanted to correct a few mistakes in the french translation of phpWebSite, but I have stopped quite quickly after I have found a major problem with the current translation system. The problem I am describing happens on a lot of different places actually, but to give you an easy to understand example: In english, the word "No" can mean: 1. The negative answer to a question, in opposition to 'yes' 2. A quantitative qualifier, like in "there are no news", "there is no one here" What seems to have been done with phpWebSite is that the "same" [[No]] was used for both meanings ! While with this setup, the sentences do make sense in English, they don't make any sense in french anymore because there are two (or even many more!) different words to express the two meanings of "no" in french. For instance, in the admin tool you can read: Non Category found. (should mean 'No category found') First of all, there's a missing/wrong translation here, of course. "found" is not a french word, and it reads "catégorie" in french. But the main problem is the "non" you see there. NON means "No" as in "No thanks" or "No, I haven't been there". In this sentence, however, it should be the second meaning (quantity), as in "None found" --> "Aucune catégorie trouvée", and not "Non catégorie trouvée". There are a couple of other places that have the same problem, with different words / strings. The source of the problem is that the same english word ('no') can have different meanings, and while in english it's okay to use the same word for different meanings, you just can't do so in french (or other languages, for that matter). What are we going to do about this? A customer of mine is waiting for the french translation to get ready, and I don't know what I should tell him :) Anyway, here's what I have corrected/added before stopping: <-- snip --> [[I forgot my password]] = [[J'ai oublié mon mot de passe]] [[Registered user benefits include themes manager, comments configuration, personal content box on home page, and more]] = [[Les utilisateurs enregistrés profitent de la gestion des thèmes, de la configuration des commentaires, de leur boîte de contenu personnelle, et bien plus]] [[Name of image save]] = [[Nom de l'image sauvegardée]] /* saved = sauvegardée */ ------ Alain Fontaine Analyst-Programmer NVision s.à.r.l. |
From: Christian S. <chr...@sc...> - 2001-04-02 11:53:13
|
Alain Fontaine wrote: > > Hi everyone, > > Today I wanted to correct a few mistakes in the french translation of > phpWebSite, but I have stopped quite quickly after I have found a major > problem with the current translation system. The problem I am describing > happens on a lot of different places actually, but to give you an easy to > understand example: Hi Alain, it's right the same problem with the german translation. Additionally lots of phrases and commands are not translated when the distro files are generated, although the language file contains all information. For instance most day and month names still are in english - not only in the calendar. Due to different syntactical rules in different languages the actual language file is no good option. It would be much better to use complete phrases containing all needed variables, so you can put them in the sentence, where you need them. This would make all translations much easier to handle and could avoid some very strange expressions and phrases I had to use in the german translation. Any suggestions? Chris |
From: Karsten D. <k.d...@tu...> - 2001-04-02 12:52:27
|
On Mon, Apr 02, 2001 at 01:52:10PM +0200, Christian Schims wrote: > Hi Alain, >=20 > it's right the same problem with the german translation. Additionally lots > of phrases and commands are not translated when the distro files are > generated, although the language file contains all information. For The script used to build the distribution now creates a list of all TRANSLATE statements still found in the code after translating it. This should help to spot some errors (in fact it did, I fixed a few bugs in the german translation. Chris, I hope this is OK with you).=20 > instance most day and month names still are in english - not only in the > calendar. Well, that actually is because the mont and day names are not written as TRANSLATE statements in the source, but are generated using the date function. You would have to supply the proper locale setting to that function to achieve the correct results. Regards, Karsten --=20 Why do we have to hide from the police, daddy? Because we use emacs, son. They use vi. ----------------------------- mailto:k.d...@tu... w=B3: http://www.k-fish.de/ gpg: http://www.k-fish.de/mykeys.gpg |
From: Christian S. <chr...@sc...> - 2001-04-02 13:56:20
|
Karsten Dambekalns wrote: > > The script used to build the distribution now creates a list of all > TRANSLATE statements still found in the code after translating it. This > should help to spot some errors (in fact it did, I fixed a few bugs in the > german translation. Chris, I hope this is OK with you). Gr8, all that counts is the result, not the man who fixed the bug. But my issue is the syntactical problem we have. At the moment one phrase with a variable in the middle is broken in two independent translate statements that are independently sorted into the language file. NNot quite easy to kee thiungs together this way. > Well, that actually is because the mont and day names are not written as > TRANSLATE statements in the source, but are generated using the date > function. You would have to supply the proper locale setting to that > function to achieve the correct results. My locale in the config file is DE, but it won't work. Chris |
From: Alain F. <al...@va...> - 2001-04-02 14:15:41
|
Chris, Try setting your locale to "ge" for a try... this works for me anyway, don't ask me why! Seems to be a bug somewhere.. :) > -----Message d'origine----- > De : php...@li... > [mailto:php...@li...]De la part de > Christian Schims > Envoye : lundi 2 avril 2001 15:55 > A : php...@li... > Objet : Re: [Phpwebsite-developers] French Language, general translation > woes ! > > [snip] > > My locale in the config file is DE, but it won't work. > > Chris > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > |
From: Brian W. B. <br...@ap...> - 2001-04-02 15:26:59
|
> Due to different syntactical rules in different languages the actual > language file is no good option. It would be much better to use > complete phrases containing all needed variables, so you can put them > in the sentence, where you need them. This would make all translations > much easier to handle and could avoid some very strange expressions and > phrases I had to use in the german translation. Agreed. There is no reason why the needed variables could not be included in the TRANSLATE[[....]] statements. Feel free to track these down in the core code and change them. If you look in the CVS at the Language "Changes" file: http://152.10.194.1/cvs/cvs.php/phpwebsite/make_distro/Changes You can note what has been deleted/changed/added in this file. This file is what the folks helping to keep the language files up-to-date should be using to keep any given language.pp file "in sync". Brian -- Brian W. Brown Internet Systems Architect, ESS Student Development Room 269, John Thomas Hall Appalachian State University Boone, NC 28608 vox: 828-262-7124 fax: 828-262-2585 |
From: Christian S. <chr...@sc...> - 2001-04-03 07:24:30
|
"Brian W. Brown" wrote: > > > Due to different syntactical rules in different languages the actual > > language file is no good option. It would be much better to use > > complete phrases containing all needed variables, so you can put them > > in the sentence, where you need them. This would make all translations > > much easier to handle and could avoid some very strange expressions and > > phrases I had to use in the german translation. > > Agreed. There is no reason why the needed variables could not be included > in the TRANSLATE[[....]] statements. Feel free to track these down in the > core code and change them. If you look in the CVS at the Language "Changes" > file: Is it senseful to do this work now or shall I better wait for the rewritten code? Chris |
From: Alain F. <al...@va...> - 2001-04-03 07:40:58
|
Hi Christian, If I were to give my vote, I'd say it's useful now :) > -----Message d'origine----- > De : php...@li... > [mailto:php...@li...]De la part de > Christian Schims > Envoye : mardi 3 avril 2001 09:24 > A : php...@li... > Objet : Re: [Phpwebsite-developers] French Language, general translation > woes ! > > > "Brian W. Brown" wrote: > > > > > Due to different syntactical rules in different languages the actual > > > language file is no good option. It would be much better to use > > > complete phrases containing all needed variables, so you can put them > > > in the sentence, where you need them. This would make all translations > > > much easier to handle and could avoid some very strange > expressions and > > > phrases I had to use in the german translation. > > > > Agreed. There is no reason why the needed variables could not > be included > > in the TRANSLATE[[....]] statements. Feel free to track these > down in the > > core code and change them. If you look in the CVS at the > Language "Changes" > > file: > > Is it senseful to do this work now or shall I better wait for the > rewritten code? > > Chris > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > |
From: Brian W. B. <br...@ap...> - 2001-04-03 13:05:29
|
>> Agreed. There is no reason why the needed variables could not be >> included in the TRANSLATE[[....]] statements. Feel free to track >> these down in the core code and change them. If you look in the CVS >> at the Language "Changes" file: > > Is it senseful to do this work now or shall I better wait for the > rewritten code? Good point. Ultimately, your call. A re-write at this point is a sure thing, but there might be a fairly long waiting period before this is released and is usable. I might post a question to the language list on SF and see how it strikes those who would have to update language files... Brian -- Brian W. Brown Internet Systems Architect, ESS Student Development Room 269, John Thomas Hall Appalachian State University Boone, NC 28608 vox: 828-262-7124 fax: 828-262-2585 |
From: Alain F. <al...@va...> - 2001-04-04 11:07:01
|
Hi, I volunteer to help with the french one if someone tells me what to do once the new strings have been defined. > -----Message d'origine----- > De : php...@li... > [mailto:php...@li...]De la part de > Brian W. Brown > Envoyé : mardi 3 avril 2001 15:02 > À : php...@li... > Objet : Re: [Phpwebsite-developers] French Language, general translation > woes ! > > {snip} > > Good point. Ultimately, your call. A re-write at this point is a sure > thing, but there might be a fairly long waiting period before this is > released and is usable. I might post a question to the language > list on SF > and see how it strikes those who would have to update language files... > > Brian > |
From: Matthew M. <mcn...@tu...> - 2001-04-02 13:27:56
|
Geoff, I am not planning on supporting the calendar included with phpWS any longer. Instead, I am concentrating on the plug-in conversion which should be completed this month. If you would like to fix the bug, we be more than happy to host the changes. Sincerely, Matthew McNaney > I'm having the problem with the screwed up months in the calendar. > Here's the bug report: > > https://sourceforge.net/tracker/index.php? func=detail&aid=405305&group_id=15 > 539&atid=115539 > > I'd like to go ahead and fix it, but, I don't want to step on anyone's > toes. > > It's assigned to Matthew. (So, if you are working on it ...) > > Anyway, I need it fixed ASAP, so, I'm happy to do it! > > Geoff > > Geoff Staples, > Founder > Action Agenda <http://www.actionagenda.com/> |
From: Geoff S. <Ge...@Ho...> - 2001-04-02 14:30:58
|
Matt: Are you writing a NEW calendar for phpWebSite? Can you give a more specific time frame then "this month"? Will it have a user submission similar to user submission for news articles? AS FOR THE BUG in the current calendar: I installed phpWebSite at www.txsd16democrats.org and the calendar was screwed up. But, once I got an event for April into it, the calendar started working correctly. Then, I installed phpWebsite at www.glsendallas.org and the calendar seemed to work correctly "out of the box". Both are on the same server, so... ANYWAY, if I can make the existing calendar work by adding a few events to it, and you are writing a replacement, there's not much point to finding the bug. Can I do something to help with the new calendar? Geoff Geoff Staples, Dallas, Texas 75219-4432 Hostricity Web Hosting <http://www.hostricity.com/> -----Original Message----- From: php...@li... [mailto:php...@li...]On Behalf Of Matthew McNaney Sent: Monday, April 02, 2001 7:22 AM To: php...@li... Subject: Re: [Phpwebsite-developers] Fixing Calendar Bug Geoff, I am not planning on supporting the calendar included with phpWS any longer. Instead, I am concentrating on the plug-in conversion which should be completed this month. If you would like to fix the bug, we be more than happy to host the changes. Sincerely, Matthew McNaney > I'm having the problem with the screwed up months in the calendar. > Here's the bug report: > > https://sourceforge.net/tracker/index.php? func=detail&aid=405305&group_id=15 > 539&atid=115539 > > I'd like to go ahead and fix it, but, I don't want to step on anyone's > toes. > > It's assigned to Matthew. (So, if you are working on it ...) > > Anyway, I need it fixed ASAP, so, I'm happy to do it! > > Geoff > > Geoff Staples, > Founder > Action Agenda <http://www.actionagenda.com/> _______________________________________________ Phpwebsite-developers mailing list Php...@li... http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers |