When you create your widgets, it makes it easy for you to define which strings should be translated, by simplyĪdding. That said, this package is meant both for the one person app developer, and the big company team. ThisĬurrent package is also about reducing boilerplate for translations, so it doesn't do anything you can't already do with ForĮxample, async_redux is about Redux without boilerplate,Īnd align_positioned is about creating layouts using fewer widgets. I'm always interested in creating packages to reduce boilerplate. Print("Hello %s, this is %s".i18n.fill()) Prints 'Olá John, aqui é Mary' in Portuguese. Print("There is a person".gender(Gender.they)) // Prints 'There is a person'Īlso, interpolating strings is easy, with the fill method: // Prints 'Hello John, this is Mary' in English. Print("There is a person".gender(Gender.female)) // Prints 'There is a woman' So you could create gender versions for Gender modifiers: print("There is a person".gender(Gender.male)) // Prints 'There is a man' For example, some languages have different Print("There is 1 item".plural(2)) // Prints 'There are 2 items'Īnd you can invent your own modifiers according to any conditions. Print("There is 1 item".plural(1)) // Prints 'There is 1 item' You can also provide different translations depending on modifiers, for example plural quantities: print("There is 1 item".plural(0)) // Prints 'There are no items' And so on for any other locales you want to support. If the current locale is 'pt_BR', then the text in the screen will be "Olá, como vai você?", the Portuguese Or you can also use identifiers, as you prefer: Text(greetings.i18n) i18n to the string: Text("Hello, how are you?".i18n) Start with a widget with some text in it: Text("Hello, how are you?") one issue per one thing to keep things manageable.I18n_extension # Non-boilerplate Translation and Internationalization (i18n) for Flutter # I'm always listening at but if you want to use the public bug tracker instead, please use it as is common, i.e. I'm not sure what purpose would making the items bold serve - it won't improve visibility and it does more harm than good when most items aren't translate (a more common case).
Plus Ctrl+Enter navigation gets you right to them. Untranslated items are immediately obvious and noticeable because the right column is empty. Original untranslated strings in Bold to make it easier to find when not grouped on top of the list. But it seems highly likely that you know what you're doing, so I trust you do ) (Also, I absolutely can't recommend bulk-ignoring the fact that some translations do need work to be good. Having the toggle in the toolbar was crappy and confusing UI. You have the Edit menu for editing operations, including this. Toolbar button to bulk mark as Needs Work. I may eventually get to it myself, especially if more people complain (count so far: 2), but I'll be honest: as something unintentional to begin with, it's not a priority. On Windows, wxWidgets' wxDataViewCtrl control is lacking it - but if you feel really strongly about this, you can implement it in wxWidgets and it will bubble down into Poedit. That said: 2.0 actually (again, accidentally) brings this to macOS. It doesn't make sense as a feature in Poedit, because this is primarily useful for picking an entry from a list, an operation not done in Poedit list.
This never was a feature, but an accidental side-effect of the control used… on Windows - one, to be perfect honest, that I wasn't even aware of until recently. Navigation with keys (e.g.: Pressing the keyboard "C" key to scroll to the next string starting with "C" letter)
That said, feel free to (in fact, please do if required) correct me if I get it wrong below: There were changes, some just cosmetic, yes, and it's a human nature to resist change, and I see why you may dislike some of them, but they aren't what I'd describe as "features". Lot some features that disapeared in v.2.x.