Op Do, 2011-01-13 om 17:37 + skryf Michael Bauer:
Is there a specific reason you mention them in this order? I usually try
to sort alphabetically or in order of frequency if it is obvious (for
example I usually list the capitals last). Where shall we position the
Tironian ampersand (when we decide which one to use :-)?
Errr, no, sorry, they just group that way phonologically in Gaelic,
alphabetically is fine.
As a total outsider it seems as if 204A could hold some advantages, but
in terms of the practicalities I can't cast a judgement. The ideal would
be if we gradually do things better, but it is hard to convince people
to improve font support for small languages. It is a common problem in
Africa for languages needing extra diacritics. Now if you could get some
government to mandate language support for imported products, it might
just get fixed quite quickly :-)
Ya that would be the thing. I did a test page and a straw poll on my
Facebook account. Last time I ran a test, virtually everyone had boxes
but this time, only about half reported probles and then usually linked
to Google Chrome; interestingly cross-OS support has improved. What
worries me is that mobile devices can't handle 204A at all by the looks
of it, whereas most seem to do the other one fine. So I think we'll go
with the second-best option for now; I'll monitor development and when I
can see a majority of platforms supporting 204A, we can make the change.
For now, it's more important that it displays, rather than encoding purity.
If it improved quickly, I guess it will get even better. Chrome has some
font issues; I'm guessing it will just disappear one of these days. The
releases of Pootle we make now, only affect people installing this in
future, targeting even later usage.
I just had a new idea: adding both. This way people can make the choice
per application they are translating. It seems that only mobile
applications might need the wrong character. What do you think about
that idea?
Similar things to what would help improving OpenOffice.org. We can use
a spell checker and autocorrect data exactly as they are used in
OpenOffice.org. I guess Kevin Scannel is the best person to talk to
with regards to spell checkers. I can help you build the necessary
autocorrect files - we have some scripts to take a spreadsheet of
incorrect - correct columns and generate the file needed for Virtaal
and OpenOffice.org.
There already is one:
http://extensions.services.openoffice.org/en/project/faclair-afb (though
the server seems to be down just now). Is there some way we can utilise
that?
Perfect. I can upload it soon. Just say - do you feel it is ready for
general use for localisers? The beta warning is very bold here :-)
Friedel
--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/versions-dependencies-different-distributions
-
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
