Description:
Machine translation of this page (e.g. De-De and Fr-Fr) tends to
break the table format by translating some of the escaped pipe
characters as cell dividers instead of keeping them as code
within the first column.
Thanks to d-Rickyy-b (Rico) for noting this issue in the De-De version.
Proposed changes:
- Add code block back ticks around the command line arguments
in the first column to keep them from being translated.
- adjustment of white space (blanks) for consistency.
issue ticket closure or reference:
Ref. #4604 (wait for migration to translated pages before closing)
- re-add the removed `> [!NOTE]` line for the new note
- properly remove an added line which should have been replaced
- remove trailing spaces (redundant blank space at the end of the lines)
Description:
Based on community feedback and recommendation, this document can be
improved by adding notes regarding Delivery Optimization and endpoints.
Thanks to Stephen Leuthold for providing feedback and the information.
See also issue ticket "Delivery Optimization" (#4638).
Proposed changes:
- add a note containing the text suggested by SLeuthold
- add MarkDown compatibility quote spacing (33)
Caveats:
- The added text does not necessarily have to be in the form of a Note.
- The added text can, if required, be placed somewhere else on the page.
issue ticket closure or reference:
Closes#4638
Description:
As reported & discussed in issue ticket #5089 (Certutil command wrong),
the certutil command modifiers need to be in a comma separated list,
otherwise you will get the error message "too many arguments".
This behavior has been verified by TechNet moderator Steven_Lee0510:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/847c13d5-a32e-4799-bb83-2f8ead98a069/certutil-too-many-arguments?forum=winserversecurity
Thanks to Digiroka for reporting and pointing out this issue.
Proposed changes:
- replace the modifier/argument spaces with commas
- add missing MD compatibility spacing in 2 MarkDown notes
issue ticket closure or reference:
Closes#5089
- Aligned and evened out the column spacing in column 1, "Error code",
by removing redundant spaces and aligning the values (same width).
- Removed a misplaced number in the "Handler errors" table.
This is a "best effort" attempt at keeping code names from being
translated by automatic translation/machine translation.
The main change here is to add a MarkDown back tick (code tag) before
and after each code name reference in the tables, to block translation.
The side effect of seeing a massive text change appears because of the
text being shifted at least 2 spaces sideways for the entire Message
column, some times more due to code names also appearing in the
Description text. I have also taken the liberty to add spacing to clean
up the table layout, to improve readability for future edits. This also
affects the appearance of massive change.
Browsing the PR content in Rich Text Diff view will be most useful.
A couple of minor typos are also corrected (cancelled -> canceled)
(according to Webster).
This content should in theory close issue ticket #4933, but it remains
to be seen if blocking the code names from being translated will be as
effective as we are hoping for. Hence, I will only reference issue
ticket #4933 and not apply automatic git closure.
Ref. Перевод констант #4933
Description:
As reported in issue ticket #4936, the link win.data.microsoft.com
does not work as a an endpoint for diagnostic data services.
On the other hand, settings-win.data.microsoft.com does.
Thanks to amirsc3 for finding and reporting the incorrect links.
Proposed changes:
- add table outer limit markers
- correct 3 links by adding the missing prefix "settings-"
- replace hyphens with colon to separate descriptions and data
- add extra line breaks in the tables to separate different data
- add 1 missing MarkDown space in a Note further down
issue ticket closure or reference:
Resolves#4936
Description:
As noted in issue ticket #5166 (Has Data Export been retired?),
streaming Advanced Hunting events to your Storage account
is only available if you turn on the Preview feature switch in
Settings -> Advanced Features.
Thanks to Daniel Snelling (dancs85) for reporting this issue.
Proposed change:
- Add a required procedural step to turn on **Preview features**
Additional notes:
The format and placement of this information is very much subject to
change before merging into the existing document page, depending on
factual feedback from the document author or manager.
issue ticket closure or reference:
Closes#5166
