Re: [LogiLogi-list] gettext, proposal and user interfase

> Well, I've been doing this _("") adding stuff... :)
> 
> I hope there are not too many un-closed parenthesis or errors as I
> couldn't test it on my local copy.

I have ran rake gettext:harvest and I got no errors there...

What error / problem are you encountering ? Note that you should have
the gettext-package installed on ubuntu, and the gettext-gem.

(we can discuss it over IRC, but at least Manta should be able to run
with gettext and xapian on debian-based distro's and preferably on
other distro's and the mac too (using FF for the front-end))

> I used as standard not to include characters like ":" after "Step 1"
> for example, so if we decide to remove/add it we just have to take it
> out in the code and not in every language.

Ok, that's good :)

> Also I found some possible problems with a pluralize() function...
> will this function pluralize words like "time" to "times"? how will it
> do it in spanish? :)

It will not work in spanish, so the pluralize will have to be replaced
by a (@somethings > 1 ? _('somethings') : _('something'))

> I also had some situations like the following that need variables so
> can be moved as have different position in different languages:
> <%= _("Remove the %{peer_group_ll_link} peergroup")
> %{:peer_group_ll_link => peer_group_ll_link(@peer_group)} %>

These are good. In the translation the translator will have to move
the %{peer_group_ll_link} around in the translation-string.

> I also did this one: <%= _("You can %{link_to}") %{:link_to =>
> (link_to _('get an account here'), signup_sessions_url)} %>
> 
> I hope they are oK .. :P In case it's wrong, the pattern to search for
> all of them would be grep -Hnr "%{:" *

I hot no errors so I assume it works correctly...

> I also modified the order of the cancel buttons in the panels so it
> would not cancel when hitting return, but I'm not sure if changing the
> order of display will just do or need to set some tab-index in the
> modal box settings...

Hm, that does not seem a good idea to me as it is some kind of
unwritten standard (at least for Windows and Sun) that cancel-buttons 
are on the right...

So we can best set the tab-order (but the overboxes are going to go
anyway, so we will come back to this).

> About the proposal I still have to finish it up, but that will be
> tomorrow for sure, so hope we can comment on it tomorrow too.

Ok.

> Then we should take some days (not many) to define our next release
> elements on pages, and on that re-organize the user interface. In your
> last proposal Wybo, there has been a radical spin on the tags
> approach, which I mostly like and will be doing some additions, and
> will add some minimalism to it, and also to the entire interface. We
> need to take things out of the way, and we will do it and succeed on
> this... But, not tonight, maybe the day after tomorrow I'll start
> writing the specifications and after that start drawing... (by the
> way, svg UI drwaing is great way to explain right? :)

Agree.

In the meantime I will start making the needed changes in the back-
end. Will still take some time, but I am already booking progress.

Wybo

> Greetings all.
> 
> -- 
> Bruno