From: "bovirus \(gmail\)" <bovirus@gmail.com>
To: <grub-devel@gnu.org>
Subject: Grub2 language .po files - Doubts about original strings syntax
Date: Fri, 5 Apr 2024 21:21:48 +0200 [thread overview]
Message-ID: <001d01da878e$8178e2e0$846aa8a0$@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 716 bytes --]
Hi.
I have some doubts about language sorurce strings syntax
Starting lowercase (instead uppercase) with multiline strings. Ex
other software is using the embedding area, and there is not enough room for
core.img. Such software is often trying to store data in a way that avoids
detection. We recommend you investigate
String multiline that strt in lowercase and end without ".". Ex:
Sector %llu is already in use by raid controller `%s'; avoiding it. Please
ask the manufacturer not to store data in MBR gap
String with double spaces
Multiline strings without "." at the end
Double \\ in some strings. Ex.
Usage: %s -o OUTPUT CKBMAP_ARGUMENTS...\\n
All are right?
Thanks.
[-- Attachment #1.2: Type: text/html, Size: 3637 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
reply other threads:[~2024-04-05 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001d01da878e$8178e2e0$846aa8a0$@gmail.com' \
--to=bovirus@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).