• you would still have to download the language files from the web server (unless it's a local one)
  
• you need to know which program to use for translation,
  
• you need to start this program,
  
• you need to select the language file and maybe the source code for automatic scanning for codes,
  
• you need to upload the language file(s) to the web server
  
• etc.
  

• listing all plugins (and GetSimple) for selection by the user,
  
• scanning the selected plugin to see, if it conforms to the internationalization guidelines for GetSimple plugins,
  
• scanning the php files to find the codes used,
  
• displaying all available languages and their translation percentage
  
• allowing the user to translate from any language to any other language displaying the languages (and the codes) side-by-side, and
  
• saving the updated or new language files directly on the server,
  
• so that it can be tested immediately!
  
• And if you like it, you submit it to Extend with one mouse click! (future feature)
  

Joshas Wrote:One issue - autogrow js fails to load if site is in subdirectory.

Joshas Wrote:Tested with latest r418 version - still doesn't work correctly - variable $SITEURL is empty. Tested in WampServer on Windows. Fixed it by replacing $SITERURL with .. (dir up). It works, but in translations with many lines autogrow causes a noticalbe slowdown. I'd suggest to replace autogrow with more basic solution.
Finally, there are several unclosed "</strong" tags in translate.php causing problems with layout.

ccagle8 Wrote:Wow Mvlcek: i am very impressed. I wonder if we should turn this into a service @ get-simple.info instead of or in addition to a plugin?

Thank you for this...

yojoe Wrote:

ccagle8 Wrote:Wow Mvlcek: i am very impressed. I wonder if we should turn this into a service @ get-simple.info instead of or in addition to a plugin?

Thank you for this...

Definitely. I mentioned some time ago that there should be a way to automatically add translation files to uploaded plugins

ccagle8 Wrote:Yeah, and that may or may not happen - but the service I was walking about would be the ability to "create" a new language file for GetSimple right from our site. mvlcek would you mind if we used parts of this code to create a "language file creator" right on this site?

• For each plugin allow registered users to upload language files
  
• In the plugin info also list the languages included with the plugin
  
• The language files are available as separate downloads, not automatically included in the plugins
  
• Each language exists at most once (it has no owner like plugins), but a history of the uploaded files is kept
  
• Possibility to download all language files - zipped on-the-fly - mainly useful for developers, who want to include the languages in the plugin file
  
• Nice to have: The list of the language files should have the completeness percentages - where the codes that have to be translated are determined by the union of codes in the language files within the plugin and (maybe) the codes found by the source scan - these percentages must be calculated on submission of a language file and (for all language files) on submission of a new version of the plugin
  
• By having a completeness percentage it would not be important to specify a "for plugin version x" for the language files
  

• The codes are the union of all codes in all language files WITHIN the plugin - theoretically they should be the same ;-)
  
• The php files can also be parsed like in the plugin - and the found codes added - and those not found grayed out in the editor (it might not be correct, if the code contains $myvar='code'; i18n($myvar) )
  
• The language files OUTSIDE the plugin (those described above) are also displayed in the creator - it must be possible to see which are inside and which are outside
  
• you might want to provide a facility to save "work in progress" under the user's account - I think that's not necessary as long as the language files' history is available
  

• introduce and enforce the plugin name (= filename without extension) as a secondary unique key - it's the only information available from the plugins in GetSimple to identify a plugin. I don't think we have duplicate names yet - the earlier you do it the better
  
• new API functionality: plugin by name - same results as in current plugin by id - allows GetSimple to display current versions of plugins and suggest updates
  
• new API functionality: list available languages by plugin name - if available with completeness percentages
  
• new nice-to-have API functionality: search for plugins, returns list of results instead of a single result
  

• Now the success and error messages are not only generated but also shown ;-)
  
• Thus undo is also available.
  
• German translation
  

mvlcek Wrote:As you will see in the error message (hopefully), you need to create a writeable directory backups/translate, where backups for undo are stored.

Regarding the speed, I'm not 100% happy with the autogrow textareas, but it's the best way to display editable texts with varying lengths. Using Chrome 10 instead of Firefox 3.6 cut the time for displaying GetSimple's translations from 20 to 5 seconds (whole request) for me, on my faster computer it doesn't matter so much - both a few seconds.

mvlcek Wrote:But even if it's 20 seconds, it's not too much in comparison to how long you will spend on the page before submitting and how much time you save by not downloading the language file, opening it in a program, saving it and uploading it again.

hameau Wrote:Translate v0.2.2: No change with the GS core language file. I click 'Save' and I just go back to the previous screen. No messages, no GSDEBUG errors. Same result with Chrome. It does work with the language file from i18n Base.

polyfragmented Wrote:Nice pitch indeed. To avoid thread jacking, why not create a new thread in the plugins section for feedback?