Update translations from Weblate #1
Open
Conversation
This file contains hidden or 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
github-actions
bot
force-pushed
the
update-translations/weblate
branch
2 times, most recently
from
2cd3f29 to
323e644
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
from
323e644 to
71d1fcf
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
2 times, most recently
from
40f3c4f to
28e4431
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
from
28e4431 to
14491db
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
2 times, most recently
from
279a12c to
b0805f1
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
from
b0805f1 to
7bb9c53
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
2 times, most recently
from
86b3f96 to
367a2bd
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
2 times, most recently
from
e573478 to
22a7818
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
2 times, most recently
from
8e0920e to
24c061c
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
from
24c061c to
300c9ec
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
from
300c9ec to
1459952
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
2 times, most recently
from
b999379 to
4458e17
Compare
github-actions
bot
force-pushed
the
update-translations/weblate
branch
from
4458e17 to
1baca18
Compare
Thanks Komyyy for this idea, which I took from PR zulip#1363. Co-authored-by: Komyyy <[email protected]>
Servers can't yet start sending null without breaking clients. Releasing this will start lowering the number of client installs that would break, and eventually there will be few enough that the breakage is acceptable; see discussion (same link as in comment): https://chat.zulip.org/#narrow/channel/378-api-design/topic/.60user_settings.2Etwenty_four_hour_time.60/near/2220696
See the doc: https://pub.dev/documentation/intl/latest/intl/DateFormat-class.html > Formatting dates in the default 'en_US' format does not require > any initialization. (And we haven't been doing the described initialization for 'en_US' or any other locale; it's asynchronous, and we have a better plan for international formatting described in zulip#45, using ffi.)
…nvariants` To include the "senders don't match" case, and rename it to `showSender`.
github-actions
bot
force-pushed
the
update-translations/weblate
branch
from
20d2034 to
67b48b8
Compare
…nish These tests scroll a long way, in order to be sure to scroll to the end of the list. That means they invoke overscroll. The details of how overscroll behaves are changing in an upstream PR: flutter/flutter#173849 The new behavior will take more than a single `pump` to reach the end state where the subsequent checks behave as expected. These tests aren't about the overscroll behavior, so just gloss over any wrinkles by calling `pumpAndSettle`.
Fixes zulip#1523. Chris reported the issue, debugged, and wrote the core of the fix. I added the test, found that the left and right insets reappeared, debugged why, and added removeLeft and removeRight to fix those. Co-authored-by: Chris Bobbe <[email protected]>
This will result in better organization when more tests are added for another type of settings (IntGlobalSettings) in the following commits.
This `init` function has only one caller, `prepare` (it could probably be inlined?); simplify by removing this param and the code inside that was never being exercised.
See discussion: zulip#1784 (comment)
Fixes: zulip#524 [chris: rebased atop some notification-test refactors in the last few commits] Co-authored-by: Chris Bobbe <[email protected]>
github-actions
bot
force-pushed
the
update-translations/weblate
branch
from
67b48b8 to
cd8bfab
Compare
Downloaded from: https://github.com/googlefonts/noto-emoji/blob/b3e3051a0/fonts/Noto-COLRv1.ttf See Unicode 16 Emoji changelog: https://www.unicode.org/emoji/charts-16.0/emoji-released.html For full Unicode 16 support (new emoji reactions and :emoji_name:), the server will need an update for emoji data, CZO thread: https://chat.zulip.org/#narrow/channel/9-issues/topic/seems.20like.20server.20doesn't.20parse.20unicode.2015.20emojis.20yet/near/2253956
This reflects the condition that's directly encoded by this boolean. (Through several conditionals in the rest of the function, we end up confirming that this value is true just if the element does in fact have two `.vlist-r` children, as the old name suggests. But that comes later and more indirectly.)
…t it Mostly this moves and revises comments. Also rename one local to "depthStrut" to match its name in the KaTeX JS, which we also now use in the explanatory comment.
…t doc And leave a comment so we remember to keep this order when adding more fields.
Like HasUserStore for data about users (added in 623bcb4), and HasRealmStore for data about the realm, this will help make it convenient for other substores to refer to data about channels.
This way, this substore becomes a valid home for methods that need to refer to data about both messages and channels. See also fab85ca, where we provided UserStore to ChannelStore.
github-actions
bot
force-pushed
the
update-translations/weblate
branch
from
cd8bfab to
34f56db
Compare
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.
Automated changes by create-pull-request GitHub action