Bulgarian translation of Racket

[Alexander Shopov]

Hi everyone,

I am Alexander Shopov and I am announcing that I have started Bulgarian translation of Racket's strings. 

Bulgarian is a South Slavic language, official in Bulgaria.

I have been translating FLOSS for about 16 years now and I finally got to Racket

I am about 10% done with the 1250 messages.

My approach is similar to the one described in this mail:

http://lists.racket-lang.org/dev/archive//2014-September/014652.html

Since you have already split the whole of Racket into multitude of modules published via GitHub, I have forked racket/string-constants (as announced in http://blog.racket-lang.org/2015/06/racket-v62.html) and will publish via pull request (unless instructed otherwise).

I see string-constants is licensed GNU LGPL (https://github.com/racket/string-constants/blob/master/string-constants/LICENSE.txt) and will state in my translation that it is licensed under the same terms as the string-constants package. Since you just point to the GNU page: http://www.gnu.org/copyleft/lesser.html I assume currently you mean version 3 of the license and will automatically relicense to new versions as they get published. (I am fine with that, just wanted it explicitly confirmed).

Do you have any timeframe for the next version, do plan on major interface changes that will massively change the interface strings?

Kind regards:

al_shopov

[Robby Findler]

On Mon, Jul 27, 2015 at 1:52 AM, Alexander Shopov <a...@kambanaria.org> wrote:
> Hi everyone,
>
> I am Alexander Shopov and I am announcing that I have started Bulgarian
> translation of Racket's strings.
>
> Bulgarian is a South Slavic language, official in Bulgaria.
>
> I have been translating FLOSS for about 16 years now and I finally got to
> Racket
>
> I am about 10% done with the 1250 messages.

Thanks!

Just in case it wasn't clear: this is only for the IDE -- error
messages and other text in Racket is currently only in English.

> My approach is similar to the one described in this mail:
> http://lists.racket-lang.org/dev/archive//2014-September/014652.html
>
> Since you have already split the whole of Racket into multitude of modules
> published via GitHub, I have forked racket/string-constants (as announced in
> http://blog.racket-lang.org/2015/06/racket-v62.html) and will publish via
> pull request (unless instructed otherwise).

That sounds great.

> I see string-constants is licensed GNU LGPL
> (https://github.com/racket/string-constants/blob/master/string-constants/LICENSE.txt)
> and will state in my translation that it is licensed under the same terms as
> the string-constants package. Since you just point to the GNU page:
> http://www.gnu.org/copyleft/lesser.html I assume currently you mean version
> 3 of the license and will automatically relicense to new versions as they
> get published. (I am fine with that, just wanted it explicitly confirmed).

Yes.

> Do you have any timeframe for the next version, do plan on major interface
> changes that will massively change the interface strings?

We try to avoid that, if at all possible.

Best,
Robby

> Kind regards:
> al_shopov
>
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-dev/3f89accf-5ccd-49af-8adf-1072c4211aed%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Alexander Shopov]

​Hello everyone,

I have finished the Bulgarian translation of DrRacket and am in the final stages of testing and improving it. I expect to submit a pull request in a fortnight.​

I have several questions:

1. There are some messages that are commented out with ';' - should I translate them - are they left in on purpose or are they going to be deleted?

2. Are there any other Bulgarian speaking people interested in testing the translation?

3. Is there interest in converting to and from gettext po-message format?

4. Are improvements in original messages in English welcome - there are places for small improvements in typography for example. This will not place additional burden on other translators?

5. There are some messages that have not been included for translation, most probably an omission. Should I send patches for such messages? This will place additional burden on other translators.

6. Is there a way to checkout the whole source of DrRacket - not module by module?

Kind regards:

al_shopov

[Robby Findler]

On Wed, Dec 9, 2015 at 2:06 PM, Alexander Shopov <a...@kambanaria.org> wrote:
> Hello everyone,
>
> I have finished the Bulgarian translation of DrRacket and am in the final
> stages of testing and improving it. I expect to submit a pull request in a
> fortnight.
>
> I have several questions:
> 1. There are some messages that are commented out with ';' - should I
> translate them - are they left in on purpose or are they going to be
> deleted?

Don't translate them.

> 2. Are there any other Bulgarian speaking people interested in testing the
> translation?
> 3. Is there interest in converting to and from gettext po-message format?

I'm not sure about this one.

> 4. Are improvements in original messages in English welcome - there are
> places for small improvements in typography for example. This will not place
> additional burden on other translators?

No, that's fine. Do you have an example of what you're thinking of so
I know what you mean?

> 5. There are some messages that have not been included for translation, most
> probably an omission. Should I send patches for such messages? This will
> place additional burden on other translators.

Yes, do that. But perhaps before you put a lot of work into that,
maybe show me a few examples.

> 6. Is there a way to checkout the whole source of DrRacket - not module by
> module?

You can check it out pkg by pkg and mostly of the GUI things are in
the "gui" and the "drracket" pkg. (Is that what you're asking?)

Robby

[Alexander Shopov]

>> improvements in original messages in English

> example of what you're thinking of so I know what you mean?

Replace triple dot ... with Unicode ellipsis …
Replace simple double quotes "text" with English curly ones: “text” -
no need to escape these

>> messages that have not been included for translation

> show me a few examples
Typical examples
1. Initial message:
Welcome to DrRacket, version 6.3 [3m].
Language: racket; memory limit: 128 MB.
The phrase 'memory limit' cannot be translated
2. Most of the labels in the dialog Preferences -> Tools

>> way to checkout the whole source of DrRacket

> check it out pkg by pkg … (Is that what you're asking?)
No, this will not do. There should be some way you checkout the whole
source of DrRacket - it used to be one repo, right? I expect you do
something like this for releases and packaging. Perhaps you use git
submodules or something similar. I need context for some of the
messages which means checking in code what kind of arguments
(sometimes deducible by the name of variables around the message or
the name of the function where the message is used).

Kind regards:
al_shopov

[Paul A. Steckler]

On Wed, Dec 9, 2015 at 12:11 PM, Robby Findler
<ro...@eecs.northwestern.edu> wrote:
>> 2. Are there any other Bulgarian speaking people interested in testing the
>> translation?

I know a native Bulgarian speaker near me. If it's useful, I can ask
him if he'd be willing to review the
translation.

-- Paul

[Robby Findler]

On Wed, Dec 9, 2015 at 3:15 PM, Alexander Shopov <a...@kambanaria.org> wrote:
>>> improvements in original messages in English
>> example of what you're thinking of so I know what you mean?
> Replace triple dot ... with Unicode ellipsis …
> Replace simple double quotes "text" with English curly ones: “text” -
> no need to escape these

I see. That would be very helpful, thank you!

>>> messages that have not been included for translation
>> show me a few examples
> Typical examples
> 1. Initial message:
> Welcome to DrRacket, version 6.3 [3m].
> Language: racket; memory limit: 128 MB.
> The phrase 'memory limit' cannot be translated
> 2. Most of the labels in the dialog Preferences -> Tools

Ah, I see. Yes, that would be great!

>>> way to checkout the whole source of DrRacket
>> check it out pkg by pkg … (Is that what you're asking?)
> No, this will not do. There should be some way you checkout the whole
> source of DrRacket - it used to be one repo, right? I expect you do
> something like this for releases and packaging. Perhaps you use git
> submodules or something similar. I need context for some of the
> messages which means checking in code what kind of arguments
> (sometimes deducible by the name of variables around the message or
> the name of the function where the message is used).

No, we don't do that any more. We use the pkg system. We do not have a
single repo (just like the source code for your operating system isn't
in a single repo either (yes we have big ambitions! :)).

There should perhaps be improvements to the documentation, but let me
suggest you have a look at the pkg docs. You'll want to think of the
pkgs that you are modifying as "yours" for the purpose of those docs.
One particularly useful operation for your workflow is "raco pkg
update --clone <pkg-name>". And if you wish to make suggestions or
have questions, please ask them on this mailing list.

Robby