[wp-trac] [WordPress Trac] #60509: Font Collection: Font name and description are not translatable

[WordPress Trac]

#60509: Font Collection: Font name and description are not translatable
--------------------------+---------------------
 Reporter:  wildworks     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.5
Component:  Editor        |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+---------------------

Comment (by swissspidy):

 @mmaattiiaass @wildworks Are font names typically translated? How do other
 projects handle that? Are font names translated in Google Docs or MS
 Office?

 If we want to translate all font names from Google Fonts, we would need to
 do it ourselves. But asking polyglots to translate 1600 (!) font names is
 a lot! We would need to create a separate translation project for this on
 translate.wordpress.org (like continents & cities), update language packs,
 update WP-CLI, etc. I don't think this is feasible for 6.5.

 For the sake of this ticket I'd suggest focusing on collection name &
 description for now. Translating font names is a whole different beast and
 would warrant its own ticket due to the increased scope.

 ----

 > > Now that I think about it more, I think we should update
 wp_register_font_collection to accept an array of options as a second
 argument regardless of how we'll do i18n.
 > This is currently working like that. See these 2 examples:

 But it's not possible to provide a JSON file AND options, which is what
 Riad suggested.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60509#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform