Ineuw
Northern Hegaz
editThanks for trying to help with The Northern Hegaz, but I have got it already partly prepared in my computer, and so the raw text that you add is quite unnecessary, as I am going to replace it anyway. -- Jan Kameníček (talk) 22:41, 5 April 2023 (UTC)
- Ah, now I can see that you have already added all the remaining pages. Well, never mind, it has not caused any damage, it was just quite unnecessary. --Jan Kameníček (talk) 22:43, 5 April 2023 (UTC)
- I created it just to read the contents. The subject is very interesting to me, especially the Hejaz Railroad built by the Ottomans and Germany, extending from Istanbul to Saudi Arabia. I know the value of one's work and wouldn't think of disturb it. Please feel free to reverse it. — ineuw (talk) 19:02, 6 April 2023 (UTC)
Strictly about The History of Suffrage project proofreading format
edithyphenated page end words
editMy working environment is Linux desktop/laptop, using Linux Mint Cinnamon 21.1 OS, and Firefox 113.0.1.
- The Ws templates are applied by a keyboard macro app, Autokey-gtk, which is the equivalent of AutoHotkey in Windows.
- It repeats the key strokes which makes encapsulating of hyphenated words very quick. The alternative solution demonstrated here: See bottom of this page page and the top of this page. — ineuw (talk) 03:00, 24 May 2023 (UTC)
Lint Concerns.
editDuring the process of adding {{fs85}} and related, you appear to have some unpaired templates within Page: ns.
Perhaps you could take a second look at these , with a view to "pairing" the templates concerned appropriately? Given the comments you left on my talk page I don't feel confident attempting a direct repair on these.
ShakespeareFan00 (talk) 08:35, 22 May 2023 (UTC)
- I've carefully tried to resolve these linter concerns. ShakespeareFan00 (talk) 13:25, 22 May 2023 (UTC)
- I am going through the pages again and again. I am aware of a chapter in volume 2, where the paragraph font size was reduced and I had to follow suit. Otherwise everything else afterward didn't fit.
- I expect it to be so in later volumes as well. Having some personal experience, I observed old style newspaper typesetting by Linotype. They changed fonts to fit the story.
- In this case, it seems that the small fonts were chosen to reduce costs. I learnt that E. S. Cady, and S. B. Anthony were strict managers of funds. — ineuw (talk) 21:35, 22 May 2023 (UTC)
mdash spacing
editPage:History of Woman Suffrage Volume 1.djvu/61 - Did you miss this one in removing the spacing? or was there a reason why you had not changed this one?
https://en.wikisource.org/w/index.php?search=insource%3A%2F+%E2%80%94+%2F+intitle%3A%22History+of+Woman+Suffrage%22&title=Special%3ASearch&profile=advanced&fulltext=1&ns0=1&ns100=1&ns102=1&ns104=1&ns106=1&ns114=1 If you were standardizing across the entire 6 volumes. ShakespeareFan00 (talk) 15:34, 22 May 2023 (UTC)
- You have hawk eyes. You will find them in projects where I couldn't tell the difference between dash and mdash, I used Python to identify them by surrounding them with space but it was wrong. They are mostly in the contents of previous works. — ineuw (talk) 20:49, 22 May 2023 (UTC)
- It's not necessarily hawk eyes, it's knowing what patterns to look for, and I still get caught out by
by words duplicated over a line break sometimes. :( ShakespeareFan00 (talk) 21:34, 22 May 2023 (UTC)
- It's not necessarily hawk eyes, it's knowing what patterns to look for, and I still get caught out by
- When you see duplicated words or whole paragraphs and other anomalies, change the page to Problematic. That's the simplest way to bring it to any editor's attention. Check who did the last edit, because other editors avoided dealing with hyphenated words at the page breaks and several pages needed to be redone.
- I haven't the time to write clarifications as to "why", but they are based on years of experience by observing the appearance of text in HTML environment. Appearance is very important to me in regard to non-editors who read on and offline and print. — ineuw (talk) 22:27, 22 May 2023 (UTC)
Some questions and suggestions
edit@ShakespeareFan00:I looked at your contributions in the main namespace and realized that you never created a project of your own, and completed it to the end.
Why don't you? You could do anything you want within community guidelines. It would help you realize the necessity of consistency in a project.
I know that the material is here for everyone to edit. But, if you undertake a new project, I will support the notion of temporary directorship until the project is completed in a timely fashion.
Obviously, these six volumes on suffrage way passed "in timely fashion", but consider the past three years globally, which also include my slow ability to comprehend the direction and implementation of new web technologies. — ineuw (talk) 08:37, 25 May 2023 (UTC)
- https://en.wikisource.org/wiki/User:ShakespeareFan00/Completed was the list of works I'd but a substantial effort into (including a consistency of style I might add). I can have another look at those in terms of main-space transclusions, but typically, I sometimes wait until issues like missing images were added, before transcluding to mainspace.
- The most recent efforts in terms of 'de-linting' pages, aren't necessarily going to show up in main-space. ShakespeareFan00 (talk) 16:41, 29 May 2023 (UTC)
- I do have certain fairly big and rather technical projects I'd appreciate someone took on a mentorship role for. ShakespeareFan00 (talk) 16:42, 29 May 2023 (UTC)
- @ShakespeareFan00: What are you looking for, and what do you mean by "mentorship"? — ineuw (talk) 00:34, 23 August 2023 (UTC)
Simple temporary addition recommended for table design
edit@JAM3SP196, @ShakespeareFan00: In case you are interested:
- The temporary addition of the word "border" following a table declaration helps to compare our result with the original. I made changes to the table design using "border" with table declaration . On the basis of the outline, it was obvious what needed to be adjusted.
- In regard to floating tables, the best practice is no width declarations to allow the object's natural behavior determine the object width.
- Floating tables must be succeeded by any of the following:
{{clear}} or {{nopt}} or <!---->
Question about replacement of text with images of text
editHi, I noticed that in a number of cases you have replaced transcribed text with images of the text (e.g. title page, colophon, etc.) and was wondering why you were doing this?Chrisguise (talk) 05:28, 29 July 2023 (UTC)
- @Chrisguise: I wanted to convey a sense of the original as an introduction, because we could not replicate it, so far. There is no other reason. I also used images of tables which were to large and complex to reproduce. — ineuw (talk) 08:33, 29 July 2023 (UTC)
Delinting efforts and your comments on my talk page.
editI'm sorry, that you feel that the de-linting efforts (intended in good faith) I'd been doing are 'disruptive', potentially due to the systemic nature of them, affecting more than a handful of works in which you were trying to maintain a consistent approach. I am currently thinking that the best approach would be to abandon the de-linting effort entirely, until you and the other more experienced contributors can develop some guidelines on how mass de-linting can be done in a responsible way, if at all.
I'd like to continue editing here, and would like to ask if you would be willing to temporarily mentor or help bring a specific project I had in mind from scan to transclusion? ShakespeareFan00 (talk) 23:41, 29 May 2023 (UTC)
- I can help, but you should realize that I can only help in my style of editing. My work is limited to my interests and end up using the same style. Afterwards, you do with it whatever the community rules let you. — ineuw (talk) 13:44, 30 May 2023 (UTC)
- What I was working on to get back into proofreading mindset rather than 'linting' was a short work here:-
- Index:Stenotypy- or, Shorthand by the typewriter .. (IA stenotypyorshort00quin).pdf
- The exact concern I had is the inter-'word' spacings in the monospaced portions, might not be quite the same as in the original, although I've attempted very hard to match the scan where possible. Reading late 19th century txtspk isn't easy. ShakespeareFan00 (talk) 13:52, 30 May 2023 (UTC)
- I am starting to understand why you left the comment you did though. ShakespeareFan00 (talk) 13:52, 30 May 2023 (UTC)
Lints.
editDespite the disagreements we've had, I thought you might want to know about these:-
Based on your past comments, I won't be attempting repairs, but you might want to do a careful review. ShakespeareFan00 (talk) 10:54, 29 June 2023 (UTC)
- Much thanks, and we don't have disagreements. It's just difficult to know a person by an occasional online conversation. Please let me know of any errors anywhere I worked on. I will repair them all. — ineuw (talk) 19:15, 29 June 2023 (UTC)
- Page:The complete poetical works and letters of John Keats, 1899.djvu/46 - line 6 in main body, missing {{fs85/e}}?
- https://en.wikisource.org/wiki/Special:LintErrors/stripped-tag?namespace=&titlecategorysearch=History+of+Woman+Suffrage&exactmatch=&tag=all&template=all {{fs85/s}} {{fs85/e}} pairing.
- ShakespeareFan00 (talk) 09:52, 30 June 2023 (UTC)
- https://en.wikisource.org/wiki/Special:LintErrors/missing-end-tag?namespace=&titlecategorysearch=History+of+Woman+Suffrage&exactmatch=&tag=b&template=all
- https://en.wikisource.org/wiki/Special:LintErrors/missing-end-tag?namespace=&titlecategorysearch=History+of+Woman+Suffrage&exactmatch=&tag=i&template=all
- Note the I tag results include a number of semi-false positive results for pages that have not yet been proofread, and those results can be ignored until those pages have been proof-read. ShakespeareFan00 (talk) 10:17, 30 June 2023 (UTC)
- P tag results omitted as you've previously explained why those exist ShakespeareFan00 (talk) 10:17, 30 June 2023 (UTC)
- @ShakespeareFan00: Please ignore pages that have not been proofread, My start page today will be page 536 of volume 2. The rest are yet to be checked. — ineuw (talk) 23:04, 30 June 2023 (UTC)
Comment deletion
editPlease take care not to delete other people's comments. --EncycloPetey (talk) 19:49, 5 July 2023 (UTC)
- My apologies, this must have happened as we posted simultaneously. Please don't assume the worst. I never deleted anyone's post deliberately. But, it did happen a couple of times when posting. Would you care to explain why would you assume that? — ineuw (talk) 20:15, 5 July 2023 (UTC)
- No, it could not be a simultaneous posting. Koavf responded after I commented, and you deleted my comment as well as Koavf's reply.
- Where in my comment did I claim your action was deliberate? Where did I "assume the worst"? --EncycloPetey (talk) 20:21, 5 July 2023 (UTC)
- I apologize again for misposting. In addition, posting here is not my favorite activity. If this apology is not accepted, then we can meet for a duel to restore your honour. But the time, must be no earlier then the afternoon EDT. I like to sleep in. — ineuw (talk) 20:50, 5 July 2023 (UTC)
Lints.
editCan you re-check Page:History of Woman Suffrage Volume 3.djvu/69? I'm seeing a div-span flip that suggests
paragrpah1
<p>
paragrpah2
should be
paragrpah1
<p></p>
paragrpah2
The other lint on the page is a ''
instead of "
.
I haven't attempted a repair given you previous comments. ShakespeareFan00 (talk) 13:12, 10 August 2023 (UTC)
- Thanks for pointing them out. You will find more in these volumes and go ahead, if you feel like repairing them. In the beginning, I needed to know what is going on, since my contributions have fallen considerably over the past 2-3 years.
- I am aware of the italics versus double quote errors, and correct them when I check the results in the main namespace. This was the unfortunate result of my Python script and already corrected it. The script was designed for proofreading
- The History of Mexico volumes which was scanned by a different OCR scanning equipment, and OCR software, used by Internet Archive or the donor.
- I was under the impression that <p> is a standalone tag like <br> or <br />. Please correct me if I am wrong. I used them to separate paragraphs when the font-size is less than 80% by my calculations.
- Looked at the poem definition, the footer, and {{smallrefs}}, and realized that my knowledge of templates are way outdated. Modifications and improvements made over the years to the templates, are only noticed when the change is visual. — ineuw (talk) 18:39, 11 August 2023 (UTC)
<p>
is not a stand-alone tag. It has to be used as<P>(content)</P>
ShakespeareFan00 (talk) 00:03, 12 August 2023 (UTC)- Thanks, in that case there are a number of them in the volumes. — ineuw (talk) 00:08, 12 August 2023 (UTC)
- And I've carefully done some attempted repair work this morning:) Pausing in case you wanted to check for formatting concerns I didn't spot. ShakespeareFan00 (talk) 09:29, 12 August 2023 (UTC)
- Much thanks for all the help. I really appreciate it. — ineuw (talk) 11:28, 12 August 2023 (UTC)
- And I've carefully done some attempted repair work this morning:) Pausing in case you wanted to check for formatting concerns I didn't spot. ShakespeareFan00 (talk) 09:29, 12 August 2023 (UTC)
- Thanks, in that case there are a number of them in the volumes. — ineuw (talk) 00:08, 12 August 2023 (UTC)
Lint concern- Italics and hws..
editexample:- Page:Popular Science Monthly Volume 22.djvu/579
Trying to wrap the italics using the HTML directly, seemingly generates mal-formed HTML according to the linter. The approach that works reliably is to move the italicisation entirely within the template parameters and use the title option on the hws/hwe pair.
I'm fixing these manually from the linter output, but would appreciate a review from yourself as the original proofreader.
I will also note that the linter/parser doesn't seem to like line-feeds inside span-based templates where the generated span template also sits wthin a DIV. That is a use case you might want to review elsewhere. ShakespeareFan00 (talk) 10:55, 29 October 2023 (UTC)
- Thanks, there are a few such cases, that I remember using years ago. But no longer do this. — ineuw (talk) 16:20, 29 October 2023 (UTC)
- Rather than me listing concerns of this nature individually, monitoring - https://en.wikisource.org/wiki/Special:LintErrors/misnested-tag?wpNamespaceRestrictions=104&titlecategorysearch=&exactmatch=1&tag=all&template=all will give more of these concerns. Not a high priority, but it would be nice to resolve these at some point. ShakespeareFan00 (talk) 09:02, 6 November 2023 (UTC)
- You are a prince. I will correct them. Thanks. — ineuw (talk) 19:00, 6 November 2023 (UTC)
Why are you using nonstandard page labelling on this index? Pages 1, 13, and 35 are using chapter numbers in place of page numbers. Pages iii - ix all have the same label "int", which will prevent external linking to a specific page by number. Is this temporary numbering that will be corrected when the work is finished? --EncycloPetey (talk) 22:07, 7 January 2024 (UTC)
- Thanks for pointing this out. My intent is to conform to the standard and will correct this immediately after creating the main namespace pages. I needed it for chapter identification. I will also check all my past contributions and correct them accordingly. — ineuw (talk) 01:57, 8 January 2024 (UTC)
- @EncycloPetey: I have no knowledge or experience with assigning the starting roman page numbers. The {{roman}} is missing the old documentation. Could you please correct this volume? I will check all the indexes worked on. Main namespace contributions are listed on my home page, so it's easy to check. — ineuw (talk) 18:46, 12 January 2024 (UTC)
- Done --EncycloPetey (talk) 18:52, 12 January 2024 (UTC)
- @EncycloPetey: I have no knowledge or experience with assigning the starting roman page numbers. The {{roman}} is missing the old documentation. Could you please correct this volume? I will check all the indexes worked on. Main namespace contributions are listed on my home page, so it's easy to check. — ineuw (talk) 18:46, 12 January 2024 (UTC)
I was looking at this template's code and noticed the the warning about it's use within another template. And I am asking if my use is acceptable, or not. No explanation needed, just a recommendation of a safe alternative.
THIS PAGE is one example of the many, where I used Gap within {{Right}}, but never at the end as in the example, because this template was created for Popular Science Monthly. — ineuw (talk) 01:59, 8 February 2024 (UTC)
- Hmm. Did you intend to post this at WS:S/H? In any case, there's no general limitation about using {{gap}} inside other templates. The warning in the documentation is about avoiding using {{gap}} for things it's either not intended for, or for which a better solution exists. Rule of thumb: don't use it for something that's most naturally described as a "margin". The examples it gives are to not use {{gap}} to achieve a block left margin or for adding a right margin to a right-aligned block. The way you've used it on Page:History of Woman Suffrage Volume 3.djvu/441 looks perfectly fine to me: you're putting an extra gap between two words inside a single line, which is exactly what the template is for. Xover (talk) 11:28, 23 February 2024 (UTC)
- I don't use it in such a way. My aesthetics would not allow that. I have a decent sense of the relationship between HTML and the wiki code. — ineuw (talk) 19:14, 23 February 2024 (UTC)
Smallrefs with font size
editHi,
I notice you routinely specify an explicit font size for every {{smallrefs}} in History of Womam Sufferage. I have created a style sheet for all six volumes (e.g. Index:History of Woman Suffrage Volume 6.djvu/styles.css) and added your preferred font size there, so specifying it explicitly in the template is no longer necessary. This is generally a (much) better way to do such per-text customizations (set it once, applies to everything in the book). The font size parameter to the template is in the process of being phased out, so I recommend using the per-text CSS for all your projects. You should be able to just copy and paste the relevant bit of the stylesheet to the indexes for other works; and feel free to ask for help at WS:S/H if needed.
However, that being said… So far as I can tell this text doesn't actually use any noticeably smaller footnote font than other works, so I don't quite see the rationale for deviating from the standardized font size for {{smallrefs}}. If this is about your personal preference for smaller text for the footnotes, rather than about some aspect of the actual text, then you should move the font size adjustment to your personal stylesheet (either in your web browser, or in the .css for whatever skin you're using (I see you have user scripts / styles for monobook, Vector, and Vector 2022 so I don't know which you're using). Xover (talk) 11:40, 23 February 2024 (UTC)
- Much thanks for the changes. I compared the font sizes of smallrefs with other works, and realized that the size difference is only for my own eyes. I stop using it, and thanks for the explanations. I am using Vector 2010 with Ubuntu and Hack font in Firefox. If you come across my edit anomalies, please let me know so that I can learn with practice. — ineuw (talk) 19:04, 23 February 2024 (UTC)
Hello. I note that you moved this index to a better name. It seems that there were already some pages created:
Page:Volume 1.djvu/10- Page:Volume 1.djvu/11
- Page:Volume 1.djvu/12
- Page:Volume 1.djvu/21
- Page:Volume 1.djvu/22
- Page:Volume 1.djvu/23
- Page:Volume 1.djvu/9
-- do you know if they should just be moved to match the new index name ? Or might that cause problems ? -- Beardo (talk) 06:03, 28 February 2024 (UTC)
- @Beardo: As an example, I copied page 10 and pasted it in the new version. That is the only thing that can be done with 7 pages. — ineuw (talk) 10:05, 28 February 2024 (UTC)
Reminder to vote now to select members of the first U4C
edit- You can find this message translated into additional languages on Meta-wiki. Please help translate to your language
Dear Wikimedian,
You are receiving this message because you previously participated in the UCoC process.
This is a reminder that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) ends on May 9, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.
Please share this message with members of your community so they can participate as well.
On behalf of the UCoC project team,
Ilf and Petrov novel
editYou mentioned here that you were interested in the old translation of Twelve Chairs. The copy I asked for came through; it was published in New York and didn’t comply with the formalities, so it’s in the public domain in the United States. If you would like, I can scan it in so that you can proofread it. TE(æ)A,ea. (talk) 19:30, 21 May 2024 (UTC)
- @TE(æ)A,ea. You are very generous to offer your time. Much appreciated, but only if its as much a pleasure for you to do it, as it is for me to edit and read it. At this point I don't know how to do that, but plan to learn. — ineuw (talk) 22:19, 22 May 2024 (UTC)
- — ineuw: Here you go: Index:Diamonds To Sit On.pdf. I also scanned the cover and title page in higher quality, because of the images; although the image on the title page can probably be found elsewhere. TE(æ)A,ea. (talk) 21:23, 29 May 2024 (UTC)
- Much thanks. Your are a prince, even though I am a Republican (not the US kind, the France and Canada kind). — ineuw (talk) 23:54, 30 May 2024 (UTC)
Question about unused files
editHi! I was checking Category:GFDL to see if the files were eligible for w:Wikipedia:Licensing update and I noticed some of the files you uploaded are unused and marked as a temporary or test file. For example File:1 - Preferences - Edit page setup.jpg. Are the files supposed to be deleted or what is the plan? --MGA73 (talk) 18:53, 14 August 2024 (UTC)
- It has no relevance, I want to delete it but can't. You are welcome to do so. Also, the file should be in the Public Domain. — ineuw (talk) 21:41, 14 August 2024 (UTC)
- I can't delete either. But perhaps you can add a {{sdelete|7}} to the files? --MGA73 (talk) 22:34, 14 August 2024 (UTC)
Hi! I see the file was deleted. It seems that these files are also unused:
- File:1536x864res.jpg
- File:1664x936res.jpg
- File:2_-Preferences_-_Gadgets_1.jpg
- File:3_-_Preferences_-_Gadgets_2.jpg
- File:4_-_Advanced_toolbar_-_Special_characters.jpg
- File:5_-_Advanced_toolbar_-_Proofread_tools.jpg
- File:New_Proofreading_tools.jpg
- File:Header_and_footer_are_forced_below_the_main_textbox_in_Vivaldi.jpg
- File:Header-footer_toggle.jpg
- File:T219048.jpg
- File:Page_tools.jpg
- File:Over_under_editing_window.jpg
- File:Misaligned_text_pages.jpg
- File:Matching_toolbar_2.jpg
Enjoy the weekend :-) --MGA73 (talk) 17:12, 16 August 2024 (UTC)
- Done. — ineuw (talk) 17:21, 16 August 2024 (UTC)
You've done some work on that, which now looks more-or-less finished, and it's had a {{under construction}} tag ever since. Mind if I remove it? — Alien333 ( what I did
why I did it wrong ) 22:29, 29 August 2024 (UTC)
- @Alien333: Thanks. I removed it. — ineuw (talk) 00:13, 30 August 2024 (UTC)
Legacy toolbar
editHi Ineuw,
According to MediaWiki's stats there is only one active user on enWS that uses the so-called "Legacy toolbar" (the one visible in this screenshot, aka. the "2006 toolbar"). The software doesn't tell me who that user is (for obvious privacy reasons), but I seem to recall in a previous discussion you mentioned you used this. Do I recall correctly?
This old (old old) code is a bit costly to maintain for just one user, so I'd like to look into alternatives. For example, if the reason you're not using the new(er) editing toolbar (the one now called the "2010 toolbar") is that it is missing some functionality or other, that would be a good thing to know (and might be possible to fix). Would you be willing to experiment a bit and try to pinpoint any specific issues, for you, with switching to the 2010 toolbar? Xover (talk) 06:17, 6 September 2024 (UTC)
- Hi Xover,
- It will be either me or Billinghurst. I have the gadget for the legacy toolbar switched on, but I also currently have the 2010 override in place because one of the works I'm dealing with requires the OCR functionality because the text layer is crap. The only button I actually use on either toolbar is the hyphenated word end one when I've needed to use hws on the previous page. The advantage of the 2006 legacy toolbar is that the CharInsert line always drops to the bottom when proofreading. With the 2010 it's sometimes at the bottom and sometimes at the top. When doing pages with lots of characters needing to be pulled in, it's frustrating to not know where the gadget will show up. (I'm using the Monobook skin, of course.) Beeswaxcandle (talk) 07:32, 6 September 2024 (UTC)
- @Beeswaxcandle: Ah, thanks. But then, if we could get charinsert to behave consistently in the 2010 editor we could retire the 2006 toolbar? Xover (talk) 08:48, 6 September 2024 (UTC)
- And reduce the screen real-estate that the 2010 toolbar consumes. When the 2006 toolbar was initially force-retired in 2018, the 2010 was too horrible and I operated for two years without a toolbar at all—except when training someone. Then in Feb 2021 Billinghurst "gadgetified" what enWP had done to get the toolbar back. The neat and compact toolbar that slots between the header and body fields is ideal. The sprawling version that is the current default takes up too much room on a laptop screen. Beeswaxcandle (talk) 09:08, 6 September 2024 (UTC)
- @Beeswaxcandle: I don't think that's likely to be possible, but I'll follow up on your talk page so poor Ineuw won't get spammed with our discussion. :) Xover (talk) 09:50, 6 September 2024 (UTC)
- I don't mind visitors to my talk page. I will check my alter ego account User:IneuwPublic. But, I am a Vector(2010) ever since it became available and usable. This includes the toolbar, because there is no setting in the current Preference pages of Edit and Gadget. If something is missing, I deal with it using a keyboard macro. — ineuw (talk) 20:25, 6 September 2024 (UTC)
- The account was disabled at my request months ago. Does the 2006 toolbar still appears? — ineuw (talk) 18:55, 8 September 2024 (UTC)
- I don't mind visitors to my talk page. I will check my alter ego account User:IneuwPublic. But, I am a Vector(2010) ever since it became available and usable. This includes the toolbar, because there is no setting in the current Preference pages of Edit and Gadget. If something is missing, I deal with it using a keyboard macro. — ineuw (talk) 20:25, 6 September 2024 (UTC)
- @Beeswaxcandle: I don't think that's likely to be possible, but I'll follow up on your talk page so poor Ineuw won't get spammed with our discussion. :) Xover (talk) 09:50, 6 September 2024 (UTC)
- And reduce the screen real-estate that the 2010 toolbar consumes. When the 2006 toolbar was initially force-retired in 2018, the 2010 was too horrible and I operated for two years without a toolbar at all—except when training someone. Then in Feb 2021 Billinghurst "gadgetified" what enWP had done to get the toolbar back. The neat and compact toolbar that slots between the header and body fields is ideal. The sprawling version that is the current default takes up too much room on a laptop screen. Beeswaxcandle (talk) 09:08, 6 September 2024 (UTC)
- @Beeswaxcandle: Ah, thanks. But then, if we could get charinsert to behave consistently in the 2010 editor we could retire the 2006 toolbar? Xover (talk) 08:48, 6 September 2024 (UTC)