You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Outlook for Mac is using ic_fluent_text_number_list_20_regular in many scenarios, and the released version used in Outlook is 1.1.221.
This icon displays normal in LTR language.
Then it is mirrored in RTL language, but the number "1,2,3" was flipped that seems not as expected. And we do not provide versions for languages like Arabic.
Potential cause
In the metadata.json of Text Number List of the latest version 1.1.222, the directionType is unique and the singleton is LTR. Looks like this will result in a single language-direction icon for number list.
After looking into the Content.json of ic_fluent_text_number_list_20_regular which generated in iOS/FluentIcon/Assets/IconAssets.xcassets path, we're providing only one version of language-direction for this icon. So that Xcode can only use this icon and its mirror.
Question/Expected
Is this as by design or a bug?
Do we need to provide various kinds of icon for LTR/RTL languages, just like what Apple does in SF Symbols?
Summary
Outlook for Mac is using
ic_fluent_text_number_list_20_regular
in many scenarios, and the released version used in Outlook is1.1.221
.This icon displays normal in LTR language.
Then it is mirrored in RTL language, but the number "1,2,3" was flipped that seems not as expected. And we do not provide versions for languages like Arabic.
Potential cause
Text Number List
of the latest version 1.1.222, the directionType isunique
and the singleton isLTR
. Looks like this will result in a single language-direction icon for number list.ic_fluent_text_number_list_20_regular
which generated in iOS/FluentIcon/Assets/IconAssets.xcassets path, we're providing only one version of language-direction for this icon. So that Xcode can only use this icon and its mirror.Question/Expected
Cc @nickromano
The text was updated successfully, but these errors were encountered: