headers
Sonic | 1 Mar 12:47
Picon

Formatting problem in Midgard documentation

Hi!

I've noticed this several times now and thought I'd post ist to the list: 
There seems to de a formatting problem in Midgard's documentation pages, 
which has the effect that underscores are not displayed, but converted to 
<em> tags. This might be a feature, but in the case of class or method names, 
it's a bug. For example get_current_leaf() is displayed as getcurrentleaf() 
where "current" is written in italics. See 

http://www.midgard-project.org/documentation/concepts-midcom-specs-components-styleguide/

Section Naming conventions - Classes for more examples.

Bye,

Andreas

--

-- 
Adding sound to movies would be like putting lipstick on the Venus de Milo. -- 
Mary Pickford, 1925
Permalink | Reply | 1 comment |
headers
Arttu Manninen | 1 Mar 12:59
Picon

Re: Formatting problem in Midgard documentation

Sonic wrote:
> Hi!

Hi, Andreas!

> I've noticed this several times now and thought I'd post ist to the list: 
> There seems to de a formatting problem in Midgard's documentation pages, 
> which has the effect that underscores are not displayed, but converted to 
> <em> tags. This might be a feature, but in the case of class or method names, 
> it's a bug. For example get_current_leaf() is displayed as getcurrentleaf() 
> where "current" is written in italics. See 
> 
> http://www.midgard-project.org/documentation/concepts-midcom-specs-components-styleguide/
> 
> Section Naming conventions - Classes for more examples.

This is both a bug that came along, when old 'de.linkm.taviewer'
documentation was ported to 'net.nemein.wiki' documentation, and a
possible mistake of document writers, I think.

Wiki formatting sees underscore (_) as a start of italics unless an
escape character has been used with it (\_). This means that
get_current_leaf() will display as get<i>current</i>leaf().

Functions and methods are easy to write wrong and when reading your own
text, italics are still relatively easy to miss in a long text.

I have been correcting every time I see these mistakes. I have been
editing loads of old mgd_*** functions, but I haven't caught them all.
The same goes with other parts of the documentation.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Torben Nehmer | 1 Mar 13:21
Gravatar

Re: Formatting problem in Midgard documentation


Hi,

--Arttu Manninen wrote on 2006-03-01 12:59:
>> I've noticed this several times now and thought I'd post ist to the list: 
>> There seems to de a formatting problem in Midgard's documentation pages, 
>> which has the effect that underscores are not displayed, but converted to 
>> <em> tags. This might be a feature, but in the case of class or method 
>> names, it's a bug. For example get_current_leaf() is displayed as 
>> getcurrentleaf() where "current" is written in italics. See
>
> This is both a bug that came along, when old 'de.linkm.taviewer' 
> documentation was ported to 'net.nemein.wiki' documentation, and a possible 
> mistake of document writers, I think.
> 
> Wiki formatting sees underscore (_) as a start of italics unless an escape 
> character has been used with it (\_). This means that get_current_leaf() will
> display as get<i>current</i>leaf().
> 
> Functions and methods are easy to write wrong and when reading your own text,
> italics are still relatively easy to miss in a long text.

Yeah, this is a well-known problem nowadays, but not trivial to fix because, as
you say, these cases are not exactly easy to spot.

When we start fixing this, I recommend some different approach. Instead of
masking the underscores and thus having the function name set in normal type,
quote it using backticks, like this:

"some text with `a_function_name()` being mentioned"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Henri Bergius | 1 Mar 19:54
Favicon
Gravatar

Re: Formatting problem in Midgard documentation

On Mar 1, 2006, at 13:59, Arttu Manninen wrote:
> Wiki formatting sees underscore (_) as a start of italics unless an
> escape character has been used with it (\_). This means that
> get_current_leaf() will display as get<i>current</i>leaf().

The PHP implementation of Markdown will be smarter about this when we  
upgrade to the version shipping with MidCOM 2.5...

http://www.michelf.com/projects/php-markdown/extra/#em

> Arttu Manninen

/Bergie

Henri Bergius
Consultant Partner, Nemein
henri.bergius@...

Midgard CMS
www.midgard-project.org
Permalink | Reply | 0 comments |
headers
Sonic | 2 Mar 03:09
Picon

Exorcist Delete

Hi!

Just a quick question: Does Exorcist have support for exporting deletes 
already? 

If no: Is this planned for the future? 

If yes: It doesn't work for me. I deleted one Style Element on the staging 
server, ran Exorcist and still had it on my live server afterwards. Do I have 
to make some special configuration for this to work?

Bye,

Andreas
--

-- 
Adding sound to movies would be like putting lipstick on the Venus de Milo. -- 
Mary Pickford, 1925
Permalink | Reply | 3 comments |
headers
Jukka Zitting | 2 Mar 10:00
Picon
Gravatar

Re: Exorcist Delete

Hi,

On 3/2/06, Sonic <sonic <at> sonicpictures.de> wrote:
> Just a quick question: Does Exorcist have support for exporting deletes
> already?

Yes, with some restrictions. See the warning below.

> If yes: It doesn't work for me. I deleted one Style Element on the staging
> server, ran Exorcist and still had it on my live server afterwards. Do I have
> to make some special configuration for this to work?

Are you are using a XSLT selection to only replicate the
mgd:midgard_style content? The delete information is exported as
separate mgd:delete elements at the end of the XML export, so you'll
be able to replicate the deletions if you add something like
<xsl:apply-templates select="mgd:delete"/> to your stylesheet.

WARNING: The exported deletions contain *only* the deleted GUID, so
there is currently no way to restrict the deletions to just one object
class (like styles or style elements) or object tree (like some
specific style A). The class information would be possible to include,
 but not the tree information because of the way Midgard currently
handles parent links.

BR,

Jukka Zitting

--
(Continue reading)

Permalink | Reply | 2 comments |
headers
Sonic | 2 Mar 11:37
Picon

Re: Exorcist Delete

Am Donnerstag, 2. März 2006 10:00 schrieb Jukka Zitting:
> Hi,
>
> On 3/2/06, Sonic <sonic@...> wrote:
> > Just a quick question: Does Exorcist have support for exporting deletes
> > already?
>
> Yes, with some restrictions. See the warning below.
>
> > If yes: It doesn't work for me. I deleted one Style Element on the
> > staging server, ran Exorcist and still had it on my live server
> > afterwards. Do I have to make some special configuration for this to
> > work?
>
> Are you are using a XSLT selection to only replicate the
> mgd:midgard_style content? The delete information is exported as
> separate mgd:delete elements at the end of the XML export, so you'll
> be able to replicate the deletions if you add something like
> <xsl:apply-templates select="mgd:delete"/> to your stylesheet.
>
> WARNING: The exported deletions contain *only* the deleted GUID, so
> there is currently no way to restrict the deletions to just one object
> class (like styles or style elements) or object tree (like some
> specific style A). The class information would be possible to include,
>  but not the tree information because of the way Midgard currently
> handles parent links.

Hi!

Thanks for the fast reply! Yes, I'm not replicating the entire db, just Styles
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jukka Zitting | 2 Mar 12:34
Picon
Gravatar

Re: Exorcist Delete

Hi,

On 3/2/06, Sonic <sonic <at> sonicpictures.de> wrote:
> Thanks for the fast reply! Yes, I'm not replicating the entire db, just Styles
> and Snippets, and I've deleted a lot of User accounts from the staging server
> after the last complete synchronisation. Needless to say, these are still
> needed on the live server, so being able to restrict deletes to certain
> classes would be most helpful!

OK, I'll take a look at this. Can you file an issue for this either in
the Midgard issue tracker on tigris or in the Exorcist issue tracker
on sourceforge?

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - info <at> yukatan.fi
Software craftsmanship, JCR consulting, and Java development
Permalink | Reply | 0 comments |
headers
Koffi Marcel | 7 Mar 15:37
Picon
Favicon

Re: About google analytics.

Hello,
I'm interested on webalizer stats
.....
--- Henri Bergius <henri.bergius@...> a écrit :

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ok, I've removed Google Analytics from the site. So
> from now on we  
> will count again on webalizer...
> 
> (BTW, if anybody is interested in the webalizer
> stats, let me know)
> 
> On Feb 11, 2006, at 13:51, Tarjei Huse wrote:
> 
> > -1
> > On fre, 2006-02-10 at 21:05 +0200, Henri Bergius
> wrote:
> >> Any +1/-1 votes for keeping Google Analytics on
> the Midgard site?
> >>
> >> On Jan 23, 2006, at 19:06, David Schmitter wrote:
> >>
> >>> I notice the same. google-analytics.com
> increases the response  
> >>> time by
> >>> several seconds. That is on a 2Mbit line...
> >>>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Christiaan Briggs | 7 Mar 17:53
Picon

Mac OS X install file

Hi, I'm curious to know why the binary download for Mac OS X is a  
Bzip2 compressed Disk Image file. Why isn't it simply a Disk Image file?

http://www.midgard-project.org/osx/installer/Midgard.dmg.bz2

Cheers,
Christiaan
Permalink | Reply | 0 comments |

Gmane