Missing Ldraw Colors

[Sven v. Beuningen]

We call that colour Pearl Light Grey, LDraw Code 135
I don't know why it is matched to lego id 179 in ldconfig.ldr. Maybe Willy knows?

You picked an interesting example, Sven. My personal opinion is that the connection in ldconfig.ldr between lego id 179 and ldraw code 135 is not correct.

Every time the LDraw and LEGO color number does not match it's a clear indicator that we already had a LDraw legacy color and based on the RGB and other information picked a LEGO color. Sometimes sources where not clear and it was all about a guessing game. What we also had in mind was an AFOL approach rather than a LEGO one. This means that if there was a BL name available we would favour the BL name. Therefore "Maersk Blue" over "Pastel Blue". Keep also in mind that we are working with "shadow colors". The RGBs LEGO provides are the ones used on there systems to represent a brick color and does NOT match 100% the real ABS color.

Back to "296 Cool Silver". Apparently BL also uses "Pearl Light Grey" and what about 179 and 135. Proposals -  and please use a very practical approach?

w.

Hi Willy,

what about keeping the mapping for LEGO color 179 to Ldraw 135 for backwards compatibility reasons. In addition we could introduce a new color for 296 Cool silver? If we do it this way we can clearly distinguish the colors. At least from their IDs. If the optical difference is near zero, we could map LEGO color 296 also to Ldraw 135. But we need the information from someone who owns parts in both colors. 
Therefore I suggest:

LEGO color 179 (Silver Flip Flop) -> Ldraw 135 (Pearl Light Grey)

LEGO color 296 (Cool Silver) -> new ID, new RGB and new Ldraw name 
or
LEGO color 296 (Cool Silver) -> Ldraw 135 (Pearl Light Grey)

What do you think?

So Long

Sven