-
Notifications
You must be signed in to change notification settings - Fork 0
Idea #1
Comments
firehist wrote: @PascalPrecht It's going well! :) I can push on it, I just have no access to "settings" of this project (for example to edit the title + description GItHub). That's not really a problem. BTW, I think about an other application "extra angular-translate" to manage the translations dictionnary as well as now. I use angularJS in my job (http://teads.tv and http://manager.teads.tv) and we have to internationalize the app with an external translator team. What do you think about provide a rapid "translations manager" interface with persistent translation and manage delete/add/update throught grunt-angular-translate ? (I think about use deployd to store and angularJS to provide a rapid standalone manager per project). |
DWand wrote: @firehist, @PascalPrecht, yea, I want to build a GUI app to manage translations. I had even started, but was interrupted by work and academy. There are almost nothing done at the moment. |
knalli wrote: JSON based files, or what are you planning? |
firehist wrote: @DWand @PascalPrecht MMMh it looks like we'll rocks this together :) pretty cool. First, we can create a repository to start discussions about global goal of this application. First of all which name to handle this useful project ? BTW, two questions. @knalli I think it should be good to use deployd or similar tools to provide a persistent data and allow us to do more funny things faster. You should be able to import/export JSON files, PoEdit files. // Import "language JSON files"
// en_US.json
{
"MY_TRANSLATION_KEY": "MY_LANGUAGE_TRANSLATION",
"MY_TRANSLATION_KEY_01": "MY_LANGUAGE_TRANSLATION_01"
} // Import "keys JSON files"
// i18n_keys.json
{
"count": 2,
"updated": "Jan 21 2014 13:36:47 GMT+0100 (CET)",
"keys": ["MY_TRANSLATION_KEY", "MY_TRANSLATION_KEY_01"]
} etc. |
tspaeth wrote: 👍 In the last enterprise project, we had the translations as java properties - files. That transformation to JSON btw is quite easy. Was just some little sources on the Java side (I couldn't find an easy mapper for properties2json in the JS ecosystem...). |
DWand wrote: Hm... It seems that I thought in completely different direction :) I thought to use sqlite3 as a persistent translations holder to be able to use it independent from the language used in development. Also I thought to use node-webkit as an environment to be able to use web technologies in development, since all people here are familiar with HTML, CSS and Javascript. I have already used node-webkit once to develop app for my course work (but I used it to connect to SQL Server, not sqlite3). This solution seems to be completely cross-platform, but also has some disadvantages. UPD: |
knalli wrote: Regarding properties: Well, you have to support some encodings as well as the So, if we are speaking in a Java context.. a simple maven plugin or a servlet filter should be fine? |
DWand wrote: |
tspaeth wrote: @DWand Yes, the solution is different, but I was just thinking from the practical perspective out of a dozen of projects. Depending on who translates, when and who checks - a direct translation table mostly will not work as even translation texts might be quality assured by the business dept. before deployment. Therefore mostly the conversion to the app deployment has been a technical task, but the creation of the translation texts was a task of probably external people having limited or no access to the app infrastructure. Therefore something like the po-file-gettext-editors come out of that. Or even excel-tables to be parsed :-). Usually the KISS principle. But if someone manages a google calc style HTML/AJS editor for moving and editing in "translation tables" (whatever format they are and from whatever source they come from) - could be a killer app though :-) |
DanielaValero wrote: I am arriving late to the thread. After reading your comments, there are two points which are not clear to me,
I think that before speaking about the architecture, we should define clearly what we want or need. (which is not clear to me after reading the evolution of the conversation) What is the problem/necessity we want to solve? I think is how can we integrate into the angular-translate workflow those translators, who are used to working with poEdit or linguan, generating .po, .xml or .xls. Or maybe I misunderstood and you want to build another translator manager, which generates output for different projects written in different architectures. In such case, then ignore me :) |
tspaeth wrote: @DanielaValero exactly this questions I see also - great post though! |
tspaeth wrote: @DWand From the usability perspective, this includes a lot of clicking, typing, submitting for the translation of e.g. 50 variable texts - or not?! Technically, this looks good, but I would say the translation speed with this concept is slower compared e.g. to direct JSON or Java-properties style aka plain text ;) |
DWand wrote: @tspaeth, which is why I agree that "Programmer should never create UI" 😄 This is what I thought one or two month ago being alone. Now we can combine all our thoughts and create much more useful and better app. The only thing I'm sure now is that relational database is the best thing to keep translations because it ensures data consistency out of the box. And also it could be moved wherever people want. Moving DB to some server enables team to work with translation together at the same time from different locations. If I understood right @firehist mentioned something about it. |
firehist wrote: Hey @DWand, I'm sorry about the latency but we made a new version of our AdServer and I took a long time on it. So let's move on. Then, by reading posts, it should be great to provide a standalone version of this product and implement a user system to allow different people to use this application. This application can looks like your mockup and implement user/profile to describe a workflow for translation. This solution can be used by all kind of organization, from smallest to biggest. So, to summarize we can in a first version work around theses points:
Thereafter, we can think about:
BTW I have a question about angular-translate. Is it plan to implement dictionnary? I can start the work on this feature if it's not already started, I think that it is a must have in large app. Have a good day 😋 |
Just found this one as Yet another... |
I think this is a great idea, sadly it seems it died half way through... If you need some help I would gladly help. |
Hi, @TheCodeDestroyer. This idea is not dead. We just have not enough time to make it real now. angular-translate is a great thing and we love all things and ideas to make it better, but it's not how we make money. Personally I will be able to do something here in about 1 or 2 month. |
Cool! Thanks for the info... |
@Phoscur Not yet. At the moment, I do not see this will coming in the next time.. no staff, no plan, no detailed concept. |
This idea is a much-welcomed one! Hopefully it will be realized someday. |
+1 |
1 similar comment
+1 |
For anyone who is still interested in this, I stumbled upon this nifty page. |
An idea of the manager
The text was updated successfully, but these errors were encountered: