Bug #55201 [Opn->Fbk]: markup markup
| From: | yannick@php.net | Date: | Thu, 21 Jul 2011 23:17:28 +0000 |
| Subject: | Bug #55201 [Opn->Fbk]: markup markup | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-6910@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=55201&edit=1
ID: 55201
Updated by: yannick@php.net
Reported by: philip@php.net
Summary: markup markup
-Status: Open
+Status: Feedback
Type: Bug
Package: Online Doc Editor problem
Operating System: Irrelevant
PHP Version: Irrelevant
-Assigned To:
+Assigned To: yannick
Block user comment: N
Private report: N
New Comment:
The first proposal is effectively too magic...
For the second, could you propose me what you thinks about ? witch content ?
You can view what is actually used here :
http://svn.php.net/viewvc/web/doc-editor/trunk/js/ui/cmp/FilePanel.js?view=markup
About line 178, you can view the "text" properties used in the list into the panel, and
line 186, the beginning of the content.
Could you please make a proposal to implement ?
Best,
Yannick
Previous Comments:
------------------------------------------------------------------------
[2011-07-13 10:28:04] philip@php.net
Description:
------------
The editor has a "markup" option that inserts markup for roles such as
"examples" and "errors" but the current markup only
applies to a refentry, which is not applicable outside of our reference/ area.
Example: Two days ago someone inappropriately inserted an example refsect1 into a chapter, so this
broke the build.
I'm not sure the best way to handle this, but the following may (or may not) work:
- When inside refentry, append the current refsect1 info
- Otherwise, remove it and &reftitle.*; but leave the <para>
If that's too much magic, then we could adjust the "markup" button to offer multiple
options per type so, for example, have
"seealso refsect1" and "seealso standard" options. Something like that.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=55201&edit=1