Re: [Libreoffice-qa] How to report double used and/or not working as expected mnemonics?
Hi Thomas, Thomas Hackert wrote (28-10-13 04:54) As far as I know, there are mnemonics that are added in the code and ones that are auto-generated. O.K. For the first ones, I would make an issue for those that are in the same menu or window combined. But how do I know, if they were added in the code or were auto- generated? Hmm, I think most default buttons work like that and part of the menu's But it can be seen in the source of course. Unless you know who is working on that area, then an issue may be superfluous? I have not the faintest idea, sorry ... :( Me neither most of the time. Thus just ask on irc or the list, I would say. (Also, since regular localisers are working in this erea too, there must be some among them that have experience, I would expect.) Cheers, Cor -- - Cor Nouws - http://nl.libreoffice.org - The Document Foundation Membership Committee Member ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] How to report double used and/or not working as expected mnemonics?
Hello Cor, *, On Montag, 28. Oktober 2013 09:37 Cor Nouws wrote: Thomas Hackert wrote (28-10-13 04:54) [mnemonics auto-generated or added by code?] But how do I know, if they were added in the code or were auto- generated? Hmm, I think most default buttons work like that and part of the menu's But it can be seen in the source of course. But only, /if/ you can read the code ... ;) And I cannot, sorry ... :( Unless you know who is working on that area, then an issue may be superfluous? I have not the faintest idea, sorry ... :( Me neither most of the time. Thus just ask on irc or the list, I would say. O.K. Maybe someone else here on the list can tell me/us ... ;) (Also, since regular localisers are working in this erea too, there must be some among them that have experience, I would expect.) O.K. Thank you for your answer Thomas. -- NP: Soul in Sadness – Irritation ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
[Libreoffice-qa] [ANN] LibreOffice 4.1.3 RC2 available
Dear Community, The Document Foundation is pleased to announce the second release candidate of LibreOffice 4.1.3. The upcoming 4.1.3 will be the third in a sequence of frequent bugfix releases for our feature-packed 4.1 line. Please be aware that LibreOffice 4.1.3 RC2 is not been flagged as ready for production use yet, you should continue to use LibreOffice 4.1.2 for that. The release is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/download/pre-releases/ Should you find bugs, please report them to the FreeDesktop Bugzilla: https://bugs.freedesktop.org A good way to assess the release candidate quality is to run some specific manual tests on it, our TCM wiki page has more details: http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test For other ways to get involved with this exciting project - you can e.g. contribute code: http://www.libreoffice.org/get-involved/developers/ translate LibreOffice to your language: http://wiki.documentfoundation.org/LibreOffice_Localization_Guide or help with funding our operations: http://donate.libreoffice.org/ A list of known issues and fixed bugs with 4.1.3 RC2 is available from our wiki: http://wiki.documentfoundation.org/Releases/4.1.3/RC2 Let us close again with a BIG Thank You! to all of you having contributed to the LibreOffice project - this release would not have been possible without your help. On behalf of the Community, Christian ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] How to report double used and/or not working as expected mnemonics?
Hi Thomas, *, Am 28.10.2013 05:13 schrieb Thomas Hackert thack...@nexgo.de: Good morning Cor, *, On Sonntag, 27. Oktober 2013 18:37 Cor Nouws wrote: Thomas Hackert wrote (18-10-13 10:10) […] Is there a possibility to report this as fast and easy as possible? Fastest one would be to skip the bug report and instead push a patch to gerrit. Should I open a new bug for every found one? No, that doesn't make sense. You would need to create a list of the menu items to decide what entry will get the most natural one and what entries get second choice or autogenerated one. From my POV it is also important to keep familiar keystrokes intact, so newly added items should get an automatically assigned one unless there is a reason not to. Finding the place in the source code is not different from finding bad mnemonics in a translation. Look up the entry in pootle and there you have the reference. Or grep in the sources. Search in opengrok might also be possible, but not sure whether you need to escape the mnemonic marker/whether it includes the character in the search index. Ciao Christian ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] The garbage into the dev-builds.libreoffice.org
Hi Thorsten, Florian R. Thorsten Behrens wrote So feel free to poke me (one of the tinderbox admins) in the future. Poke :) Could you please rename the binaries in the Master branch so that they are named master~2013-10-27_23.53.26_LibreOfficeDev_4.2.0.0.alpha0_Win_x86.msi like the other tinderboxes? (i.e. remove the libo- prefix which is redundant?) Currently your tinderbox is the only one producing daily binaries from the Master branch for the Windows platform, so thank you for listening (and for fixing the capital X in the TB name) I don't know if this is deliberate but when doing a Custom install most of the components don't show up? (the user can only change the Optional Components) (For Florian Reisinger) In addition, a parallel install will not work (under Windows XP Pro x86 SP3) because of a missing MSVCR110.dll Probably the installer doesn't go through that step when doing a parallel install? Best regards, Pedro -- View this message in context: http://nabble.documentfoundation.org/The-garbage-into-the-dev-builds-libreoffice-org-tp4074218p4080208.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] How to report double used and/or not working as expected mnemonics?
Hi Thomas, Le 28/10/2013 16:19, Christian Lohmaier a écrit : Hi Thomas, *, Am 28.10.2013 05:13 schrieb Thomas Hackert thack...@nexgo.de: Good morning Cor, *, On Sonntag, 27. Oktober 2013 18:37 Cor Nouws wrote: Thomas Hackert wrote (18-10-13 10:10) […] Is there a possibility to report this as fast and easy as possible? Fastest one would be to skip the bug report and instead push a patch to gerrit. Should I open a new bug for every found one? No, that doesn't make sense. You would need to create a list of the menu items to decide what entry will get the most natural one and what entries get second choice or autogenerated one. From my POV it is also important to keep familiar keystrokes intact, so newly added items should get an automatically assigned one unless there is a reason not to. Finding the place in the source code is not different from finding bad mnemonics in a translation. Look up the entry in pootle and there you have the reference. Or grep in the sources. Search in opengrok might also be possible, but not sure whether you need to escape the mnemonic marker/whether it includes the character in the search index. If you grep, just be aware that now there is two kinds of mnemonics: [~] for the previous dialogs, [_] for the ported to .ui dialogs. AFAIK, only the main menus are scripted, the others are placed by the dialog creator or the translators. Kind regards Sophie ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] How to report double used and/or not working as expected mnemonics?
Hi Christian, *, On Montag, 28. Oktober 2013 16:19 Christian Lohmaier wrote: Am 28.10.2013 05:13 schrieb Thomas Hackert thack...@nexgo.de: On Sonntag, 27. Oktober 2013 18:37 Cor Nouws wrote: Thomas Hackert wrote (18-10-13 10:10) […] Is there a possibility to report this as fast and easy as possible? Fastest one would be to skip the bug report and instead push a patch to gerrit. do I not need commit rights to do it ;? The other prob is, that I have no programming experience, so I am not really sure, if I am able to help ... :( Should I open a new bug for every found one? No, that doesn't make sense. O.K. You would need to create a list of the menu items to decide what entry will get the most natural one and what entries get second choice or autogenerated one. But how should I know, which one will get the most natural one? And again, how should I know, which one are autogenerated and which one are coded? From my POV it is also important to keep familiar keystrokes intact, so newly added items should get an automatically assigned one unless there is a reason not to. O.K. Finding the place in the source code is not different from finding bad mnemonics in a translation. Look up the entry in pootle and there you have the reference. Or grep in the sources. Search in opengrok might also be possible, but not sure whether you need to escape the mnemonic marker/whether it includes the character in the search index. Do I remember it right, that there are two different mnemonics? ~ and _? Or are there more, which I do not know yet? Have a nice evening Thomas. -- We have ears, earther...FOUR OF THEM! ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] The garbage into the dev-builds.libreoffice.org
On 28/10/13 17:44, Pedro wrote: (For Florian Reisinger) In addition, a parallel install will not work (under Windows XP Pro x86 SP3) because of a missing MSVCR110.dll Probably the installer doesn't go through that step when doing a parallel install? iirc the MSVC runtime DLLs are installed into C:/Windows, and that does of course not happen when doing an administrative installation with MSI since that does not change C:/Windows. you can download the Visual Studio 2012 Redistributable (x86) from Microsoft and just install that. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] The garbage into the dev-builds.libreoffice.org
(For Florian Reisinger) In addition, a parallel install will not work (under Windows XP Pro x86 SP3) because of a missing MSVCR110.dll -- Install the MS_VCR_ 2012_x86 in your system. -- View this message in context: http://nabble.documentfoundation.org/The-garbage-into-the-dev-builds-libreoffice-org-tp4074218p4080225.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] The garbage into the dev-builds.libreoffice.org
Pedro wrote: Could you please rename the binaries in the Master branch so that they are named master~2013-10-27_23.53.26_LibreOfficeDev_4.2.0.0.alpha0_Win_x86.msi like the other tinderboxes? (i.e. remove the libo- prefix which is redundant?) Can look into that - out of curiosity, why does that matter? Currently your tinderbox is the only one producing daily binaries from the Master branch for the Windows platform, so thank you for listening (and for fixing the capital X in the TB name) No prob - but I see up-to-date binaries in http://dev-builds.libreoffice.org/daily/master/Win-x86@42/current/ as well? I don't know if this is deliberate but when doing a Custom install most of the components don't show up? (the user can only change the Optional Components) No idea, but it may well be due to the fact the box is _not_ doing release builds, but rather ~minimal developer builds. Happy to tweak configure options (the very first line in the body part of the tinderbox detailed log), if there's consensus it is worthwhile. Thanks for the update! Cheers, -- Thorsten signature.asc Description: Digital signature ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] The garbage into the dev-builds.libreoffice.org
Hi Thorsten Thorsten Behrens wrote Can look into that - out of curiosity, why does that matter? Firstly it makes it easier to automate download/installation using tools such as Florian's SI GUI and secondly because when the user is browsing for the Master installers (files are usually sorted by name), all other builds are under M and yours are under L, which is obviously not a big problem, just annoying :) One other request: your Tinderbox is not creating the txt files with the build info. Unfortunately this is the only element that allows QA to know from which TB each binary came from (before installing, obviously) so it is quite important that it is generated with the binary... Ex: http://dev-builds.libreoffice.org/daily/master/Windows-x86@47-TDF/2013-10-15_13.31.21/ Thorsten Behrens wrote Currently your tinderbox is the only one producing daily binaries from the Master branch for the Windows platform, so thank you for listening (and for fixing the capital X in the TB name) No prob - but I see up-to-date binaries in http://dev-builds.libreoffice.org/daily/master/Win-x86@42/current/ as well? Ehr... Tinderbox #42 IS your tinderbox... And current is a virtual folder pointing at the latest successful build :) I don't see any other recent Windows Master builds in the other tinderboxes... Thorsten Behrens wrote I don't know if this is deliberate but when doing a Custom install most of the components don't show up? (the user can only change the Optional Components) No idea, but it may well be due to the fact the box is _not_ doing release builds, but rather ~minimal developer builds. Happy to tweak configure options (the very first line in the body part of the tinderbox detailed log), if there's consensus it is worthwhile. Yes, but all previous minimal builds before the Optional Components allowed the user to select LibreOfficeDev Program Modules... I'm just mentioning this because it seems like a regression. If this won't affect the release build installer then just forget I mentioned it ;) Cheers, Pedro -- View this message in context: http://nabble.documentfoundation.org/The-garbage-into-the-dev-builds-libreoffice-org-tp4074218p4080245.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] The garbage into the dev-builds.libreoffice.org
Hi Michael, ape Michael Stahl-2 wrote iirc the MSVC runtime DLLs are installed into C:/Windows, and that does of course not happen when doing an administrative installation with MSI since that does not change C:/Windows. That is what I figured. This means that parallel instals under Windows XP will not work from now on unless the user previously installed MSVCR 2012... Michael Stahl-2 wrote you can download the Visual Studio 2012 Redistributable (x86) from Microsoft and just install that. Yes, I know that. I was just warning Florian Reisinger about this limitation. Maybe SI GUI needs to have a warning or run some system check? It probably makes sense to also add a warning to the Wiki page on Parallel install? Cheers, Pedro -- View this message in context: http://nabble.documentfoundation.org/The-garbage-into-the-dev-builds-libreoffice-org-tp4074218p4080246.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] The garbage into the dev-builds.libreoffice.org
Pedro wrote One other request: your Tinderbox is not creating the txt files with the build info. Unfortunately this is the only element that allows QA to know from which TB each binary came from (before installing, obviously) so it is quite important that it is generated with the binary... Not really a problem... just inconvenient. Fortunately it is trivial to obtain the build details from the Tinderbox Status Page -- either the Summary log or the Full log of each build. To locate, you only need to adjust from local time stamp to its UTC time stamp to locate the correct log. Unfortunately that currently gives just a 48 hour rolling window showing just the recent builds. Once beyond that window and posted to the corresponding TB directory on http://dev-builds.libreoffice.org/daily/master/ without the build text for each msi package, there is no way to know what commit signature to use to locate the build via cgit query -- http://cgit.freedesktop.org/libreoffice/core/log/?qt=rangeq= And at that point, it is only when installed that the Dev build is tagged with the final commit signature--viewable in the Help -- About as the Build ID. It might be helpful to extend to sliding window for the TB, maybe out to 7 days. Alternatively, it has always seemed unfortunate that the Build ID commit signature is not exposed within the Windows MSI installer package. Not sure how difficult that would be to implement, but it would eliminate dependence on the external logs and reinforce use of Git resources. -- View this message in context: http://nabble.documentfoundation.org/The-garbage-into-the-dev-builds-libreoffice-org-tp4074218p4080247.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] How to report double used and/or not working as expected mnemonics?
sophi wrote If you grep, just be aware that now there is two kinds of mnemonics: [~] for the previous dialogs, [_] for the ported to .ui dialogs. AFAIK, only the main menus are scripted, the others are placed by the dialog creator or the translators. Yes that is correct. Unfortunately the legacy assignments with ~ pulled from the various .xcu configurations are not being fully ported to their _ counter part for .ui configurations. That currently leaves things in a bit of a mess. Frankly, we no longer are maintaining HIG and accelerators/shortcuts long established from OOo and our LibreOffice practices. The template manager and start center are two examples of things breaking as we've implemented GTK based UI. The current documented short-cuts and accelerators are published to Wiki help, some UX-advise and Dev discipline is now needed to see that we reestablish our published norms under the .ui configurations--or republish user guides that match the new implementations (what ever those evolve into). Also, a gentle reminder that accelerator/short-cut implementation really should be consistent cross platform. Also, getting this right has considerable impact on Accessibility and Assistive Technology support. So, please review these published guides and consider the issue in that context. https://help.libreoffice.org/Common/General_Shortcut_Keys_in https://help.libreoffice.org/Common/Shortcuts_Accessibility https://help.libreoffice.org/Writer/Shortcut_Keys_for_Writer https://help.libreoffice.org/Writer/Navigating_and_Selecting_With_the_Keyboard -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-How-to-report-double-used-and-or-not-working-as-expected-mnemonics-tp4078583p4080253.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
