colorButton_colors doesn't allow to specify "name" and color

[Alfonso Martínez de Lizarrondo]

This is not related to showing a custom text for each color as that can be done including the proper entries in editor.lang.colors

Instead, it's related to the functionality of FCKeditor to specify

FCKConfig.FontColors = 'ff9900/FontColor1,0066cc/FontColor2,ff0000/FontColor3' ;
FCKConfig.CoreStyles.Color =
	{
		Element		: 'span',
		Attributes	: { 'class' : '#("Color")' },
		Overrides	: [ { Element : 'span', Attributes : { 'class' : /^FontColor(?:1|2|3)$/ } } ]
	} ;

Now the only option seems to be to use something like

colorButton_colors : 'ff9900,0066cc,ff0000',

colorButton_foreStyle :
	{
		element : 'span',
		attributes : { 'class' : 'Color(color)' }
	},

but that requires to use class names like Colorff9900, instead of being able to specify whatever they need.

[Alfonso Martínez de Lizarrondo]

Proposed patch

[Alfonso Martínez de Lizarrondo]

Revised patch

[Garry Yao]

The '##(color)' change in config entries introduced a compatibility issue, we should somehow handle it.

[Alfonso Martínez de Lizarrondo]

Revised patch

[Garry Yao]

Just to make L128 more readable before commit, how about using

!colorName.match( /^#/ ) && ( colorName = '#' + colorName );

[Alfonso Martínez de Lizarrondo]

Fixed with [5230]