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
{{ message }}
Repository navigation
Better support for migrating existing localization schemes from Android/iOS to Flutter #37031
Given a user who already has an iOS style Localizable.strings or a collection of Android strings.xml, create a conversion tool or an import tool for using them in Flutter.
Another option would be to have a localization delegate which at runtime loads up the platform resources via a per platform mapping mechanism (which can be manually added to users' platform projects and communicates the map value via platform channel).
I have not looked into this issue. Assuming that Flutter developers use the dart intl package, this issue is a request to create tooling for that package.
I spoke to @zoeyfan about this and our thinking is that we should probably plan to do this in Q4 but may need to do it earlier depending on how many customers are feeling blocked on this.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
xster commentedon Jul 26, 2019
Another option would be to have a localization delegate which at runtime loads up the platform resources via a per platform mapping mechanism (which can be manually added to users' platform projects and communicates the map value via platform channel).
zoeyfan commentedon Aug 7, 2019
@HansMuller, are you the right person to look at this?
CC @GaryQian
HansMuller commentedon Aug 13, 2019
I have not looked into this issue. Assuming that Flutter developers use the dart intl package, this issue is a request to create tooling for that package.
CC @alan-knight
Hixie commentedon Aug 21, 2019
I spoke to @zoeyfan about this and our thinking is that we should probably plan to do this in Q4 but may need to do it earlier depending on how many customers are feeling blocked on this.
@zanderso @HansMuller I expect this would be a joint effort between your teams?
HansMuller commentedon Sep 27, 2019
There's a proposal (and pointers to a prototype) that's related to this issue here: #41437
HansMuller commentedon Oct 16, 2019
I've removed the critical and customer:header labels because the customer's actual issue is to be addressed by #41437.
github-actions commentedon Jul 11, 2025
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.