2008/2/20, Drupal CVS administrator <cvs-applications(a)drupal.org>:
> udienz,
> We are pleased to inform you that your CVS account request has been approved. It will be activated within one or two hours.
>
> Kind regards,
> AjK.
>
> --------------------
> User:
> http://drupal.org/user/166199
>
> Motivation message:
> I want to help Drupal project especially translation into mu language,
> because at my country many people use drupal but they don't have own
> localizaton. i saw indonesian contributor just one person so want to
> help
>
Thank's!
--
------------------------------------------------------------------
udienz (Mahyuddin Susanto)
Personal blog http://udienz.wordpress.com,
"pikiran anda bukan hanya di isi. tapi untuk di nyalakan"
Hi everyone!
My reason for asking here is Serbian translation of Drupal. There is one
on drupal.org but it is very outdated. I have some .po file extracted from
Drupal installation for 5.x, so I would like to share it to community.
I read whole documentation about translating on drupal.org and found some
informations, which I need to be cleared. Should I update smaller .po files
from this big one and then create an issue so someone will then update
project page or go directly to new localization server, which I found that
is on test phase?
I also checked one where I see several Slavic languages
(http://www.drupaler.ru/). My question is also are those localization
servers temporary, so after that all will be moved to drupal.org (i.e.
l10n.drupal.org) or they will stay in current look (separated for each
language)? If they move to central server on drupal.org, will all
translations be moved over there? Are those current servers updated with
new strings and are those translations automatically updated on drupal.org
or there is need for manual update?
We could create translation team for Serbian and thats why I ask you about
servers, since it would be easier to translate for Drupal 6 and for
numerous modules with collaboration.
Also I must ask you where I could find updated pots for 5.x, since those
here (http://drupal.org/project/drupal-pot) are from July of last year?
I'm sorry for my numerous questions, if you find time, please answer
them.
Thanks in advance.
Milan Dinić
Hi Drupal translators,
I recently have created the new structure/files for Romanian D6
translation. I have created the new .po files
(http://drupal.org/node/11311) and I have build the directory
structure and move the files to that directories (using the modified
build.php found in HU translation). Now my D6 translation
directories/files look like this:
ro/
modules/
aggregator/
translations/
modules-aggregator.ro.po
block/
[...]
profiles/
[...]
themes/
[...]
I have committed successful this structure to CVS. You can find it at
http://cvs.drupal.org/viewvc.py/drupal/contributions/translations/ro/.
I added a new branch DRUPAL-6--1 needed for development snaphost
releases and create the dev release. The new release
ro-6.x-1.x-dev.tar.gz was created (see: http://drupal.org/node/221670)
even if is not displayed on project page (no official release is
published yet!).
And now... guess what? I downloaded the release
(http://ftp.drupal.org/files/projects/ro-6.x-1.x-dev.tar.gz) and I
open it. I found differences between what I have committed and what is
in the tar.gz file:
* I found in the release (in the root) two new files: LICENSE.ro.txt
and STATUS.ro.txt which I had never committed.
* The ro/modules/system/ directory structure is different. Mine is
ro/modules/system/translations/
general.ro.po
includes.ro.po
misc.ro.po
modules-system.ro.po
... and what I found in the .tar.gz file is like:
ro/
aggregator/
module/
translations/
aggregator-module.ro.po
[...]
system/
module/
translations/
system-module.ro.po
install/
translations/
system-install.ro.po
[...]
No other comitters were comitted to CVS... see:
http://drupal.org/project/cvs/11490
Can this be explained?
Thank you!
Claudiu
Hey,
Drupal 6.0 is out: http://drupal.org/drupal-6.0
All of you working on translations already know about all the new
stuff, so it does not make much sense to reiterate what's on the page.
However, feel free to grab the page and publish a translated version
at your local community site. CSS is included inline in the HTML code
(to make it easier to translate as well9, so do not only copy the
text.
Also, please make sure that all translations ready are packaged and
available on drupal.org as well. If you don't see your release showing
up, check the "All releases" page and see whether there was some
packaging error. Let me know if there is any problem you cannot solve
yourself, and I'll be happy to help out.
Thanks for your hard work in making this release even more pleasant
for our users,
Gábor
Hey,
http://drupal.org/drupal-6.0-rc4 is out and includes a small number of
string changes (was 12 changed or new strings in total as I counted).
Unfortunately we found some menu bugs which needed some new strings
and a string change, and there were some oversights in wording in some
strings as well.
New translation templates are out for those working in CVS only:
http://drupal.org/node/219513
Again, I hope this will the final last RC, and the stable 6.0 version
might be out early next week. We will see how the critical bugs queue
progresses.
Gabor
Hello,
I'm looking to create a multilangauge site but I need to change the theme
used based on the current language.
Anyone know how to achieve this?
Thanks
Hey,
I just managed to level the differences between the 4 branches of potx
module, so now potx 5.x-1.2 contains the best code for you to
translate Drupal 6. Please do the following to continue Drupal 6
translation:
- update to potx 5.x-1.2 (the latest stable version in the 1.x series)
- update to the latest l10n_server development version (there were
some fixes related to export file placement, see
http://drupal.org/node/212594#comment-712331)
- grab Drupal 6 RC3 and parse it in
You will notice that there are a small number of new strings to
translate due to potx finding stuff better and RC3 contains some
translatability fixes for strings which were not translated before.
Note that Drupal 6 final is expected for early next week. Use the flat
export format to export files and commit to drupal.org CVS, so your
translation will be available on launch.
Happy translating!
Gabor
Hey,
Drupal 6.0 RC3 is out and it means a small amount of work for you. We
noticed some string which were not translatable and needed to modify
one or two strings as well. It should be quick to adapt to this
version. Note that Drupal 6 final is expected to be out sometime next
week, unless something wrong happens, so if you can get your work out
to be committed to Drupal.org, then all our users could use the
translations.
Drupal 6 itself includes instructions on how one can download
translation packages from Drupal.org, so it would be important to have
the packages sitting there. A note to l10n_server users: upgrade to
the latest version and use the flat export format to export files for
CVS commits.
Let me know if there are any problems / questions.
Gabor
I am just wondering on the status of the localization server.
It seems that there are numerous translation teams who have installed the
localization server on their own websites and Gabor mentioned on his e-mail
regarding D6 packaging that:
"The latest version of localization server also includes a flat export
format, which exports files as you need to commit them to Drupal.org
CVS.
So get those translations flowing!"
Should we install our own localization server or should we just wait for it
to be installed in a drupal.org subdomain? Either of the two is okay...I am
just wondering what our course of action will be.
****Gabor, what do you recommend?
Best regards,
John (JohnNoc)
--------------------------------------
http://drupalnorge.nohttp://drupal.org/project/nbhttp://drupal.org/project/nn