![translation memory poedit translation memory poedit](https://d33wubrfki0l68.cloudfront.net/33831166f544332a0b1a5241c4670a08dbfc410e/edcd7/images/icons/poedit/icon_96x96.png)
I'm not sure how this would work with the specific requirements of the projects/files division, though. For adding and removing projects, I'd like to see something akin to the existing pattern used in gnome-music, gnome-boxes, etc. I'm not certain of the design of the project view, however.
![translation memory poedit translation memory poedit](https://wplang.org/wp-content/uploads/2014/07/Poedit-Select-Language.jpg)
Translation Memory: Poedit comes with a builtin translation memory to help you translate faster. Not to worry, though, Poedit checks for common problems and warns you. One accidentally added may break things if you’re unlucky. Safety Checks:Gettext can be tricky at times. I think the current design is largely good. Just you and the translation, no distractions.I'd like to see example strings, since with five plural forms it can be easy to forget which one is which. I'd like to see how this would be handled. Would it work to divide the space into three, like transifex does? String list on the left, editing in the center, suggestions and glossary (possibly can change between, like the top buttons used in gnome-music, etc.) on the right? I suggest this in part to allow for the creation of the glossary, but also because in thinking about the editing area, I realized that some languages (including the one I work on) may have numerous plural entries.I don't know that I need to see the whole string at once, but a bit more space to get an idea would be good. Joining separate translation files Poedit provides the translation memory feature that is a kind of dictionary/database to make this task easier. This is a bit of a nitpick, but I'd also like to see more space given to the strings listing, since many strings are very long.
![translation memory poedit translation memory poedit](https://2.bp.blogspot.com/-FQGA6Ql1I_A/Vug3FxKKV8I/AAAAAAAAAKg/-kSaavOjHiUxe0WymzcjFqk2UDj8NNRLw/s1600/Poedit-Pro-1.8.6-Crack-Serial-Key-Free-Download.jpg)
The projects could then contain packages or subprojects or something of the sort which were the individual PO files. I think of projects more as different open source communities, each probably with its own translator profile. That said, there are a ton of PO files to work on for GNOME, and GNOME isn't the only PO-based project I work on. I also like that the recent files concept is pretty much scrapped entirely. I like the notion of giving the string its own frame with the ability to link various things to it, and the idea for marking translated/fuzzy/untranslated matches what I was thinking. I like a lot of the idea in these first concepts.A comprehensive solution for fetching, translating, and uploading translations.Pull in suggested strings from a built-in translation memory.
TRANSLATION MEMORY POEDIT CODE
Provide a path for the user to discover location of string in the code (does not need to be a part of the main interface).Show comments about original string and comments about translated string.Display status of file (total number of strings, number of translated, untranslated, and fuzzy strings, and percent complete).Clearly mark difference between translated, fuzzy, and untranslated strings.Allow the user to easily find additional information.Present a clear and intuitive interface for basic translation.Gtranslator is in need of an interface rework in order to make better use of space and improve the user experience.