Resolve 2199 #2300
Draft
Resolve 2199 #2300
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- run po4a script on user guides and moneropedia entries - fix issues in _i18n/es/resources/user-guides/remote_node_gui.md - removed leftovers of removed guide canonically_unique_host
✅ Deploy Preview for barolo-time-757cf9 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
plowsof
commented
Jun 23, 2024
| @@ -16,18 +16,16 @@ Pruned-Nodes keine Nachteile bezüglich der Privatsphäre oder Sicherheit. | |||
|
|
|||
| Es gibt drei Möglichkeiten des Prunings: | |||
|
|
|||
| - *Synchronisieren eines Pruned-Nodes von Grund auf:* Du synchronisierst und | |||
There was a problem hiding this comment.
example of "fuzzy" not cleaned up by the original commit author/dropping translations. there are other cases. todo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #2199
2199 has merge conflicts with a timestamp in unlocktime.po / .pot files which is fixed.
when cherry picking the commit in 2199 there after, the ring-size in russian translation has to be corrected back to 16.