Can anyone help me determine why configuring roboto flex using jetpack compose typography API's rend...

# compose-android

[dazza5000]

Can anyone help me determine why configuring roboto flex using jetpack compose typography API's renders differently than roboto using GenericFontFamily access?

[dazza5000]

the code is here https://github.com/dazza5000/fontsforever/blob/master/app/src/main/java/com/example/typography/MainActivity.kt

[dazza5000]

Row {
                MaterialTheme(
                    typography = robotoTypography(),
                ) {
                    Column {
                        Text("b",
                            style = MaterialTheme.typography.headlineLarge.copy(
//                                fontSynthesis = FontSynthesis.None
                            ),
                            maxLines = 1
                        )
                    }
                }

                MaterialTheme {
                    Column {
                        Text("b",
                            style = MaterialTheme.typography.headlineLarge.copy(
//                                fontSynthesis = FontSynthesis.None
                            ),
                            maxLines = 1
                        )
                    }
                }


            }

[dazza5000]

another sample

[dazza5000]

Here is another one that has two custom fonts and the default/generic font

https://github.com/dazza5000/fontsforever/blob/master/three_font_variant.png▾

[dazza5000]

Screenshot_20231213_230546.png

[dazza5000]

also logged it here https://stackoverflow.com/questions/77661356/why-does-why-configuring-roboto-flex-using-jetpack-compose-typography-apis-rend

[dazza5000]

Setting includeFontPadding to false results in a more consistent rendering as seen below

[dazza5000]

I found a solution for this and posted it here https://stackoverflow.com/a/77704556/3268303

[dazza5000]

It looks like this will no longer be relevant in upcoming versions of compose material 3 libs