Tag Cloud: Remove strtolower around taxonomy name

[Soean]

Description

In German we have Kategorien (categories) and Schlagwörter (tags). The first letter needs to be uppercase.

[Soean]

I added the copy review label:
Is it okay to use the uppercase Tags instead of tags?
Your sites doesn’t have any Tags, so there’s nothing to display here at the moment.

[michelleweber]

Hmm. That doesn't really work in English; "tags" isn't a word that would be capitalized except in a headline/title.

[Soean]

Thanks for your feedback. So we have to change the sentence.

[aduth]

Thanks for your feedback. So we have to change the sentence.

Are you aware of any prior art for how these issues have been dealt with in the past, as a general point of localization best practices? I'd wonder if in the worst case it might be reasonable to have logic to switch on the locale in deciding the appropriate treatment for the word.

[ocean90]

Have you thought about using a more generic string instead?

Your site doesn't have any items in the selected taxonomy, so there's nothing to display here at the moment.

Otherwise see get_post_type_labels() and get_taxonomy_labels(). Both can be used to define new labels which depend on the post type/taxonomy name.

[melchoyce]

I'd like to avoid using words like "taxonomy" if we can, since it's a pretty technical word.

[ocean90]

But it's something the user has selected in the block settings, see

gutenberg/packages/block-library/src/tag-cloud/edit.js

Lines 69 to 74 in 39f568f

	<SelectControl
	label={ __( 'Taxonomy' ) }
	options={ taxonomyOptions }
	value={ taxonomy }
	onChange={ this.setTaxonomy }
	/>

.

[melchoyce]

Yeah, I mean tbh I'd love to find a better way to write that, too.

[melchoyce]

@michelleweber How do you feel about @ocean90's suggestion? I might just be overthinking this.

[ocean90]

Not sure about the label of the select field but here are some other ideas:

With the current settings there’s nothing to display here at the moment.

There’s no content that matches your selection, yet.

[michelleweber]

I'd definitely like to avoid using the word "taxonomy." We could definitely go general with something like "There's no content to show here yet," but if there's a way to include specific messaging that both explains and nudges the user toward a next step/way to resolve, that would be far, far preferable.

[Soean]

Thanks for the Feedback, I updated the text to: There's no content to show here yet.. This is translatable in all languages and doesn't include the word 'taxonomy'.

[michelleweber]

"No content to show yet" is fine, but it would be really great if, as @aduth suggests, we figure out ways to fine-tune localization. Ideally we're describing things as clearly as possible, and in this case, that means using the word "tags."

[swissspidy]

Well the only way to do that is by extending the list of available taxonomy labels, as mentioned earlier in this thread. See get_taxonomy_labels() in core.

So just like we have labels like Add New Tag and Add New Category, there would need to be new labels Your site doesn't have any tags, so there’s nothing to display here at the moment. / Your site doesn't have any categories, so there’s nothing to display here at the moment.

I'm not sure if it's really worth it to add such a new label for this specific use area.

[Mamaduka]

Hi, @Soean

Can you rebase the branch? I think we can merge this after #16112 (comment) is addressed.

[Soean]

@Mamaduka thanks, I rebased the branch.

[Mamaduka]

Thanks for the follow-up, @Soean 🙇

The feedback was addressed.