![\"\"](\"\/wordpress\/wp-content\/uploads\/2023\/06\/forms1-555x1024.png\")
<\/a><\/p>\n
\n \nread forms\n\nName: FORMS DOCUMENTATION - VERSION 1.\nType: DOCUMENT\nDate: 25-SEP-1985 17:33 by CHIP\nSize: 33205\n\nThis is the latest version of the FORMS Documentation. It includes all\nenhancements in the forms program up to September 24, 1985.\n\nKeywords: SPECIFIC AREAS, FORMS, TEXTRIEVE\n\nACTION> dis\n\n\n\n\n\n\n\n\n\nFORMS SPECIFICATIONS\n\n\nVERSION 1.0\n\n\n\n\nI. The GVC Forms system is designed to be a powerful and\nfriendly method of gathering and distributing highly\nspecific information from users. Users are presented with\nexplanatory text and questions that are completely under the\ncontrol of the forms designer. At any time during the\nprocess of filling out a form, a user can press CTRLZ to\nenter REVIEW mode. At the REVIEW> prompt, a user can scan\nhis previous answers, change any of them, leave the form, or\nreturn to where he was when he typed CTRLZ.\n\nII. Some uses of the forms program are:\n\ni. Catalogs and Online Ordering\n\nii. Surveys\n\niii. Request Forms\n\niv. User Feedback\n\nv. Convention, Seminar or Warrenty Registration\n\nvi. Database Data Entry\n\nvii. Password-Protected Text\n\n\nIII. The forms program is integrated with GVC's proprietary\nTextrieve system. Forms are placed in Textrieve in the same\nmanner that text is enterred, using the POST command (i.e.\nPOST <return> or POST filename <return>). The Textrieve\narea must be configured by GVC personnel to accept forms.\nHowever, any text enterred into a forms-configured area that\ndoes not have .FORM at the start of the first line will be\ntreated as regular text.\n\nIV. After a form is designed and loaded into the system, the\ndesigner should immediately run the form. If there are any\nerrors detected by the system, they will be displayed during\nthe operation of the form, and the form will abort before\nallowing users to enter information. The forms designer \f\nPage 2\n\n\nshould look at the error notices, find where the mistakes\nwere made and fix them, continuing this process until the\nform is operating properly.\n\nV. Completed forms are processed via electronic mail. They are\nsent immediately to the username(s) specified by the forms\ndesigner. If the forms designer so designates, the user can\nhave a copy of the complete form sent to his own mailbox.\n\nVI. A form can contain a maximum of 255 questions and comments.\nA question can have a maximum of 255 characters (with no\ncarriage returns). A text response can have a maximum of\n255 characters (with no carriage returns).\n\nVII. The following dot commands (dot commands have a period \".\"\nin the first column followed by a command word) can be used\nin a form. Commands in parentheses are the acceptable\nabbreviations for the command. As with GVC's text\nformatting commands, users will not SEE these commands.\n\nCharacter capitalization (upper vs lower) does not matter to\nthe commands. However, case does affect how the text is\npresented to the users.\n\ni. .FORM\n\nThis command must be at the top of the form. If it is\nnot there, the form will not be processed, and the user\nwill be presented with the commands rather than with the\nform itself.\n\nOn the line following the .FORM should be placed the\nForm Name. The Form Name will be the \"Subj:\" when the\nform is sent via electronic mail. Form Name can not be\non more than one line. It has a maximum length of 255\ncharacters. For example:\n\n.FORM\nWidget Order Form <= Form Name\n\nWhen a form is created or altered, it should be tested.\nTo properly test a form, place a \"\/\" i front of the Form\nName. Then run the form. The \"\/\" will put the program\ninto Test Mode and tell the program to run a more\ncomplete diagnistic on the form. When you are satisfied\nthat the form is working properly, remove the \"\/\". The\nforms program will operate in Test Mode, but it will be\nsomewhat slower for the user.\n\nii. .QUESTION (.QU)\n\nThis command is followed by a question name (15\ncharacters max, with no \">\", \"<\" or \"\/\") and by the\nactual text of the question (255 characters max). For\nexample: \f\nPage 3\n\n\n.QUESTION\nLast name <= Question Name\nWhat is your last name? <= Question\n\nIf the question is omitted, the question name is used to\nprompt the user (followed by a colon). For example:\n\n.QUESTION\nLast name\n\nIn this example, the user would be prompted:\n\nLAST NAME :\n\nIf you wish to restrict the size of the response to\nsomething less than 255 characters, you may put the\ncharacter limit in <>'s after the .QUESTION (with no\nspaces in between). The limit must be between 1 and 255\ninclusive. For example:\n\n.QU<25>\nLAST NAME\nWhat is your last name?\n\nThe above example will ask the user to reenter his\nresponse if the initial response is longer than 25\ncharacters. It will inform him of the 25 character\nlimit.\n\niii. .YESNO (.YN)\n\nThis command is followed by a question name and question\nthat is to be answered with a yes or a no (y or n). If\nthe question is omitted, the question name (followed by\na colon) is used as the prompt. For Example:\n\n.YESNO\nSame address\nDo you want it shipped to your billing address? (y\/n)\n\niv. .MCHOICE (.MC) and .CHOICE (.CH)\n\nThis command is followed by a question name and a\nquestion requiring the user to select between several\nchoices (20 choices maximum, 255 characters max per\nchoice). As with the text of a question, the case of\nthe letters in the choices determines the case that is\ndisplayed to the user. The choices are placed after the\ndot command .CHOICE (.CH). For example:\n\n.MCHOICE\nEducation\nHow much education have you had?\n.CHOICE\nNone \f\nPage 4\n\n\n.CHOICE\nGrammar school\n.CHOICE\nHigh scholl\n.CHOICE\nCollege\n.CHOICE\nGraduate School\n\nA special case of the .MCHOICE command occurs when the\nlast choice is OTHER.\n\n.MCHOICE\nSex\nWhat is your sex?\n.CHOICE\nMale\n.CHOICE\nFemale\n.CHOICE\nOther\n\nIn the above example, if the user selects OTHER, he will\nthen be prompted:\n\nPlease explain :\n\nHis explanation will be used as the response (rather\nthan the word OTHER).\n\nv. .COMMENT (.CO) and .END COMMENT (.ECO)\n\nThis command is follow by text that is to be displayed\nat any part of the form during the filling-out process.\nThe command .END COMMENT (.ECO) will signify end of the\ntext. Text placed in here will be treated the same as\nother outputed text (i.e. text-formatting dot commands\nwill be recognized). There is no limit to the amount of\ntext that can be put within a comment. For example:\n\n.COMMENT\n.center ELEPHANT ORDER FORM\n.blank\n.indent 4\nThis form allows you to place your order for African \nand American elephants. Elephants will be shipped \nfreight-collect (Collars, leashes and riding baskets \nnot included in price).\n.END COMMENT\n\nvi. .INTEGER (.INT)\n\nThis command forces the user to respond with an integer.\nFor example: \f\nPage 5\n\n\n.INTEGER\nSTORIES TALL\nHow many floors are there in your office building?\n\nIf the user responds with something other than an\ninteger, he is asked to enter a whole number or integer.\n\nvii. .DOLLAR (.DOL)\n\nDOLLAR is similar to .INTEGER except that it requires\nthe user to respond with an answer that is in dollars.\nIt will accept any number with between 0 and 10 decimal\nplaces and convert it to 2 decimal places. If the user\ntypes in a non-numeric character, he is asked to reenter\nhis answer in dollars.\n\nviii. .DATE\n\nDATE requires the user to enter a date in the form\nmm\/dd\/yy, m\/d\/yy, mm-dd-yy, mm\/dd\/y, etc. It will also\naccept responses such as Next Tuesday and Yesterday. It\nproduces an 11 character string in the form dd\/mmm\/yyyy.\nFor example:\n\n.DATE\ndeparture\nWhen would you like to leave?\n\nIn the above example, if the user responds with 4-5-88,\nthe system will convert it to 04-JAN-1988. If the user\nenters less than complete information, the system\nassumes the nearest date in the future that contains the\ninformation passed. To have the system assume a date in\nthe past, use the <past> qualifier. For example:\n\n.DATE<past>\nbirth date\nWhen were you born?\n\n\nix. .PASSWORD (.PW)\n\nPASSWORD is used to test a users knowledge of a certain\nword or phrase. .PASSWORD must be followed by a \/\/YES\nor \/\/NO (see below). If the password is entered\ncorrectly, the system is set at YES for the condition\nstatement.\n\nWhen the user types in the password, it is not displayed\non his terminal. At a later point in the form, if a\nuser does a scan, he will not be shown the password (as\nhe would be shown any other response made on the form).\n\nThe actual password is the Question Name. It is\nrestricted to 15 characters maximum. A Question MUST \f\nPage 6\n\n\nfollowing the Question Name. Remember, the Question\nName is not public information in this instance. For\nexample:\n\n.PW \/\/NO \/\/QUIT\nAAARDVARK\nWhat's the secret animal code name?\n\nIn the above example, if the user does not type in\nAARDVARK, he is taken out of the form (see \/\/YES, \/\/NO\nand \/\/QUIT described later in this text).\n\nx. .TEXT (.TX)\n\nThe .TEXT command allows the user to enter more than one\nline of text in response to a question (up to a maximum\nof 20 lines). He concludes his text input with a CTRLZ\nto enter, or a CTRLC to reenter. He is given a prompt\nsimilar to the mail prompt which explains these commands\nto him.\n\nAfter the text has been enterred, the user can go back\nand replace a single line or the whole response.\n\nxi. .DISPOSE (.DS)\n\nThis command is used to specify what is to be done with\nthe completed form. It must be used and should appear\nonly once. Username(s) are placed on the line following\nthis command to specify mail addresses where the form is\nto be mailed. \/\/KEEP can be used to signify that the\nuser can have a copy of the form sent to his mailbox.\nTwo examples:\n\n.DISPOSE\nWES JOHNWG\n\n.DISPOSE\nMARCJ \/\/KEEP\n\nIn the first example, the form will be electronically\nmailed to usernames WES and JOHNWG.\n\nIn the second example, the form will be electronically\nmailed to username MARCJ. The user will be asked\nwhether he wishes to have the form sent to his mailbox.\nIf he responds affirmatively, then the program will mail\nhim a copy of the completed form.\n\nIf the form is to be placed in a file the \/\/FILE= option\nis included. For example:\n\n.DISPOSE\n\/\/FILE=GARBAGE.DAT \f\nPage 7\n\n\nIn the above example, the form would be copied to file\nGARBAGE.DAT.\n\nxii. .OUTPUT (.OP) and .END OUTPUT (.EOP)\n\nIf a specific format for the form that is actually sent\nis required, then the .OUTPUT command must be used. If\n.OUTPUT is ommitted, then the output will be in\nstructured with each question name followed by the\nuser's response in the order that the questions were\nasked.\n\nAll text that is placed on lines following the .OUTPUT\ncommand is treated as text that is meant to be included\nin the output form, with the following exceptions:\n\ni. \/\/question name\/\/\n\nAnywhere this appears, the system substitutes the\nactual response to the question. For example:\n\nMy favorite color is \/\/favorite color\/\/.\n\nThe above would put the response to question about\nfavorite color into the sentence. If the user said\nRED, then in the outputed form, the sentence would\nread:\n\nMy favorite color is RED.\n\nThe question name only has to be long enough to make\nit unique. If FAVORITE COLOR is the only question\nname beginning with an F, then \/\/F\/\/ would also work\n(although it might be confusing to the manager who\nis debugging or editting the form).\n\nA special case of the \/\/question name\/\/ is used if\nthe users username is to be inserted into the form.\nThen the format is:\n\n\/\/*USERNAME\/\/\n\nA second special case of the \/\/question name\/\/ is\nused if the current date is to be inserted into the\nform. The date will be inserted as dd-mmm-yyyy (11\ncharacters). The format is:\n\n\/\/*DATE\/\/\n\nA third special case of the \/\/question name\/\/ is\nused if the current time is to be inserted into the\nform. The time will be inserted as hh-mm (5\ncharacters) where hours are on a 24 scale and the\ntime is system time (Eastern time). The format is: \f\nPage 8\n\n\n\/\/*TIME\/\/\n\nIf a fixed amount of characters is to be set aside\nfor the response, such as in a list, then the format\nis \/\/question name<width,jusification>\/\/, where\nWIDTH is the number of characters allocated for the\nform and JUSTIFICATION is how the response should be\npositioned within the allocated space (L for left\njustified, R for right justified and C for center\njustified). A few examples:\n\n\/\/price<10,R>\/\/\n\n\/\/title<80,C>\/\/\n\n\/\/last name<30,L>\/\/\n\nIn the first example, the response to the question\nabout price is right justified within the 10\ncharacters allotted to the response. In the second\nexample, the response to the question about title is\ncentered on the form. In the third example, the\nresponse to the question about last name is left\njustified within the allotted 30 characters. If the\nlength of the response exceeds the allotted width,\nthen all spaces within the allotted area are filled\nwith asterisks (\"*\"s).\n\nii. .PRINTIF and .END PRINTIF\n\nThe .PRINTIF command is used to decide whether a\ngroup of lines should be included in the output. If\nthe condition following the .PRINTIF command is\nsatisfied, then all text following it will be\nincluded in the output. If the condition is not\nsatisfied, then all text following the .PRINTIF\ncommand but preceding an .END PRINTIF command will\nnot be included (in either case, the .PRINTIF and\n.END PRINTIF themselves will not be included in the\noutput).\n\nThe .PRINTIF command has two formats.\n\n1. .PRINTIF<question name>\n\nIn this format, if the question was responded to\nwith anything other than a blank, then the\nsubsequent lines will be included in the output.\n\n2. .PRINTIF<question name response>\n\nIn this format, if the response to the question\nis the same as the response in the statement,\nthen the condition is true and the subsequent\nlines are included in the response. The \f\nPage 9\n\n\nRESPONSE can be abbreviated to as few characters\nas are likely to make it unique.\n\nA few examples of .PRINTIF\n\n.PRINTIF<ship address>\n\n.PRINTIF<continue y>\n\nIn the first example, if the question about SHIP\nADDRESS was answered with a non-blank response, then\nsubsequent lines would be included. In the second\nexample, if the question about CONTINUEing was\nresponed to with a YES, the the subsequent lines\nwould be included.\n\n\n\nVIII. The following additional \/\/ statements can be used in a\nform. \/\/ statements are meant for the experienced forms\ndesigner. Friendly and complete forms can be created\nwithout using these statements.\n\ni. \/\/GOTO statement\n\nA \/\/GOTO statement tells the program to move to\nsomeplace other than the next question when it is done\nwith the current question or comment. If the GOTO moves\nback to a question that has already been answered, then\nall responses after that question are erased so that\nthey can be reentered.\n\n\/\/GOTO is followed by the question name of the question\nthat the program should move to. The entire question\nname is not needed, only enough of it to make the\nselection unique. If the question name in the \/\/GOTO\nstatement does not exist, the GOTO is ignored.\n\n\/\/GOTO can follow .QUESTION, .YESNO, .MC, .TEXT,\n.INTEGER, .DOLLAR and .COMMENT. It can not be placed\nanywhere else. If no GOTO statement is used, the system\nselects the next question or comment in the file. An\nexample of \/\/GOTO:\n\n.qu \/\/goto address\nNAME\nWhat is your name\n\nii. \/\/Condition Statements\n\n\/\/Condition statements combine an IF statement with a\n\/\/GOTO. If the condition in the \/\/Condition is\nsatisfied, then the program will move on the the\nquestion indicated after thw \/\/Condition. \/\/Condition\nstatements are only used with .YESNO, .PASSWORD and \f\nPage 10\n\n\n.MCHOICE. Condition statements are followed by the\nQuestion Name of the question that is to be asked if the\ncondition is satisfied. No \/\/goto is needed (or can be\nused) with a condition statement.\n\nOnly one \/\/Condition or \/\/GOTO can be used after a given\n.YESNO, .PASSWORD or .MCHOICE.\n\nThere are two possible condition statements which can\nfollow .YESNO or .PASSWORD:\n\n1. \/\/YES\n\nThis is true if the question is responded to with a\nYES. For example:\n\n.yn \/\/yes last name\ngive name\nWould you like to leave your name? (y\/n)\n\nIn the above example, if the user responds with a Y,\nthe system moves to the LAST NAME question. If he\nresponds with N, it goes to the next question or\ncomment in the file.\n\n2. \/\/NO\n\nThis is true if the question is responded to with a\nNO (or the password was entered correctly).\n\nMultiple choice Condition Statements use the format:\n\/\/{choice number}, where choice number is the choice\nthat must be selected to satisfy the condition. For\nexample:\n\n.mchoice \/\/2 type of dog\nanimal type\nWhat kind of pet do you have?\n.choice\nCat\n.choice\nDog\n.choice\nFish\n.choice\nWombat\n.choice\nOther\n\nIn the above example, if the user selects DOG, the\nprogram will go to the TYPE OF DOG question. Dog is the\nsecond choice and the \/\/condition is \/\/2. If he selects\nsomething other than Dog, the program will move to the\nnext question or comment in the file. \f\nPage 11\n\n\niii. \/\/QUIT\n\n\/\/quit is a special word that can be placed after a\n\/\/GOTO or \/\/Condition. It tells the system that instead\nof going to another question, leave the program straight\naway. No confirming prompt will be given to the user.\n\/\/QUIT is designed to be used primarily when the form\ncontains extensive text at the top (using .COMMENT).\nWhen the user has read all of this explanatory text (but\nhas not yet invested any time and effort into entering\ninformation), he is asked if he wants to fill out the\nform. If he resonds with an N, the system reverts back\nto Textrieve. For example:\n\n.co\nThe Caveman convention is being held this year on \nDecember 19th at the Bedrock Convention Center in \nFlint, Michigan. It will run through the 21st. \nThe registraction fee is $45 per attendee. This\ncan be paid by MasterCard, Visa or check. Lodging\nis available in abundance. \n.eco\n.yn \/\/no \/\/quit\nregister\nWould you like to register for the convention? (y\/n)\n\niv. \/\/COMPLETE\n\n\/\/Complete is similar to \/\/Quit. It follows \/\/Goto and\n\/\/Condition statements. However, instead of aborting\nthe program, \/\/Complete tells the system that the user\nhas finished filling it out and is ready to send it.\nThe system calls its own \/\/Complete when it reaches the\nlast question or comment in the form. An example of\n\/\/Complete:\n\n.yn \/\/no \/\/complete\nmore to tell\nWould you like to tell us more? (y\/n)\n\n\n\f\nPage 12\n\n\n\nSAMPLE 1\n(Simple example, no \/\/s)\n\n\n\n\n.FORM\nWOMBAT Order Form\n.comment\nThis is a form to order Wombats. If you do not wish to \norder any of our special Wombats, please press CTRL_C to\nquit.\n.eco\n.qu\nname\nWhat is your name?\n.qu(25)\nstreet address\nWhat is your street address?\n.qu(25)\ncity\nWhat city do you live in?\n.qu(2)\nstate\nWhat state do you live in?\n.integer\nzip code\nWhat is your zip code?\n.qu\nphone number\nWhat is your phone number?\n.comment\nNow that you have given us your background\ninformation, please select the Wombat of your\ndreams.\n.end comment\n.mc\ncolor\nWhat color Wombat do you want?\n.ch\nBlue\n.ch\nRed\n.ch\nGreen\n.ch\nBrown\n.yn\nother colors ok\nWill you accept another color? (y\/n)\n.mc\nsize\nWhat size Wombat do you prefer?\n.ch \f\nPage 13\n\n\nSmall\n.ch\nMedium\n.ch\nLarge\n.ch\nObese\n.yn\nother sizes ok\nWill you accept another size? (y\/n)\n.co\nThank you for ordering from Western Wombat Distributors.\nYour Wombat will arrive by Pony Express in the next few\nweeks.\n.eco\n.dispose\nwombatman \f\nPage 14\n\n\n\nSAMPLE 2\n(Complicated Example)\n(Contains \/\/GOTO, \/\/Conditions, \/\/QUIT, \/\/COMPLETE)\n\n\n\n\n.form\nCarpentry Estimate Application\n.co\nMy name is Martha, and I'm an online carpenter.\nI can fix broken roofs, put up beautiful aluminum\nsiding, renovate kitchens, and build additions to\nyour home.\n.b\nI give FREE estimates.\n.eco\n.yn \/\/no \/\/quit\nwant estimate?\nWould you like me to come over and make an estimate?\n.mc \/\/2 build what\ntype of work\nWhat do you need done?\n.ch\nFix Something\n.ch\nBuild Something\n.text\nfix what\nWhat do you need fixed?\n.qu\nwhen broke\nWhen did it break?\n.date<past> \/\/goto estimate\nfix when\nWhen do you need it fixed?\n.mc \/\/1 addition\nbuild what\nWhat do you need built?\n.ch\nAddition to the house\n.ch\nNew Kitchen\n.ch\nRemodeled Bathroom\n.ch\nSomething Else\n.co \/\/goto estimate\nWe can do that easily.\n.eco\n.integer\naddition size\nApproximately how many square feet is the addition?\n.integer \f\nPage 15\n\n\nfloors\nHow many floors will it have?\n.mc \/\/3 another\nestimate time\nWhen can I come over to give you a free estimate.\n.ch\nMonday\n.ch\nTuesday\n.ch\nWednesday\n.ch\nThursday\n.ch\nFriday\n.comment \/\/goto \/\/complete\nThat will be fine. I will see you then.\n.eco\n.yn \/\/yes estimate\nAnother day OK\nWednesday's a bad day for me. Could we try another day?\n.comment\nThat's too bad. I will try an make it over on Wednesday.\n.eco\n.dispose\nthecarpenter \/\/keep\n.output\nThis is an appointment to visit \/\/*USERNAME\/\/ and give an\n.printif<fix what>\nestimate to fix \/\/fix what\/\/.\n.printif<build what>\nestimate to build \/\/build what\/\/.\n.end printif\nI will come over on \/\/estimate t\/\/.\n.end output\n\n\n\nACTION> \n<\/pre>\n
\nFORMS<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"A summary for those that haven’t been keeping up with this series: I found a number of 5.25″ disks at a thrift store a number of years ago. I finally got around to acquiring a 5.25″ disk drive and extracting the contents a while back. Since then I have been posting the contents here. Based on the contents, at least some of these disks were apparently once owned by someone named Connie who used to run the \u201cClose Encounters\u201d Special Interest Group (SIG) on Delphi in the mid 1980s. A specific definition of this SIG was found in a document on one of the disks: “This SIG, known as ‘Close Encounters’, is a forum for the discussion of relationships that develop via computer services like the Source, CompuServe, and Delphi. Our primary emphasis is on the sexual aspects of those relationships.” This service was text based and was accessed via whatever terminal program you used on your computer to dial in to Delphi\u2019s servers. Many of these disks have forum messages, e-mails and chat session logs. All of this is pre-internet stuff and I don\u2019t know if there are any archives in existence today of what was on Delphi in […]<\/p>\n","protected":false},"author":1,"featured_media":31262,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[2913,2042,2362,2914],"class_list":["post-31260","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-computer-arcana","tag-delphi","tag-digital-archaeology","tag-retrocomputing","tag-telecommunications"],"_links":{"self":[{"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/31260","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/comments?post=31260"}],"version-history":[{"count":1,"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/31260\/revisions"}],"predecessor-version":[{"id":31264,"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/posts\/31260\/revisions\/31264"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/media\/31262"}],"wp:attachment":[{"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/media?parent=31260"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/categories?post=31260"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.megalextoria.com\/wordpress\/index.php\/wp-json\/wp\/v2\/tags?post=31260"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![](\"https:\/\/cdn.steemitimages.com\/DQmbt7ArCQ39zUHcTQWf91uS9PeKLwNrxPWh22myzD2DSXE\/2018-07-2009.36.39_1.jpg\")
<\/center><\/p>\n![\"\"](\"\/wordpress\/wp-content\/uploads\/2021\/12\/disk_013_1.png\")
<\/p>\n![\"\"](\"\/wordpress\/wp-content\/uploads\/2021\/12\/disk_013_2.png\")
<\/p>\n