I18n

i18n@lists.geany.org

300 discussions

Re: [Geany-i18n] I18n Digest, Vol 75, Issue 2
by André Glória 17 Jan '16

17 Jan '16

Hello, I just want to give you my 2 cents on this discussion. I agree with you, proper names should never be translated. And those examples are quite good, Geany, MS Word, LibreOffice, etc. In this plugin's particular case I would never translated "Bird's Eye" but I would say that since it is called "Overview" it should. My reasoning is the following, the former name does not really imply the plugin's functionality while the latter is more of its function/action than its name. And if you look at other Geany's plugins I would say that this is their main idea also, GeanyPy is a name but "Split Window" is a function/action. Ultimately you have to assume that the translation is made to help people that have zero knowledge on the original's program language, and therefore the more you translate the better. While translating a name like "Geany "does not give you any benefits (imho), translating a function/action does. Off course you could argue that at least in Geany's case the plugins are presented on a list with a succinct description right under their name which could make translating their "name" irrelevant. I would agree with such argument but I would still stand by the fact that if the plugin's name is more of its function/action than a name per se it still brings more value to translated than not. Kind regards, André 2016-01-16 9:00 GMT+00:00 <i18n-request(a)lists.geany.org>: > Send I18n mailing list submissions to > i18n(a)lists.geany.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.geany.org/cgi-bin/mailman/listinfo/i18n > or, via email, send a message with subject or body 'help' to > i18n-request(a)lists.geany.org > > You can reach the person managing the list at > i18n-owner(a)lists.geany.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of I18n digest..." > > Today's Topics: > > 1. Re: Incorrect russian translation of overview plugin > (Matthew Brush) > 2. Re: Incorrect russian translation of overview plugin > (Yan Pashkovskiy) > 3. Re: Incorrect russian translation of overview plugin > (Matthew Brush) > > > ---------- Mensagem reencaminhada ---------- > From: Matthew Brush <mbrush(a)codebrainz.ca> > To: i18n(a)lists.geany.org > Cc: > Date: Fri, 15 Jan 2016 06:56:44 -0800 > Subject: Re: [Geany-i18n] Incorrect russian translation of overview plugin > On 2016-01-15 12:48 AM, Yan Pashkovskiy wrote: > >> I was talking about View - Show overview. If this string was >> untranslated - it was hard to understand what is it. Plugin name >> should be translateable too imho. >> >> > Mostly I was just wondering why it should be translated in some places and > not in others. Looking at other plugins, it seems to be a mix of plugin > names being translated or not. I was previously under the impression that > proper names weren't to be translated, for example how plugin author names > aren't translated. Is the rule that you only translate names of things but > not people? > > I guess an example would be 'Geany', does it get translated as well? > Something with meaning of 'magic man who comes out of bottle'? If Geany > doesn't get translated, would 'Overview' be translated if it's name was > 'Goverview'? What about 'GeanyPy', would it be translated as 'Snake of the > editor' or something? > > Apologies if these are stupid questions, I just want to understand as I > only speak English and French. In Canadian English and French I don't think > proper names of things get translated (although people's names sometimes > are - my name sometimes becomes Mathieu). But, for example, 'Hitachi' > company name is not translated to 'Sunrise' in English, and 'Apple' > computer name is not translated to 'Pomme' in French here. > > I don't care either way, I just want to know what rule to consistently > apply to my plugins' names, if possible. > > Cheers, > Matthew Brush > > As for Russian language: I don't know whether name should be >> capitalized or not (grammar rules say that shouldn't, but it is >> plugin name!). I just think it shouldn't be more than 20 symbols: >> "карта документа", "обзор документа" are valid, but "показать обзор >> документа" not (show document overview). And I also think that >> "затемнение" is definitely bad l10n :) >> >> Regards, Yan >> >> >> 15 янв. 2016 г., в 11:22, Matthew Brush <mbrush(a)codebrainz.ca> >>> написал(а): >>> >>> On 2016-01-14 7:25 PM, Baurzhan Muftakhidinov wrote: >>>> Hi, >>>> >>>> In Russian writing "Обзор Документа" is incorrect - it should be >>>> "Обзор документа" >>>> >>>> On Fri, Jan 15, 2016 at 4:21 AM, Yan Pashkovsky <yanpaso(a)gmail.com> >>>>> wrote: >>>>> Oh, I've forgot to mention original naming, it is "затемнение". How can >>>>> I participate in renaming? I may provide git patch of ru.po (or just >>>>> new >>>>> .po file) >>>>> By the way are there any plans to move to transifex or launchpad >>>>> translations? :) Seems to be handy tools >>>>> >>>>> 15.01.2016 01:34, Frank Lanitz пишет: >>>>> >>>>>> On 14.01.2016 23:22, Yan Pashkovsky wrote: >>>>>>> High everybody! >>>>>>> >>>>>>> Overview plugin in russian l18n should be translated to "Обзор >>>>>>> Документа" or like in Notepad++ "Карта документа" (document map). >>>>>>> Currently it means eclipse, which is weird >>>>>>> >>>>>> Not a native, but somehow I like Обзор Документа more -- sounds nice >>>>>> ;) >>>>>> >>>>> >>> Is it customary to translate the "proper name" of a piece of software? >>> >>> I figured it wasn't so I didn't mark the plugin name as translatable, >>> but I see a few places in the UI file where I used it as a proper name but >>> neglected to correctly capitalize it (I guess that's where the strings in >>> question come from?) >>> >>> Should I mark the plugin name as translatable? >>> >>> Also, is it worthwhile to fix the capitalization in the English UI >>> strings? >>> >>> Cheers, >>> Matthew Brush >>> _______________________________________________ >>> I18n mailing list >>> I18n(a)lists.geany.org >>> https://lists.geany.org/cgi-bin/mailman/listinfo/i18n >>> >> _______________________________________________ >> I18n mailing list >> I18n(a)lists.geany.org >> https://lists.geany.org/cgi-bin/mailman/listinfo/i18n >> >> > > > > ---------- Mensagem reencaminhada ---------- > From: Yan Pashkovskiy <yanpaso(a)gmail.com> > To: Geany translations mailing list <i18n(a)lists.geany.org> > Cc: > Date: Fri, 15 Jan 2016 20:21:37 +0300 > Subject: Re: [Geany-i18n] Incorrect russian translation of overview plugin > I see it like this: unique things, such as MS Word shouldn't be > translated, and common things like "find and replace" should. > Overview is not unique (np++, sublime) and users will only suffer from > incorrect translation or missing of translation. By the way overview is > common English word, it's not a brand. Currently translation exists and it > is incorrect. > > > > 15 янв. 2016 г., в 17:56, Matthew Brush <mbrush(a)codebrainz.ca> > написал(а): > > > >> On 2016-01-15 12:48 AM, Yan Pashkovskiy wrote: > >> I was talking about View - Show overview. If this string was > >> untranslated - it was hard to understand what is it. Plugin name > >> should be translateable too imho. > > > > Mostly I was just wondering why it should be translated in some places > and not in others. Looking at other plugins, it seems to be a mix of plugin > names being translated or not. I was previously under the impression that > proper names weren't to be translated, for example how plugin author names > aren't translated. Is the rule that you only translate names of things but > not people? > > > > I guess an example would be 'Geany', does it get translated as well? > Something with meaning of 'magic man who comes out of bottle'? If Geany > doesn't get translated, would 'Overview' be translated if it's name was > 'Goverview'? What about 'GeanyPy', would it be translated as 'Snake of the > editor' or something? > > > > Apologies if these are stupid questions, I just want to understand as I > only speak English and French. In Canadian English and French I don't think > proper names of things get translated (although people's names sometimes > are - my name sometimes becomes Mathieu). But, for example, 'Hitachi' > company name is not translated to 'Sunrise' in English, and 'Apple' > computer name is not translated to 'Pomme' in French here. > > > > I don't care either way, I just want to know what rule to consistently > apply to my plugins' names, if possible. > > > > Cheers, > > Matthew Brush > > > >> As for Russian language: I don't know whether name should be > >> capitalized or not (grammar rules say that shouldn't, but it is > >> plugin name!). I just think it shouldn't be more than 20 symbols: > >> "карта документа", "обзор документа" are valid, but "показать обзор > >> документа" not (show document overview). And I also think that > >> "затемнение" is definitely bad l10n :) > >> > >> Regards, Yan > >> > >> > >>>> 15 янв. 2016 г., в 11:22, Matthew Brush <mbrush(a)codebrainz.ca> > написал(а): > >>>> > >>>> On 2016-01-14 7:25 PM, Baurzhan Muftakhidinov wrote: > >>>> Hi, > >>>> > >>>> In Russian writing "Обзор Документа" is incorrect - it should be > >>>> "Обзор документа" > >>>> > >>>>> On Fri, Jan 15, 2016 at 4:21 AM, Yan Pashkovsky <yanpaso(a)gmail.com> > wrote: > >>>>> Oh, I've forgot to mention original naming, it is "затемнение". How > can > >>>>> I participate in renaming? I may provide git patch of ru.po (or just > new > >>>>> .po file) > >>>>> By the way are there any plans to move to transifex or launchpad > >>>>> translations? :) Seems to be handy tools > >>>>> > >>>>> 15.01.2016 01:34, Frank Lanitz пишет: > >>>>>>> On 14.01.2016 23:22, Yan Pashkovsky wrote: > >>>>>>> High everybody! > >>>>>>> > >>>>>>> Overview plugin in russian l18n should be translated to "Обзор > >>>>>>> Документа" or like in Notepad++ "Карта документа" (document map). > >>>>>>> Currently it means eclipse, which is weird > >>>>>> Not a native, but somehow I like Обзор Документа more -- sounds > nice ;) > >>> > >>> Is it customary to translate the "proper name" of a piece of software? > >>> > >>> I figured it wasn't so I didn't mark the plugin name as translatable, > but I see a few places in the UI file where I used it as a proper name but > neglected to correctly capitalize it (I guess that's where the strings in > question come from?) > >>> > >>> Should I mark the plugin name as translatable? > >>> > >>> Also, is it worthwhile to fix the capitalization in the English UI > strings? > >>> > >>> Cheers, > >>> Matthew Brush > >>> _______________________________________________ > >>> I18n mailing list > >>> I18n(a)lists.geany.org > >>> https://lists.geany.org/cgi-bin/mailman/listinfo/i18n > >> _______________________________________________ > >> I18n mailing list > >> I18n(a)lists.geany.org > >> https://lists.geany.org/cgi-bin/mailman/listinfo/i18n > > > > _______________________________________________ > > I18n mailing list > > I18n(a)lists.geany.org > > https://lists.geany.org/cgi-bin/mailman/listinfo/i18n > > > > ---------- Mensagem reencaminhada ---------- > From: Matthew Brush <mbrush(a)codebrainz.ca> > To: i18n(a)lists.geany.org > Cc: > Date: Fri, 15 Jan 2016 16:56:35 -0800 > Subject: Re: [Geany-i18n] Incorrect russian translation of overview plugin > On 2016-01-15 9:21 AM, Yan Pashkovskiy wrote: > >> I see it like this: unique things, such as MS Word shouldn't be >> translated, and common things like "find and replace" should. >> Overview is not unique (np++, sublime) and users will only suffer from >> incorrect translation or missing of translation. By the way overview is >> common English word, it's not a brand. Currently translation exists and it >> is incorrect. >> >> > Hmm, OK. But I guess MS Word isn't unique either, for example there's > LibreOffice Writer which does the same thing but has a different name. > Similarly, I don't think NP++ or Sublime call their minimap "Overview". The > original name of the plugin was "Bird's Eye" (as in "Bird's Eye View"), but > someone suggested the name "Overview", and I liked it, so I changed it. > > Anyway, I guess there's no solid rules to follow in natural languages :) > > If anyone wants to let me know if I should mark any of my plugins' names > for translation and I'd happily do it, that way it will show up with a more > meaningful name in the Plugin Manager dialog. Right now it looks like some > plugins do this and some don't. > > Thanks for the info. > > Cheers, > Matthew Brush > > >> 15 янв. 2016 г., в 17:56, Matthew Brush <mbrush(a)codebrainz.ca> >>> написал(а): >>> >>> On 2016-01-15 12:48 AM, Yan Pashkovskiy wrote: >>>> I was talking about View - Show overview. If this string was >>>> untranslated - it was hard to understand what is it. Plugin name >>>> should be translateable too imho. >>>> >>> >>> Mostly I was just wondering why it should be translated in some places >>> and not in others. Looking at other plugins, it seems to be a mix of plugin >>> names being translated or not. I was previously under the impression that >>> proper names weren't to be translated, for example how plugin author names >>> aren't translated. Is the rule that you only translate names of things but >>> not people? >>> >>> I guess an example would be 'Geany', does it get translated as well? >>> Something with meaning of 'magic man who comes out of bottle'? If Geany >>> doesn't get translated, would 'Overview' be translated if it's name was >>> 'Goverview'? What about 'GeanyPy', would it be translated as 'Snake of the >>> editor' or something? >>> >>> Apologies if these are stupid questions, I just want to understand as I >>> only speak English and French. In Canadian English and French I don't think >>> proper names of things get translated (although people's names sometimes >>> are - my name sometimes becomes Mathieu). But, for example, 'Hitachi' >>> company name is not translated to 'Sunrise' in English, and 'Apple' >>> computer name is not translated to 'Pomme' in French here. >>> >>> I don't care either way, I just want to know what rule to consistently >>> apply to my plugins' names, if possible. >>> >>> Cheers, >>> Matthew Brush >>> >>> As for Russian language: I don't know whether name should be >>>> capitalized or not (grammar rules say that shouldn't, but it is >>>> plugin name!). I just think it shouldn't be more than 20 symbols: >>>> "карта документа", "обзор документа" are valid, but "показать обзор >>>> документа" not (show document overview). And I also think that >>>> "затемнение" is definitely bad l10n :) >>>> >>>> Regards, Yan >>>> >>>> >>>> 15 янв. 2016 г., в 11:22, Matthew Brush <mbrush(a)codebrainz.ca> >>>>>> написал(а): >>>>>> >>>>>> On 2016-01-14 7:25 PM, Baurzhan Muftakhidinov wrote: >>>>>> Hi, >>>>>> >>>>>> In Russian writing "Обзор Документа" is incorrect - it should be >>>>>> "Обзор документа" >>>>>> >>>>>> On Fri, Jan 15, 2016 at 4:21 AM, Yan Pashkovsky <yanpaso(a)gmail.com> >>>>>>> wrote: >>>>>>> Oh, I've forgot to mention original naming, it is "затемнение". How >>>>>>> can >>>>>>> I participate in renaming? I may provide git patch of ru.po (or just >>>>>>> new >>>>>>> .po file) >>>>>>> By the way are there any plans to move to transifex or launchpad >>>>>>> translations? :) Seems to be handy tools >>>>>>> >>>>>>> 15.01.2016 01:34, Frank Lanitz пишет: >>>>>>> >>>>>>>> On 14.01.2016 23:22, Yan Pashkovsky wrote: >>>>>>>>> High everybody! >>>>>>>>> >>>>>>>>> Overview plugin in russian l18n should be translated to "Обзор >>>>>>>>> Документа" or like in Notepad++ "Карта документа" (document map). >>>>>>>>> Currently it means eclipse, which is weird >>>>>>>>> >>>>>>>> Not a native, but somehow I like Обзор Документа more -- sounds >>>>>>>> nice ;) >>>>>>>> >>>>>>> >>>>> Is it customary to translate the "proper name" of a piece of software? >>>>> >>>>> I figured it wasn't so I didn't mark the plugin name as translatable, >>>>> but I see a few places in the UI file where I used it as a proper name but >>>>> neglected to correctly capitalize it (I guess that's where the strings in >>>>> question come from?) >>>>> >>>>> Should I mark the plugin name as translatable? >>>>> >>>>> Also, is it worthwhile to fix the capitalization in the English UI >>>>> strings? >>>>> >>>>> Cheers, >>>>> Matthew Brush >>>>> _______________________________________________ >>>>> I18n mailing list >>>>> I18n(a)lists.geany.org >>>>> https://lists.geany.org/cgi-bin/mailman/listinfo/i18n >>>>> >>>> _______________________________________________ >>>> I18n mailing list >>>> I18n(a)lists.geany.org >>>> https://lists.geany.org/cgi-bin/mailman/listinfo/i18n >>>> >>> >>> _______________________________________________ >>> I18n mailing list >>> I18n(a)lists.geany.org >>> https://lists.geany.org/cgi-bin/mailman/listinfo/i18n >>> >> _______________________________________________ >> I18n mailing list >> I18n(a)lists.geany.org >> https://lists.geany.org/cgi-bin/mailman/listinfo/i18n >> >> > > > _______________________________________________ > I18n mailing list > I18n(a)lists.geany.org > https://lists.geany.org/cgi-bin/mailman/listinfo/i18n > > -- Se encaminhar esta mensagem, por favor: 1. Apague o meu e-mail e o meu nome. 2. Apague também os endereços dos amigos antes de reenviar. 3. Encaminhe como cópia oculta (Cco ou Bcc) aos SEUS destinatários. Agindo sempre assim dificultaremos a disseminação de vírus, spams e banners e manteremos a nossa privacidade. Obrigado

3 2

Incorrect russian translation of overview plugin
by Yan Pashkovsky 15 Jan '16

15 Jan '16

High everybody! Overview plugin in russian l18n should be translated to "Обзор Документа" or like in Notepad++ "Карта документа" (document map). Currently it means eclipse, which is weird Kind regards, Yan

5 8

[ANN] Geany 1.26 is out!
by Colomban Wendling 15 Nov '15

15 Nov '15

We are happy to announce a new release of Geany! For a comprehensive list of changes please see: http://www.geany.org/Documentation/ReleaseNotes Some highlights: * New plugin API (Thomas Martitz). * Add support for "proxy" plugins (Thomas Martitz). * Fix spurious "source file has been modified" messages (Jiří Techet). * Update Scintilla to version 3.6.1. * Keeping undo history when reloading files is now enabled by default. * Restore modern design of native file dialogs under Windows. * Update translations: de, el, es, fr, hu, id, kk, pt, sk, sv, ru. We want to thank all developers, translators and everyone who contributed to this release with patches, feedback, bug reports and so on. Thank you! As usual, all downloads can be found on http://www.geany.org/Download/Releases. - Colomban

2 1

Geany-Plugins 1.26 are out!
by Frank Lanitz 15 Nov '15

15 Nov '15

Hi, We are happy to announce a new version of the combined Geany-Plugins release -- right after Geany 1.26 has been released. There have been a lot of changes, but here are some of the most prominent or noteworthy ones: * Add GTK3 support to Addons and GeanyVC * Addons: new Copy Path feature * Addons: Fix bookmark list when the document changes * Spellcheck: Add support for showing suggestions directly in the editor menu * Scope: Improve GDB communication * Update translations: de, fr, nl, pt * New translation: kk A more complete list of changes can be found in the https://raw.githubusercontent.com/geany/geany-plugins/1.26.0/NEWS file Thanks to all people involved and to you for using it ;) As usual, you can find source tarballs and Windows installer for the new release on http://plugins.geany.org/downloads.html. Cheers, Frank

1 0

Geany localization
by Baadur Jobava 11 Nov '15

11 Nov '15

Hello, I can't find anywhere information about the process used for localizing Geany. Can you tell me something about that? Also, if you have a rough outline of future releases and possible deadlines. I am interested in taking a look at the Romanian localization, but can't make firm promises in that regard just yet. Jobava

2 1

String freeze for Geany 1.26 -- Please translate!
by Frank Lanitz 04 Nov '15

04 Nov '15

Hi translators and friends of Geany, As by our new release cycle I'm happy to announce the first kind of regular string freeze. We now have to get the best translations for our users in place! In preparation of that I've update po-files for Geany core project inside github repositories and asking you whether you could update translations, review them or maybe add new languages. Why not having a Klingonion one? ;) I'd be very happy if you could send a patch, a pull request or single file with translation to either the geany-i18n mailing list or direct to me within the next two weeks so we can include it to the next release. Deadline will be 2015-11-14 CET. To get most recent files you could just clone the repositories from Geany: https://github.com/geany/geany This can be done e.g. with git clone https://github.com/geany/geany.git Also at http://i18n.geany.org or are statistics and daily updated files available -- the push of tonight will be there tomorrow CET. If your language was translated by two or more in past, please double check directly with them or by pinging me, so we don't need to translate same things two or three times. Also please feel to ping me for every question or if you like to start a new translation for an unsupported language. If you have any questions, don't hesitate to ping me directly via IRC: geany @freenode Jabber/XMPP: frlan(a)jabber.ccc.de or via Mail: look above or some of the mailing lists. Thanks and happy translating Frank

4 7

String freeze for Geany-Plugins 1.26
by Frank Lanitz 01 Nov '15

01 Nov '15

Hi translators, As Geany is getting a new major release, the plugins are getting updated also. Even not many features or new plugins have been added this time, we still got a huge amount of work to do any many user kudos are asking to get earned! In preparation update po-files for Geany-Plugins at github now and asking you whether you could update translations, review them or maybe add new languages. As on Geany core, I'd be very happy if you could send a patch, a pull request or single file with translation to either the geany-i18n mailing list or direct to me within the next two weeks so we can include it to the next release. Deadline will be also 2015-11-14 CET. To get most recent files you could just clone the repositories from Geany: https://github.com/geany/geany-plugins This can be done e.g. with git clone https://github.com/geany/geany-plugins.git Also at http://i18n.geany.org/plugins are statistics and daily updated files available -- the push of tonight will be there tomorrow CET. Happy translating! Cheers, Frank

1 0

Geany-Plugins website down because of issue at sf
by Frank Lanitz 21 Jul '15

21 Jul '15

Hi folks, As on different channels people are getting nervous: SF had some major issues with the storage. They are currently in recovering mode. Until they finished, plugins.geany.org will not be available -- at least I hope so it will be back later. Proactive information from sf was not given so I only have the information from Twitter¹ and related pages We might will need to switch also plugin pages to our infrastructure later. Our github-Repos are not effected by this as well as geany.org is fine. Cheers, Frank ¹ https://twitter.com/sfnet_ops

3 2

Re: [Geany-i18n] [Geany-Users] Geany-Plugins website down because of issue at sf
by Frank Lanitz 20 Jul '15

20 Jul '15

Am 20.07.2015 um 10:31 schrieb Harold Aling: > Sourceforge.net is blocked by default here (see attachment). This might > be a good moment to move to a non-badware code hosting site? Maybe. The geany-plugins downloads have not been effected by the "add adds to installer"-issue earlier, so we just did not discussed it in a deeper way. Cheers, Frank

1 0

ANN: Geany-Plugins 1.25 is out
by Frank Lanitz 13 Jul '15

13 Jul '15

Hi folks, Right after the release of Geany 1.25 we are happy to announce also the release of Geany-Plugins 1.25 available via http://plugins.geany.org/ A lot of smaller and bigger changes have been made. For details on a special plugin, please check its ChangeLog. However, these are the most amazing ones: General: * GProject is renamed to ProjectOrganizer * New plugin Automark * New plugin GeanyCtags * New plugin GitChangeBar * New plugin Overview Addons: * Improve URI selection Autoclose: * Add Whitesmith style bracket formatting support CodeNav: * Implement Go to File feature Commander: * Improve sorting algorithm Debugger: * Fix crash with GDB 7.7 GeanyLaTeX: * Fix automatic capitalization of multi-byte characters GeanyVC: * Add support for WinMerge external diff viewer ProjectOrganizer: * Add an "external directory" feature * Add find tag by name * Add ignored file patterns * Performance improvements in tag generation using updated Geany API MultiTerm: * Fix build with recent Vala versions PairTagHighlighter: * Fix clearing previous indicators (PR #200) PoHelper: * Add a statistics dialog * Fix handling of plural forms Scope: * Fix building on GNU/Hurd (PR #146) Spellcheck: * Don't check code of scripting languages embedded in HTML * Add option to perform a spell check on document open Tableconvert: * Improve handling of non-LF line ends * Add support for DokuWiki syntax WebHelper: * Add support for basic bookmarks Internationalization: * Update translations: de, fr, pt, ru You can download a Windows-installer as well as source-tarballs from http://plugins.geany.org/downloads.html For user of Apple's MacOS X it's included to the package. Have fun! Frank

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
30
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

I18n