http://wiki.list.org/display/DEV/Summer+of+Code
Gentlebeings,
I have updated the summer of code page above to indicate my current progress and record the synthesis of the opinions I have received so far.
Thank you for the excellent feedback you've provided so far; don't be shy about continuing, either here or on the wiki.
~ethan fremen
emf wrote:
http://wiki.list.org/display/DEV/Summer+of+Code
Gentlebeings,
I have updated the summer of code page above to indicate my current progress and record the synthesis of the opinions I have received so far.
Thank you for the excellent feedback you've provided so far; don't be shy about continuing, either here or on the wiki.
~ethan fremen
Hi Ethan,
Since you are working on Web Interface, I have an important suggestion/request on the charset we use.
I think we should use 'UTF-8' exclusively on WUI. We can eliminate many problems we have on current web pages including the pipermail archive, while current language-charset database should be retained for email message usage.
Cheers,
-- Tokio Kikuchi, tkikuchi@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
Tokio Kikuchi wrote:
Hi Ethan,
Since you are working on Web Interface, I have an important suggestion/request on the charset we use.
We will use UTF-8 exclusively on WUI, with the caveat that I will be sniffing any charset information contained in emails and attempt displaying (individual) emails with the charset referenced.
Pretty please, I need to set up a copy of someone's translation toolchain; can someone using OS X or Linux as their work operating system work with me to get an *exact* replica of their toolset?
I want to make translating as painless as possible but from what I can tell so far gettext is very low level and I suspect that people use more than just it to translate... am I right?
~ethan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jun 29, 2006, at 12:58 PM, emf wrote:
We will use UTF-8 exclusively on WUI, with the caveat that I will be sniffing any charset information contained in emails and attempt displaying (individual) emails with the charset referenced.
I'm sure this was ages ago, but IIRC, UTF-8 was discussed at some
point and the decision was made not to use it because it's support
was pretty spotty in the browsers of the time. I'm sure this has
improved vastly now and UTF-8 makes the most sense.
Pretty please, I need to set up a copy of someone's translation toolchain; can someone using OS X or Linux as their work operating system work with me to get an *exact* replica of their toolset?
I want to make translating as painless as possible but from what I can tell so far gettext is very low level and I suspect that people use
more than just it to translate... am I right?
Have you gotten any love on this issue Ethan? To be honest, I'm not
a translator (heck, I barely speak English despite years of at least
2 other languages in high school and college :). When I was working
out the basic i18n support I implemented a stupid rot13 translation
using nothing more sophisticated than XEmacs and the gettext tools.
Please, can any i18n'ers help Ethan out with a better tool set?
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin)
iQCVAwUBRKk7GHEjvBPtnXfVAQJ8SgP/dlOdTK59NTZrDrcWlSnD2iD29+rRazhx vO7xPUDpL68U2mhKhDVW7i3CN6afrvlR6yZ2+r6fxOJwQsEL1mjED4VCUQku6gQJ dCri7KNGGwFiLpWFSoq9OE35+p8IJg6mW1+rXokjBzuq76+uz9rI2leWhAcS1g/Y vMUeGZLhUCw= =LGTW -----END PGP SIGNATURE-----
Barry Warsaw wrote:
I'm sure this was ages ago, but IIRC, UTF-8 was discussed at some point and the decision was made not to use it because it's support was pretty spotty in the browsers of the time. I'm sure this has improved vastly now and UTF-8 makes the most sense.
Yeah, that sounds like an early-90's conversation; UTF-8 is the one charset no browser messes up these days, as far as I know.
Pretty please, I need to set up a copy of someone's translation toolchain; can someone using OS X or Linux as their work operating system work with me to get an *exact* replica of their toolset?
Have you gotten any love on this issue Ethan?
No love as of this writing. I'm continuing to kick the i18n ball down the field until I can do a translation myself (into gods-knows-what - I'll probably have to rely on my lovely and talented wife to give Russian/Italian a stab.)
When I was working out the basic i18n support I implemented a stupid rot13 translation using nothing more sophisticated than XEmacs and the gettext tools.
Yeah, I can do that if need be. I just assumed there was Something More out there; if not it might be worth the effort to put together a minimalist translation interface.
~ethan
Ethan replied to Barry:
Pretty please, I need to set up a copy of someone's translation toolchain; can someone using OS X or Linux as their work operating system work with me to get an *exact* replica of their toolset?
Have you gotten any love on this issue Ethan?
No love as of this writing. I'm continuing to kick the i18n ball down the field until I can do a translation myself (into gods-knows-what - I'll probably have to rely on my lovely and talented wife to give Russian/Italian a stab.)
I've got MacOS X 10.4, but I don't do any sort of translation, and I don't have the slightest clue as to how you'd go about trying to do that. I don't speak any foreign language well enough to even think about making any attempt to do so.
That said, I'd be glad to provide whatever help I can.
-- Brad Knowles, <brad@stop.mail-abuse.org>
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755LOPSA member since December 2005. See <http://www.lopsa.org/>.
participants (4)
-
Barry Warsaw -
Brad Knowles -
emf -
Tokio Kikuchi