Victor Engmark wrote:
> > > - Maybe the language title attribute should say something like
> > > "Change language to X".
> The reason was simply that the @title is just the name of the language
> translated into the current locale, as in
> <a href="" href="http://www.gnuherds.org/Home.php?language=en_US">http://www.gnuherds.org/Home.php?language=en_US" title="Inglese"
> lang="en">English</a>
> I'm not sure how the current @title helps, that's all.
Now, I underdand!. Sorry. I have added {t}Change language to{/t} to
@title. You can get the result at:
http://www.gnuherds.org/templates/header.tpl
I have not used:
{t}Change language to English{/t}
{t}Change language to Spanish{/t}
{t}Change language to French{/t}
...
to avoid duplication for the translators. If we add some translation to
our site which has problems with this construction
{t}Change language to{/t} {t}lang{/t}
we could think about it again.
Very good, but now I'm wondering if that's a bit verbose. Maybe {t}Change language{/t} is enough? The language is explicit in @hreflang and the content of the element.
> By the way, if we internally use the country code with the language (as in
> "_US"), we should use the same in the language attributes. It's more precise
> and accurate, and if we get languages like fr_CA or en_UK later, it's a good
> idea to make sure the system is built that way bottom-up.
Modified too.
You can get the result at: http://www.gnuherds.org/templates/header.tpl
I have checked it with
validator.w3.org and with the textual browser
'w3m'. If you think it is right, you can get the .tpl file from the above
URL and commit it to CVS.
Oh, OK. I'll do it.
> > You could setup your own development environment [...]
> I'll see if I can - I already have a server running which I don't want to
> mess with. It would be great to have a central testing environment for this
> kind of thing, but I guess it's too much work for now.
For my development environment, I use the same
www.gnuherds.org host
(hosted now at my home :P ), with a no-public host-name "g-00.org" ,
which I have added to the /etc/hosts file:
192.168.0.2
g-00.org
I did not add it to the DNS server, to avoid Google and others search
engines index it, adding so that mess to the search results :P
Better than a central testing environment, each developer should have her
own environment. It is possible!. If you are unable to setup one at your
home, I can setup one for you at this same machine, following the below
steps:
1. I create an account for you
2. I add
g-your-name.org to /etc/hosts
3. I create the virtual domain of g-your-name.org at Apache
4. You add the below line to your /etc/hosts
217.127.236.41 g-your-name.org
If you agree, let me know the name for your account, "victor"?
and for your development domain, "
g-victor.org" ?