diff --git a/README.md b/README.md
index ed468205c098b4bcb6cdec6f2106fbc8a936fba4..d90e195590d534342a8c8ccb8695aa33479f0043 100644
--- a/README.md
+++ b/README.md
@@ -1,92 +1,63 @@
 # TamilTransciption
 
+##Preparation
 
+Before even running any program following Software are required:
+[] Java (Java 17 used in this project, get [here] (https://www.oracle.com/java/technologies/javase/jdk17-archive-downloads.html))
+[] JavaFX (20.0.1 Windows any(64) SDK used in this project, get [here](https://gluonhq.com/products/javafx/))
 
-## Getting started
+After installing Java 17 and downloading JavaFx, put both close to each other in the Java Folder
+(here C:\Program Files (x86)\Java\javafx-sdk-20.0.1 was used)
 
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+## Quick Executing with Jar
 
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+For running only the Jar file open the use the bat 
+run.bat File or get your command prompt (cmd) to the folder with the TamilTranscription.jar. For executing it type following command:
 
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://git.noc.ruhr-uni-bochum.de/mahaddkm/tamiltransciption.git
-git branch -M main
-git push -uf origin main
 ```
+example (depending on JavaFx Folder):
+java -jar --module-path "C:\Program Files\Java\javafx-sdk-20.0.1\lib" --add-modules javafx.controls,javafx.fxml TamilTranscription.jar
 
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://git.noc.ruhr-uni-bochum.de/mahaddkm/tamiltransciption/-/settings/integrations)
-
-## Collaborate with your team
+general:
+java -jar --module-path $PATH JAVAFX LIB$ --add-modules javafx.controls,javafx.fxml TamilTranscription.jar
 
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+```
 
-***
+## Compiling and Executing
 
-# Editing this README
+JavaFx project needs to compile main.java and tamilController.java before running anything.
+For compiling following command with the neccessary JavaFx Modules is used in cmd:
+```
+example (depending on JavaFx Folder):
+javac --module-path "C:\Program Files\Java\javafx-sdk-20.0.1\lib" --add-modules javafx.controls,javafx.fxml main.java tamilController.java
 
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
+general:
+javac --module-path $PATH JAVAFX LIB$ --add-modules javafx.controls,javafx.fxml main.java tamilController.java
+```
+For running it you can use the next command:
+```
+example (depending on JavaFx Folder):
+java --module-path "C:\Program Files\Java\javafx-sdk-20.0.1\lib" --add-modules javafx.controls,javafx.fxml main
 
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+general:
+java --module-path $PATH JAVAFX LIB$ --add-modules javafx.controls,javafx.fxml main
 
-## Name
-Choose a self-explaining name for your project.
+```
 
 ## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+This program allows the user to transcript from tamil script into philological transcript (ISO 15919) and from the philological transcript to tamil script. Moreover, it also allows to copy past any tamil script/ philological transcript to transcript it into the the other script. In case the user do not have any keyboard layout, the button has been added to make this program also useable for with only mouse.
 
 ## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+Use it to transcript tamil <-> philogical transcript (ISO 15919) via direct input with buttons or via copy paste any text passages.
 
 ## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+No active support, but in any case reach out to the owner of this project.
 
 ## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
+This Project has been made by Dilsan Mahadeva. AB big acknowledgement for Dr. Sven Wortmann (Cologne University) for introducing the philolog transcript (ISO 15919) for the tamil script 
 
 ## License
-For open source projects, say how it is licensed.
+MIT License, free for all, explore and develop it further
 
 ## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+Currently Done, might have some bugs, but you know there are no bugs only features ;)