[drupal-devel] PO-files missing in contributions
I have checked out the contributions, to know which modules do mis the *.po-file for translation purposes. In the list here, you'll see which modules still need a po-file generated: - actions; - admnotify; - affiliate; - album; - amazon_items; - amazon_search; - anyfilter; - api; - article; - atom; - attached_node; - attachement; - auction; - automember; - autopath; - binder; - blogadmin; - bloggerauth; - blogroll; - bookreview; - cafepress; - captcha; - clipper; - codefilter; - collimator; - commentcloser; - commentrss; - contactdir; - contextlink; - copyright; - cvslog; - daily; - dba; - delicious; - dkosfilter; - donations; - download; - dwiki; - ecommerce; - edit_temaplate; - emailpage; - excerpt; - ezmlm; - fckeditor; - feature; - filebrowser; - filemamanger; - fileserv; - fixentities; - flickr/flickrauth; - foaf; - folksonomy; - fontsize; - form_mail; - forms; - friendlist; - gallery; - handango; - htmlarea; - htmlcorrector; - htmltidy; - im; - image_browse; - image_filter; - import_export; - importpage; - inactive_user; - inset_paragraph; - jsdomenu; - keyword_links; - lanparty; - latex; - Idap_addressbook; - Idap_integration; - legal; - libdb; - listhandler; - livediscussions; - livejournal; - livesearch; - macrotags; - mail; - mail_archive; - mailalias; - mailhandler; - marksmarty; - mass_url; - massmailer; - memebers; - menu_otf; - mime_registry; - moblog; - mypage; - navigation; - navlinks; - navtable; - news_page; - nicelinks; - nmoderation; - node_aggregator; - node_image; - node_import; - node_privacy_byrole; - nodewords; - og; - oldwarning; - optin; - opusfilter; - over_text; - paypal_framework; - paypal_subscription; - paypal_tipjar; - pdfview; - periodical; - poormanscron; - popup; - postcounr_rank; - project; - quickpost; - quicktags; - quotes; - recipe; - recorder; - relatedlinks; - review; - revision; - ride; - role_to_file; - rsvp; - scripturefilter; - secions; - series; - shamu; - shoutbox; - sidebar; - sidecontent; - simpletest; - site_map; - site_menu; - spam; - spam_mtbacklist; - spellcheck; - stats_plot; - stock; - style; - subscriptions; - summary; - survey; - svn; - swish; - sxip; - syndication; - tag; - taggame; - taxnav; - taxonomy_access; - taxonomy_block; - taxonomy_browser; - taxonomy_context; - taxonomy_dhtml; - taxonomy_hide; - taxonomy_html; - taxonomy_image; - taxonomy_menu; - taxonomy_multi_edit; - taxonomy_otf; - teaser; - tec; - tellafriend; - term_access; - term_statistics; - textile; - theme_editor; - theme_dev; - title; - trackback; - typecat; - upload; - upload_indexer; - urlfilter; - userposts; - validation; - variable; - vocabulary_list; - volunteer; - wallpaper; - waypath; - webserver_auth; - week; - weight; - wmfilter; - workflow; - workspace; - ystock; Above listed module all are missing the PO-file!!! Which is quite a lot... Please place the PO-file in a subdirectory of your module, called 'po', so youll get: '$module/po/$module-module.po'.. (Maybe we should write this down in the contribution guidelines?) Also when we are currently in a code freeze, we should generate new PO-files of the drupal core.. Anyone wants to take this?? Stefan.
Above listed module all are missing the PO-file!!! Which is quite a lot... Please place the PO-file in a subdirectory of your module, called 'po', so youll get: '$module/po/$module-module.po'.. (Maybe we should write this down in the contribution guidelines?)
Also when we are currently in a code freeze, we should generate new PO-files of the drupal core.. Anyone wants to take this??
Code freeze is far from interface text freeze!!! It is very easy to generate the interface strings (at least for me :), but it should not be anyone's impression that the strings currently in Drupal core are anything like final for 4.6.0. Dries will accept useability fixes for a long time being, as well as some bug fixes might unearth t() bugs, so the strings might change quite a bit. Goba
Gabor Hojtsy wrote:
Code freeze is far from interface text freeze!!! It is very easy to generate the interface strings (at least for me :), but it should not be anyone's impression that the strings currently in Drupal core are anything like final for 4.6.0. Dries will accept useability fixes for a long time being, as well as some bug fixes might unearth t() bugs, so the strings might change quite a bit.
Bug fixes, usabibility improvements, documentation improvements, and performance improvements are still being accepted. The more "polish" the better. -- Dries Buytaert :: http://www.buytaert.net/
On Wed, 2 Feb 2005, Stefan Nagtegaal wrote:
Above listed module all are missing the PO-file!!! Which is quite a
They are missing the PO_T_ file (PO _template_).
lot... Please place the PO-file in a subdirectory of your module, called 'po', so youll get: '$module/po/$module-module.po'.. (Maybe we should write this down in the contribution guidelines?)
I think that translators should provide those files if they are needed. We could also create a request form maybe through the contact module. I will look into this.
Also when we are currently in a code freeze, we should generate new PO-files of the drupal core.. Anyone wants to take this??
We are in feature freeze, not code freeze. This means that strings can still change. I (or Goba) will create new PO files shortly before the release. Cheers, Gerhard
Gerhard Killesreiter wrote:
I think that translators should provide those files if they are needed. We could also create a request form maybe through the contact module. I will look into this.
It would be nice if the contact.module would let us create forms to contact a number of people (eg. everyone with the 'site maintainer' role, or everyone with the 'translator' role). -- Dries Buytaert :: http://www.buytaert.net/
On Wed, 2 Feb 2005, Dries Buytaert wrote:
Gerhard Killesreiter wrote:
I think that translators should provide those files if they are needed. We could also create a request form maybe through the contact module. I will look into this.
It would be nice if the contact.module would let us create forms to contact a number of people (eg. everyone with the 'site maintainer' role, or everyone with the 'translator' role).
Not sure. I already get some drupal.org related mail through the contact module. When I have the time to do what is asked I found that somebody else already did it. We should rather use the project module for this. It can act as a ticket system. Cheers, Gerhard
Gerhard Killesreiter schreef:
On Wed, 2 Feb 2005, Dries Buytaert wrote:
Gerhard Killesreiter wrote:
I think that translators should provide those files if they are needed. We could also create a request form maybe through the contact module. I will look into this.
It would be nice if the contact.module would let us create forms to contact a number of people (eg. everyone with the 'site maintainer' role, or everyone with the 'translator' role).
Not sure. I already get some drupal.org related mail through the contact module. When I have the time to do what is asked I found that somebody else already did it. We should rather use the project module for this. It can act as a ticket system.
Maybe it is even better to automate the PO-generation? That would make more sense imo, and is much more effective! Stefan
On Wed, 02 Feb 2005 18:32:41 +0100, Dries Buytaert <dries@buytaert.net> wrote:
It would be nice if the contact.module would let us create forms to contact a number of people (eg. everyone with the 'site maintainer' role, or everyone with the 'translator' role).
It seems like this would be a little beyond the scope of that module's purpose, unless it would be configurable to use only specific roles. I could see a business website (oops...am I suggesting that Drupal might be appropriate for that?) using it for providing a contact form for "Sales", "Support", and "Accounting" or somesuch while offering the complete list of roles would not be desirable.
participants (5)
-
Chris Cook -
Dries Buytaert -
Gabor Hojtsy -
Gerhard Killesreiter -
Stefan Nagtegaal