You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(38) |
Jun
(26) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(8) |
Nov
(5) |
Dec
|
2012 |
Jan
(22) |
Feb
(33) |
Mar
(21) |
Apr
(25) |
May
(284) |
Jun
(90) |
Jul
(43) |
Aug
(29) |
Sep
(41) |
Oct
(14) |
Nov
(27) |
Dec
(51) |
2013 |
Jan
(69) |
Feb
(14) |
Mar
(32) |
Apr
(33) |
May
(7) |
Jun
(16) |
Jul
(20) |
Aug
(27) |
Sep
(38) |
Oct
(48) |
Nov
(31) |
Dec
(8) |
2014 |
Jan
(7) |
Feb
(6) |
Mar
(16) |
Apr
(2) |
May
(28) |
Jun
(16) |
Jul
(5) |
Aug
(23) |
Sep
(3) |
Oct
(19) |
Nov
(42) |
Dec
(28) |
2015 |
Jan
(1) |
Feb
(4) |
Mar
(15) |
Apr
(36) |
May
|
Jun
(2) |
Jul
(20) |
Aug
(5) |
Sep
(43) |
Oct
(33) |
Nov
(17) |
Dec
(26) |
2016 |
Jan
(81) |
Feb
(24) |
Mar
(3) |
Apr
(12) |
May
(12) |
Jun
(11) |
Jul
(4) |
Aug
|
Sep
(2) |
Oct
(13) |
Nov
(16) |
Dec
(6) |
2017 |
Jan
(17) |
Feb
(8) |
Mar
(36) |
Apr
(15) |
May
(12) |
Jun
(11) |
Jul
(13) |
Aug
(7) |
Sep
(4) |
Oct
(1) |
Nov
(2) |
Dec
(6) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(2) |
Dec
(7) |
2021 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
(2) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Denis B. <dbi...@wa...> - 2012-08-13 14:37:53
|
Hi, I guess there should be a space at the end of the string "Normal Mode (current master document :" in Texmaker (!) context. -- Denis |
From: Denis B. <dbi...@wa...> - 2012-08-13 14:34:48
|
Le lundi 13/08/12 à 16h01, Denis Bitouzé <dbi...@wa...> a écrit : > strings "open documents" and "current document" in findGlobalDialog > context should be capitalized. Maybe also should be capitalized "sweave" in QFormatConfig context. -- Denis |
From: Denis B. <dbi...@wa...> - 2012-08-13 14:30:59
|
Hi, the drop down list Options -> Configure TXS -> Adv. Editor -> Line Wrapping is not enough large: as French translations are longer than original English strings, even with a maximized window, the items of this list are truncated. -- Denis |
From: Denis B. <dbi...@wa...> - 2012-08-13 14:17:30
|
Hi, if I'm right, the string: <i>a</i>: absolute path, <!--<i>r</i>: relative path, --><i>m</i>: basefile name without extension,<i>e</i>: extension<br /> <i>"</i>: enclose with "..", . (point): ends placeholder with a point, (space): ends placeholder and add a space, <i>)</i>: ends placeholder <br /> examples: ?ame": complete absolute filename enclosed in ", ?e) just the extension (without leading point), <br /> ?m" (filename without extension, identical to %) ?me (filename with extension like example.tex) 1. is missing some colons (there is such a colon after the example ?ame", but not after the others), 2. the opening parentheses of "(filename without extension" and "(filename with extension" are wrongly located: it should be "filename (without extension" and "filename (with extension" -- Denis |
From: Denis B. <dbi...@wa...> - 2012-08-13 14:02:24
|
Hi, to be consistent, I guess strings "open documents" and "current document" in findGlobalDialog context should be capitalized. -- Denis |
From: Denis B. <dbi...@wa...> - 2012-08-13 13:56:26
|
Hi, in Tools -> Analyse Text dialog box, the Source drop down list items are only "Whole document" and "Selection" but the tooltip says: "Determines if the whole document, only the selection, or only a certain chapter are analysed." -- Denis |
From: Tim H. <hof...@hi...> - 2012-08-12 19:49:50
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Sonntag, 12. August 2012 19:46 > > Le dimanche 12/08/12 à 15h47, > "Tim Hoffmann" <hof...@hi...> a écrit : > > > > > 5. IMO, "Manipulate Tables" should be a top menu, as is Math. > > I don't think so. It's too specialized for a top level menu. If we add > > more of this kind of functionalities (e.g. for better beamer support, > > for pdf comments, for minipages etc.) it will crowd the menu. > > The idea is that, basically, tables are often needed and are one of the most > complicated things to typeset with LaTeX: when I give LaTeX courses, students > are often seduced by LaTeX until tables are treated, they feel very > uncomfortable with them and are convinced that LaTeX is too complicated for > this matter. So, as most of the users have to typeset tables and they fright > beginners (especially in humanities), IMO tables should have their own menu, > just as maths have. > > Beamer is also often needed but is far less complicated. Other subjects look > very anecdotal compared to tables. Still I'm not in favor of a top-level table menu. But if more people speak up for it, we can change it. Anyway, you'll want to use the toolbar, if you work a lot with tables. > Yes, that's very nice, many thanks for this! I'll surely advice its use with TXS > when it will be released. BTW, is the next TXS release planned? Yes planned and hopefully about to release soon. But there are some issues with the document structure on linux, that should be fixed before, if possible. Only this is holding up a release. > > I really recommend, not using the Bibliography tools of TXS, but some > > other software and push citations to TXS. If you are using tools other > > than JabRef, place a feature request to these tools that they should > > provide a possibility to push citations to TXS. It's really straight > > forward (just run "texstudio --insert-cite citation" from the other > > program). That said, I currently won't work on the bibliography part > > of TXS. > > OK. But as this BibTeXDialog does exist, and if it isn't too complicated, it could > nevertheless be nice. Ok, I'll but it on my low-priority list. > > > 9. In Macros -> Edit Macros dialog box, the tooltip for the trigger > > > is > > indicated > > > with a blue "?". Maybe the other ones in TXS should be indicated in > > > the > > same > > > way, for instance those in Wizard -> Insert Graphic... > > I don't think that we should put blue question marks everywhere. > > Maybe only everywhere tooltips are implemented. > > > It's not a standard way for providing help (and a bit distracting if > > there are blue question marks all over the place. > > Are they so many tooltips? Without blue question marks, some users may miss > tips. Of course, things should be self-explanatory, if possible. If additional information is required, I prefer tooltips, because everybody knows them. There are quite a few, especially in the options, and some more could be useful. > Anyway, IMO, it should be better to have either question marks everywhere or > nowhere. > -- > Denis > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Denis B. <dbi...@wa...> - 2012-08-12 17:46:23
|
Le dimanche 12/08/12 à 15h47, "Tim Hoffmann" <hof...@hi...> a écrit : > > > the new string "..." is not translatable. > In which context? Is there a need to translate this? It's likely the > same in every language, isn't it? Sorry, I was unclear: I just picked up the sentence "<something> is not translatable" from my OP, but without rewriting the complete string (namely "You have enabled the advanced options, etc."), to say that another string wasn't translatable. > > 5. IMO, "Manipulate Tables" should be a top menu, as is Math. > I don't think so. It's too specialized for a top level menu. If we > add more of this kind of functionalities (e.g. for better beamer > support, for pdf comments, for minipages etc.) it will crowd the > menu. The idea is that, basically, tables are often needed and are one of the most complicated things to typeset with LaTeX: when I give LaTeX courses, students are often seduced by LaTeX until tables are treated, they feel very uncomfortable with them and are convinced that LaTeX is too complicated for this matter. So, as most of the users have to typeset tables and they fright beginners (especially in humanities), IMO tables should have their own menu, just as maths have. Beamer is also often needed but is far less complicated. Other subjects look very anecdotal compared to tables. > > 8. The panels in BibTeXDialog context should be resizable. > The BibTeXDialog is just a very rough help for generating BibTeX > entries. Bibliography management from within TXS is limited in many > ways. The primary focus is to make TXS a good LaTeX editor, and there > are still so many ideas to be implemented... On the other hand, there > are already good bibliography management tools and we currently do > not plan to extend TXS in that direction. Instead we have created an > interface, which allows to push references from a bibliography > software to TeXstudio. A first implementation is available for JabRef. Yes, that's very nice, many thanks for this! I'll surely advice its use with TXS when it will be released. BTW, is the next TXS release planned? > I really recommend, not using the Bibliography tools of TXS, but some > other software and push citations to TXS. If you are using tools > other than JabRef, place a feature request to these tools that they > should provide a possibility to push citations to TXS. It's really > straight forward (just run "texstudio --insert-cite citation" from > the other program). That said, I currently won't work on the > bibliography part of TXS. OK. But as this BibTeXDialog does exist, and if it isn't too complicated, it could nevertheless be nice. > > 9. In Macros -> Edit Macros dialog box, the tooltip for the trigger > > is > indicated > > with a blue "?". Maybe the other ones in TXS should be indicated in > > the > same > > way, for instance those in Wizard -> Insert Graphic... > I don't think that we should put blue question marks everywhere. Maybe only everywhere tooltips are implemented. > It's not a standard way for providing help (and a bit distracting if > there are blue question marks all over the place. Are they so many tooltips? Without blue question marks, some users may miss tips. Anyway, IMO, it should be better to have either question marks everywhere or nowhere. -- Denis |
From: Tim H. <hof...@hi...> - 2012-08-12 13:48:05
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Sonntag, 12. August 2012 00:02 > > Le samedi 04/08/12 à 12h26, > Denis Bitouzé <dbi...@wa...> a écrit : > > > the new string "..." is not translatable. In which context? Is there a need to translate this? It's likely the same in every language, isn't it? > Another one: "No open project or tex file to clean." in Tools -> Clean Auxiliary > Files..., for instance when no file is open. Already done by Jan. > BTW, > > 1. The string: > > If "show all" is selected, all phrases are shown. > If "minimum phrase length" is selected, a phrase is only shown if it has at least > so many characters. (e.g. "a test" has 6 characters) If "minimum word length > (one)" is selected, a phrase is only shown if a word of it has at least so many > characters. (e.g. "a test" has 4 > characters) If "minimum word length (all)" is selected, a phrase is only shown if > all words of it has at least so many characters. (e.g. "a test" has 1 character) If > "completely ignore" is selected, shorter words are completely ignore. (e.g. with > length 3, the sentence "this is a test" is equally to "this test", while the other > options would separate it in "this is", "is a", "a test", even if non of this phrases > would be shown) > > is missing a period at its end and contains English typos, as some of the other > strings of the "TextAnalysisDialog" context. done > 2. "Log File not found !" -> "Log File not found!" done > 3. In "RandonTextGenerator" context: > (a) "punctation" -> "Punctation" > (b) "ignore case" -> "Ignore case" done > 4. In "ThesaurusDialog" context, all the strings should be capitalized. done > 5. IMO, "Manipulate Tables" should be a top menu, as is Math. I don't think so. It's too specialized for a top level menu. If we add more of this kind of functionalities (e.g. for better beamer support, for pdf comments, for minipages etc.) it will crowd the menu. Also these things only have a reasonable use in certain contexts. So for usability the best way would be to provide easy access to these functions only in context. E.g. via context menu or via a context toolbar that adapts to the environment of the cursor. But this is all not yet possible. Furthermore by current design, every functionality has to appear somewhere in the menu. One could discuss if this should be moved to the Edit/Idefix menu but I'd prefer to just leave it here for the moment. > 6. In "Identifier, which is used to reference the label; e.g. using \ref{thisLabel}", > shouldn't it be "... to reference the graphic"? done > 7. Maybe "<new file>" and "<current file>" should be capitalized. done > 8. The panels in BibTeXDialog context should be resizable. The BibTeXDialog is just a very rough help for generating BibTeX entries. Bibliography management from within TXS is limited in many ways. The primary focus is to make TXS a good LaTeX editor, and there are still so many ideas to be implemented... On the other hand, there are already good bibliography management tools and we currently do not plan to extend TXS in that direction. Instead we have created an interface, which allows to push references from a bibliography software to TeXstudio. A first implementation is available for JabRef. I really recommend, not using the Bibliography tools of TXS, but some other software and push citations to TXS. If you are using tools other than JabRef, place a feature request to these tools that they should provide a possibility to push citations to TXS. It's really straight forward (just run "texstudio --insert-cite citation" from the other program). That said, I currently won't work on the bibliography part of TXS. > 9. In Macros -> Edit Macros dialog box, the tooltip for the trigger is indicated > with a blue "?". Maybe the other ones in TXS should be indicated in the same > way, for instance those in Wizard -> Insert Graphic... I don't think that we should put blue question marks everywhere. It's not a standard way for providing help (and a bit distracting if there are blue question marks all over the place. Simple explanations can go to a tooltip. The standard way for more help information would be the WhatIsThis feature, even though I have the feeling it is not widely used by users and developers. > 10. The "Key replacement: % before/after word" macro names are not > translated. Not sure if we can make Macro names translatable. Benito, Jan? > 11. The string "Automatically select filename extension (.txsprofile)" > cannot be translated. As Jan said, this is something by Qt. > That's all for this evening :) > -- > Denis > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Jan S. <sun...@gm...> - 2012-08-12 09:03:00
|
On 12.08.2012 00:02, Denis Bitouzé wrote: > Automatically select filename the first string is now translatable. 11) seems to be a qt string which is (or is not) translated by qt itself. |
From: Denis B. <dbi...@wa...> - 2012-08-11 22:03:03
|
Le samedi 04/08/12 à 12h26, Denis Bitouzé <dbi...@wa...> a écrit : > the new string "..." is not translatable. Another one: "No open project or tex file to clean." in Tools -> Clean Auxiliary Files..., for instance when no file is open. BTW, 1. The string: If "show all" is selected, all phrases are shown. If "minimum phrase length" is selected, a phrase is only shown if it has at least so many characters. (e.g. "a test" has 6 characters) If "minimum word length (one)" is selected, a phrase is only shown if a word of it has at least so many characters. (e.g. "a test" has 4 characters) If "minimum word length (all)" is selected, a phrase is only shown if all words of it has at least so many characters. (e.g. "a test" has 1 character) If "completely ignore" is selected, shorter words are completely ignore. (e.g. with length 3, the sentence "this is a test" is equally to "this test", while the other options would separate it in "this is", "is a", "a test", even if non of this phrases would be shown) is missing a period at its end and contains English typos, as some of the other strings of the "TextAnalysisDialog" context. 2. "Log File not found !" -> "Log File not found!" 3. In "RandonTextGenerator" context: (a) "punctation" -> "Punctation" (b) "ignore case" -> "Ignore case" 4. In "ThesaurusDialog" context, all the strings should be capitalized. 5. IMO, "Manipulate Tables" should be a top menu, as is Math. 6. In "Identifier, which is used to reference the label; e.g. using \ref{thisLabel}", shouldn't it be "... to reference the graphic"? 7. Maybe "<new file>" and "<current file>" should be capitalized. 8. The panels in BibTeXDialog context should be resizable. 9. In Macros -> Edit Macros dialog box, the tooltip for the trigger is indicated with a blue "?". Maybe the other ones in TXS should be indicated in the same way, for instance those in Wizard -> Insert Graphic... 10. The "Key replacement: % before/after word" macro names are not translated. 11. The string "Automatically select filename extension (.txsprofile)" cannot be translated. That's all for this evening :) -- Denis |
From: TeXstudio <be...@be...> - 2012-08-06 12:40:38
|
Idea #11: switch thesaurus in statusbar It would be very nice, if one could also switch the thesaurus language in the statusbar, just as you can do this for the spell checker language. Tags: (none) -------------------------SOLUTION:------------------------ switch thesaurus in statusbar by iholdap Add new QtActionGroup to statusbar with all thesaurus databases availabl |
From: Tim H. <hof...@hi...> - 2012-08-04 13:56:49
|
Should now be fixed. > Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Samstag, 4. August 2012 12:22 > > Le samedi 04/08/12 à 11h46, > "Tim Hoffmann" <hof...@hi...> a écrit : > > > Simplified. > > Well: > > 1. Previous "Allows in-place substition of commands. Example:..." string isn't > declared as obsolete. > > 2. In the new one, substition -> substitution. > > 3. The new "Size of the tab bar at the bottom or top of the completer" > string contains extra HTML declarations (<!DOCTYPE HTML PUBLIC, etc.) > -- > Denis > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Denis B. <dbi...@wa...> - 2012-08-04 10:27:24
|
Hi, when activating the advanced options in "Options" -> "Configure TXS", the new string "You have enabled the advanced options, etc." is not translatable. -- Denis |
From: Denis B. <dbi...@wa...> - 2012-08-04 10:22:19
|
Le samedi 04/08/12 à 11h46, "Tim Hoffmann" <hof...@hi...> a écrit : > Simplified. Well: 1. Previous "Allows in-place substition of commands. Example:..." string isn't declared as obsolete. 2. In the new one, substition -> substitution. 3. The new "Size of the tab bar at the bottom or top of the completer" string contains extra HTML declarations (<!DOCTYPE HTML PUBLIC, etc.) -- Denis |
From: Tim H. <hof...@hi...> - 2012-08-04 09:46:59
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Samstag, 4. August 2012 11:01 > > Hi, > > Wow: only two weeks of vacation and so many strings to translate! ;) This shows > TXS development is active :) > > One remark and one question: > > 1. In the following string the ending punctuation (periods) should be > consistent: > > Allows in-place substition of commands. Example: > - \textbf{foo} > - Put cursor behind "text". > - Start completer by Ctrl+Space > - Select \textrm > - The result is \textrm{foo} > > 2. I definitively don't understand the sentence "Size of the command set tabs at > the bottom or top of the completer". Simplified. > -- > Denis > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Denis B. <dbi...@wa...> - 2012-08-04 09:01:47
|
Hi, Wow: only two weeks of vacation and so many strings to translate! ;) This shows TXS development is active :) One remark and one question: 1. In the following string the ending punctuation (periods) should be consistent: Allows in-place substition of commands. Example: - \textbf{foo} - Put cursor behind "text". - Start completer by Ctrl+Space - Select \textrm - The result is \textrm{foo} 2. I definitively don't understand the sentence "Size of the command set tabs at the bottom or top of the completer". -- Denis |
From: Tim H. <hof...@hi...> - 2012-07-17 20:16:14
|
Dear TeXstudio users, to enhance integration with existing bibliography software, we recently implemented an interface, that allows external programs to push BibTeX keys to TXS. The first user of the interface is a JabRef plugin (thanks to Morton Omholt Alver from the JabRef team). It is available here: http://sourceforge.net/projects/texstudio/files/texstudio/JabRef%20Plugin/Pu shToTeXstudio-1.0.jar/download You can try it out with TXS SVN versions >3013. Furthermore, if you are not a JabRef user, you may encourage the bibliography software of your choice to also implement the interface. It's really simple, because it's just one program call. A description is in the manual. Tim |
From: Tim H. <hof...@hi...> - 2012-07-11 10:11:59
|
Thanks. Changed. > -----Ursprüngliche Nachricht----- > Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Mittwoch, 11. Juli 2012 10:09 > An: tex...@li... > Betreff: [TeXstudio-list] Trailing sentence in translated string > > Hi, > > if I'm right, the sentence: > > "failed after the old content was deleted." > > isn't needed in the new translated string: > > "Only part of the file could be written: > %1 > > failed after the old content was deleted. > > The file may have been corrupted by this! You should save to another > location or fix the problem to prevent data loss. Possible causes > include disk failure or a full harddisk." > -- > Denis > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Denis B. <dbi...@wa...> - 2012-07-11 08:09:18
|
Hi, if I'm right, the sentence: "failed after the old content was deleted." isn't needed in the new translated string: "Only part of the file could be written: %1 failed after the old content was deleted. The file may have been corrupted by this! You should save to another location or fix the problem to prevent data loss. Possible causes include disk failure or a full harddisk." -- Denis |
From: Tim H. <hof...@hi...> - 2012-07-09 05:25:58
|
> Von: Denis Bitouzé [mailto:dbi...@wa...] > Gesendet: Montag, 9. Juli 2012 07:09 > > Hi, > > I have few questions in ending punctuation of some translated strings. > > 1. Wouldn't it be a question mark at the end of ``The command has > been expanded to %1 levels. Do you want to continue expanding "%2".'' Yes. > 2. Isn't missing a period at the end of "Uses SVN revisions to undo > before last saved version" No, it's a label for a checkbox in the options. I don't think you put periods there. But it should be "Use SVN..." > 3. Isn't missing a period at the end of "No, kill the programm" (the > string just before is "Yes, try to recover."). Not sure, because it's a button label. But I wouldn't insert a period here. Anyway it should be consistent. |
From: Denis B. <dbi...@wa...> - 2012-07-09 05:09:03
|
Hi, I have few questions in ending punctuation of some translated strings. 1. Wouldn't it be a question mark at the end of ``The command has been expanded to %1 levels. Do you want to continue expanding "%2".'' 2. Isn't missing a period at the end of "Uses SVN revisions to undo before last saved version" 3. Isn't missing a period at the end of "No, kill the programm" (the string just before is "Yes, try to recover."). -- Denis |
From: Denis B. <dbi...@wa...> - 2012-07-07 12:24:07
|
Le samedi 07/07/12 à 13h29, Benito van der Zander <be...@be...> a écrit : > Perhaps on Windows. I'm using Linux. > It doesn't work at all on my computer. > > I need to press Alt+M, Escape, Alt+M to open the second. Yes, you're right. > And to make it worse, the menu that opens first is the menu that has > not been closed last, so if you're editing, you don't really know > which menu will open, without looking at the screen Right. -- Denis |
From: Tim H. <hof...@hi...> - 2012-07-07 11:30:19
|
> Von: Benito van der Zander [mailto:be...@be...] > Gesendet: Samstag, 7. Juli 2012 13:30 > > >> it is enough to press the shortcut twice to reach the second menu. > > Right. > Perhaps on Windows. > > It doesn't work at all on my computer. > > I need to press Alt+M, Escape, Alt+M to open the second. On Windows it works with Alt+M, Alt+M But that's something I also had to figure out. In submenus, it works like Alt (keep pressed) M, M Anyway I agree that we should try to avoid doubling of accelerators at the top level menu entries. > And to make it worse, the menu that opens first is the menu that has not been > closed last, so if you're editing, you don't really know which menu will open, > without looking at the screen > > > > On 07/07/2012 01:04 PM, Denis Bitouzé wrote: > > Le samedi 07/07/12 à 12h35, > > "Tim Hoffmann"<hof...@hi...> a écrit : > > > >> Just to be precise, we are talking about the accelerators, right? > > Yes. > > > >> Changing them in translations is common and perfectly fine. > > Phew! :) > > > ---------------------------------------------------------------------------- -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > TeXstudio-list mailing list > TeX...@li... > https://lists.sourceforge.net/lists/listinfo/texstudio-list |
From: Benito v. d. Z. <be...@be...> - 2012-07-07 11:25:34
|
>> it is enough to press the shortcut twice to reach the second menu. > Right. Perhaps on Windows. It doesn't work at all on my computer. I need to press Alt+M, Escape, Alt+M to open the second. And to make it worse, the menu that opens first is the menu that has not been closed last, so if you're editing, you don't really know which menu will open, without looking at the screen On 07/07/2012 01:04 PM, Denis Bitouzé wrote: > Le samedi 07/07/12 à 12h35, > "Tim Hoffmann"<hof...@hi...> a écrit : > >> Just to be precise, we are talking about the accelerators, right? > Yes. > >> Changing them in translations is common and perfectly fine. > Phew! :) |