public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: ic <lists@benappy•com>
To: Justin Valceanu <justin@odm•ro>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bip-0039/Wordlist - Romanian
Date: Wed, 4 Aug 2021 15:28:55 +0200	[thread overview]
Message-ID: <680CB4BF-5991-4648-8DF0-78077E514482@benappy.com> (raw)
In-Reply-To: <112f5fa6-510c-8280-4f65-fbb0d41a5aa4@odm.ro>

Hi,

> On 4 Aug 2021, at 12:30, Justin Valceanu via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> 
> I have created a new Romanian wordlist for Bip-0039;
> Requesting permission to push to github the attached modified files.

Although I don’t think it ’s hard requirement, it would be great if the words could be uniquely identified using the first 4 letters (most metal backup “plates” only have space for 4 letters).

I see several occurrences of conflicting words in the first page alone.

++ ic



  reply	other threads:[~2021-08-04 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d40d7068-3b13-64ad-aef5-30210212a79c@odm.ro>
2021-08-04 10:30 ` Justin Valceanu
2021-08-04 13:28   ` ic [this message]
2021-08-04 22:29     ` s7r
2021-08-05  6:16       ` Justin Valceanu

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=680CB4BF-5991-4648-8DF0-78077E514482@benappy.com \
    --to=lists@benappy$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=justin@odm$(echo .)ro \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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