b94239a61e
Instead of creating an empty object and then setting keys one at a time, it is possible to pass a dict object to configuration_data(). This is nicer because it doesn't require repeating the name of the cfg_data object over and over. There is one exception: the 'conf' object, where we store values that are used directly by C code. In that case, using a dict object is not feasible for two reasons: first of all, replacing the set_quoted() calls would result in awkward code with a lot of calls to format(); moreover, since code that modifies it is sprinkled all over the place, refactoring it would probably make things more complicated rather than simpler. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com> |
||
|---|---|---|
| .. | ||
| as.po | ||
| bg.po | ||
| bn_IN.po | ||
| bs.po | ||
| ca.po | ||
| cs.po | ||
| da.po | ||
| de.po | ||
| el.po | ||
| en_GB.po | ||
| es.po | ||
| fi.po | ||
| fr.po | ||
| gu.po | ||
| hi.po | ||
| hu.po | ||
| id.po | ||
| it.po | ||
| ja.po | ||
| kn.po | ||
| ko.po | ||
| libvirt.pot | ||
| LINGUAS | ||
| meson.build | ||
| mk.po | ||
| ml.po | ||
| mr.po | ||
| ms.po | ||
| nb.po | ||
| nl.po | ||
| or.po | ||
| pa.po | ||
| pl.po | ||
| POTFILES.in | ||
| pt_BR.po | ||
| pt.po | ||
| README.rst | ||
| ru.po | ||
| si.po | ||
| sr.po | ||
| sr@latin.po | ||
| sv.po | ||
| ta.po | ||
| te.po | ||
| tr.po | ||
| uk.po | ||
| vi.po | ||
| zh_CN.po | ||
| zh_TW.po | ||
Libvirt Message Translation
Libvirt translatable messages are maintained using the GNU Gettext tools and file formats, in combination with the Fedora Weblate web service.
https://translate.fedoraproject.org/projects/libvirt/libvirt/
Source repository
The libvirt GIT repository stores the master "libvirt.pot" file, which is to be refreshed at time of feature freeze.
The "po" files stored in GIT have source locations removed in order to cut down on storage size, by eliminating information already present in the "pot" file. All files are stored with strings sorted in alphabetical order rather than source location order, to minimize movement of strings when source locations change.
The "po" files are to be EXCLUSIVELY UPDATED by merge requests sent from the Fedora Weblate service. Other contributors MUST NEVER send changes which touch the "po" file content, as that will create merge conflicts for Weblate. IOW any bug fixes to translations should be made via the Weblate application UI.
After the "pot" file in libvirt GIT, Weblate will automatically run "msgmerge" to update the "po" files itself and send back a merge request with the changes.
Translation updates made in the Weblate Web UI will be committed to its fork of the GIT repo once a day. These commits will be submitted back to the master GIT repo via merge requests. If a merge request from Weblate is already open, commits will be added to this existing merge request. Weblate will take care of rebasing whenever changes happen in Git master. In order to avoid having to do translations merges 30 times a month, merge requests from Weblate will usually be left open until feature freeze arrives. During the freeze period, they will be accepted more promptly to ensure they make it into the new release.