CB

The list of parsed files is listed in the cb->build->tools->languageparser->readme.md file and is the following:

awk -v title='Community Builder (TM) Default (English) language file Frontend' \
-v copyright='(C) 2004-2014 www.joomlapolis.com / Lightning MultiCom SA - and its licensors, all rights reserved' \
-v outfilename='components/com_comprofiler/plugin/language/default_language/language.php' \
-v comment='WARNING:\n* Do not make changes to this file as it will be over-written when you upgrade CB.\n* To localize you need to create your own CB language plugin and make changes there.' \
-f build/tools/languageparser/languageparser.awk \
libraries/CBLib/CB/Application/*.php \
libraries/CBLib/CB/Database/*.php \
libraries/CBLib/CB/Legacy/*.php \
libraries/CBLib/CB/Database/Table/*.php \
libraries/CBLib/CBLib/*/*.php \
libraries/CBLib/CBLib/*/*/*.php \
libraries/CBLib/CBLib/*/*/*/*.php \
libraries/CBLib/Imagine/*/*.php \
libraries/CBLib/Imagine/*/*/*.php \
administrator/components/com_comprofiler/comprofiler.class.php \
administrator/components/com_comprofiler/plugin.class.php \
administrator/components/com_comprofiler/plugin.foundation.php \
components/com_comprofiler/*.php \
components/com_comprofiler/*.xml \
components/com_comprofiler/plugin/user/*/*.php \
components/com_comprofiler/plugin/user/*/*.xml \
components/com_comprofiler/plugin/user/*/*/*.php \
components/com_comprofiler/plugin/user/*/*/*/*.php \
components/com_comprofiler/plugin/templates/*/*.php \
components/com_comprofiler/views/*/*.xml \
components/com_comprofiler/views/*/*/*.php \
modules/mod_cblogin/*.php \
modules/mod_cblogin/*/*.php \
modules/mod_comprofilermoderator/*.php \
modules/mod_comprofilermoderator/*/*.php \
modules/mod_comprofileronline/*.php \
modules/mod_comprofileronline/*/*.php \
plugins/communitybuilder/*.php \
plugins/communitybuilder/*.xml \
build/tools/languageparser/languageparser.awk \
administrator/components/com_comprofiler/*.xml \
administrator/components/com_comprofiler/xmlcb/*.xml \
administrator/components/com_comprofiler/xmlcb/*/*.xml \
components/com_comprofiler/plugin/user/*/*/*.xml \
components/com_comprofiler/plugin/user/*/*/*/*.xml

tell me what changes I need to make and I will make them.

Don't think it's an use issue, more like a bug in the language parser awk tool: the xml file reported above is after the delimiter, and its description attributes should not go into language.php file.

If I move the parsing of

components/com_comprofiler/plugin/user/*/*.xml

then there are lots of changes that happen.

see attached diffs.

Wondering how many such FE strings are defined that way (comparded to the large number of long sentences that get translated and loaded in front-end unneededly).

If not too many, would make sense to define them in a way that they are taken by FE part too.

Either by defining them elsewehere (too), or by adding a translation-specific attribute for the language-parser to pick them up for front-end ?

I assume a plugins XML file can be given the same backend default attribute treatment. The parsing would need to be tested and see if the output is expected.

Agree, Kyle.

Reassigning to Nick so that language parser can be updated and plugins re-parsed..