IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Change the translation of HA with 'Cluster' to 'High availability' to avoid
confusion.
Co-Authored-By: Ольга Миронова <omiro@basealt.ru>
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
recently we got an update for our chinese translation with a lot of
fixes[1], but the external contributor forgot to remove the fuzzy
lines on fixed entries, so do this now. I left out commented out
entries for time reasons, we can always fix them up if they get
included again.
[1]: commit 59baa74279717cfcfb4b680f7bac9e970b93678cq
rsync everything in a temporary build directory and let buildpackage
handle the rest.
Has the advantage that both packages can be assembled in one
buildpackage run, whereas previous it was called twice.
Further, we can omit the do `make install` manually before calling
dpkg-buildpackage and use .SECONDARY so that make keeps the files.
It's not used anywhere else in our build systems and not really
needed.
If a new language gets added just run:
make init-XY.po
This won't happen that often, so an auto create has not a real use,
especially as the .po file must then be edited anyway.
Also we now can reuse the new 'messages.pot' target in the 'update'
target and a strict separation between initialising a new language
and updating a existing one seems reasonable.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
instead of creating a po file per source package
(that are: pmg-gui, proxmox-widget-toolkit and pve-manager),
but combine the messages from them and create one
po file per language.
to not include unneeded strings in the (pve|pmg)-lang-*.js files,
we use the references value in po2js.pl to filter out unwanted strings
also include a git submodule update in the 'update' target, so that
we get the newest version when updating the po file
