gmane.comp.audio.musicbrainz.i18n

[mb-i18n] Translation of documentation

Ian McEwen — 2013-02-19T02:43:22

Hi all; just wanted to quickly note that I'm starting to look into facilitating translation of documentation. I'd appreciate if some translators could look at my proposed solution; I've written it up in a comment on http://tickets.musicbrainz.org/browse/MBS-1406 -- presumably the bits about translators and for the process when a style guideline is updated (roughly, the bottom half of the comment) are most interesting to those on this list.

Feel free to respond here on the mailing list, on the ticket, or to me directly!

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

Re: [mb-i18n] Possible move of translations

Ian McEwen — 2013-02-09T14:11:33

As I understand it, that's only one option -- you can also configure a specific email to use for *all commits* for a project, which is probably what we'd do for privacy's sake. I don't know what attribution this provides, however -- I think the ideal situation would be it uses the actual person's name, but does not reveal their email.


This is because the 'command line client' is pulling from a git repository. No need to custom clients when you're using an existing protocol. No need to even add translations as submodules -- it commits directly to the appropriate location *in your actual source tree*. For example, clone git://git.weblate.org/freeplane-1-2-x.git and you'll see it's far from just translations :)


Note that there's several more projects on https://l10n.cihar.com/... but now that I look you're the last translator there. So you may have noticed that :P

In any case, it's based on translate toolkit, which can read and import a wide variety of translation formats -- it's not adopted by all that m

Re: [mb-i18n] Possible move of translations

Frederik "Freso" S. Olesen — 2013-02-09T13:42:54

Den 09-02-2013 04:07, Ian McEwen skrev:

I'm still messing around with it, but a few first impressions:

Good/better:
A) They're up front that one's name and e-mail address will be somewhat 
public (it says so on the registration page for the project sites). It's 
good that they state this so clearly, so translators are less likely to 
be surprised by this, although an option to register with a proper 
e-mail and use a bogus one for submissions/crediting purposes would be 
better. (I haven't actually made an account yet, so not sure if this is 
already possible. :))
B) Translations stored directly in Git. And we all know Git is the only 
proper way to handle any data. http://git.willfixeverything.com/ \o/

Bad/worse:
a) There seems to be no nifty command line client to help automate a lot 
of the workflow. For translators, this of course isn't the biggest 
issue, but as a translator-developer, I really like(d) the tx client, 
despite its shortcomings. However, coupled with B) above, perhaps 
translations can

[mb-i18n] Possible move of translations

Ian McEwen — 2013-02-09T03:07:12

Hi -- there are some definite problems with transifex that people have brought up and it seems to not be well-integrated with how people want to be doing things. Earlier today via RSS I saw http://blog.cihar.com/archives/2013/02/08/hosted-weblate-and-new-website/ and I'm wondering what people would think of us moving our translation stuff to weblate. It's my understanding that weblate fixes a few of our issues (perhaps most notably, weblate supports checks of various things, and it's more openly developed so it would be easier for me to contribute code fixes to them).

They have a demo site at http://demo.weblate.org -- could folks try it out and see what they think of weblate?

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

[mb-i18n] (Re)mix & (re)master in German

Simon Reinhardt — 2013-01-27T15:48:05

Hi,

I'm trying to translate these words into German and was wondering what other native speakers think about the words that various dictionary sites come up with. While I normally tend towards more native words in the translations I'm worried that people might not find what they're looking for because the advertising world speaks Denglisch anyway. Plus, some of them sound weird. :-)

So, I found this:

http://dict.tu-chemnitz.de/deutsch-englisch/abmischen.html
http://dict.tu-chemnitz.de/deutsch-englisch/Endbearbeitung.html
http://dict.leo.org/ende?lp=ende&p=DOKJAA&search=remix&trestr=0x4002
http://www.dict.cc/?s=abmischen
http://www.dict.cc/?s=remastered

Which would give us in the context of relationships (e.g.):

artist mixed recording - Künstler mischte ab Aufnahme
artist remixed recording - Künstler mischte neu ab Aufnahme
artist mastered release - Künstler endbearbeitete Veröffentlichung
artist remastered release - Künstler überarbeitete Veröffentlichung
release remaster of release - Veröffentl

[mb-i18n] Various Updates

Ian McEwen — 2013-01-15T23:28:32

With the holiday season over, i18n-related updates are back! The .pot files have just been updated:

* regular changes, such as added strings and a new language (Lakota)
* assorted bugfixes
* some splitting into contexts requested by v6lur -- things that appear both in headers/menus and on buttons are now split into two strings with contexts. However, operating on the assumption most languages won't care about the distinction, previous translations of any of the split strings have been migrated to both new versions. So, if your language cares about headers versus buttons, make sure to review those strings specifically.

I also have a vague todo list for all of my MB-related work, which is visible at https://trello.com/board/ianmcorvidae-s-mb-todo-list/50f4b3969b1f067b7600c04f -- if there's anything I should be looking at that's not there, direct it my way.

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1

Re: [mb-i18n] .pot file update, and other notes

Ian McEwen — 2012-11-28T15:42:05

Since at present we don't run tests with translations on, it should be fine to use &nbsp; if you'd like -- if you want to be consistent with the original, use the numerical escapes for potentially unclear characters (&#xa0; for nbsp, &#x2013; for ndash, &#x2014; for mdash) and unicode characters for anything easily distinguished (e.g. raquo). nbsp, especially, is pretty hard to tell apart from a plain space, hence using the escape.



--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

Re: [mb-i18n] .pot file update, and other notes

Mihkel Tõnnov — 2012-11-28T13:24:19

2012/11/28 Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org>


Is it okay to still use e.g. &nbsp; in translation? Or should I use the
literal character (" ") instead, like with "–", "—" etc.?

Mihkel

[mb-i18n] .pot file update, and other notes

Ian McEwen — 2012-11-27T22:21:02

.pot files have been updated, just normal code changes except for one bit, which is that for some obscure reasons related to testing well-formedness of HTML5 we changed a bunch of things that had &ndash; &mdash; &nbsp; or &raquo; in them. I've created a migration script, so your old translations shouldn't be lost, but don't be confused if you see &#x2013; (ndash), &#x2014; (mdash), or &#xa0; (nbsp) now while translating. Sorry for any confusion this potentially causes, and thanks for translating!

Feel free to pester me if anything looks weird, as always.

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

[mb-i18n] .pot files updated

Ian McEwen — 2012-10-31T20:01:57

I've just updated the .pot files on transifex. The most notable difference here is that autoeditor election statuses now have contexts, plus the usual churn of code changes. As I prepare to ship an upcoming branch that contextualizes a number of other things, I'll be working on a script to migrate translations with/without contexts, which I'll make sure to also run on the autoeditor election statuses. However, if you don't want to wait, you can retranslate them on transifex.

Happy translating!

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

[mb-i18n] Small snafu with .pot files/transifex

Ian McEwen — 2012-10-05T11:04:20

I manually uploaded some files and forgot to update my update-pot branch. When transifex then updated automatically later some strings disappeared, since it was looking at the old branch.

Sorry for the inconvenience; the translations should be on https://github.com/96187/musicbrainz-server/commit/3d6bc39235f3489e3a6edde1d4bdabcd5d9b25f6 for the most part.

And I've learned my lesson about manually uploading because I'm impatient, I suppose :)

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

[mb-i18n] .pot files updated

Ian McEwen — 2012-10-01T21:13:32

The usual sorts of changes; the 'server' and 'statistics' domains are the ones that have updated this time, including a number of v6lur and nikki's requests as well as the usual code updates and additions.

I've also updated the .po files used on beta, since we're out of freeze. In the developer meeting today we agreed that (at least for now), we'll update translations until the thursday before release (and thus somewhat after the code freeze), so hopefully in two weeks this won't be such a huge update.

Thanks as always to all the translators! :)

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

Re: [mb-i18n] Strings varying only by period or colon

Alexander Dupuy — 2012-10-01T15:28:57

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ian McEwen wrote:


In Western languages, there are a few cases where the use of punctuation is different; notably in French it is preferred to have a space before and after a colon (http://french.about.com/library/writing/bl-punctuation.htm) but I am not sure that would necessarily be desired in the typical use of colon in MBz.

However, if there are ever any localizations of MBz into non-Western languages, especially those using scripts other than Latin, Cyrillic, or Greek, it is quite likely that different punctuation would be desirable.  The Wikipedia article for "Full Stop" (http://en.wikipedia.org/wiki/Full_stop#Asian_period) lists a number of alternate symbols for period in Asian languages, ideographic full stop (U+3002 http://www.fileformat.info/info/unicode/char/3002/index.htm), Arabic full stop (U+06D4 http://www.fileformat.info/info/unicode/char/6d4/index.htm), Devanagari danda (U+0964 http://www.fileformat.info/info/unicode/char/964/index.htm), and S

[mb-i18n] Strings varying only by period or colon

Ian McEwen — 2012-10-01T01:07:37

See http://tickets.musicbrainz.org/browse/MBS-4822 -- I'm wondering how it'll work in all your various languages-of-choice to either:

a.) just plain move the . or : out of the string, and have it hardcoded
b.) have an extra string for e.g. "{item}." and "{item}:"

Or, put differently: are there any cases where you'll want to vary this sort of terminating punctuation (differently than it's done on the english site) based on the content of {item}?

I'd guess probably not, but there's often strange language-specific things I don't know about, so I like to ask.

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

[mb-i18n] i18n.mbsandbox.org codebase updated

Ian McEwen — 2012-09-21T01:03:08

I've updated the codebase running on i18n.mbsandbox.org to current beta, which should mean there aren't any (or at least *many*) inconsistencies between there and what you see on beta. i18n.mbsandbox.org is still where translations update automatically, so that's the place to test out new translations!

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

[mb-i18n] Translations are now on beta

Ian McEwen — 2012-09-19T20:10:28

Specifically: German, Estonian, Spanish, French, Italian, Dutch, Finnish, and Greek. I'll try to keep these updated; it's not automatic at present; feel free to pester me if I'm slacking :)

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

[mb-i18n] .pot files updated

Ian McEwen — 2012-09-11T20:38:05

It make take a bit of time for Transifex to pick them all up, but the .pot files have been updated to current beta. No particularly notable changes; should just be line number updates and such.

--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

Re: [mb-i18n] Enabling the translations on the beta server

Ian McEwen — 2012-09-01T13:40:34

I've actually already put it on the agenda for the developer meeting next Tuesday; I'm hoping to set up all the languages with 50% completion or better. Assuming (hopefully correctly) that everyone's okay with that, I'll work on the setup to make that happen and hopefully get things running before the next beta freeze next Friday.

On Sat, Sep 01, 2012 at 03:31:17PM +0200, Maurits Meulenbelt wrote:



--
Ian McEwen <ianmcorvidae-smx0hEoDkINGRWwXwiz5DA< at >public.gmane.org> <ihm08-6juwt9BsmR7V1CgomF1qdQ< at >public.gmane.org>
A262 D5C4 40CB 0E1C 5F24 C3A1 ABED 1ABD 7131 A76F
http://ianmcorvidae.net/

[mb-i18n] Enabling the translations on the beta server

Maurits Meulenbelt — 2012-09-01T13:31:17

Yo,

Is there any ETA on when the translations will be enabled on the beta 
server? I know a lot of translations are not yet complete, but working 
with the translations in a day-to-day situation with live data will make 
testing easier for me (and hopefully others).

Re: [mb-i18n] Strings needing context

Mihkel Tõnnov — 2012-08-28T20:36:10

2012/8/25 Mihkel Tõnnov <mihhkel-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>


And more:
From Estonian point of view, "Name" (and "Name:") should be split based on
whether it applies to works/recordings/tracks/releases/RGs or
artists/labels, since the first lot should have a 'title' in Estonian, not
'name'.

Also, the verb "Tag" (on the button) should be split from the noun "Tag"
(e.g. in the search dropdown near the top-right corner).

Best regards,
Mihkel

Re: [mb-i18n] Strings needing context

Mihkel Tõnnov — 2012-08-25T13:35:51

2012/8/25 Mihkel Tõnnov <mihhkel-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>


Oh, and:
anything in the timeline graphs which appears in contexts à la "123456
Edits" should be a separate string to be correctly translated into Estonian
(and a few other laguages, too, like Finnish -- or actually all languages
that would have the word for "Edits" be lowercase in a context like "123456
Edits").

Best regards,
Mihkel