public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: Call for small translation (for [PATCH 1/9] pakfire: Refactor dblist seperating UI and logic)
Date: Wed, 23 Mar 2022 22:09:53 +0100	[thread overview]
Message-ID: <a124956e58c9d04ed56ec6c950435609967198cf.camel@sicho.home> (raw)

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

Hi All

For the changes in "[PATCH 1/9] pakfire: Refactor dblist seperating UI
and logic", Michael pointed out that we should take advantage of the
code change to translate a few extra strings:

'core update' => 'Core-Update',
'pak update' => 'Update',
'release' => 'Release',
'version' => 'Version',

As used on pakfire.cgi listing the available updates:
$Lang::tr{'core update'} -- $pakfire_status{'CoreVersion'} --
$Lang::tr{'release'}: $pakfire_status{'Release'} ->
$pakfire_status{'AvailableRelease'}

For example:
Core-Update -- 2.27-x86-64 -- Release: 163 -> 164

and
$Lang::tr{'pak update'}: $pak -- $Lang::tr{'version'}:
$upgradelist{$pak}{'ProgVersion'} ->
$upgradelist{$pak}{'AvailableProgVersion'} -- $Lang::tr{'release'}:
$upgradelist{$pak}{'Release'} -> $upgradelist{$pak}{'AvailableRelease'}

For example:
Update: zabbix-agentd -- Version: 4.2.6 -> 5.0.21 -- Release: 4 -> 5

Could anyone on this list capable of translating these 4 strings in any
other language please reply with translations, so that I can
immediately integrate them in the patch.

I already have translations for Dutch.

Many thanks

Robin

-- 
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.


             reply	other threads:[~2022-03-23 21:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 21:09 Robin Roevens [this message]
     [not found] <AB791BDC-08B2-4757-A7B5-81715ABFBCD7@sicho.home>
2022-03-28 14:03 ` Michael Tremer
2022-04-19 19:14   ` Robin Roevens
2022-04-20 11:17     ` Leo Hofmann
2022-04-20 21:19       ` Robin Roevens
2022-06-23 21:01         ` Robin Roevens
2022-06-29 22:31           ` Robin Roevens
2022-07-06 10:04             ` Michael Tremer
     [not found] <9EB2EA84-CCA9-481A-B11E-5375A721119D@gmail.com>
2022-07-02 15:48 ` Stefan Schantl
     [not found] <626C7C30-DA39-4CBD-A8BF-6AD76F1068D4@sicho.home>
2022-07-07 11:38 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a124956e58c9d04ed56ec6c950435609967198cf.camel@sicho.home \
    --to=robin.roevens@disroot.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox