Hi,

I don't really know what to do. Both using many files and one single
file have their advantages and disadvantages. One file can get a big
mess, but many files are hard to find stuff.

Sometimes I wish the scopes were all backwards: Then you would be able
to group translations together based upon their functionality instead
of their usage.

I don't use any of these projects yet, but I am going to use tolk in
the near future, so I can't say anything about that yet.

- iain

On Tue, Jun 8, 2010 at 06:45, andresgutgon <[email protected]> wrote:
>
>
> On Jun 7, 3:02 pm, Andrés gutiérrez <[email protected]> wrote:
>> Hello I've been watching these two projects [1] and [2]. Both look good. But
>> I see it is not possible to have a complex structure inside the locale
>> folder.
>>
>> The two projects  caught the .yml and displayed in a web interface for ease
>> translate each string.
>>
>> But with a Base of folders a bit complex. Example:
>>
>> locale
>>   |-es.yml
>>   |-models
>>       |-users
>>           |-es.yml
>>       |-articles
>>           |-es.yml
>>   |-views
>>       |-users
>>       |--articles
>>   formtastic
>>      |-es.yml
>>
>> It is possible to translate this. Or should I put all the strings in a
>> single file?
>>
>> [1]http://github.com/newsdesk/translate
>> [2]http://github.com/dhh/tolk
>
> Please, Does anyone else separated into folders or am I the only one?
>
> --
> You received this message because you are subscribed to the Google Groups 
> "rails-i18n" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/rails-i18n?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"rails-i18n" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rails-i18n?hl=en.

Reply via email to