1. 10 6月, 2020 16 次提交
  2. 09 6月, 2020 6 次提交
  3. 08 6月, 2020 4 次提交
  4. 05 6月, 2020 10 次提交
  5. 04 6月, 2020 4 次提交
    • D
      po: go back to storing the .pot file in git · 611e0312
      Daniel P. Berrangé 提交于
      To integrate with weblate the only practical option currently is to
      store the .pot file in git. This is required so that it can add new
      languages by cloning the .pot file. It also enables weblate to run
      msgmerge on the languages whenever pulling in new changes from git.
      
      The pot file will have to be the full content including the source
      locations, so this is going to result in unpleasant diffs when it
      is updated periodically.
      Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      611e0312
    • D
      po: stop stripping non-translated strings from po files · 35d68db5
      Daniel P. Berrangé 提交于
      We previously adopted a minimization technique for po files which
      stripped source locations and non-translated msgids in order to save
      space in the git repos and have saner commit diffs.
      
      At this time it is not possible to integrate with weblate while having
      non-translated msgids stripped, as it will immediately add them back
      again.
      
      By keeping all non-translated msgids, our .po files are about x2 the
      size at 37 MB vs the original 18 MB. This is still way better than the
      original po/ directory which was 109 MB. We're saving 38 MB by still
      omitting source file locations, and another 34 MB are saved by the
      dropping of all languages which are 100% untranslated.
      Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      35d68db5
    • D
      po: generate .pot file with strings in alphabetical order · 737cadff
      Daniel P. Berrangé 提交于
      The .po files are stored with strings in alphabetical order instead of
      source file location order, because this minimizes the diffs created
      when code moves around within or between files.
      
      By default msgmerge will honour the order of strings in the .pot file
      when creating a .po file, so it is useful if we also create the .pot
      file with desired ordering.
      Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      737cadff
    • D
      po: rename the .mini.po files to have just a .po suffix · 59e6bf20
      Daniel P. Berrangé 提交于
      A .mini.po file is exactly the same format as a .po file. We just used
      the alternative extension as we wanted to be able to store both full and
      minimized forms in the same directory.
      
      This complicates integration with some translation tools, however, which
      only really expect to see $LANG.po as a filename.
      
      With this change we drop the rules for creating non-minimized po files,
      and thus the po/*.po are always minimized. A useful side effect is that
      we no longer run msgmerge during creation of the gmo files, and thus
      don't need to have a date override to get reproducible builds.
      Reviewed-by: NPavel Hrdina <phrdina@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      59e6bf20