Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Migrations to xorriso
Date: Wed, 19 May 2010 23:23:44 +0200	[thread overview]
Message-ID: <4BF456E0.8090009@gmail.com> (raw)
In-Reply-To: <106227837017031@192.168.2.69>

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

Thomas Schmitt wrote:
> Hi,
>
> reviewing my grub-mkrescue 1.98 test script
> i see these options which will cause the files
> in /boot to have low block addresses:
>
>    xorriso ... -as mkisofs ... \
>    --sort-weight 0 / --sort-weight 1 /boot \
>    ...
>
> The boot catalog gets a low LBA by default.
>
> I remember Vladimir mentioned that some BIOSes
> need low addresses.
> So probably one should add these options to
> grub-mkrescue.in.
>
>   
Ok, will do.
> Vladimir Serbinenko wrote:
>   
>> @Thomas: grub-mkisofs was partially translated. Could you look into
>> reusing translation strings for xorriso?
>>     
>
> Currently there is no internationalization in
> xorriso. I would probably need some advise and
> an interested translator to make it ready for
> that.
>
>   
Actually it seems that xorriso doesn't have a lot of common strings with
grub-mkisofs so probably there is no much value in reusing strings.
As for advice: you already have automake so adding gettext should be
easy change in Makefile.am followed by marking all translatable strings
with _() and including proper header.
But the hic is if xorriso uses any like
printf("Device %s is %s.", devname, valid ? "valid" : "invalid");
will need to be changed to:
printf(valid ?_("Device %s is valid."):_("Device %s is invalid."), devname);
since string operations are untranslatable.

>
> Have a nice day :)
>
> Thomas
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  reply	other threads:[~2010-05-19 21:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 21:33 Migrations to xorriso Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-18  8:49 ` Thomas Schmitt
2010-05-18 12:50 ` Thomas Schmitt
2010-05-19 19:45 ` Thomas Schmitt
2010-05-19 21:23   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-05-20  6:31     ` Thomas Schmitt
  -- strict thread matches above, loose matches on Subject: below --
2010-05-19 12:01 Thomas Schmitt
2010-05-19 12:13 ` Colin Watson
2010-05-19 13:23   ` Thomas Schmitt
2010-05-19 21:02     ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-19 18:40   ` Isaac Dupree
2010-05-19 19:34     ` Thomas Schmitt
2010-05-19 21:10       ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-19 21:35         ` Seth Goldberg
2010-05-19 21:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-20  9:30 Thomas Schmitt

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=4BF456E0.8090009@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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