(2020-02-01, 23:55)Sylvain Sauvage Wrote: Hi all,

BrickLink just changed the names for the Flesh colours: https://www.bricklink.com/message.asp?ID=1178151

Actually, it started yesterday with replacing “Flesh” with “Nougat” but now they replaced the colour “Dark Flesh” with “Medium Brown” and added “Dark Nougat” (previously conflated with “Earth Orange”).

(2020-02-01, 23:55)Sylvain Sauvage Wrote: Whoopee… maybe.

(2020-02-02, 10:12)Magnus Forsberg Wrote: I say we have to correct ldconfig now, for another reason.
Ldraw code 86 is exactly the same as ldraw code 128. Both have RGB = #AD6140



I think we should change ldraw code 86 to match LEGOID 217 and use the name "Medium Brown"
And also remove the word "Flesh", and use "Nougat" in ldraw code 78, 84 and 92

(2020-02-02, 8:42)Philippe Hurbain Wrote: Thanks for the heads up...
Speaking of things affecting LDConfig.ldr, two new opalescent "colors" surfaced:
360 Transparent with Opalescence and 363 Transparent Brown with Opalescence (https://www.newelementary.com/2020/02/lego-dots-new-pieces-opalescence.html)

(2020-02-02, 11:23)Willy Tschager Wrote: Sounds good. I'll update the file an post it.

w.

(2020-02-02, 11:33)Magnus Forsberg Wrote: Did you read the message on Bricklink?
What do they mean by this, "Changes to the color names in Item Names are forthcoming."?

(2020-02-02, 11:49)Willy Tschager Wrote: I'd say Chris has to fasttrack all these:

https://www.ldraw.org/cgi-bin/ptscan.cgi?q=with+light+flesh

w.

(2020-02-03, 22:47)Magnus Forsberg Wrote: If you scan the library for only Flesh there is 115 files to change.....

https://www.ldraw.org/cgi-bin/ptscan.cgi?q=flesh

(2020-02-01, 23:55)Sylvain Sauvage Wrote: Hi all,

BrickLink just changed the names for the Flesh colours: https://www.bricklink.com/message.asp?ID=1178151

Actually, it started yesterday with replacing “Flesh” with “Nougat” but now they replaced the colour “Dark Flesh” with “Medium Brown” and added “Dark Nougat” (previously conflated with “Earth Orange”).

Whoopee… maybe.

(2022-08-19, 15:22)Sylvain Sauvage Wrote: A few new name changes that aren’t in ldconfig (2022-04) yet:
— 128 Medium_Brown should be Light_Brown (conflicts with the new 370 Medium_Brown)
— 510 Fabuland_Pastel_Green has been finally recognized by BL as different from Lime and named Fabuland Lime.
— 368 Vibrant_Yellow should be Neon_Yellow (seems BL has finally settled on this one)

And (LEGO) 371 Warm Tan / (BL) 241 Medium Tan is missing (#CCA373 according to Ryan Howerter).

(2022-08-19, 17:14)Max Murtazin Wrote: Also Bricklink now recognizes flip/flop colors as "Bionicle" ones, as well as Pearl Black

(2022-08-19, 23:54)Orion Pobursky Wrote: If you're looking to have the LDConfig updated, the next Parts update will be in a month.

(2022-08-21, 22:56)Orion Pobursky Wrote: I think you took my message the wrong way. I wasn't trying to be flippant or dismissive. I was simply noting that there's time for discussion and inclusion in the next update.

(2022-08-21, 23:27)Orion Pobursky Wrote: I think most of our regulars are still on some sort of summer holiday or break. Summer is kind of slow in LDraw land.

(2022-08-22, 16:19)Philippe Hurbain Wrote: Someone once told me of "August frantic slowdown" 😂 ("le ralentissement effréné du mois d'août" in French...)

(2022-08-19, 22:28)Sylvain Sauvage Wrote: BL => LEGO (=> LDraw, maybe change the name?)
239 Bionicle Silver => 179 Silver Flip/Flop (=> 179 Flat_Silver)

(2022-08-22, 18:07)Sylvain Sauvage Wrote: Ah, this one causes a problem (in Studo at least):
BL has:
— 66 Pearl Light Gray supposed to match both LEGO 131 Silver & 296 Cool Silver 
— 96 Flat Silver supposed to match LEGO 315 Silver Metallic

LDraw has:
— 135 Pearl_Light_Grey to match LEGO 131, 296 & 315
— 179 Flat_Silver… which is then misnamed or a “real” Flat_Silver to match LEGO 315/BL 96 is missing.

(2022-08-22, 18:53)Max Murtazin Wrote: BL's silver colors is one of the most complicated messes ever

Quote:The issue is that some BrickLink members in the past have seen distinctions between the colors and have registered their findings in the inventory system and to a certain extent in their listings.

Merging Flat Silver and Pearl Light Gray is something we will likely to in the future. But it needs to be planned, announced, and carried out in a way to cause the least disruption.

(2022-08-22, 19:04)Sylvain Sauvage Wrote: Russell Callender recently said there:
https://www.bricklink.com/message.asp?ID=1349550

So, even corporate agrees, but it won’t change tomorrow.

(2022-08-19, 15:22)Sylvain Sauvage Wrote: A few new name changes that aren’t in ldconfig (2022-04) yet:
— 128 Medium_Brown should be Light_Brown (conflicts with the new 370 Medium_Brown)
— 510 Fabuland_Pastel_Green has been finally recognized by BL as different from Lime and named Fabuland Lime.
— 368 Vibrant_Yellow should be Neon_Yellow (seems BL has finally settled on this one)

And (LEGO) 371 Warm Tan / (BL) 241 Medium Tan is missing (#CCA373 according to Ryan Howerter).

(2022-08-19, 15:22)Sylvain Sauvage Wrote: A few new name changes that aren’t in ldconfig (2022-04) yet:
— 128 Medium_Brown should be Light_Brown (conflicts with the new 370 Medium_Brown)

(2022-08-19, 15:22)Sylvain Sauvage Wrote: — 510 Fabuland_Pastel_Green has been finally recognized by BL as different from Lime and named Fabuland Lime.
— 368 Vibrant_Yellow should be Neon_Yellow (seems BL has finally settled on this one)

(2022-08-19, 15:22)Sylvain Sauvage Wrote: And (LEGO) 371 Warm Tan / (BL) 241 Medium Tan is missing (#CCA373 according to Ryan Howerter).

(2022-10-24, 10:45)Willy Tschager Wrote: I'm trying to figure out what you want me to do:

* LEGO 128 - Dark Nougat has its LDraw equivalent in 128 - Dark_Nougat
* LEGO 370 - Medium Brown has its LDraw equivalent in 370 - Medium_Brown

w.

(2022-08-19, 22:28)Sylvain Sauvage Wrote: BL => LEGO (=> LDraw, maybe change the name?)
237 Bionicle Copper => 176 Rep Flip/Flop
238 Bionicle Gold => 178 Yellow Flip/Flop
239 Bionicle Silver => 179 Silver Flip/Flop (=> 179 Flat_Silver)

(2022-10-25, 15:29)Willy Tschager Wrote: Colors are always a mess. 178 is currently matched with LEGO 147 Metallic Sand Yellow which has been replaced by LEGO 297 Warm Gold. I have to think about.

w.

(2022-08-19, 22:28)Sylvain Sauvage Wrote: BL => LEGO (=> LDraw, maybe change the name?)
237 Bionicle Copper => 176 Rep Flip/Flop
238 Bionicle Gold => 178 Yellow Flip/Flop
239 Bionicle Silver => 179 Silver Flip/Flop (=> 179 Flat_Silver)

(2022-08-19, 22:28)Sylvain Sauvage Wrote: 234 Trans-Medium Purple => 236 Transparent Bright Reddish Lilac (=> 44 Trans_Bright_Reddish_Lilac)

• 86 (Old)Medium_Brown renamed to Light_Brown
  
• 371 Medium_Tan added
  
• 83 Metallic_Black renamed to Pearl_Black
  
• 510 Fabuland_Pastel_Green renamed to Fabuland_Lime
  

• 178 Flat_Dark_Gold renamed to Pearl_Yellow
  
• 179 Flat_Silver renamed to Pearl_Silver
  
• 176 named Pearl_Red
  
• 147 named Pearl_Dark_Gold
  

(2023-05-05, 11:31)Sylvain Sauvage Wrote: What 

• 178 Flat_Dark_Gold renamed to Pearl_Yellow
  
• 179 Flat_Silver renamed to Pearl_Silver
  
• 176 named Pearl_Red
  
• 147 named Pearl_Dark_Gold
  

What happened to the Bionicle_* names to match the BrickLink names?  Why revert to Peeron’s names?

(2023-05-05, 11:31)Sylvain Sauvage Wrote: Also, now that BrickLink has Bionicle Silver to match LEGO 179 Silver Flip/Flop, LDraw doesn’t have a separate silver colour to match BL 95 Flat Silver (LEGO 315 Silver Metallic only).
Studio uses LD 179 for BL 95 Flat Silver.
Should Studio switch to Pearl Light Grey instead?    It seems wrong to me.  Well, it was already wrong before….
(Plus, it’s not for the immediate future but BL plans to split BL 66 Pearl Light Gray to separate LEGO 131 Silver from LEGO 296 Cool Silver.)

(2023-05-05, 15:27)Willy Tschager Wrote: We discussed this and agreed that we don't wanna use theme names for a color but (as we do for part names) be as much as we can generic. Since those are pearl colors and we already have pearl colors "Pearl" seamed a logical choice.

w.

(2023-05-05, 15:30)Willy Tschager Wrote: This has been discussed ad nauseam:

https://forums.ldraw.org/thread-24059-post-45467.html#pid45467

It will stay as it is.

w.

(2023-05-05, 15:52)Sylvain Sauvage Wrote: But all I (and others) have to go with is the guidelines here.  I (and others) can’t be aware of secret discussions and unpublished decisions.

(2023-05-05, 15:52)Sylvain Sauvage Wrote: Well, if you don’t want it to pop up in the forums every next thursday, maybe an official statement somewhere would help.  (Maybe in the page linked above?)
(No, “This was discussed before, get lost!” in a forum post isn’t an official statement that explains why an official guideline isn’t followed.)

(2023-05-05, 18:54)Orion Pobursky Wrote: What Willy is trying to say is that all of this is discussed on the forums. This is the public record and is searchable. I'm not going to link to every single spec discussion.

(2023-05-05, 18:54)Orion Pobursky Wrote: You asked the question, it was answered. The tone didn't seem dismissive to me but I apologize if it seemed that way to you. Please remember that English is a second or third language for most of us (not me but almost everyone else) and that the medium of text removes non-verbal context clues.

(2023-05-05, 18:54)Orion Pobursky Wrote: Also, I'm not sure what "official guideline" we're not following as there are no requirements listed in the page you link to.