master

GGitHubLocalized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)

f5fd4848创建于 13 天前历史提交

文件	最后提交记录	最后更新时间
cs	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
de	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
es	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
fr	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
it	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
ja	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
ko	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
pl	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
pt-BR	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
ru	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
tr	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
zh-Hans	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
zh-Hant	Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2741383 (#28093)	13 天前
Authenticode.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
AuthorizationManagerBase.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
AutomationExceptions.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
CatalogStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
CimInstanceTypeAdapterResources.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
CmdletizationCoreResources.resx	Remove the `<assembly>` element for from `CmdletizationCoreResources.resx` (#27900)	1 个月前
CommandBaseStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ConsoleInfoErrorStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
CoreClrStubResources.resx	Protect the fallback temporary home directory by enforcing and checking its file mode on Unix platforms (#27985)	19 天前
CredUI.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
Credential.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
CredentialAttributeStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
DebuggerStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
DescriptionsStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
DiscoveryExceptions.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
EnumExpressionEvaluatorStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ErrorCategoryStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ErrorPackage.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
EtwLoggingStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
EventResource.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
EventingResources.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ExperimentalFeatureStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ExtendedTypeSystem.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
FileSystemProviderStrings.resx	Improve validation for `Copy-Item -FromSession` (#28006)	30 天前
FormatAndOutXmlLoadingStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
FormatAndOut_MshParameter.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
FormatAndOut_format_xxx.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
FormatAndOut_out_xxx.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
GetErrorText.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
HelpDisplayStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
HelpErrors.resx	Add `GetImportModuleCommand` method back and check for session restriction in `ShowCommand` (#25557)	1 个月前
HistoryStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
HostInterfaceExceptionsStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
InternalCommandStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
InternalHostStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
InternalHostUserInterfaceStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
Logging.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
Metadata.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
MiniShellErrors.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
Modules.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
MshHostRawUserInterfaceStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
MshSignature.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
MshSnapInCmdletResources.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
MshSnapinInfo.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
NativeCP.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
PSCommandStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
PSConfigurationStrings.resx	Tolerate IO/JSON errors reading the per-user `powershell.config.json` (#27373) Co-authored-by: Justin Chung <chungjustin@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>	23 天前
PSDataBufferStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
PSListModifierStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
PSStyleStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ParameterBinderStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ParserStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
PathUtilsStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
PipelineStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
PowerShellStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ProgressRecordStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ProviderBaseSecurity.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
ProxyCommandStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
RegistryProviderStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
RemotingErrorIdStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
RunspaceInit.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
RunspacePoolStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
RunspaceStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
SecuritySupportStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
Serialization.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
SessionStateProviderBaseStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
SessionStateStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
StringDecoratedStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
SubsystemStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
SuggestionStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
TabCompletionStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
TransactionStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
TypesXmlStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
VerbDescriptionStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前
WildcardPatternStrings.resx	Fix the W3C URIs in `.resx` resource files (#27729) This PR essentially reverts https://github.com/PowerShell/PowerShell/pull/3331, which updated all W3C URIs in the `.resx` files from `http` to `https`. That change turned out to be wrong. Those W3C URIs are namespace identifiers, not fetchable URLs -- they must be byte‑exact. Changing them to use `https` corrupted them, and thus `ManagedParser` in the localization pipeline can't recognize the schema, which resulted in the `BL1024 "child table to itself"` error. - This PR makes pure, mechanical 2-line substitution in every `.resx` file: `https://www.w3.org → http://www.w3.org`. - The `ClipboardResources.resx` was using Schema version 1.3, and it's changed to version 2.0 as the rest `.resx` files in this PR.	2 个月前