# CSS file editing instructions

Information in this document only applies to the css-legacy extlink which was the default css extlink only in freedomeditor version 0.2.6.7 and previous.
If you want to use the css-legacy extlink, goto settings > open editor core_client cfg, ext_links{, paste the css-legacy references below the css extlink references.

Relevant configuration options:
Settings menu > Editor core-client (or * handling) > Structure menu >
ext_links > Editor menu > "desired_fileextension: css;" (css = method of handling which spawns behaviour described in first 2 notes below)
extlink_parser to be precise.
Relevant file for css extlink parser setting is fc/parser/css/prepare_write.php which gets called by core_client/editor/fc/parser/css/write/init.php
which is selected in the core_clients/editor/writebackmainediteddata.php after noting both the current_extlink and if at this point a php function named writefile2 exists, or only a function named writefile. By default, the css extlink it's parser enables a writefile2 function to kick in, while all other text file types use the "regular" writefile function.
This behaviour can be altered for each file type.

- Language packs editing or using css files for database purposes

If you ever need to use any of these characters: "{", "}", ";" in your css elements use them respectively like this: "\{", "\}", "\;"
Editing freedomeditor configuration css files in other applications can be performed by respecting these transformations:
"_dotcm_", "_brace_", "_bbrace_", "_nwln_"), = (";", "{", "}", '<br />'

- /* CSS Comments */
  Simply said, when you see/type in the edit field "*/;", it will be changed to ";*/" when the file is actually saved to disk
- Deprecated Browser CSS incompatibility solution
  By making use of the loader.php file as the default GUI template does, you can create seperate css elements for different user agent strings. The loader.php file ofcourse uses intelligent browser cache checking.