Re: [libreoffice-l10n] "save and load a list of gradient files"?
Commendations to you, Jesper. Now, I've just 'searched' for the definition of 'gradient files' only to find site after site dealing with color imaging ??? but nary a site dealing with defining this concept ;-( Therefore, I would suggest that LO's page first define this concept then re-word this convoluted sentence to one which the layman can readily understand ;-) Here's hoping that someone will define this concept ... and here's sending you, Jesper, all the best in your many endeavours, From: Jesper Hertel Date: Sun, Nov 30, 2014 at 4:26 PM Subject: Re: [libreoffice-l10n] "save and load a list of gradient files"? To: anne-ology 2014-11-29 23:36 GMT+01:00 anne-ology : I agree with you, Jesper; >manual after manual these computer guys have used convoluted > language which makes it next to impossible to understand what's what - I > gave up years ago reading these manuals learning instead by sitting down, > opening up whatever program & checking all those menu options along the > top. > > Well, that is also the way I learn new programs. :-) But now I decided to be a translator, and part of it is translating the help file, so I am trying to do my best with that. But then I need to be sure I understand the original English text. Jesper -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Re: Adding own twitter accounts to localized homepage
Hi, AFAICS, no localized site even included other feeds into the new site design, so who else could help me do it? Thanks, m. 2014-11-25 16:33 GMT+01:00 Martin Srebotnjak : > Hi, > > I am finishing the Slovenian localization of the redesigned website in > Silverstripe and still cannot set Slovenian twitter accounts to show on the > homepage. Also adding feeds seems not to work (or I don't know how use the > Manage feeds widget). > > Could someone please guide me? > > Thanks, m. > -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't
2014-12-01 20:38 GMT+02:00 Rimas Kudelis : > > It would for example also be possible to have "master" project in > > pootle (instead of just for the release-branches), so that the amount > > of changes are incremental, and not all one or two months before a new > > major release. > > (but that of course means applying a translation to multiple projects, > > so not sure whether that really reduces the work and not causing more > > work for translators...) > > For at least a few years, I performed most of my Mozilla localization > work on their master branch. When branches were cut and repositories > migrated, I would migrate my repos too. I can imagine a scenario where > at least some teams would want to work on LibO master as well. There > even is potential that such process could help avoid some problems by > signaling them early enough so that they can be fixed or undone. > > Obviously though, this should not be required from all teams. And if we > have at least two simultaneously active release branches, this might not > be the best approach. > I for one -- i.e. the Estonian team :) -- would very much like to work on master branch. Br Mihkel -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't
Hi Christian, 2014.12.01 00:32, Christian Lohmaier wrote: > On Sun, Nov 30, 2014 at 10:16 PM, Olivier Hallot > wrote: >> On 30/11/2014 18:52, Rimas Kudelis wrote: >>> 2014.11.30 19:13, Olivier Hallot wrote: >> painless migration was my hope when I raised the issue, but saddly it >> didn't show up in time. Such Changes In Capital Letters And Semicolons >> Are Suitebale in EN But Does Not Affect Other Languages Where This Rule >> Does Not Apply. > It's impossible to automatically decide which of those changes are > purely cosmetic and which not. I'm not sure what you mean here. It can't be hard to distinguish such lines where only straight apostrophes, straight quotes or three-dots-as-an-ellipsis are being replaced with their fancier equivalents. And with these changes filtered out, I don't think it would be impossible to propagate them to localized files by changing msgid's in them to reflect these cosmetic updates. > And there likely won't be anyone who > manually goes through all the changes and manually creates mapping > from old to new so that old translations can be pulled in. And with > changes like changing casing and adding colons it is more likely that > the translation will also want to apply the change, so just staying > silent and not flagging the string as changed is not really an option > here. I believe we could have cheated even with colons by adding them to the translations automatically (probably on an opt-out or opt-in basis). As for case changes, I guess it depends on their nature: if en-US would decide to make a massive change between say Title Case and Sentence case, I guess most locales would find it very much acceptable to just keep what they already have. On the other hand, if the change was to or from lowecase, the expectations might differ. >> Nevertheless, it may be time to create a T/LSC Translation/Linguistic >> Steering Commitee to address the issues raised here. LiBO does not have >> a linguistic revision of terms used in the UI. > Not progressing just for the sake of not causing work for anybody is > the wrong approach. > But that doesn't mean the workflow as a whole cannot be improved. Fully agreed. > It would for example also be possible to have "master" project in > pootle (instead of just for the release-branches), so that the amount > of changes are incremental, and not all one or two months before a new > major release. > (but that of course means applying a translation to multiple projects, > so not sure whether that really reduces the work and not causing more > work for translators...) For at least a few years, I performed most of my Mozilla localization work on their master branch. When branches were cut and repositories migrated, I would migrate my repos too. I can imagine a scenario where at least some teams would want to work on LibO master as well. There even is potential that such process could help avoid some problems by signaling them early enough so that they can be fixed or undone. Obviously though, this should not be required from all teams. And if we have at least two simultaneously active release branches, this might not be the best approach. Regards, Rimas -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Follow-up on en_US changes
Hi all, Opening a new thread on the changes on the en_US version, I propose to follow-up on the project@ list so we could associate the developers and design teams and discuss together how to handle that in our workflow. Some changes are necessary and the en_US version has to be maintained too but that shouldn't have an impact or at least, as limited as possible on the l10n work. I'm not sure it's the good moment to open the discussion now because we are all catching dead lines, but I propose to do it on week 2 next year, after the hard code freeze for 4.4.0. Is it ok for you all? if yes, I'll open a ticket on Redmine. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] n’t → n't
On 12/01/2014 01:11 PM, Christian Lohmaier wrote: On Mon, Dec 1, 2014 at 5:58 AM, Yury Tarasievich wrote: On 11/30/2014 11:52 PM, Rimas Kudelis wrote: And why is not anyone (besides me) discussing automation, of that same problem, too? Probably because there is nothing to discuss as it has already been explained that it can be done/to what extend it can be done/how it can be done. Excepting whether anything actually would be done, and by whom. Right now the issue is being gracefully shoveled off into the translators' hands. Yury -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't
Hi all, Le 30/11/2014 23:32, Christian Lohmaier a écrit : > Hi Olivier, *, > > On Sun, Nov 30, 2014 at 10:16 PM, Olivier Hallot > wrote: >> On 30/11/2014 18:52, Rimas Kudelis wrote: >>> 2014.11.30 19:13, Olivier Hallot wrote: >> >> painless migration was my hope when I raised the issue, but saddly it >> didn't show up in time. Such Changes In Capital Letters And Semicolons >> Are Suitebale in EN But Does Not Affect Other Languages Where This Rule >> Does Not Apply. > > It's impossible to automatically decide which of those changes are > purely cosmetic and which not. And there likely won't be anyone who > manually goes through all the changes and manually creates mapping > from old to new so that old translations can be pulled in. And with > changes like changing casing and adding colons it is more likely that > the translation will also want to apply the change, so just staying > silent and not flagging the string as changed is not really an option > here. > > it's different with one-to-one changes that can easily > (=automatically) be undone to look for the string as it was before the > cosmetic change. > > The auto-translations of the help strings with changed help-ID works > that way (although there is quite a bit of manual work involved to > create the mapping). But once you have a mapping "old-helpid" → > "new-helpid", you can easily apply the old translation. > >> Nevertheless, it may be time to create a T/LSC Translation/Linguistic >> Steering Commitee to address the issues raised here. LiBO does not have >> a linguistic revision of terms used in the UI. > > Not progressing just for the sake of not causing work for anybody is > the wrong approach. Agreed > But that doesn't mean the workflow as a whole cannot be improved. > It would for example also be possible to have "master" project in > pootle (instead of just for the release-branches), so that the amount > of changes are incremental, and not all one or two months before a new > major release. > (but that of course means applying a translation to multiple projects, > so not sure whether that really reduces the work and not causing more > work for translators...) Something we should discuss then. For information, I've discussed with the Design team about their changes and asked them to take care of the work load it causes to the l10n team. I asked them also to open an issue each time they make a change in the UI that is not reflected in the help files so we can track them. Cheers Sophie -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Co-founder - Release coordinator The Document Foundation -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Re: [libreoffice-l10n] n’t → n't
On Mon, Dec 1, 2014 at 5:58 AM, Yury Tarasievich wrote: > On 11/30/2014 11:52 PM, Rimas Kudelis wrote: > > And why is not anyone (besides me) discussing automation, of that same > problem, too? Probably because there is nothing to discuss as it has already been explained that it can be done/to what extend it can be done/how it can be done. ciao Christian -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] New(?) colors in UI svx
What colors are Sunburst, Brownie, Sunset and Clay? I have searched the web for these colors. They are not in https://en.wikipedia.org/wiki/Web_colors. Any clues? They are not colors, but color gradients. You can see them if you e.g. draw a rectangle, choose Area in context menu of the rectangle and go to the Gradient tab. Best regards, Stanislav -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] New(?) colors in UI svx
Hi :) They sound like themes or collections of colours rather than individual colours. Kinda "dumbing things down" to make it easier for 'normal user' to understand. If you look at a "sunset" there is usual a huge range of different shades of several different colours. So i think the "sunset" theme is trying to evoke the general feeling of a sunset by using a range of colours that you might associate with sunsets. I'd be expecting lots of reds, yellows, maybe orange, purples. With Brownie i'd expect earthy colours, like Ubuntu themes - so there would be some overlap with sunset. With clay i'd think of greys tending towards earthy colours but none of the fiery colours. I think it's just to give 'normal users' an idea of what kind of colours to expecting and to have an idea of what the designers were aiming for. Regards from Tom :) On 1 December 2014 at 04:59, Yury Tarasievich wrote: > > On 12/01/2014 07:07 AM, Donald wrote: > >> In the UI: svx/source/dialog.po there are some colors to be translated: >> Tango green, Tango red and others with Tango in the name. What is the >> significance of the word Tango? Is it part of the color name or is it >> software or something else? >> > > Tango scheme. > > What colors are Sunburst, Brownie, Sunset and Clay? >> > > Why not look on those in the LibO itself? These are artist descriptive > names anyway. > > Yury > > > -- > To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org > Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to- > unsubscribe/ > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.libreoffice.org/global/l10n/ > All messages sent to this list will be publicly archived and cannot be > deleted > -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
