Browse Prior Art Database

In-line customization of customizable text

IP.com Disclosure Number: IPCOM000248745D
Publication Date: 2017-Jan-05
Document File: 7 page(s) / 144K

Publishing Venue

The IP.com Prior Art Database

Abstract

The article relates to the customization of text, where the reader can take influence on names and objects used throughout the text, by choosing concrete individual values. Thereby, the focus is on high usability for both the author of the customizable text and the reader of the customizable text.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 30% of the total text.

1

In-line customization of customizable text

The article relates to the customization of text, for example, the customization of a list of instructions. Thus, instead of having the reader confronted with a text containing symbolic names for values the writer could not know at writing time, like "$User1" or "<YourWorkingDir>", the reader can fill in concrete values reflecting the reader's environment and preferences. The idea proposed here simplifies the customization of documents, by using the following principle:

replaceable values are marked as such by the author, using an easy to  understand syntax for distinguishing replaceable tokens from regular text that is not supposed to be replaced; multiple identical replaceable tokens occurring throughout the text as considered  as the same instance, i.e. they are supposed to have the consistent same value throughout the text; the first occurrence of multiple identical replaceable tokens is rendered as text  entry field in-line in the text, allowing to change the value; all further occurrences (second, third, ... occurrence) of the same identical replaceable token are then rendered by the value currently entered in the as text entry field associated with the first occurrence of that replaceable token. distinct replaceable tokens do not influence or disturb each other, i.e. each first  occurrence of each distinct replaceable token is rendered as a distinct text entry field, allowing to change the value for that replaceable token.

The method works in 4 phases.

In the following, we show an example where concrete file names and file contents are used, and the syntax for distinguishing replaceable tokens from regular plain text is derived from variable name syntax in the Unix shell: a replaceable value is marked by a leading "$" symbol. As initial value of a replaceable value, the variable name without the leading "$" is used.

Phase 1 • Writer enters text into “mytext.txt” • Within the text, variables (i.e. replaceable tokens) do start with a “$” symbol.

Phase 2 • Text is pre-processed: “PreprocessData mytext.txt” • This generates the file “mytext.html”

Phase 3 • Text is post-processed: “RunInvention mytext.html” • During this step, the file “mytext.html” is further modified, thereby applying the following changes: • The first occurrence of each replaceable token is substituted by an editable text field; • As initial content of the editable text field, the variable name without the leading "$" symbol is used; • Further occurrences are substituted by that text field’s current content.

Phase 4

2

• Reader opens the html file “mytext.html”, using a browser that is able to render html files; • Reader provides preferred individual values for the replaceable tokens; • Reader works with the customized steps which reflect preferences and needs. Remarks:

phase 1 results in a plain text file with name “mytext.txt” ... this could be any  other file name and file format. phase 2 transforms the plain text file...