Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default to English for XML nodes when no xml:lang is present #2440

Merged
merged 5 commits into from Sep 29, 2023

Conversation

zorgiepoo
Copy link
Member

@zorgiepoo zorgiepoo commented Sep 27, 2023

This only applies when multiple XML nodes are present with the same name. E.g. multiple description or releaseNoteLink elements with different xml:lang's specified.

Also generate a warning if a language has to be interpreted implicitly when there is no xml:lang explicitly specified and there are multiple node items.

Related: #2437

Misc Checklist

  • My change requires a documentation update on Sparkle's website repository
  • My change requires changes to generate_appcast, generate_keys, or sign_update

Only bug fixes to regressions or security fixes are being backported to the 1.x (master) branch now. If you believe your change is significant enough to backport, please also create a separate pull request against the master branch.

Testing

I tested and verified my change by using one or multiple of these methods:

  • Sparkle Test App
  • Unit Tests
  • My own app
  • Other (please specify)

Tested two description elements in test app with one element not set, and other set to es. Changed system language to English and Spanish.
Tested two description elements in test app with one element set to en, and other set to es. Changed system language to English and Spanish.

macOS version tested: 14.0 (23A344)

This only applies when multiple XML nodes are present with the same name. E.g. multiple description or releaseNoteLink elements with different xml:lang's specified.

Also generate a warning if an language has to be interpreted implicitly when there is no xml:lang explicitly specified and there are multiple node items.
@zorgiepoo zorgiepoo added this to the 2.6 milestone Sep 27, 2023
@zorgiepoo zorgiepoo merged commit f6a86f5 into 2.x Sep 29, 2023
2 checks passed
@zorgiepoo zorgiepoo deleted the explicit-xml-lang branch September 29, 2023 03:02
@zorgiepoo zorgiepoo modified the milestones: 2.6, 2.5.1 Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant