Tue 26 Oct 2010 04:26:07 AM UTC, comment #68:
Hi,
Everything works, thanks :)
|
Mon 25 Oct 2010 08:51:23 PM UTC, comment #67:
Hi,
I committed it, and also installed it at Gna!
Does it work?
|
Mon 25 Oct 2010 05:20:23 AM UTC, comment #66:
Oh, sorry. It remained from previous version.
Fixed version attached.
(file #10932)
|
Sun 24 Oct 2010 08:33:06 PM UTC, comment #65:
Thanks a lot Roman!
There's a mistake somewhere:
$ msgfmt -c --statistics -o ru.gmo ru.po
ru.po:25: nplurals = 3...
ru.po:1326: ...but some messages have only 2 plural forms
ru.po:1747: format specifications in 'msgid_plural' and 'msgstr[0]' for argument 1 are not the same
/usr/bin/msgfmt: found 3 fatal errors
750 translated messages, 261 fuzzy translations, 949 untranslated messages.
Can you fix it?
|
Fri 22 Oct 2010 11:50:53 AM UTC, comment #64:
Hello
I have more complete russian translation for savane.
I attached it.
(file #10880)
|
Mon 09 Feb 2009 10:38:15 PM UTC, comment #63:
Hi,
Nice to see someone new here!
we're tuned in, however it's quite a lot of time no significant translation effort is done on savannah. If you'd like to help, you're most welcome!
On my part, this could be a good hint to update the Italian translation ;-).
Matteo
|
Mon 09 Feb 2009 07:28:58 PM UTC, comment #62:
Hello!
I've ask -unavailable- about translation of Savannah at gnu.org. They said, that I need to consult here 'bout that.. But I see, that last comment here dated by "28.11.2006 at 08:08, comment #61"... That is little ancient, isn't it? So - is anybody here, or I ask to abyss? :)
Waiting reply!
Regards, Oleg. koptev.oleg <at> gmail <dot> com
|
Tue 28 Nov 2006 08:08:52 AM UTC, comment #61:
Only one day before the release:
$ make stats
ca.po:
1785 translated messages, 96 fuzzy translations, 81 untranslated messages.
de.po:
1779 translated messages, 95 fuzzy translations, 88 untranslated messages.
fr_FR.po:
1864 translated messages, 45 fuzzy translations, 53 untranslated messages.
it_IT.po:
1733 translated messages, 137 fuzzy translations, 92 untranslated messages.
ja.po:
453 translated messages, 886 fuzzy translations, 623 untranslated messages.
pt_BR.po:
453 translated messages, 886 fuzzy translations, 623 untranslated messages.
ru.po:
534 translated messages, 346 fuzzy translations, 1082 untranslated messages.
sv.po:
1962 translated messages.
I'm considering not including pt_BR, ja.po and ru.po in the next release as they are too partially complete.
|
Wed 22 Nov 2006 01:50:32 PM UTC, comment #60:
You probably received a mail that asked you to update pofiles.
Strings should be frozen until next release is delivered, which is due to happen November 29th (task #3633).
|
Fri 17 Nov 2006 06:02:40 PM UTC, comment #59:
Next release will probably be done Tuesday 28th. Currently, the trunk is not up to date so there is no need to update i18n. If you want starting updating i18n, check branch dev-2006.10-MarkupAndSpamFilterAndMetaUsers/
|
Wed 08 Nov 2006 04:58:36 PM UTC, comment #58:
Po files have been rebuilt with plenty of new string on the current dev branch (task #3776).
I'll announce when this branch will be merged with the trunk. In the meantime, if you want to update i18n, please do it only on the branch to avoid merge conflicts afterwards.
New strings relates mostly to squads and markup.
|
Mon 02 Oct 2006 08:57:08 AM UTC, comment #57:
As announced in comment #55, the release will be made tomorrow.
|
Wed 27 Sep 2006 04:28:08 PM UTC, comment #56:
Sorry translators, bug #7207 forced me to update one string.
|
Fri 22 Sep 2006 07:03:50 AM UTC, comment #55:
I can confirm now that the string freeze will occur the 26th and the release will be made the 3rd October (unless delayed by unplanned issue).
|
Thu 14 Sep 2006 01:15:44 PM UTC, comment #54:
Hello, in fact, Savane 2.0 (was 1.5) will be released after the 27th september. So the freeze string will probably be on that date.
|
Thu 14 Sep 2006 01:15:43 PM UTC, comment #53:
Hello, in fact, Savane 2.0 (was 1.5) will be released after the 27th september. So the freeze string will probably be on that date.
|
Mon 11 Sep 2006 04:17:07 PM UTC, comment #52:
Hello translators!
Savane 1.5 is due to be released in a near future, see task #2862. I cannot promise right now a string-freeze, however most strings should not change.
|
Thu 01 Dec 2005 03:45:41 PM UTC, comment #51:
Strings should be or less frozen now.
|
Tue 29 Nov 2005 08:26:31 AM UTC, comment #50:
The release is likely to be done the 6th December.
I cannot promise a string freeze until friday.
|
Sun 13 Nov 2005 05:10:00 AM UTC, comment #49:
nice :)
> Omid, features boxes are on the frontpage, it is on purpose that
> they disregard format_date in order to save space. I dont know
> how to deal with that otherwise.
could you add a new function like "format_strftime"?
|
Sat 12 Nov 2005 03:55:39 PM UTC, comment #48:
Hello,
Just a little message to say that we'll have a new release in the next coming month.
Omid, features boxes are on the frontpage, it is on purpose that they disregard format_date in order to save space. I dont know how to deal with that otherwise.
|
Sun 23 Oct 2005 07:47:16 AM UTC, comment #47:
Please post a bug report for the bug you found.
About the calendar, post another report.
|
Sat 22 Oct 2005 08:56:50 PM UTC, comment #46:
Thanks Mathieu :)
a little bug in localizing date at include\features_boxes.php at line 157.
please replace strftime with "format_date".
Regards.
P.S: where should i talk about other calendars/dates? i was developed Gregorian/Jalali/... Savane.
|
Sat 22 Oct 2005 05:50:32 AM UTC, comment #45:
We already had this discussion and I'm strongly, firmly and definitively against the idea of Savane reinventing the wheel in this regard.
When you use 'ls', when you use 'konqueror', when you use 'gimp', etc, there is no way to configure the language inside the software.
Because this is supposed to be done already on top, in the desktop configuration. Adding such option would be severely confusing, would incitate users to expect software to behave in inconsistant way, to work with setup broken by design.
That's not an option. A web application is an application and there's no reason to push users, to incitate users to think it is the correct way to get i18n to be configured for the 100 web application they use with a form inside each.
There are many benefits of having a properly configured browser (to name one: apache redirects per language), that provide i18n settings, that's what we must recommend. That the ideal way to do things and this is not pure theory.
There are some web application that have such form to configure i18n, but I think the choice their made was from the start a bad one. If you cannot get a necessary configuration information, the way to go is not to ask the user to fill it one more time, but to work on getting the information properly from where it comes.
|
Fri 21 Oct 2005 09:28:25 PM UTC, comment #44:
I found the problem.
My default language of my browser is "en", "en_US", "fa"...
So your i18n.php file, use the FIRST language and "break" from while.
but i want to set the main language in the system. (the $sys_default_locale value)
now, i fixed my own version, but for others, i think this is not suitable, default of all browsers is "en" and mostly non of users change it to their current language.
|
Thu 20 Oct 2005 07:21:50 AM UTC, comment #43:
thanks.
this is the output:
# locale -a | grep "fa"
fa_IR
fa_IR.utf8
|
Wed 19 Oct 2005 03:58:22 PM UTC, comment #42:
Could you send the output of the following command?
$ locale -a | grep "fa"
You need to have the fa_IR.utf-8 locale available on your system. I suspect that this is not the case.
|
Tue 18 Oct 2005 09:37:38 PM UTC, comment #41:
Thanks Mathieu for your fast reply :)
nothing happend! this is what i did:
- i added a new po file named "fa_IR.po" to "po" directory.
- change i18n.php files and add the following lines to it:
"fa" => "IR.UTF-8",
"fa_IR" => "IR.UTF-8"
AND
$plural_rule["fa_IR"] = ($n > 1);
- make savane and make install po ddirectory as root (all things work fine in this section)
- open savannah.conf.pl and change $sys_default_locale to "fa_IR" (it was uncommented before)
- run sv_update_conf
and check the system, but it is english :(
this is header of po file:
=============================
"Project-Id-Version: fa_IR\n"
"POT-Creation-Date: \n"
"PO-Revision-Date: 2005-10-11 20:34+0330\n"
"Last-Translator: [[no spam]]\n"
"Language-Team: [[no spam]]\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-Language: Persian\n"
"X-Poedit-Country: IRAN, ISLAMIC REPUBLIC OF\n"
"X-Poedit-SourceCharset: utf-8\n"
=============================
and when i run "ls /usr/share/locale/fa*" i saw:
=============================
/usr/share/locale/fa:
./ ../ LC_MESSAGES/
/usr/share/locale/fa_IR:
./ ../ LC_MESSAGES/
=============================
and for "ls /usr/share/locale/fa/LC_MESSAGES/" i have:
=============================
authconfig.mo
redhat-menus.mo
system-config-network.mo
glib20.mo
system-config-mouse.mo
system-config-securitylevel.mo
=============================
and for "ls /usr/share/locale/fa_IR/LC_MESSAGES/" i have:
=============================
savane.mo
=============================
thanks a lot.
|
Tue 18 Oct 2005 08:55:56 PM UTC, comment #40:
You have to edit frontend/php/include/i18n.php (see how it is done for other languages) and run
make
make install # (as root)
in the po/ directory of the main savane directory.
|
Tue 18 Oct 2005 08:34:57 PM UTC, comment #39:
We traslate your system to Persian, how can we add the configurations to savane files? (we need to install it on our test system before public publishing)
our lang code is "fa_IR".
regards, Omid
|
Sun 02 Oct 2005 03:54:17 PM UTC, comment #38:
Dear Matt, i sent a file for you, did you get it?
i need to send a file, where should i send?!
|
Thu 29 Sep 2005 11:40:38 PM UTC, comment #37:
yes, exactly i want to develop your system to can use other calendars :)
as i told you in private email, i developed serendipity (s9y.org) to support Jalali calendar, and users can select their calendar from their control panel.
as i see, i must do the following works:
- add two-three new functions for date (really NEW functions :) ) for Jalali calendar and convertion between Jalali & Gregorian...
- develop your "format_date" function. this function should find which LANGUAGE is selected and show the correct calendar. (default=gregorian)
for prob1, as i told above... i want to know which language is selected in the "format_date" function :) my question is HOW can i find which language selected?!
thanks Math and sorry to disturb you.
|
Thu 29 Sep 2005 05:13:38 PM UTC, comment #36:
Do you want to implement somehow a way to show dates with a calendar which is not the usual one (Gregorian I think it is)?
Well, that may be tough, are there other software that support such calendars? Anyway such change would probably requires many changes. Such work would have to be made on a branch, or submitted by patches.
About prob1, every variables used in functions in utils.php have access to these. Apart from that, you should check in the code, I cannot tell without reading it.
|
Thu 29 Sep 2005 04:52:30 PM UTC, comment #35:
the translation started before and is in progress...
but i need to develop calendar of this system, i can develop it for myself, but i want to publish it for other persian/iranian guys.
i will change the calendar (i18n!) and send the final file for you.
but please answer to my questions to can develop it faster :)
(please answer mu prob1 question :) if i must ask it somewhere else, please tell me, but i think "calendar" are "i18n"-related)
|
Thu 29 Sep 2005 09:01:52 AM UTC, comment #34:
I think it would be best to first start with what is doable without changing the code, and then, afterwards, looking for more complicated issues.
|
Thu 29 Sep 2005 08:54:35 AM UTC, comment #33:
Thanks for your reply :)
i want to change "format_date" function, and it is in "utils.php"...
i want to develop Jalali (Persian) calendar for your system and i should change "format_date" function, so i ant to change "utils.php" file...
TRANSLATE is something diffeent from CALENDAR....
i need to change that file, because of calendar, not translating.
regards.
|
Thu 29 Sep 2005 08:25:18 AM UTC, comment #32:
You dont have to bother with the stuff in utils.php, unless there's a bug it will do anything necessary.
How dates are used is of general scope. If in some place you really think it should be local and is not, fill a bug report. But so far, the system is supposed to behave properly in this regard.
Translating should not require any changes in utils.php.
|
Wed 28 Sep 2005 08:57:24 AM UTC, comment #31:
prob1:
i saw that lines and the mapping system, i want to know, do i have access to this variable in utils.php file?
prob2:
sure, i will discuss you, i will email you soon to trust me :) and ...
the date function called in a lot of places, some of them is because you want to generate GMT date....
but somwhere else, like faq/export_textinfo.php in line 46 (ver1.9) you called it directly... i think it can/must be local :)
regards.
|
Wed 28 Sep 2005 08:48:07 AM UTC, comment #30:
prob2: It would be best to let any changes to utils.php to be discussed later. Where date is directly called, it is probably because a specific date formatting is required, override locales.
prob1: The selected language (locale) is the one configured in your web browser. It must also be supported by the web server, and some mappings are defined in include/i18n.php
|
Wed 28 Sep 2005 08:40:47 AM UTC, comment #29:
dear mathieu,
i want to localize your system calendar (date)...
i found "format_date" in "utils.php" file, but i have two problem and one question...
prob.1:
how can i find which language is selected? is it "$locale"?? is it valid in "utils.php" page?
prob.2:
there are some direct calls of "date" function in your program (eg faq/export_textinfo.php) could you/i change them to use "format_date"?
question.1:
could i change "utils.php" on my own and then send it to you?!
regards, omid
|
Tue 27 Sep 2005 03:50:42 PM UTC, comment #28:
thanks mathieu,
yes, i know what is gettext and how can i use/change it :)
|
Tue 27 Sep 2005 01:20:06 PM UTC, comment #27:
I had to update the po files, but only 1 or 2 strings changed.
|
Tue 27 Sep 2005 11:40:38 AM UTC, comment #26:
That would be nice. Are you familiar with gettext?
|
Tue 27 Sep 2005 10:00:13 AM UTC, comment #25:
Hello,
i want to add Prsian (farsi, fa_IR) language to your system.
regards, omid
|
Fri 23 Sep 2005 07:30:19 AM UTC, comment #24:
Reminder: a prerelease of Savane will be made next monday. And Savane will finally be released on Thursday.
|
Thu 15 Sep 2005 02:49:08 PM UTC, comment #23:
Hello,
Release 1.2 will be probably made during the next week, see task #2170 for more details.
Strings should more or less frozen (as much as possible).
|
Thu 01 Sep 2005 08:58:31 AM UTC, comment #22:
We are about to make a new release, do not hesitate to update i18n
(see task #1955)
|
Mon 21 Mar 2005 11:59:13 AM UTC, comment #21:
Next release is about to be done, normally only a few strings should change. A good time to update po files.
|
Mon 22 Nov 2004 08:44:38 AM UTC, comment #20:
The Potfile on the trunk is now up-to-date.
|
Wed 17 Nov 2004 10:42:11 AM UTC, comment #19:
I'll update the potfile on monday, after the trunk feature-froze.
|
Thu 11 Nov 2004 10:04:44 AM UTC, comment #18:
I added the file doc/devel/TRANSLATION
----------------------------------------------------
Interested in translating Savane?
--------------------------------
Post a comment on task #115 first.
Howto start from scratch a translation?
---------------------------------------
Savane use gettext.
(to be completed with an URL or else)
Howto update a translation?
---------------------------
First, never override previous translation choices until you are 100% sure
that your change is best. In doubt, please send a mail to savane-dev-i18n.
For instance, previous French translator decided to use the french word item
to translate item and courriel to translate email. No one should change that
until he demonstrates on savane-dev that he got a better translation to
propose.
In doubt, send a mail to savane-dev-i18n.
Secondly, never "correct" previous translations without first checking with
aspell/ispell (or whatever dictionnary you are comfortable with) that you
are right.
-----------------------------------------------------
I also created the list savane-dev-i18n dedicated specifically to translation issues.
Persons that have recently contributed a translation have been added automatically, they should receive a notification.
|
Tue 09 Nov 2004 02:09:15 PM UTC, comment #17:
Note for people updating translation: please never override previous translation choices until you are 100% sure that your change is best. In doubt, please send a mail to savane-dev.
|
Sat 18 Sep 2004 02:42:19 AM UTC, comment #16:
Temporary location for my Russian translation for Savane project (unfinished).
|
Mon 06 Sep 2004 04:01:48 PM UTC, comment #15:
Ventura, you're welcome to ask anything you'd like to ask to the development list savane-dev
|
Mon 06 Sep 2004 04:01:46 AM UTC, comment #14:
Hi, Mathieu!
It is not that I am in a hurry or something. I was just wondering whether this thing is working. Any way, it is not preventing me from translating!
Regards,
|
Sun 05 Sep 2004 09:53:36 PM UTC, comment #13:
It works; I just did not already handled it. I'll do it tomorrow.
Regards,
|
Sat 04 Sep 2004 08:06:12 PM UTC, comment #12:
Hi, Elfyn McBratney!
Tried this link some times (2-3 days) ago -- still no response.
I will wait some more days before I'll retry.
|
Sat 04 Sep 2004 02:54:06 PM UTC, comment #11:
To the CVS? :)
You could request an account at https://gna.org/my/groups.php (using `savane' as the group for the inclusion request), or put it up on the web somewhere, and someone else with CVS access can commit it for you.
If you do the latter, let -unavailable- know. :)
|
Fri 03 Sep 2004 08:28:01 PM UTC, comment #10:
Ok, yesterday I did begin the spanish l10n. Now, I have c. 500 strings translated.
Where I should send my doubts to?
|
Fri 03 Sep 2004 08:27:16 PM UTC, comment #9:
Ok, yesterday I did begin the spanish l10n. Now, I have c. 500 strings translated.
Where I should send my doubts?
|
Wed 01 Sep 2004 10:06:24 PM UTC, comment #8:
Not that we are aware of.
|
Wed 01 Sep 2004 10:00:25 PM UTC, comment #7:
I downloaded the distribution and extracted the .pot file for a spanish translation.
Are there more people with this task?
Regards,
VV
|
Sat 03 Jul 2004 07:09:00 PM UTC, comment #6:
I'm starting the italian translation (still at the beginning).
I hope to work more over this after July 7th. Won't probably make it in next release.
|
Thu 12 Feb 2004 12:14:26 AM UTC, comment #5:
A quick update: I just sent out the mail to the other three translators (pt_BR, ja, ko) asking about their ability to review/update their .po-files before the next release.
|
Wed 11 Feb 2004 07:25:28 PM UTC, comment #4:
1. I'm going to mail the translators.
2. The statistics: I'm just using KBabel, which does all the calculating... ;-)
|
Wed 11 Feb 2004 07:17:15 PM UTC, comment #3:
For the French i18n, yes, we will update it. Considering the % of French developers in the project Savane, it is not really a big problem, and the gettext support was implemented by a French anyway :))
The korean translator show up only once, so it is unclear whether he will keep contributing.
One solution is to mail translators, another one would be to add all of them in Cc: of this task, so they would get a notice of every update of the task.
Out of curiosity, how do you get the number of strings fuzzy / unstranslated ?
|
Wed 11 Feb 2004 06:46:14 PM UTC, comment #2:
I'm currently going through the code to fix some issues with i18n. While doing this, some translations to other languages than German become "fuzzy" or even invalid. When I'm done with German, hopefully most of the i18n bugs/inconsistencies in the code should be resolved.
I think it would be a good idea to contact the people who did the existing translations to give them a chance to resolve the fuzzy/untranslated messages in their language before releasing the next version.
Some statistics, as of tonight: (fuzzy/untranslated)
French: 116/122
Portuguese: 309/175
Japanese: 309/175
Korean: 341/810
French, Portuguese and Japanese are quite realistic to include in the next release, while Korean is a lot of work to do. Anybody knows about the Korean translator?
I can mail all translators, of course, but maybe someone of the members of this project already has made some contacts? If noone has, I'm willing to try to reach the translators. Just drop me a note.
Concerning the French translation: I guess you guys are probably doing it yourself, right? Do you intend to brush up the French .po file before the release?
|
Mon 02 Feb 2004 02:56:27 PM UTC, comment #1:
ok nice, give me files to translate and i will translate them to french
|
Sun 01 Feb 2004 12:02:59 PM UTC, original submission:
We are always looking for translation contributions.
|