All Comments

French is my main language, I started to learn English almost 20 years back. I propose my time to help translating anything into French. Every bit I will suggest will be checked by me but also with tools to improve my works but mostly avoid errors.

---

Bonjour,

Le Français est ma langue principale, j’ai commencé à apprendre l'anglais il y a presque 20 ans de cela. Je propose mon temps pour aider à traduire n’importe quoi en français. Chaque bout que je suggérerais sera vérifié par moi mais aussi avec des outils pour améliorer mon travail et éviter les erreurs.

Regards/Cordialement, GASPARD DE RENEFORT Kévin

In my opinion, names in form <code>Embedded_Handbook/Boards/Pine64/QuartzPro64</code> should be avoided by four reasons:

1. All Board articles are independent articles and they are not part of the Handbook. By including an article in the Handbook namespace, others may think that the articles are written by Gentoo developers, and that's wrong. Most of the articles are provided AS IS, without any audit. The Handbook should remain generic, laptop pages are not part of the Handbook, so why should boards be?
2. Long names separated by slashes are hard to read.
3. Manual categorization will never work.
4. Some official names include slashes (e.g. Embedded_Handbook/Boards/QNAP_TurboStation_109/209/409 - others may treat ''QNAP_TurboStation_109'' and ''209'' as categories).

I suggest categorizing everything like Category:Laptops.

Hi handbook maintainers,

Recently, translated articles started using {{Link}} and {{Anchor}} (see Help:Translating#For_Editors:_Marking_translatable_sections for details) for better link updating. In order for a {{Link}} to a section to work, it requires the linked (target) article to have {{Anchor}}s in its section headers. Usually I edit target articles myself and get it work, but I'm not permitted to edit the Handbook. Some articles already have links to a specific section in the Handbook, and now they're not working in their translated versions.

Can anybody add these {{Anchor}}s in the Handbook?

it says <span id="MIPS_Handbook" next to the link of the MIPS handbook, I think this is a mistake that needs to be fixed.

Hi Handbook maintainers.

Under Viewing the Handbook are 12 architectures. Due to big amount of links, translating them is a bit tricky.

I think it would be more appropriate to create more smaller translate sections, one for each architecture.

Thank you for considering this suggestion. -- Szymon Scholz (talk) 16:19, 20 April 2021 (UTC)

AMD Ryzen 3, 5, 7, 9, and Threadripper, are all part of the same Ryzen family. Therefore, I suggest Threadripper is removed as its own CPU variant, or at least added within brackets to state it is included in the Ryzen family of CPUs.

Some pages accumulated changes that are neccessary for translating other pages (f.e. latest "Kernel" is marked but "Kernel/Dist-kernel" is not, which requires translator to temporarily use old-name references in new places), other are just nice to have. Thanks!

By design the Note, Tip, and Warning templates do not accept a second unnamed parameter... so they are not broken. They are just not built to that expectation.

This affects Template:Note, Template:Tip, Template:Warning and probably other templates.

Example 1:

<pre><nowiki>

</nowiki></pre>

Example 2 (the feature is listed in Template:Note/doc):

<pre><nowiki>

</nowiki></pre>

Hello, dear handbook maintainers. Below is a listing of some excerpts from this documentation entry (i.e. Handbook:Main_Page) in which I am inclined to believe there may be typos.

'''Disclaimer:''' English is not my first language and I may have interpreted some or all of the listed things in a wrong way. If so, I apologize upfront. Thank you for the consideration.

• Handbook:Main_Page#PPC_Handbook: the final sentence reads '' "Readers of this handbook may '''which''' to take a look at (...)" ''. I believe '''wish''' was intended where it currently reads '''which'''.

• Handbook:Main_Page#PPC64_Handbook: the final sentence also reads '' "Readers of this handbook may '''which''' to take a look at (...)" ''. Again, I believe '''which''' was supposed to read '''wish'''.

• Handbook:Main_Page#Can't_the_Handbook_be_dynamically_generated_for_each_installation_choice?: the end of the second paragraph reads " ''(...) and alternate init systems are explained other areas around the wiki in publicly modifiable namespace (hint: anyone with wiki account can edit them!).'' " As a non-native English speaker I must say that I missed some elements. Personally, I would rewrite this as something like (changes highlighted): " ''(...) and alternate init systems are explained '''in''' other areas around the wiki in publicly modifiable '''namespaces''' (hint: anyone with '''a''' wiki account can edit them!).'' "

• Handbook:Main_Page#Can't_the_Handbook_be_dynamically_generated_for_each_installation_choice?: the final paragraph reads " ''We ask our readers to search wiki and discover what is already available (...)'' ". Since the wiki being referred here is very well determined, I miss a ''the'' before the word ''wiki'', resulting in something like " ''(...) to search '''the''' wiki (...)'' ".

• Handbook:Main_Page#Can't_the_Handbook_be_dynamically_generated_for_each_installation_choice?: the final paragraph also reads " ''(...) before requesting a new section or addition to be added to the Handbook.'' " The word ''addition'' feels somewhat out of place, especially with the verb ''added'' so close to it. I believe something on the lines of " ''(...) before requesting the addition of a new section to the Handbook.'' " could read better. Or if new additions are not necessarily in the form of ''sections'', then something like " ''(...) before requesting a new section or addition to the Handbook.'' " could suffice.

• Handbook:Main_Page#Can't_the_Handbook_be_dynamically_generated_for_each_installation_choice?: still under the final paragraph it reads " ''If you believe a new generic section is necessary to add to the Handbook, (...)'' ", maybe it would compose better with the previous sentence if it read something along the lines of " ''If you still believe it necessary to add a new generic section to the Handbook, (...)'' ".

• Handbook:Main_Page#Can't_the_Handbook_be_dynamically_generated_for_each_installation_choice?: still under the final paragraph it reads " ''then propose a request by {{following the instructions below.'' " I believe the two ''{{'' that appear near the word ''following'' (at least they do appear on my end) should not be there.

• Handbook:Main_Page#How_do_I_improve_the_Handbook.3F: the start of the first paragraph reads " ''Suggestions, comments, or ideas on how to make the Handbook better (...)'' ". I believe the second comma should not be there, so it would read " ''Suggestions, comments or ideas on how to make the Handbook better (...)'' ".

Again, thank you for the consideration. --Gabe (talk) 05:52, 13 February 2024 (UTC)