Board Thread:General Discussion/@comment-43596541-20200126015656/@comment-43596541-20200126040854

@Andrewds1021 Not quite ...   The SPECIAL:Export replaced the Cut &amp; Paste of the Source Code I used to to and is much simpler for other use :)  I Simply rename the .XML to .TXT file and I'm in business ...   I am already able to create "wiki-text" using EXCEL @CONCAT  and CHR(10), "|","!-" to create  tables lines and cell content ... And with "" &amp; "" I can "replace" a  Page Name with a Clickable Page Link (in-wiki in my case)  ...

For instance if a Wiki had 200 Pages for  200 Episodes of a TV show but only an index on Season/Episode  but has  sections with TITLE,  CHARACTERS,  AIR-DATE  and would like to build a table from the 200 Pages ... With 10 Season of 20  Episodes with Each Season a Category ... I could use SPECIAL:Export for the 10 CATEGORIES, genererate a source file with the wiki-text of the 200 pages  create an Excel table that list all the fields needed  and then  create a a new Tab that contains all the need  "source-code"  in the format

!- !2019-12-01
 * S01
 * E01
 * Sample Title of an Epispode
 * Jill, John,  Jack
 * - ... all the 199 remaining Episode lines​​​​​​

Then copying it and pasting in text file makes it possible to copy/paste in the Source Editor in between the {| wiki-table   |} markers ... or in any other layout for that matter ...  It could be the other around  and  include  a line parsed Character List into an Episode page based on a provided table  where "JIll", "John " and "Jack" are created as "SUBHEADING1"  (i.e.

Jack
Easy for only a few names, but if the table contained a list of 5 - 10 names (hopefully cooma or semi-colon delimited)    the cut and paste  beats the hell of retyping and avoids any typo (assuming the origianl table/list was already proof-read)

There is probably zillions of ways to prodiuce and parse the "raw" wiki-text ... I'd like to share my method and read others ... Thanks for the link,  I did bookmark the  delmited  (CSV) script for future refrerence as it is much more complete than what I did but then I don't need any scripting tool or HTML parser  with my "poor-man" method which essential does the "inner lines loop" of the CSV Script.

I also gather from your answer that the discussion is probably appropraite for the Getting Technical Forum ... I wasn't sure ...