Re: [libreoffice-l10n] Uploading LO User Guides
Hi, Sophie On 27/05/13 18:11, Sophie Gautier wrote: Hi Donald, On 27/05/2013 01:50, Donald Rogers wrote: Hi everyone Could someone please explain how and where to upload the User Guides ODT and PDF files for languages other than English? How is it that the files athttps://wiki.documentfoundation.org/Documentation/Publications have paths such as this: https://wiki.documentfoundation.org/images/d/d8/GS4001-IntroducingLibreOffice.odt while the code has: [[Media:GS4001-IntroducingLibreOffice.odt|ODT]] ornbsp; ? The documentation using_odfauthors.odt only talks about the English version. I want to know what the localization teams do. You can build a wiki area in your language and place the documentation there. This is what we have done for the FR documentation (see https://wiki.documentfoundation.org/Documentation/Publications/fr#Guides_utilisateur_officiels) At the top of most of the pages on the wiki, you have a language code: https://wiki.documentfoundation.org/Documentation and don't forget to create a Category for your language. Kind regards Sophie Thank you, especially for your comment about creating a category page. I had not done that previously but it is pretty painless to do. The upload just worked, and it sorted out those strange paths automagically. I added three pages based on the relevant EN and FR pages: https://wiki.documentfoundation.org/Documentation/Publications/eo https://wiki.documentfoundation.org/Documentation/eo https://wiki.documentfoundation.org/Category:EO When I uploaded the ODT and PDF files I was asked to choose a copyright type. I chose Creative Commons Attribution-ShareAlike 3.0 Unported License http://creativecommons.org/licenses/by-sa/3.0/, I presume that is okay? When I uploaded a PDF file the Wiki complained that the file had the same name as the previous ODT file (different extension of course) but I ignored that. Regards Donald -- 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] Hotkeys shmotkeys
I'm officially throwing the towel on the hotkeys. Or are they access keys? Whatever... the scope is impossible to tell, some use ~ some use and as of 4.0.1 we now also have underscore. Apart from messing with my TM, I also end up with the unpalatable choice of either totally ignoring multiple uses of the same access key in the UI or spending an extraordinary amount of time fixing them. And as LO expands, it will only get worse. We sort of had this debate before and I believe the upshot was that if you leave them out, the system will automatically assign them. I think that's what I will do from now assuming the failing access key checks in Pootle won't stop the release in my locale. If I file a bug, is it possible to remove all of them automatically? Or does the system not care if I stop assigning them manually part way through? Michael -- 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] Hotkeys shmotkeys
Dana 28.5.2013. 13:21, Michael Bauer je napisao: I'm officially throwing the towel on the hotkeys. Or are they access keys? Whatever... the scope is impossible to tell, some use ~ some use and as of 4.0.1 we now also have underscore. Apart from messing with my TM, I also end up with the unpalatable choice of either totally ignoring multiple uses of the same access key in the UI or spending an extraordinary amount of time fixing them. And as LO expands, it will only get worse. We sort of had this debate before and I believe the upshot was that if you leave them out, the system will automatically assign them. I think that's what I will do from now assuming the failing access key checks in Pootle won't stop the release in my locale. If I file a bug, is it possible to remove all of them automatically? Or does the system not care if I stop assigning them manually part way through? Michael I feel your pain. :) I'm coming from Mozilla L10n in which you have access keys as a separate strings to LO in which there is 3 different ways to mark access keys. I'm not against marking access keys inside strings, but PLEASE decide how you want to do it. Also, I'm having problems with knowing which of one word strings are free to translate and which are variables (place holders or whatever it's called, which I shouldn't translate). Not really sure why you are even offering those strings in Pootle translation if they shouldn't be translated. Best regards, Mihovil -- 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] Hotkeys shmotkeys
Hi Michael, Mihovil, all, On 28/05/2013 13:28, Mihovil Stanic wrote: Dana 28.5.2013. 13:21, Michael Bauer je napisao: I'm officially throwing the towel on the hotkeys. Or are they access keys? Whatever... the scope is impossible to tell, some use ~ some use and as of 4.0.1 we now also have underscore. Apart from messing with my TM, I also end up with the unpalatable choice of either totally ignoring multiple uses of the same access key in the UI or spending an extraordinary amount of time fixing them. And as LO expands, it will only get worse. We sort of had this debate before and I believe the upshot was that if you leave them out, the system will automatically assign them. I think that's what I will do from now assuming the failing access key checks in Pootle won't stop the release in my locale. If I file a bug, is it possible to remove all of them automatically? Or does the system not care if I stop assigning them manually part way through? Michael I feel your pain. :) I'm coming from Mozilla L10n in which you have access keys as a separate strings to LO in which there is 3 different ways to mark access keys. I'm not against marking access keys inside strings, but PLEASE decide how you want to do it. I agree with you both that it's really difficult to have those keys fixed. I've tried to get them right (I mean all different and no duplicates) in the UI but I'm not sure what the algorithm is doing beside my choices. Andras, do you have an idea on what we can do to improve that ? I don't use Pootle to search the strings, but I'm feeling the same pain when I grep my files, having now to take care of the ~ and _. Also, I'm having problems with knowing which of one word strings are free to translate and which are variables (place holders or whatever it's called, which I shouldn't translate). Not really sure why you are even offering those strings in Pootle translation if they shouldn't be translated. Because everything is in Pootle (and I like it :) So may be we have to document what the variables are on the wiki? This is up to us to document our process and the material we need to make our localization. I won't do it now because I miss time, but may be we can work on it together when the 4.1 localization round is over? Kind regards Sophie -- 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] Hotkeys shmotkeys
On Tue, May 28, 2013 at 1:21 PM, Michael Bauer f...@akerbeltz.org wrote: And as LO expands, it will only get worse. This is a problem, but LO expands slowly, so you can always sort out these issues by one of the bugfix releases. We sort of had this debate before and I believe the upshot was that if you leave them out, the system will automatically assign them. This is (or was) the case with old style widgets, I'm not sure about .ui. Regards, Andras -- 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] Hotkeys shmotkeys
Andras, I think you misunderstood me. As a one-man team running over two dozen l10n projects for my locale, I simply don't have to time to randomly browse around the LO UI and then spend 30 minutes trying to figure out which incidence of Edit has the wrong access key, then wait for a build, check, and most likely undo and try another one. Even if there was someone else on the team, it would be a questionable use of valuable translator time (small language *are* that desperate for time) plus, and that applies to a lot of languages I think, there are corners of the UI people rarely go to and I suspect even some of the bigger languages will haver bits of the UI where the access keys are messed up. The sidebar has added at least a couple hundred of these. Now multiply each by 30 minutes (a guesstimate). If the system differentiates the automatic access keying depending on where you are, then I'm stuffed. I have no idea which bits are widget and which are UI. I'm not a magician :) If that's the case I'll just have to shrug, guess at the access keys and live with the mess. On the whole, I think the whole access key thing needs a more coherent, automated approach. Or at least a codekey attached to each UI string in the test builds you you can *easily* identify the string that needs fixing. Michael -- 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] Hotkeys shmotkeys
У уто, 28. 05 2013. у 13:42 +0100, Michael Bauer пише: On the whole, I think the whole access key thing needs a more coherent, automated approach. Or at least a codekey attached to each UI string in the test builds you you can *easily* identify the string that needs fixing. This is not something I do, but it may be an option if you like to have perfect hotkeys. Open a dialog and make a screenshot. Next run the keyid build, open the same dialog, make another screenshot. Now annotate hotkeys in the first screenshot taking care there is no conflict. Finally, search for strings by keyid and add hotkeys as annotated. You should be able to fix all strings in a dialog in under 30 minutes. Best, Goran -- 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] 4.1 strings updated in Pootle
Hi, I uploaded the new templates, you can click on Update against templates in LibreOffice 4.1 UI project (help did not change). This update has the typo fixes you reported. Regards, Andras -- 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] Uploading LO User Guides
Hi Tom I suggest that the prompt be made more helpful, including that the warning can be ignored if the extensions are different or the user wants to replace the file with a new version. I leave the wording to someone who knows all the ins and outs. Regards Donald On 29/05/13 02:13, Tom Davies wrote: Hi :) Sorry about the wiki grumbling about using the same name (with different extension). It seemed to work out just fine. I can click on each one and they each open in the right way for their type so neither got over-written. Regards from Tom :) *From:* Donald Rogers donr2...@clear.net.nz *To:* l10n@global.libreoffice.org *Sent:* Tuesday, 28 May 2013, 11:01 *Subject:* Re: [libreoffice-l10n] Uploading LO User Guides Hi, Sophie Thank you, especially for your comment about creating a category page. I had not done that previously but it is pretty painless to do. The upload just worked, and it sorted out those strange paths automagically. I added three pages based on the relevant EN and FR pages: https://wiki.documentfoundation.org/Documentation/Publications/eo https://wiki.documentfoundation.org/Documentation/eo https://wiki.documentfoundation.org/Category:EO When I uploaded the ODT and PDF files I was asked to choose a copyright type. I chose Creative Commons Attribution-ShareAlike 3.0 Unported License http://creativecommons.org/licenses/by-sa/3.0/, I presume that is okay? When I uploaded a PDF file the Wiki complained that the file had the same name as the previous ODT file (different extension of course) but I ignored that. Regards Donald -- 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
