cotonti.com : Transifex translation service https://www.cotonti.com Последние сообщения в теме Cotonti en Tue, 14 Oct 2025 01:53:59 -0000 Twiebie Thanks, RoyalC!

]]>
чт, 13 июн 2013 21:39:49 -0000
RoyalC hello i can help with french translation if need.

Invite send on transifex.

 

]]>
чт, 13 июн 2013 21:32:33 -0000
schulle4u Yeah, I finally got it to work I think. :) Updated the german translation on transifex.

]]>
вт, 19 мар 2013 09:42:10 -0000
Trustmaster The only solution that I see at this point is to create another Transifex project explicitly for formal translations (or informal, if we decide to use formal in the main one).

Added 1 hours later:

Uploaded some existing locales to Transifex.

]]>
сб, 16 мар 2013 07:50:43 -0000
pieter In dutch you use different words for "you" if it is formal or informal. And also other words as well.

]]>
сб, 16 мар 2013 06:07:42 -0000
Macik What does you mean under formal/informal support? And what part of Cotonti uses it?

By the way, developers should have ability to translate their plugins same way as well. Had any ideas?

]]>
сб, 16 мар 2013 00:18:29 -0000
Trustmaster This question is still open. And it seems like they have already declined support for formal/informal in the past. Maybe a clone repo/project could work, i'm not sure.

]]>
чт, 14 мар 2013 19:38:59 -0000
Twiebie I'll update the Dutch language with the tool you wrote in Python.

One question though; what about formal and informal versions of a language?

]]>
чт, 14 мар 2013 18:31:12 -0000
Trustmaster 2 points:

  • Changes in the code a backwards-compatible. All existing plugins work as before.
  • There's a convertor tool for the main package langfiles which automates 95% of changes that need to be made in langfiles.

Added 3 days later:

Now our language files are compatible with Transifex and I've written a small guide how to translate them in bulk here.

Added 3 minutes later:

FYI: all the existing and old language files should work just fine without any problems. And nobody is forced to use Transifex, you can continue maintaining language files in your preferred way without much changes.

]]>
пн, 11 мар 2013 18:45:52 -0000
esclkm пн, 11 мар 2013 17:58:00 -0000 Trustmaster Weblate looks intriguing with its Git support and being open source, so that we could probably add missing features ourselves. But both services need testing first.

Added 3 hours later:

I would prefer a relatively popular service though and in the current situation we can't run a self-hosted solution like Weblate, so it is out.

Added 7 hours later:

Crowdin has the same problems as Transifex and adds some more: files for multiple locales cannot be imported correctly, so it's out.

I've solved most of the problems with Transifex, there's one thing left: associative arrays in $L['cfg_somename_params'].

]]>
пн, 11 мар 2013 06:46:06 -0000
Kort Sacrificing MD arrays is kinda scary. However, these are mostly used in the rarely changed plugin configuration  strings and (which is abit more painful) $Ls variables. The reward, however, looks very promising and surely outweighs the price, imho.

]]>
пн, 11 мар 2013 06:38:21 -0000
Macik The idea to use common collaborate translation service sounds great. 

But a certain limitations of Transifex make me doubt in it. And it would be good to hear mentions of a Cotonti community.

Is there any other services we can use?

I checked these services:

http://weblate.org - completelly free, works with git repository. Supported formats: http://docs.weblate.org/en/latest/formats.html  (uses translate-toolkit).
(should be checked for multidimensional arrays, and array-strings)

http://crowdin.net/ - Free for open source. (Unlimited projects, unlimited strings and collaborators). Supports many formats, zip uploading (with directory structure).
Had convinient interface, can parse multidimensional arrays. Seems do not understand string arrays (but I'm not shure). 

 

 

]]>
вс, 10 мар 2013 20:22:56 -0000
Twiebie Sounds good to me.

]]>
сб, 09 мар 2013 12:59:32 -0000
Trustmaster It's not just the difficulty of creation of our own translation system, but rather following some standards and attracting more translators who are used to those standards.

Transifex is not a replacement for our traditional file-based translations, it's just a tool to keep them in sync and collaborate. Have a look at their console client tool, I use it to upload/download there our translation files which I edit with my editor offline.

Right, if we decide to use Transifex, I'll make a tool to convert existing langfiles. The changes will affect no more than 10% of all lang strings.

]]>
сб, 09 мар 2013 10:27:42 -0000
schulle4u How difficoult or time-consuming would it be to create our own translation system? We already have the i18n plugin for pages, so couldn't this be adapted somehow? An own solution would make as indipendent from 3rd party services and their boundaries.

I personally feel more comfortable doing my translations offline using my favorite editor. Can I still work offline and then upload new and changed files to transifex or does this service only support online editing? Furthermore, as a user of screen-reading software I first have to check the service accessibility. Looks good so far, I'm registered there as schulle4u already. If there's an quick and easy way to modyfy my current files to the new array format, I have no problem with transifex migration.

Steffen

]]>
сб, 09 мар 2013 10:08:58 -0000
Trustmaster I think Transifex is one of the most popular and developed so far. Personally I'm okay with making arrays flat in langfiles, this is easier for newcomers to understand too. But before we move to Transifex, I would like to hear from other translators too.

]]>
сб, 09 мар 2013 07:51:46 -0000
Twiebie Hmm, okay.

It does probably make it easier to maintain the locales in the long run if we use a system like Transifex.
Maybe there are some other alternatives around?

]]>
пт, 08 мар 2013 19:57:23 -0000
Trustmaster Got this reply today:

Hello there,

Transifex hosts a lot of PHP projects but, having first searched for similar requests, there is no demand for supporting multi-dimensional arrays. Our roadmap is a really loaded one and we occasionally override the next thing to do if and only if there is a massive request for a particular feature. That said, it's not something that will go live soon but it may be implemented in the future, if a critical mass of requests is reached.

Thank you for your understanding,
Themis

--
The Transifex Team

So we needa change our code and langfiles if we want to use Transifex.

]]>
пт, 08 мар 2013 16:08:43 -0000
Twiebie ср, 06 мар 2013 14:13:01 -0000 Trustmaster I've sent them a request for multidimensional arrays support. In the worst case we can make all our arrays flat but this is not very good for us for several reasons.

]]>
ср, 06 мар 2013 12:13:26 -0000
Twiebie Hmm, looks like it has potential but problems like not supporting formal/informal locales is a bit of an issue for languages like Dutch.

Signed up with the nickname 'Twiebie', so let me know if you can add me to the project.

Added 14 hours later:

Just tried it out a bit and it's looks pretty good.

I really like the way you can easily see which locale is behind and which strings are not up to date. It makes it much easier to keep track of multiple locales.

If we can find solutions to the current problems that Trustmaster detected it looks like a good way forward.

]]>
вт, 05 мар 2013 21:19:48 -0000
Trustmaster As you might know, localization process is not (yet) automated in Cotonti and it is uncomfortable for some translators. I was recently pointed at Transifex service and also came across it several times and it seems that it's getting more and more popular. The advantages of this service for us are:

  • Online editing of translations only, no need to mess with code.
  • Monitoring of translation progress.
  • Online collaboration.
  • Translation memory database.
  • Automatic suggestions.
  • Tracking changes between releases.

So I decided to give it a try and created a project for us: https://www.transifex.com/projects/p/cotonti/

Our language files are organized in a more advanced way than in most systems, our language files are modular and spread around many folders, so I had to write some helper tools first: https://github.com/trustmaster/cotlang. I used those tools to separate language files from the source tree and to create Transifex configuration.

I have uploaded RU and NL locales so far and found several problems while uploading our language files. Although most language strings were handled fine, here are the problems that I have detected:

  • Formal/informal locales are not supported.
  • Syntax with array() like $L['cfg_adminemail'] = array('Administrator\'s email', 'Required'); is not supported.
  • Syntax with multiple indexes like $themelang['usersprofile']['Emailpassword'] = 'Your current password'; is not supported.
  • Syntax with strings consisting of multiple lines (ending with end-of-line) is not supported.

So if we want our translations to be handled by Transifex, then we need to make changes to our current PHP code and language strings to make all language entries flat.

I have added Russian and Dutch translations so far, let me know if you want to give it a try and send me your username on Transifex and I'll add you to the appropriate team.

Please let me know what you think about the service and the idea of migration to it to handle translations and translation updates.

]]>
вт, 05 мар 2013 20:00:10 -0000