[wp-polyglots] Bunch of new strings

[Pandem]

I tried your solution, wrote \u00f1 instead of ñ  but I'm 
probably missing something because msgfmt returns "invalid control 
sequence" when I try to generate the .mo file.

The reason why we are using html entities is that some people keep 
choosing ISO-8859-1 for their blogs, or else chose it from the beginning 
and now find it difficult to change to UTF-8. I know we could make two 
different files, one for each encoding, but it would be confusing for 
some of them and more difficult to mantain. If I could find a solution 
for this issue it would be great.

Thanks for your time and help,
Maira.

Nikolay Bachiyski escribió:
> Pandem wrote:
>> Nikolay,
>>
>> I have the last POT with the new strings, but on revision 3264 
>> akismet.php keeps being untagged. Where did you extract the POT from? 
>> Is it going to be actualized soon?
>
> The pot is always emerged from the latest wordpress sources and it is 
> usually actualized after every change in localizable strings. Well, 
> sometimes there are delays, but I hope these are rare cases :)
>
> Actually the pot was updated some minutes ago.
>
> Akismet still has some strings uninternationalized and I have proposed 
> a patch. It may take time for Matt to review it, accept it and maybe 
> apply it.
>
>>
>> I am having some trouble with html entities, they aren't parsed 
>> inside javascripts. An example of this is the on-the-fly categories 
>> Add button, in Spanish we need a ñ here. We can look for a 
>> synonim here but it would be better to find a global solution, 
>> because it may not be so easy for other languages and other strings.
>
> First of all - why don't you just insert the literal character ñ? All 
> the wordpress pages are utf8-encoded.
>
> If you for some reasons do not want to enter literal symbols in 
> javascript string you could do the following:
>
> 0. find the unicode value of your character. If you know it as an html 
> entity you could use [0] or [1]. If you just know the charcater, you 
> caould use [2]. Or use whatever way you want to grasp the hexadecimal 
> unicode value of your symbol.
>
> 1. in the javascript string enter \u{unicode-value} where 
> {unicode-value} is the value yielded in point 0. For example the 
> ndtilde is expressed as \u00d1.
>
> Have a nice Saturday,
> Nikolay
>
>
> [0] http://www.w3.org/TR/html4/sgml/entities.html
> [1] http://www.w3.org/TR/xhtml1/#h-A2
> [2] http://www.unicode.org/charts/
>
>>
>> Cheers,
>> Maira
>>
>> Nikolay Bachiyski escribió:
>>
>>> Now, the importers' and the plugins' strings are in the pot file 
>>> (about 160 new ones). If you haven't checked it for updates these 
>>> days, here it is:
>>>
>>> http://svn.automattic.com/wordpress-i18n/pot/trunk/wordpress.pot
>>>
>>> It would be really nice if somebody checks those files (plugins, 
>>> importers) for missing strings and report these to the Trac.
>>>
>>> Have a jolly day,
>>> Nikolay
>
>
> _______________________________________________
> wp-polyglots mailing list
> wp-polyglots at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-polyglots
>