> May I ask you why this 50% border exist?
Purely arbitrary.
Experience shows that translation often reach the 50% limit quite
quickly. There is a limit to avoid languages to be validated because
only a few strings have been translated before the translator
vanishes.
We had such experiences in t
On Thu, Feb 23, 2006 at 02:30:42PM +0100, Christian Perrier wrote:
> > Is it possible for Khmer to be included in beta 3 if the translation
> > won't be complete of all levels?
>
> But in any case having an incomplete translation EVEN IN LEVEL 1 will
> NOT make us withdraw your translations.
>
>
> Thank Christian, I border you too much ;-)
> But just one quick question. :-)
> Is it possible for Khmer to be included in beta 3 if the translation
> won't be complete of all levels?
Of course.
We strongly advise translators to complete level 1 and level 2. Then
levels 3 to 5 should be complet
> No. The D-I team meeting scheduled for March 4th will decide the main
> goals for beta 3 (or RC1 I can't tell right now).
>
> Maybe will we fix ourselves a deadline at this meeting...or maybe it
> will wait for the next monthly meeting.
>
> In any case, I doubt that the version following beta2 is
> Please understand that I am not waiting but i want to schedule my work.
> If it is earlier, I will put priority 1 to this translation tasks.
>
> As beta2 will be released at the beginning of 1st March, Is there any
> beta3 deadline coming?
No. The D-I team meeting scheduled for March 4th will d
Hi Christian,
> > I might repeat the question that when will be the released date of beta2?
> > then i can figure out how much time left do i need to finish all
> > strings left to be ready
> > in beta3?
> Again, do not wait for it to complete the remaining work...
> you will anyway be ready for
> I hope I did not make too much confusion; the situation is a bit messy
> ATM but almost under control, so it souldn't take too long before we
> finally have a proper set of font for g-i.
As long as we get the ttf-freefont line spacing problem fixed,
yesbut I don't see the light, here...
Gargi_1.7.ttf)
pa_IN - Punjabi (Gumurkhi) (Saab.ttf)
Frans has uploaded a new iso [1] which reflects all the changes
necessary to make sure Indic scripts work properly (see [2] for
details): now that it's available please test that image rather than
the one I built recently.
AFAICT the languag
On 2/22/06, Guntupalli Karunakar <[EMAIL PROTECTED]> wrote:
> > [4] http://www.webalice.it/zinosat/shots/hindi_pre.jpg
> > [5] http://www.webalice.it/zinosat/shots/hindi_post.jpg
>
> [5] is rendering fine for Hindi.
Davide,
I wanted to updated the wiki with the new infor regarding Bengali and Hin
On Wed, 15 Feb 2006 22:07:07 +0100
Davide Viti <[EMAIL PROTECTED]> wrote:
> [4] http://www.webalice.it/zinosat/shots/hindi_pre.jpg
> [5] http://www.webalice.it/zinosat/shots/hindi_post.jpg
[5] is rendering fine for Hindi.
Karunakar
--
*
* Work: http://www.
Yes, bengali[3] is perfect. :)
On 2/22/06, salahuddin pasha <[EMAIL PROTECTED]> wrote:
> >bengali: compare [2] with [3]
>
> bengali[3] is perfect
>
> [3] http://www.webalice.it/zinosat/shots/bengali_post.jpg
>
>
> -salahuddin66
> www.bengalinux.org
> www.debian.org
>
> On Wed, 2006-02-15 at 22:07
Best,
> da
Yes, the graphical version of the installer uses pango. We can display
Indic scripts as well in that. It does mean that Khmer will not be
supported in the text version (that uses the newt frontend).
Cheers,
FJP
pgptjFjdqbbQx.pgp
Description: PGP signature
On 2/14/06, Christian Perrier <[EMAIL PROTECTED]> wrote:
> Quoting Davide Viti ([EMAIL PROTECTED]):
> > Hi Kakada,
> > I'm bringing the discussion to debian-boot, so that other people
> > can fill the missing gaps
> >
> > > Are there anything that I can contribute to make Khmer available for
> > D-
On Fri, Feb 17, 2006 at 01:52:06AM +0100, Frans Pop wrote:
> On Thursday 16 February 2006 20:08, Davide Viti wrote:
> > Here's what I got when stripping MuktiNarrow:
> ...
> > I got this with ttf-punjabi-fonts.tgz
> ...
> > and this with ttf-devanagari-fonts.tgz
>
> Suggest you file minor bug repo
On Thursday 16 February 2006 20:08, Davide Viti wrote:
> Here's what I got when stripping MuktiNarrow:
...
> I got this with ttf-punjabi-fonts.tgz
...
> and this with ttf-devanagari-fonts.tgz
Suggest you file minor bug reports against the packages these fonts come
from.
pgph50DSjuodD.pgp
Descri
lohit_* but they worry me. Maybe somebody
> wit hmore experience in font work could help? (freefont guys, maybe,
> since we might use at some point freefont for indic scripts, too?)
lohit_* were removed from my current font environment, so I haven't tried
to strip glyphs from any of those.
uys, maybe,
since we might use at some point freefont for indic scripts, too?)
--
Regards,
EddyP
=
"Imagination is more important than knowledge" A.Einstein
On 2/15/06, Davide Viti <[EMAIL PROTECTED]> wrote:
> I also noticed we include
> DejaVuSans-BoldOblique.ttf: 858 glyphs [129360 bytes]
> FreeSansBoldOblique.ttf: 790 glyphs [74588 bytes]
Please note that the coverage for regular/blod/italic fonts is for
many fonts different, so we must make su
> After discussion with Davide on IRC, I have uploaded a new version of
> ttf-freefont in unstable with the following changes:
great
> I'l try to take care of the package as well as possible but I'll
need
> help for that probably as I'm not that deeply competent with
> font-related issues. Someo
> in the specific case of freesans fonts, oblique is slanted, while italic
> is slanted and cursive; with other fonts, i noticed the oblique being
> more slanted than italic, while not cursive.
> We should evaluate how much space it's possible saving up if italic ttf
> files are removed, and als
Frans Pop wrote:
On Wednesday 15 February 2006 17:05, Attilio Fiandrotti wrote:
Oblique is something even more "pending" than italic and the GTK
What do you mean by pending exactly? Slanted maybe?
Hmm. Are you sure that the oblique fonts are not used instead of italic?
Anyway, I'd like to
Christian Perrier wrote:
Oblique is something even more "pending" than italic and the GTK
frontend never uses oblique formatting, so the *oblique*.ttf files can
also be deleted from font packages right now to save up some Kbytes.
So, you actually mean we could remove the below *Oblique files
Viti,
> bengali: compare [2] with [3]
[3] is way better than [2]. That's a great job!
Regards,
BG
--
Baishampayan Ghose
Free Software Foundation of India
b.ghose at gnu.org.in
> PS: Christian, I noticed that hi.po does not contain the "/Choose language"
> in the msgstr;
> now I understand why it is useful
:-)
I am sure I tracked these down. The error probably came back when a
translator committed a work file he was working on while I was
correcting this mistake.
--
On Wed, Feb 15, 2006 at 10:07:07PM +0100, Davide Viti wrote: I forgot
to mention that I also uploaded the xml map [1] of the glyphs included
in the ttf files included with the iso.
Columns are:
FreeSansBold.ttf
FreeSansOblique.ttf
FreeSans.ttf
ae_AlMohanad.ttf
ja.ttf
ko.ttf
zh.ttf
MuktiNarrow_11-0
On Wed, Feb 15, 2006 at 03:07:49PM +0100, Davide Viti wrote:
> This evening I'll put what follows into practice (i.e. new test iso
> image).
just done it: you can grab it from [1]
> 3) It's also possible to strip the following (random) glyphs not
> used in the g-i (there are certainly others):
26 matches
Mail list logo
