[HtmlLang$('HelpPages')]

[HtmlLang$('Home')] | [HtmlLang$('Intro')] | [HtmlLang$('variables')] | [HtmlLang$('internal')]

[HtmlLang$('internal')]

   Internally, SiteBuilder generate some variables authomatically. Some of this variables are updated for each brach, while other remain across brachs. The internal variables are accessible across the _$() function. They are this:

_$(.envron;.docroot).   _$(0;5)          framePage relative path (without heading /)
_$(.envron;.butlabels).     _$(0;9)          macrolist                                        _$(.envvar;0).          _$(9;0)          Page Full Treebranch
_$(.envvar;1).          _$(9;1)          Page Full Languaged Treebranch                         _$(.envvar;.lang_id).     _$(9;2)          Language id (_en,_es,...)
_$(.envvar;3).          _$(9;3)          Page label (Last bracnch unlanguaged)
_$(.envvar;4).          _$(9;4)          Comma separated Full Treebranch (unlang)
_$(.envvar;5).          _$(9;5)          Second Param from label (altframe / link / mode
_$(.envvar;6).          _$(9;6)          Doc Base name (branch replaced / by _

_$(.usrstr;0).                    Content label from historic.txt (SiteBuilderPro)
_$(.usrstr;1).                    FullRoot
_$(.usrstr;2).                    The tree htmlpath. See cgilinks in pruebas.dsoft.es
_$(.usrstr;3).                    The tree dečmdent htmlpage without lang nor extension
_$(.usrstr;4).                    Exp.to exec.at page init (From SiteBuilder/sdk/page_init.txt)

_$(.envvar;0). The current full path to actual branch relative to document root. For example 'software\webdeveloper\sitebuilder'.

_$(.envvar;1). The language translated of previous, but comma separated. Continuing with previous example, it could be: 'software,Web developing,sitebuilder'.

_$(.envvar;2). The current language extension. This is an underline plus the current two letters language identifier. Maybe somethis like '_en' , '_it' or '_fr'.

_$(.envvar;3). The current branch. In our sample, 'siteBuilder'

_$(.envvar;4). Its the same that _$(.envvar;0) but the separator is a comma. This could be usefull when it is needed to access to some of the branch components in cross platform developents.

   If you need to access to some of the components of this variables, use the FN$PARM function. So, accessing to the current translated brach will be:

FN$PARM(_$(.envvar;1);FN#PARM(_$(.envvar;1))) wich in our example will return the translated phrase for 'sitebuilder'.