[asterisk-dev] [asterisk-commits] eliel: branch group/appdocsxml r150561 - in /team/group/appdocsxml: ./ includ...

Eliel Sardañons eliel at eliel.net
Sun Oct 19 08:22:07 CDT 2008

Thanks for the feedback,
                I think there is a big architectural issue here, and
don't know why it was thought in this way, maybe I am missing
something, but I don't get the way we are loading the documentation.
We are populating ->synopsis, ->syntax, ->description, etc (when we
don't find the original static doc) with the correct language chosen
by the user. Why we don't load the documentation every time it is
needed? so, only when a 'core show application/function ... ' CLI
command is issued (and only generate the output for that app), so it
is not needed to have all the documentation in memory. Also with this
change we will be able to change the default language at runtime like:
core show application Answer language es_ES

for Kevin's feedback: Yes, I will do that (Now I understand the aa_BB
:-) schema )

for Tzafrir: Yes thats the idea, but the problem right now is how we
are loading the documentation and for me is not the desired way. If I
start generating the documentation when asked for it, we will have
much power and less memory being used. I don't understand your
question about statically-linked asterisk, the modules are still there
and will continue to register applications/functions and is there
where we are loading the docs (for now).

Thanks for the feedback! and waiting for this change to be approved.

Eliel Sardanons

On 10/19/08, Tzafrir Cohen <tzafrir.cohen at xorcom.com> wrote:
> On Sun, Oct 19, 2008 at 01:36:35PM +0300, Kevin P. Fleming wrote:
>  > SVN commits to the Asterisk project wrote:
>  >
>  > > URL: http://svn.digium.com/view/asterisk?view=rev&rev=150561
>  > > Log:
>  > > Implements reading XML documentation from $(ASTDATADIR)/documentation & /documentation/thirdparty.
>  > > Every file named *-LANG.xml will be loaded from this directories where LANG is the actual language choice from asterisk.conf
>  > > option 'documentation_language'.
>  >
>  > This should also 'fallback' gracefully; if documentation_language is
>  > 'en_GB' for example, and a given documentation file is present in
>  > 'en_US' and 'en' forms but not 'en_GB', then the 'en' version should be
>  > loaded.
> Speaking of fallback, what happens when a translation is partial?
>  (Most translations are going to be partial. Keeping a translation
>  up-to-date is an awful lot of work)
>  I would suggest to have the default translation as a "C" language, or
>  somehow hardcode the "en_US" as the fallback default without any
>  need for configuration.
>  (gettext falls back to "C" when there's no translation).
>  Also, how does this affect a little statically-linked Asterisk?
>  --
>                Tzafrir Cohen
>  icq#16849755              jabber:tzafrir.cohen at xorcom.com
>  +972-50-7952406           mailto:tzafrir.cohen at xorcom.com
>  http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir
>  _______________________________________________
>  --Bandwidth and Colocation Provided by http://www.api-digital.com--
>  asterisk-dev mailing list
>  To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev

More information about the asterisk-dev mailing list