[haiku-development] Re: Locale kit, add ons and header files
- From: Oliver Tappe <zooey@xxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 15 Jun 2009 11:07:35 +0200
On 2009-06-15 at 09:52:55 [+0200], PulkoMandy <pulkomandy@xxxxxxxxx> wrote:
> 2009/6/15 Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:
> > Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote:
> >> Since that API is private to the locale kit, such a header would be
> >> expected
> >> to live in headers/private/locale.
> >
> > If this is API that is always needed in catalog add-ons, why not make
> > it part of the (private) catalog add-on API, and make the built-in add-
> > on behave the same?
> >
> > Bye,
> > Axel.
>
> This API is used only in the locale kit development tools, in the
> process of collecting the strings to translate in a C++ file, then
> linking them into a binary catalog. We only want to allow that on
> Haiku's catalog type, in order to avoid people creating catalogs in
> other formats (such as Zeta's one) with our tools.
> The plaintext catalog add on is used only in this case, to allow
> editing the catalog as a simple textfile before linking it. There is
> no other use for it in other add ons.
I'm afraid this is not quite right: the CatWalker class (which is the API we
are talking about) is for instance used by the dumpcatalog utility.
Additionally, should we ever write some kind of editor application for
catalogs, it would require to use the CatWalker, too.
cheers,
Oliver
Other related posts:
