fix(l10n): Nicer capitalization for generic messages #56283
Conversation
Follow-up to #54202 Actually seeing these in production made me realize that they look awkward without a capital letter at the start. Signed-off-by: kramo <[email protected]>
kra-mo
added
feature: files
papercut
|
Hello @kra-mo , We currently have a colorful mix on this topic in our strings. Are your changes based on a known specification? https://commission.europa.eu/document/download/c45f5b70-2d0e-4da7-b181-b5fe3a16c4bb_en says in chapter 2.7 (page 13): Same here: Do you know of any specifications that we could use in our guidelines? |
rakekniven
left a comment
rakekniven
left a comment
There was a problem hiding this comment.
See my comment.
Let us define a rule before applying such changes.
|
My only thought was that since the string before it is inserted dynamically and is in a different mood, it could never form a complete sentence with what is after it so it just felt very weird to not break it up more. I don't think capitalization after colons should be a rule in general, this is just a one-off because of the weird way this sting is constructed. But I'd love to get rid of these strings and replace them with more natural ones in the future. |
Follow-up to #54202
Summary
Actually seeing these in production made me realize that they look awkward without a capital letter at the start.
Checklist
3. to review, feature component)