Hi David,

The current Markdown interpreter used in the wiki supports the classic
Markdown format, while the one we use in the documentation seciton is the
Markdown Extra version.

But the goal of the naming scheme of the translated documentation pages in
the wiki is to allow us to automatically retrieve the content from the wiki,
and display it in the documentation section. We didn't setup the environment
yet, but when it's done, each english chapter of the book will contain a
link towards all tre available translations of this page, in the same
section (not in the wiki). 

So the wiki is more of a work environment than a publishing environment, and
I think it's not too problematic that the tables don't get rendered
correctly in it. We'll do our best to provide the publishing environment
soon. In the meantime, you can test your syntax in the online Markdown
parser at:

http://www.michelf.com/projects/php-markdown/dingus/

Cheers,

François

-----Message d'origine-----
De : [email protected] [mailto:[EMAIL PROTECTED] De
la part de David Jiang
Envoyé : mercredi 28 février 2007 16:34
À : symfony developers
Objet : [symfony-devs] The symfony wiki's markdown doesn't support table


I found that the symfony wiki's markdown doesn't support table.

http://www.symfony-project.com/trac/wiki/Documentation/zh_CN/book/1.0/02-Exp
loring-Symfony-s-Code
The code below will be displayed in one line.

Table 2-1 - Root Directories

Directory  |  Description
---------- | ------------
`apps/`    | Contains one directory for each application of the
project (typically, `frontend` and `backend` for the front and back office).
`batch/`   | Contains PHP scripts called from a command line or a
scheduler, to run batch processes.
`cache/`   | Contains the cached version of the configuration, and (if
you activate it) the cache version of the actions and templates of the
project. The cache mechanism (detailed in Chapter 12) uses these files to
speed up the answer to web requests. Each application will have a
subdirectory here, containing preprocessed PHP and HTML files.
`config/`  | Holds the general configuration of the project.
`data/`    | Here, you can store the data files of the project, like a
database schema, a SQL file that creates tables, or even a SQLite database
file.
`doc/`     | Stores the project documentation, including your own
documents and the documentation generated by PHPdoc.
`lib/`     | Dedicated to foreign classes or libraries. Here, you can
add the code that needs to be shared among your applications. The `model/`
subdirectory stores the object model of the project (described in Chapter
8).
`log/`     | Stores the applicable log files generated directly by
symfony. It can also contain web server log files, database log files, or
log files from any part of the project. Symfony creates one log file per
application and per environment (log files are discussed in Chapter 16).
`plugins/` | Stores the plug-ins installed in the application (plug- ins are
discussed in Chapter 17).
`test/`    | Contains unit and functional tests written in PHP and
compatible with the symfony testing framework (discussed in Chapter 15).
During the project setup, symfony automatically adds some stubs with a few
basic tests.
`web/`     | The root for the web server. The only files accessible
from the Internet are the ones located in this directory.





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to