https://bugs.kde.org/show_bug.cgi?id=402890
--- Comment #5 from Karl Ove Hufthammer <k...@huftis.org> --- (In reply to Simon Depiets from comment #4) > Revisiting this now, should the .po file be next to the .pot by default and > we let the user move the generated .po file by himself if he has a different > folder structure? No. The PO file structure mirrors the POT file structure. The structure is set up in the project options (root folder for the PO files, template folder for the POT files). So if the POT file is at ~/kde/trunk/l10n-support/templates/summit/messages/kpat/kpat_mimetypes.pot and the PO file is at ~/kde/trunk/l10n-support/nn/summit/messages/kpat/kpat_mimetypes.po the template folder would be set to (for example) ~/kde/trunk/l10n-support/templates/summit/messages and the root folder would be set to ~/kde/trunk/l10n-support/nn/summit/messages Lokalize handles this perfectly file if you *click* on a single POT file (which doesn’t have a PO file). The PO file is automatically stored in the correct place, in a folder structure in the root folder mirroring the folder structure in the templates folder. It’s when you instead use the ‘Open selected files’ on a folder containing POT files that the PO files generated are stored in the wrong place (and with the wrong extension, POT instead of PO). So perhaps the two ways of creating a PO file from a POT files doesn’t use the same code path? -- You are receiving this mail because: You are watching all bug changes.
