-
-
Notifications
You must be signed in to change notification settings - Fork 958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for INI-Format without section headers #5715
Comments
That might work as Java properties or Joomla files. |
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
Hmmm okay Java Properties worked but the output filename needs of course to be renamed. I'll see if I can do this via addon. Nevertheless I still want to suggest to parse ini files without sections. Sections are not needed. |
The filename is not anyhow linked with the format, whatever you specify will be used. The section requirement is caused by iniparse library which translate-toolkit uses to parse INI files. |
This issue has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
Is your feature request related to a problem? If so, please describe.
I try to import INI-files without containing section headers (e.g.
[foo]
).Weblate complains about, that no section header was found in the base file. (Screenshots)
I see no need for a header file and as this files are later read in from the target program I cannot just add a section header.
I also tried it with CSV but I cannot enter a custom separator.
Describe the solution you'd like
As I fail to see why headers are needed, I suggest to remove the need of headers in ini files. This shouldn't break anything.
Describe alternatives you've considered
One alternative would be add a parameter to enter a custom CSV separator.
On my side I've problems to integrate the weblate into the CI-process. As weblate pulls automatically I cannot run a pre-process script, which adds a foo-header nand a post-process script to remove it before pushing.
Screenshots
Additional context
These are the files I want to integrate following files into weblate:
from https://github.com/legacyclonk/LegacyClonk/tree/master/planet/System.c4g
The text was updated successfully, but these errors were encountered: