Jakub Suchy skrev:
>is the .pot file same as the one in -dev version of the modules?
>For translation server, it's best to import .tar.gz package of a module.
It is. Thank you for helping with the translation! :)
--
Sincerely,
Frederik 'Freso' S. Olesen <http://freso.dk/>
Hi,
I've contributed the Greek translation for a few third party modules. Here's a
question that arises some times.
A few modules (eg. module foo), have also sub-modules (eg. subfoo1, subfoo2,
etc.) that provide additional functionality to foo. When I run the command
line version of potx inside the module foo directory to extract the .pot
file, the default behaviour of potx is to parse all files, so it generates a
template for all existing modules in that directory (foo, subfoo1, subfoo2,
etc.). However, I am not really sure this is a correct procedure, because of
the fact that the user is able to enable only foo and not any of its
submodules. So, what's the correct procedure to handle all sub-modules?
Should there be an individual .pot file for each sub-module or one big .pot
for all?
Thanks,
--
# Vasileios Lourdas,
# Informatics Engineer, Thessaloniki (Greece)
# http://www.lourdas.name
I set up a Facebook profile where I can post my pictures, videos and events and I want to add you as a friend so you can see it. First, you need to join Facebook! Once you join, you can also create your own profile.
Thanks,
Miguel
Here's the link:
http://www.facebook.com/p.php?i=512304902&k=ZXBTZWSRUX6M51MFRC5UVQ&r&v=2
___________________
This e-mail may contain promotional materials. If you do not wish to receive future commercial mailings from Facebook, please click on the link below. Facebook's offices are located at 156 University Ave., Palo Alto, CA 94301.
http://www.facebook.com/o.php?u=1296311975&k=75c3d9
Hi,
the German translation needs a new maintainer. If you're able to cope
with constant non-constructive criticism, insults and defamation, this
is for you (cf. http://www.drupalcenter.de/node/8543).
Please mail Uwe Hermann (http://drupal.org/user/12054) to grant you
CVS access permissions. I will happily supply a database dump of the
former German translation server so that the work that has been done
can reviewed and won't get lost.
Note that I am not the actual maintainer of the German translation
(Uwe Hermann is), however, people think that I am the maintainer, so I
am putting this project up for adoption on behalf of Uwe.
Konstantin
It has happened quite a few times to me that after committing new po files,
the next morning only to find it fails drupal.org packaging script. The
error could simply be a typo in header, or mismatching line breaks. PoEdit
doesn't seem to be able to catch the latter. The fact I had to file a
support request to have release node removed before I could cvs untag it,
makes it more frustrating.
So I am wondering if the drupal.org packaging script available for download,
or is there a similar checker script I can run before committing to CVS?
hi all,
just joined this list. i am using drupal from long time (more then 2
years). i am from bangladesh. today me and my wife started the
translation of drupal to bengali. we setup http://drupalbn.lavluda.com
(drupal localization server l10n). please visit and check if we are
doing something wrong.
i search the drupal.org, no one is working on bengali translation. so i
am asking is it possible to our site on
http://drupal.org/project/l10n_server "users" list ? so that if any
other people want to work on bengali translation, (s)he can join with
us.
thanks
--
s. m. ibrahim lavlu
software engineer, deployment
somewherein...
banglablog: http://www.somewhereinblog.net
myblog: http://www.lavluda.com
Hi,
I was thinking if it would be a good idea to make some sort of an announcement
before an upcoming module release. This announcement would be some sort of a
notice that targets the translation contributors and it would actually tell
them that "Hey, in April 18th, a new version of the Foo module is expected,
go ahead and update the translation for your language and either attach it in
the project issue queue or commit it directly in the cvs (provided that you
have an account).". So, as one understands, this would be some kind of
a "warning" for translators to update their contributed translation for the
latest version, so when the new version is released, the package would
include the updated translation. Of course, there would be no obligation for
either the module maintainer to keep up with his announced schedule or the
contributor himself. It would be just a notice, that could be sent in the
current list.
I recall that this had happened in the past for the update_status module of
the 5.x branch, before the release of Drupal 6 and I think it was a nice
idea, because I had the time to contribute the translation for my language,
before its official release.
What do you think?
--
# Vasileios Lourdas,
# Informatics Engineer, Thessaloniki (Greece)
# http://www.lourdas.name
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
stef(a)caunter.ca schrieb:
> stefancaunter sent a message using the contact form at
> http://drupal.org/contact.
>
> Hi, I am one of the lynx guys. The links you use for lynx on
> http://drupal.org/cron refer to an outdated page for lynx. The correct and
> maintained page is at
>
> http://lynx.isc.org
>
> Hope that helps.
Thanks, I've updated the link.
Cheers,
Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIAjv6fg6TFvELooQRAjxvAKCrnggW466MmMcIf/OHz4TGruRLbgCcDJxA
eYiFTvO65a0ALsL8/Ku8XN0=
=v8WZ
-----END PGP SIGNATURE-----