Proofreading README.

General information

-------------------

This section provides general information about the initial structure of provided codebase.  

This section provides general information about the initial structure of the provided codebase.  

### Project structure

### Project Structure

The structure of the project provided as a base for your implementation should meet the following criteria.

1. Package ```cz.muni.fi.pb162.hw01``` contains classes and interfaces provided as a part of the assignment.

1) The information in **javadoc has precedence over everything**

2) **Interfaces** must be implemented

3) **Interfaces** must keep predefined methods

4) Otherwise, you can modify the code (unless used by tests) as you see fit

5) When in doubt **ASK**

4) Otherwise, you can modify the code (unless tests are affected) as you see fit

5) When in doubt, **ASK**

**Note:**  

*While modification of interface is not strictly prohibited, you don't want to end with [god object](https://en.wikipedia.org/wiki/God_object) implementations.    

On the other hand, you want to adhere to [single responsibility principle](https://en.wikipedia.org/wiki/Single-responsibility_principle).  

A rule of thumb should be not to modify interfaces, unless required by the assignment. Consider extending the interface as an alternative.*

*While a modification of the interface is not strictly prohibited, you don't want to end with [god object](https://en.wikipedia.org/wiki/God_object) implementations.    

On the other hand, you want to adhere to the [single responsibility principle](https://en.wikipedia.org/wiki/Single-responsibility_principle).  

A rule of thumb should be not to modify interfaces unless required by the assignment. Consider extending the interface as an alternative.*

### Names in this document

### Names in This Document

Unless fully classified name is provided, all class names are relative to the package ```cz.muni.fi.pb162.hw01``` or ```cz.muni.fi.pb162.hw01.impl``` for classes implemented as a part of your solution.

### Compiling the project

The project can be compiled and packaged in the same way you already know

### Compiling the Project

The project can be compiled and packaged in the same way you already know.

```bash

$ mvn clean install

```

The only difference is that unlike with seminar project, this time the checks for missing documentation and style violation will produce an error.

You can temporarily disable this behavior when running this command.

The only difference is that unlike the seminar project, the checks for missing documentation and a style violation will produce an error this time.

You can disable this behavior temporarily when running this command.

```bash

$ mvn clean install -Dcheckstyle.skip

You can consult your seminar teacher to help you set the ```checkstyle.skip``` property in your IDE (or just google it).

### Submitting the Assignment

Follow instructions of your tutor because the procedure to submit your solution may differ based on your seminar group. However, there are two ways of submittion in general:

Follow instructions of your tutor because the procedure to submit your solution may differ based on your seminar group. However, there are two ways of submission in general:

* Fork the project, develop your code in a development branch, and finally ask for the merge.

* Submit ```target/homework01-2023-1.0-SNAPSHOT-sources.jar``` to the homework vault.

### Supported Symbols

In contract to physical segment display, printing to console possesses certain limitation regarding character placement.

However, in case of seven segment display, we can make the symbol quite distinguishable while keeping a reasonable size.

In contrast to a physical segment display, printing to the console possesses certain limitations regarding the character placement.

However, in case of the seven segment display we can make the symbol quite distinguishable while keeping a reasonable size.

When printed to stdout, a seven segment display (capable of displaying a single symbol) is formatted as follows

Bellow is a template of symbols supported by our application. 

```

# Digits:  0123456789 (the empty space at the begining represents a clear display) 

# Digits:  0123456789 (the empty space at the begining represents an empty display) 

    _     _  _     _     _  _  _ 

   | |  | _| _||_||_ |_   ||_||_|

   |_|  ||_  _|  | _||_|  ||_|  |

```

The *error symbol* is displayed in case of an unsupported character. See the javadoc for more information.  

**Note: Make sure that the formatting of you output is exactly the same as described**

**Note: Make sure that the formatting of your output is exactly the same as described**

### Implementation Notes

To achieve proper decomposition, you are required to finish the implementation of

|--------------|-------|-----------|---------|--------------------------------------------------|-------------------|

| Size         | -s    | --size    | 1       | Total size of the display (number of characters) | \>= 1             |

Application should recognize the following positional arguments

The Application should recognize the following positional arguments

| #   | Description            |

|-----|------------------------|

| 1   | String to be displayed |

### Running the application

### Running the Application

The build descriptor is configured to produce a single runnable jar file located at `target/application.jar`. The application can be run using the following command

```

| |  | _| _||_||_ |_   ||_||_|| ||_

|_|  ||_  _|  | _||_|  ||_|  ||_||_

# Display content with unsupported symbol

# Display content with the unsupported symbol

java -jar application.jar -s 3 1a2                                                                          20:55:46

    _  _

  ||_  _|