While I start to change my valuelists that hold i18n values I stumble into the fact that it is not possible to add an i18n value into the editor before closing the valuelist editor and the valuelist chooser. That means a lot of extra mousemovements before everything is properly edited. Not to mention all possible errors…
I would really like to see a solution for this…
that is currently just the way it works.. We can’t do much about it. i think.
Or we must be able to open the i18n dialog on top of the valuelist dialog.. I will look into that.
Marcel,
I found that it’s just as easy to add my own “editor” form for my i18n entries. I just make a list form, then “show” it in a tabpanel on my DEV form.
I can create multiple language strings in seconds by duplicating records, etc. directly.
Just an idea…
Bob Cusick
Hai Bob,
That’s fun, I started making my own ‘i18n’ editor yesterday. Have experiences some strange happenings but further the idea is ok. Will release it as a project soon here.
But, that won’t do more than help some clicks. In other words it does not completely solve the issue.
Beats doing internationalization in ANY other tool - even with the extra clicks…
Bob
hmm, how about an automated built in translation engine with artificial intelligence?
I am working on i18n for 2-3 weeks now with my application… Boy what a job
Anybody out there reading this. If you haven’t seen my tip on i18n on Servoy Magazine go read it…
But ok, Bob you are right about i18n and Servoy
AI would be nice… maybe in 3.x…
I agree - getting your solution i18n compatible is a bunch of work. Even when creating a new solution, you have to think about all the strings all the time.
I’ve found that solutions 2-4 are MUCH easier, since you will have 80% of the strings you need already.
TIP: Make sure your naming conventions are EASY to remember!
Bob
Thanks for making the i18n window non-modal. already saved a lot of time!!!