caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sylvain Le Gall <sylvain@le-gall.net>
To: yoriyuki.y@gmail.com, caml-list@inria.fr
Subject: Re: [ANN] Camomile 0.7.3
Date: Fri, 14 May 2010 15:55:31 +0200	[thread overview]
Message-ID: <20100514135531.GA4870@centi.ks368928.kimsufi.com> (raw)
In-Reply-To: <AANLkTikdB6l4Qby-rmvsF_nSwowYmg9OZEbXNljjsYf4@mail.gmail.com>

In gmane.comp.lang.caml.inria, you wrote:
> 2010/5/14 Dmitry Bely <dmitry.bely@gmail.com>
>
>> How "heavy-weight" is Camomile? I was a bit scared with the size of
>> its distribution. Currently I use under Windows the following my own
>> simple Unicode-support module (implemented via
>> WideCharToMultiByte/MultiByteToWideChar Win32 API functions). Maybe
>> it's time to switch to Camomile?
>>
>>
> The size of the package is due to mapping tables of character encoding and
> localization data.  they occupy several mega bytes on the disk but it is
> nothing by today's standard.  If you still care, you can delete any .mar
> files in charmaps, locales, mappings directory.  (Deleting source files in
> these directory is not recommended, since it could cause a failure of
> compilation.)  If you delete such files, related encoding and locales do not
> function, but other functionality is intact.
>

I have just compared libcamomile-ocaml-data and locales-all packages.
The two packages contain almost the same thing:
http://packages.debian.org/sid/libcamomile-ocaml-data
http://packages.debian.org/sid/locales-all

The size is almost the same (3MB vs 5MB) but the uncompressed size is
not at all the same:
- camomile: 24MB
- locales-all (2 steps uncompression): 99MB

At least it means that camomile data is a reasonable size for this kind
of data on Linux system. On Windows system, I think these figures are
almost the same but data are part of the base windows installation.

Now, a question/suggestion/feature: is it possible to store .mar file
as .mar.gz? This would help to reduce occupation by a factor of 5...

Regards
Sylvain Le Gall


  reply	other threads:[~2010-05-14 13:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTim0Q-Kd_1cyI_0VT91V_wkCBz2TvmLRDyevQq2H@mail.gmail.com>
2010-05-12 12:13 ` Yoriyuki Yamagata
2010-05-12 13:57   ` [Caml-list] " Romain Beauxis
2010-05-12 14:24   ` Romain Beauxis
2010-05-12 22:02   ` Sylvain Le Gall
2010-05-13  1:19     ` [Caml-list] " Yoriyuki Yamagata
2010-05-13  9:52       ` Sylvain Le Gall
2010-05-14  2:51         ` [Caml-list] " Yoriyuki Yamagata
2010-05-14  6:48           ` Paolo Donadeo
2010-05-14  8:35             ` Dmitry Bely
2010-05-14 13:30               ` Yoriyuki Yamagata
2010-05-14 13:55                 ` Sylvain Le Gall [this message]
2010-05-15 12:15                   ` Yoriyuki Yamagata
2010-05-14  8:14           ` Sylvain Le Gall
2010-05-14 11:35             ` [Caml-list] " Yoriyuki Yamagata
2010-05-14 19:04           ` Florent Monnier
2010-05-18 11:04       ` Yoriyuki Yamagata
2010-05-13 22:17   ` [Caml-list] " forum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100514135531.GA4870@centi.ks368928.kimsufi.com \
    --to=sylvain@le-gall.net \
    --cc=caml-list@inria.fr \
    --cc=yoriyuki.y@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).