Closed (fixed)
Project:
Localization server
Version:
5.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Jan 2008 at 17:31 UTC
Updated:
14 Feb 2008 at 22:41 UTC
Jump to comment: Most recent file
Comments
Comment #1
gábor hojtsy- How is an install.po generated at all? What does that contain?
- what's up with other files like misc.po and includes.po?
Comment #2
sutharsan commentedInstall.po is part of the exported file from the l10n-server (Project: Drupal; release: RC2; Type: translation; format: drupal 6).
You can export a file yourselves at: http://l10n.krimson.be/index.php?q=translate/languages/nl/export and see the content.
misc.po and modules-system.po are not part of the exported file. includes.po is exported as /includes/translations/includes.nl.po while is should be /modules/system/includes.nl.po
Comment #3
sutharsan commentedComment #4
gábor hojtsyHm, well, there should be a misc.po as well with 10 strings (from JavaScript files).
Comment #5
sutharsan commentedOk, I've overlooked the misc.nl.po and modules-system.nl.po files. The complete picture is now:
In the export file:
* translations/general.nl.po
* includes/translations/includes.nl.po
* misc/translations/misc.nl.po
* modules/system/translations/modules-system.nl.po
According to the README.txt is should be:
* modules/system/translations/general.nl.po
* modules/system/translations/includes.nl.po
* modules/system/translations/misc.nl.po
* modules/system/translations/modules-system.nl.po
No root.pot exists in the drupal-pot, so currently we can ignore this.
Comment #6
gábor hojtsyAll right, just committed an untested export fix, which should fix this for Drupal core and should not have any side effects for other exports. Please update to the latest development version and report back as soon as possible, so I can alter the export as intended.
Basically, a translation should have the structure of the attached package. If the package generated by l10n_server is not like this, then we still need to fix something.
Comment #7
meba commentedSorry, didn't work :(
Checked with:
Then exported and installed Drupal. Many strings still left untranslated. After exporting in a flat file and importing, voila...
P.S.: I wonder - do we need this? Is this used as a packager on drupal.org or just committing the code to drupal.org will create correct package?
Comment #8
meba commentedMy tar.gz
Comment #9
gábor hojtsyJust committed a fix of a typo in my fix in the afternoon, which fixed this according to meba.
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.