After some time I tried again to blog from textmate on wordpress. One question, I get all the '"' translated to " also if I'm in [source] code block.
That is a problem because in the wordpress page those areas don't get interpreted, and if I change them they will go back to " next time I post it.
Any solution for this problem?
On 2 Dec 2009, at 14:47, andrea wrote:
After some time I tried again to blog from textmate on wordpress. One question, I get all the '"' translated to " also if I'm in [source] code block.
This is not something TextMate or the blogging bundle does.
It is also not something I have run into with my pretty standard WordPress setup.
Allan Odgaard ha scritto:
On 2 Dec 2009, at 14:47, andrea wrote:
This is not something TextMate or the blogging bundle does.
It is also not something I have run into with my pretty standard WordPress setup.
Ah good now it works, it was enough to change the language in the source code. By the way I never find the languages I need, maybe is better to colorize the source code by myself and then past it as it is?
Allan Odgaard mailinglist@textmate.org writes:
On 2 Dec 2009, at 14:47, andrea wrote:
This is not something TextMate or the blogging bundle does.
It is also not something I have run into with my pretty standard WordPress setup.
I understood better the problem, in short the first time I post-to-blog works fine. If I do it again it will substitute the already quoted characters with other interpreted characters.
This is very annoying and it does it with all source languages. For example I get: --8<---------------cut here---------------start------------->8--- (setq newline-force-close-alist '((python-mode . ":") (html-mode . " <br>"))) [/source] --8<---------------cut here---------------end--------------->8---
Any ideas?
On 03 Dec 2009, at 9:56, andrea crotti wrote:
Ah good now it works, it was enough to change the language in the source code. By the way I never find the languages I need, maybe is better to colorize the source code by myself and then past it as it is?
There is no support for posting syntax highlighted code, so yes, you will need to do this yourself, if you need it.
I haven’t found a good solution myself, but this looks pretty interesting: http://code.google.com/p/syntaxhighlighter/ — it does the syntax highlight in JavaScript, so you just post the “raw” source code (rather than messy markup).
On 06 Dec 2009, at 4:57, andrea wrote:
I understood better the problem, in short the first time I post-to-blog works fine. If I do it again it will substitute the already quoted characters with other interpreted characters.
This is likely a bug in WordPress or one of the plug-ins you have installed for it.
Normally WordPress shouldn’t touch stuff inside <pre> but there has been *a lot* of bugs related to this and sometimes fixed bugs reappear — I actually run a plug-in which tries to disable all the transformations that WordPress may do. That said, if your content is posted as Markdown, these transformations should happen at display-time.
-
Allan Odgaard -
andrea -
andrea crotti