the administer | locaization | manage languages | export menu supposely allows me to do "Generate a gettext Portable Object Template (.pot) file with all the interface strings from the Drupal locale database."
However, the file exported only contains the following:
# LANGUAGE translation of PROJECT
# Copyright (c) YEAR NAME
#
msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"POT-Creation-Date: 2005-12-09 14:45+0100\n"
"PO-Revision-Date: YYYY-mm-DD HH:MM+ZZZZ\n"
"Last-Translator: NAME \n"
"Language-Team: LANGUAGE \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n"
--- end of file ---
I've tried the export in firefox and opera with the same results. Am I misunderstanding something?
Comments
Comment #1
killes@www.drop.org commentedThe database gets filled by either uploading a PO file or enabling a new language and browsing the site. Did you do that?
Comment #2
dries commentedIf netbjarne didn't do so, it is not a bug, but it might still be a usability issue. It begs the question: is it clearly documented at the right place? Is there anything we can do to avoid this question in future?
Comment #3
netbjarne commentedI didn't create a new language, the only language available is the default english, so I assumed that the export would contain the english strings, ready for translation. I guess the procedure is somewhat different from that (i will dig into available documentation), but as dries suggest, it might be a usability issue calling for clearer help right there on the export page.
Regards
Bjarne
Comment #4
killes@www.drop.org commentedI guess the documentation should be improved. I don't want to change the current behaviour as it would impose a performance penalty for all users.
Comment #5
killes@www.drop.org commentedReassigning to documentation
Comment #6
sepeck commentedno activity, closing