FormulaBase - Releases

Emoji are drawn by the app, not by the viewer's device

0.4.14 bundled the full emoji set but kept it as a fallback behind the device's own font. That does not fix flags, and the reason is worth writing down: Segoe UI Emoji has glyphs for the regional indicator letters. It reports 🇯 and 🇵 as covered and simply draws them as two boxed letters instead of forming 🇯🇵 — so nothing is "missing", the browser never falls through, and the bundled font was never even downloaded. Taking only the flag code points away from the device font does not work either: U+200D has to travel with them or 🏳️‍🌈 🏳️‍⚧️ 🏴‍☠️ split into a bare flag, and once U+200D belongs to a different font than the base character, every ZWJ emoji comes apart — families, couples, professions, hair colours.

• All 1,849 emoji are now rendered from the bundled Noto Color Emoji subset (SIL OFL 1.1), on every platform. A device's own emoji font is kept behind it only as a safety net for a failed download.
• Verified on three simulated devices — a complete emoji font, a Windows-like one (has the regional indicator glyphs but cannot form flags), and none at all: all 1,849 render identically in each, flags and ZWJ sequences included.
• The font applies only to the elements that display an icon, so the app's own UI keeps the platform look and body text is untouched — characters such as © ® ™ ↔ stay plain text.
• Cost: one cached 1.7 MB download. Collections are shared, so consistent rendering is the point — everyone now sees the icon the person who picked it saw.

Emoji no longer depend on the viewer's device

0.4.13 shipped a flag-only font, which treated the symptom. The cause is that the app was letting whatever emoji font a device happens to ship decide whether an icon is readable — and flags are simply where that shows up first, because Windows has no flag glyphs on any version (Segoe UI Emoji draws 🇯🇵 as a boxed "JP" and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, a deliberate omission that updates will not fix). The same gap hits anything newer than the device's font: Segoe UI Emoji only gained the Unicode 13/14 additions (🫠 🫰 🫡 …) in Windows 11 22H2. Collections get shared, so an icon has to survive being viewed on someone else's screen.

• FormulaBase now carries all 1,849 emoji it offers, as a subset of Noto Color Emoji (SIL OFL 1.1) — the vector COLRv1 build, 1.7 MB where the bitmap build of the same coverage would be 4.4 MB.
• It is a fallback, not a replacement: the first @font-face is local() only and names the platform emoji fonts, so a device with a complete font uses its own and downloads nothing. Font fallback reaches the bundled file only for the glyphs the platform font turned out to be missing, and the browser caches it from then on.
• Measured on three simulated devices — complete emoji font: never fetched; Windows-like (emoji font present, no flags): fetched the first time a flag is drawn, not on app start; no emoji font at all: fetched on load, and every one of the 1,849 renders.
• The font pair applies only to the elements that display an icon, never to body text, so characters such as © ® ™ ↔ stay plain text everywhere else.

Flags now render on Windows

• Windows ships no flag glyphs: Segoe UI Emoji draws 🇯🇵 as a boxed "JP" letter pair and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, so the 269 flags in the icon picker were unusable there. FormulaBase now carries a flag-only subset of Noto Color Emoji (SIL OFL 1.1) and declares it with a unicode-range limited to the flag code points: the browser fetches the file the first time a flag is actually drawn — not on app start — and then caches it. Every other emoji still comes from the system font, so nothing else changes.

The icon picker now holds every Unicode emoji

• The collection icon picker used to offer a hand-picked 404 emoji. It now contains the complete Unicode 14.0 set — 1,849 emoji, in the nine official Unicode groups (Smileys & Emotion, People & Body, Animals & Nature, Food & Drink, Travel & Places, Activities, Objects, Symbols, Flags), in the official emoji-ordering sequence. The curated Calculation set stays as the first tab.
• Search box: type to filter across all 1,849 by name or keyword, in your own language (CLDR names for all 12 UI languages). Japanese search is kana-insensitive, so "ねこ" finds ネコの顔.
• Group tabs replace one long scroll, and hovering an emoji shows its name.
• The emoji set is fetched only when the picker is first opened, so the app starts just as fast as before.
• The icon input accepts longer sequences (16 units instead of 8), so multi-codepoint emoji such as 🏴󠁧󠁢󠁷󠁬󠁳󠁿 or 👩‍❤️‍💋‍👩 can be typed or pasted without being cut off.
• The emoji category names are now translated into all 12 languages.

Fixed: the Nextcloud user-status menu was broken on FormulaBase pages

• FormulaBase loads the "global" build of the Vue 3 runtime, which publishes window.Vue. A third-party library bundled into Nextcloud core (vue-resize) auto-installs into that global with the Vue 2 API — window.Vue.use(...) — which throws on a Vue 3 namespace and aborted the script that renders the user-status menu. FormulaBase now keeps its Vue copy private and leaves window.Vue untouched.

• App Store screenshots added (8, in Japanese): formula list, live calculation with step-by-step working, several results in one collection, reverse solve (target result), the template picker (2,971 templates / 64 categories), the formula editor, settings, and collection settings.

Emoji are drawn by the app, not by the viewer's device

0.4.14 bundled the full emoji set but kept it as a fallback behind the device's own font. That does not fix flags, and the reason is worth writing down: Segoe UI Emoji has glyphs for the regional indicator letters. It reports 🇯 and 🇵 as covered and simply draws them as two boxed letters instead of forming 🇯🇵 — so nothing is "missing", the browser never falls through, and the bundled font was never even downloaded. Taking only the flag code points away from the device font does not work either: U+200D has to travel with them or 🏳️‍🌈 🏳️‍⚧️ 🏴‍☠️ split into a bare flag, and once U+200D belongs to a different font than the base character, every ZWJ emoji comes apart — families, couples, professions, hair colours.

• All 1,849 emoji are now rendered from the bundled Noto Color Emoji subset (SIL OFL 1.1), on every platform. A device's own emoji font is kept behind it only as a safety net for a failed download.
• Verified on three simulated devices — a complete emoji font, a Windows-like one (has the regional indicator glyphs but cannot form flags), and none at all: all 1,849 render identically in each, flags and ZWJ sequences included.
• The font applies only to the elements that display an icon, so the app's own UI keeps the platform look and body text is untouched — characters such as © ® ™ ↔ stay plain text.
• Cost: one cached 1.7 MB download. Collections are shared, so consistent rendering is the point — everyone now sees the icon the person who picked it saw.

Emoji no longer depend on the viewer's device

0.4.13 shipped a flag-only font, which treated the symptom. The cause is that the app was letting whatever emoji font a device happens to ship decide whether an icon is readable — and flags are simply where that shows up first, because Windows has no flag glyphs on any version (Segoe UI Emoji draws 🇯🇵 as a boxed "JP" and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, a deliberate omission that updates will not fix). The same gap hits anything newer than the device's font: Segoe UI Emoji only gained the Unicode 13/14 additions (🫠 🫰 🫡 …) in Windows 11 22H2. Collections get shared, so an icon has to survive being viewed on someone else's screen.

• FormulaBase now carries all 1,849 emoji it offers, as a subset of Noto Color Emoji (SIL OFL 1.1) — the vector COLRv1 build, 1.7 MB where the bitmap build of the same coverage would be 4.4 MB.
• It is a fallback, not a replacement: the first @font-face is local() only and names the platform emoji fonts, so a device with a complete font uses its own and downloads nothing. Font fallback reaches the bundled file only for the glyphs the platform font turned out to be missing, and the browser caches it from then on.
• Measured on three simulated devices — complete emoji font: never fetched; Windows-like (emoji font present, no flags): fetched the first time a flag is drawn, not on app start; no emoji font at all: fetched on load, and every one of the 1,849 renders.
• The font pair applies only to the elements that display an icon, never to body text, so characters such as © ® ™ ↔ stay plain text everywhere else.

Flags now render on Windows

• Windows ships no flag glyphs: Segoe UI Emoji draws 🇯🇵 as a boxed "JP" letter pair and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, so the 269 flags in the icon picker were unusable there. FormulaBase now carries a flag-only subset of Noto Color Emoji (SIL OFL 1.1) and declares it with a unicode-range limited to the flag code points: the browser fetches the file the first time a flag is actually drawn — not on app start — and then caches it. Every other emoji still comes from the system font, so nothing else changes.

The icon picker now holds every Unicode emoji

• The collection icon picker used to offer a hand-picked 404 emoji. It now contains the complete Unicode 14.0 set — 1,849 emoji, in the nine official Unicode groups (Smileys & Emotion, People & Body, Animals & Nature, Food & Drink, Travel & Places, Activities, Objects, Symbols, Flags), in the official emoji-ordering sequence. The curated Calculation set stays as the first tab.
• Search box: type to filter across all 1,849 by name or keyword, in your own language (CLDR names for all 12 UI languages). Japanese search is kana-insensitive, so "ねこ" finds ネコの顔.
• Group tabs replace one long scroll, and hovering an emoji shows its name.
• The emoji set is fetched only when the picker is first opened, so the app starts just as fast as before.
• The icon input accepts longer sequences (16 units instead of 8), so multi-codepoint emoji such as 🏴󠁧󠁢󠁷󠁬󠁳󠁿 or 👩‍❤️‍💋‍👩 can be typed or pasted without being cut off.
• The emoji category names are now translated into all 12 languages.

Fixed: the Nextcloud user-status menu was broken on FormulaBase pages

• FormulaBase loads the "global" build of the Vue 3 runtime, which publishes window.Vue. A third-party library bundled into Nextcloud core (vue-resize) auto-installs into that global with the Vue 2 API — window.Vue.use(...) — which throws on a Vue 3 namespace and aborted the script that renders the user-status menu. FormulaBase now keeps its Vue copy private and leaves window.Vue untouched.

• App Store screenshots added (8, in Japanese): formula list, live calculation with step-by-step working, several results in one collection, reverse solve (target result), the template picker (2,971 templates / 64 categories), the formula editor, settings, and collection settings.

Emoji are drawn by the app, not by the viewer's device

0.4.14 bundled the full emoji set but kept it as a fallback behind the device's own font. That does not fix flags, and the reason is worth writing down: Segoe UI Emoji has glyphs for the regional indicator letters. It reports 🇯 and 🇵 as covered and simply draws them as two boxed letters instead of forming 🇯🇵 — so nothing is "missing", the browser never falls through, and the bundled font was never even downloaded. Taking only the flag code points away from the device font does not work either: U+200D has to travel with them or 🏳️‍🌈 🏳️‍⚧️ 🏴‍☠️ split into a bare flag, and once U+200D belongs to a different font than the base character, every ZWJ emoji comes apart — families, couples, professions, hair colours.

• All 1,849 emoji are now rendered from the bundled Noto Color Emoji subset (SIL OFL 1.1), on every platform. A device's own emoji font is kept behind it only as a safety net for a failed download.
• Verified on three simulated devices — a complete emoji font, a Windows-like one (has the regional indicator glyphs but cannot form flags), and none at all: all 1,849 render identically in each, flags and ZWJ sequences included.
• The font applies only to the elements that display an icon, so the app's own UI keeps the platform look and body text is untouched — characters such as © ® ™ ↔ stay plain text.
• Cost: one cached 1.7 MB download. Collections are shared, so consistent rendering is the point — everyone now sees the icon the person who picked it saw.

Emoji no longer depend on the viewer's device

0.4.13 shipped a flag-only font, which treated the symptom. The cause is that the app was letting whatever emoji font a device happens to ship decide whether an icon is readable — and flags are simply where that shows up first, because Windows has no flag glyphs on any version (Segoe UI Emoji draws 🇯🇵 as a boxed "JP" and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, a deliberate omission that updates will not fix). The same gap hits anything newer than the device's font: Segoe UI Emoji only gained the Unicode 13/14 additions (🫠 🫰 🫡 …) in Windows 11 22H2. Collections get shared, so an icon has to survive being viewed on someone else's screen.

• FormulaBase now carries all 1,849 emoji it offers, as a subset of Noto Color Emoji (SIL OFL 1.1) — the vector COLRv1 build, 1.7 MB where the bitmap build of the same coverage would be 4.4 MB.
• It is a fallback, not a replacement: the first @font-face is local() only and names the platform emoji fonts, so a device with a complete font uses its own and downloads nothing. Font fallback reaches the bundled file only for the glyphs the platform font turned out to be missing, and the browser caches it from then on.
• Measured on three simulated devices — complete emoji font: never fetched; Windows-like (emoji font present, no flags): fetched the first time a flag is drawn, not on app start; no emoji font at all: fetched on load, and every one of the 1,849 renders.
• The font pair applies only to the elements that display an icon, never to body text, so characters such as © ® ™ ↔ stay plain text everywhere else.

Flags now render on Windows

• Windows ships no flag glyphs: Segoe UI Emoji draws 🇯🇵 as a boxed "JP" letter pair and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, so the 269 flags in the icon picker were unusable there. FormulaBase now carries a flag-only subset of Noto Color Emoji (SIL OFL 1.1) and declares it with a unicode-range limited to the flag code points: the browser fetches the file the first time a flag is actually drawn — not on app start — and then caches it. Every other emoji still comes from the system font, so nothing else changes.

The icon picker now holds every Unicode emoji

• The collection icon picker used to offer a hand-picked 404 emoji. It now contains the complete Unicode 14.0 set — 1,849 emoji, in the nine official Unicode groups (Smileys & Emotion, People & Body, Animals & Nature, Food & Drink, Travel & Places, Activities, Objects, Symbols, Flags), in the official emoji-ordering sequence. The curated Calculation set stays as the first tab.
• Search box: type to filter across all 1,849 by name or keyword, in your own language (CLDR names for all 12 UI languages). Japanese search is kana-insensitive, so "ねこ" finds ネコの顔.
• Group tabs replace one long scroll, and hovering an emoji shows its name.
• The emoji set is fetched only when the picker is first opened, so the app starts just as fast as before.
• The icon input accepts longer sequences (16 units instead of 8), so multi-codepoint emoji such as 🏴󠁧󠁢󠁷󠁬󠁳󠁿 or 👩‍❤️‍💋‍👩 can be typed or pasted without being cut off.
• The emoji category names are now translated into all 12 languages.

Fixed: the Nextcloud user-status menu was broken on FormulaBase pages

• FormulaBase loads the "global" build of the Vue 3 runtime, which publishes window.Vue. A third-party library bundled into Nextcloud core (vue-resize) auto-installs into that global with the Vue 2 API — window.Vue.use(...) — which throws on a Vue 3 namespace and aborted the script that renders the user-status menu. FormulaBase now keeps its Vue copy private and leaves window.Vue untouched.

• App Store screenshots added (8, in Japanese): formula list, live calculation with step-by-step working, several results in one collection, reverse solve (target result), the template picker (2,971 templates / 64 categories), the formula editor, settings, and collection settings.