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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
ship previously used kr, which actually stands for Kanuri, as compat
symlink to avoid breaking existing setups, as those can have saved the
language in the datacenter.cfg and the users can have it in the
language cookie too. But we might want to map the kr to ko
transparently there in the future (e.g., next major release)
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
makes it slightly easier to work with it, if its deemed to bloat the
makefile to much, we could move it to its separate linguas.mk or so
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
calling do_update allows one to refresh the .po files without pulling
in new submodule updates, that is useful when external contributors
send in a translations update by sending the whole .po file via mail,
with a possible older git commit as base. This way one can refresh
line numbers and new messages while keeping the updated state they
send.
Doing the order via explicit `$(MAKE) target` invocations seems
simpler and less error prone too.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
It is useful to have a way to see the translation statistics. The
output could potentially get used to have an overview page about the
translations and invite people to help out through that.
Signed-off-by: Rhonda D'Vine <rhonda@proxmox.com>
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
