<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[LDraw.org Discussion Forums - Standards Board]]></title>
		<link>https://forums.ldraw.org/</link>
		<description><![CDATA[LDraw.org Discussion Forums - https://forums.ldraw.org]]></description>
		<pubDate>Fri, 15 May 2026 21:05:51 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[ringr.dat (deprecated name)???]]></title>
			<link>https://forums.ldraw.org/thread-29353.html</link>
			<pubDate>Sun, 25 Jan 2026 17:23:30 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=5">Willy Tschager</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-29353.html</guid>
			<description><![CDATA[Guys,<br />
<br />
working on the primref this caught my eye:<br />
<a href="https://wiki.ldraw.org/wiki/Primitives_Reference" target="_blank" rel="noopener" class="mycode_url">https://wiki.ldraw.org/wiki/Primitives_Reference</a><br />
<br />
n-fringr.dat<br />
n-frinrr.dat<br />
n-ffrinr.dat<br />
n-ffrirr.dat<br />
nn-ffrir.dat<br />
ringr.dat (deprecated name)<br />
ringrr.dat (deprecated name)<br />
<br />
Moving the content from the webpage to the wiki I just did a copy'n'paste, but this cannot be correct, right?<br />
<br />
It's actually:<br />
<br />
n-fringr.dat<br />
n-fringrr.dat<br />
n-ffringr.dat<br />
n-ffringrr.dat<br />
<br />
n-frinrr.dat (deprecated name)<br />
n-ffrinr.dat (deprecated name)<br />
n-ffrirr.dat (deprecated name)<br />
nn-ffrir.dat (deprecated name)<br />
ringr.dat (deprecated name)<br />
ringrr.dat (deprecated name)<br />
<br />
w.]]></description>
			<content:encoded><![CDATA[Guys,<br />
<br />
working on the primref this caught my eye:<br />
<a href="https://wiki.ldraw.org/wiki/Primitives_Reference" target="_blank" rel="noopener" class="mycode_url">https://wiki.ldraw.org/wiki/Primitives_Reference</a><br />
<br />
n-fringr.dat<br />
n-frinrr.dat<br />
n-ffrinr.dat<br />
n-ffrirr.dat<br />
nn-ffrir.dat<br />
ringr.dat (deprecated name)<br />
ringrr.dat (deprecated name)<br />
<br />
Moving the content from the webpage to the wiki I just did a copy'n'paste, but this cannot be correct, right?<br />
<br />
It's actually:<br />
<br />
n-fringr.dat<br />
n-fringrr.dat<br />
n-ffringr.dat<br />
n-ffringrr.dat<br />
<br />
n-frinrr.dat (deprecated name)<br />
n-ffrinr.dat (deprecated name)<br />
n-ffrirr.dat (deprecated name)<br />
nn-ffrir.dat (deprecated name)<br />
ringr.dat (deprecated name)<br />
ringrr.dat (deprecated name)<br />
<br />
w.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Partial torus naming]]></title>
			<link>https://forums.ldraw.org/thread-28838.html</link>
			<pubDate>Sun, 25 May 2025 08:55:47 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=5">Willy Tschager</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-28838.html</guid>
			<description><![CDATA[Guys,<br />
<br />
please read an have your say on:<br />
<br />
<a href="https://forums.ldraw.org/thread-28522.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-28522.html</a><br />
<br />
Various naming schemes have been layed out. Pick theone that suits best.<br />
<br />
w.]]></description>
			<content:encoded><![CDATA[Guys,<br />
<br />
please read an have your say on:<br />
<br />
<a href="https://forums.ldraw.org/thread-28522.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-28522.html</a><br />
<br />
Various naming schemes have been layed out. Pick theone that suits best.<br />
<br />
w.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Call for Votes: MATERIAL FABRIC]]></title>
			<link>https://forums.ldraw.org/thread-28749.html</link>
			<pubDate>Tue, 01 Apr 2025 20:50:28 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=11">Travis Cobbs</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-28749.html</guid>
			<description><![CDATA[Please vote on the FABRIC updates to the !COLOUR specification as presented in draft form <a href="https://www.ldraw.org/fabric-draft.html" target="_blank" rel="noopener" class="mycode_url">here</a>.]]></description>
			<content:encoded><![CDATA[Please vote on the FABRIC updates to the !COLOUR specification as presented in draft form <a href="https://www.ldraw.org/fabric-draft.html" target="_blank" rel="noopener" class="mycode_url">here</a>.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[New !COLOUR finish]]></title>
			<link>https://forums.ldraw.org/thread-28688.html</link>
			<pubDate>Sun, 23 Feb 2025 02:05:50 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=11">Travis Cobbs</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-28688.html</guid>
			<description><![CDATA[It has been requested that we set up a new !COLOUR MATERIAL to deal with fabric materials:<br />
<br />
<a href="https://forums.ldraw.org/thread-28335.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-28335.html</a><br />
<br />
In my opinion, this would probably be better as a new finish, instead of adding MATERIAL FABRIC &lt;blah blah blah&gt;. There are a number of different fabric materials, and I feel that each should be supported. At the minimum, we have:<br />
<ul class="mycode_list"><li>Standard minifigure capes<br />
</li>
<li>Qui-Gon <a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=21625&amp;idColor=69#T=C&amp;C=69" target="_blank" rel="noopener" class="mycode_url">Poncho</a><br />
</li>
<li>Buildable Boba Fett <a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=35863&amp;idColor=155#T=C&amp;C=155" target="_blank" rel="noopener" class="mycode_url">cloth pauldron</a> (Is this the same material as the poncho above?)<br />
</li>
<li>String (are there multiple types of LEGO string?)<br />
</li>
<li>Sails (same material as minifigure capes?)<br />
</li>
<li>Tepee/covered wagon<br />
</li>
</ul>
<br />
The other thread (that anyone can post to) died off, so it doesn't seem like anybody other than Willy wants to provide input, so I am proposing to add FABRIC as a new !COLOUR finish, with a required type being one of the following values:<br />
<ul class="mycode_list"><li>CAPE<br />
</li>
<li>VELVET<br />
</li>
<li>CANVAS<br />
</li>
<li>STRING<br />
</li>
</ul>
<br />
Example for buildable Darth Vader's <a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=21994&amp;idColor=11#T=C&amp;C=11" target="_blank" rel="noopener" class="mycode_url">cape</a>:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>0 !COLOUR Black_Velvet CODE 999 VALUE #0A0A0A EDGE #808080 FABRIC VELVET</code></div></div>]]></description>
			<content:encoded><![CDATA[It has been requested that we set up a new !COLOUR MATERIAL to deal with fabric materials:<br />
<br />
<a href="https://forums.ldraw.org/thread-28335.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-28335.html</a><br />
<br />
In my opinion, this would probably be better as a new finish, instead of adding MATERIAL FABRIC &lt;blah blah blah&gt;. There are a number of different fabric materials, and I feel that each should be supported. At the minimum, we have:<br />
<ul class="mycode_list"><li>Standard minifigure capes<br />
</li>
<li>Qui-Gon <a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=21625&amp;idColor=69#T=C&amp;C=69" target="_blank" rel="noopener" class="mycode_url">Poncho</a><br />
</li>
<li>Buildable Boba Fett <a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=35863&amp;idColor=155#T=C&amp;C=155" target="_blank" rel="noopener" class="mycode_url">cloth pauldron</a> (Is this the same material as the poncho above?)<br />
</li>
<li>String (are there multiple types of LEGO string?)<br />
</li>
<li>Sails (same material as minifigure capes?)<br />
</li>
<li>Tepee/covered wagon<br />
</li>
</ul>
<br />
The other thread (that anyone can post to) died off, so it doesn't seem like anybody other than Willy wants to provide input, so I am proposing to add FABRIC as a new !COLOUR finish, with a required type being one of the following values:<br />
<ul class="mycode_list"><li>CAPE<br />
</li>
<li>VELVET<br />
</li>
<li>CANVAS<br />
</li>
<li>STRING<br />
</li>
</ul>
<br />
Example for buildable Darth Vader's <a href="https://www.bricklink.com/v2/catalog/catalogitem.page?P=21994&amp;idColor=11#T=C&amp;C=11" target="_blank" rel="noopener" class="mycode_url">cape</a>:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>0 !COLOUR Black_Velvet CODE 999 VALUE #0A0A0A EDGE #808080 FABRIC VELVET</code></div></div>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[New Header Meta]]></title>
			<link>https://forums.ldraw.org/thread-28684.html</link>
			<pubDate>Thu, 20 Feb 2025 20:17:36 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2">Orion Pobursky</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-28684.html</guid>
			<description><![CDATA[I'm going to add a simple META after the !CMDLINE meta:<br />
<br />
0 !IMAGE_ADJUST &lt;x,y,z&gt; &lt;rotation matrix&gt;<br />
<br />
This will tell the Library (and any other program that wants to use it) to adjust the rotation/position of a part before rendering it. This will allow for patterns or stickers that would otherwise not be shown in the default rendering to be shown (for example <a href="https://library.ldraw.org/parts/search/suffix?basepart=14718" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/search/s...part=14718</a> ). This meta will only be included if the position adjust is not zero and the rotation matrix is not unity.<br />
<br />
A couple of notes: <br />
 - I'm already doing this internal to the Library software but it's part of the general site settings and only editable by me. This will allow authors/header editors to adjust the image without my help, persist the settings through updates, and could be useful to other software as well.<br />
 - As this is for display purposes only, a hold for for this meta would not be appropriate<br />
 - I'm not invested in "!IMAGE_ADJUST" if you have a better suggestion]]></description>
			<content:encoded><![CDATA[I'm going to add a simple META after the !CMDLINE meta:<br />
<br />
0 !IMAGE_ADJUST &lt;x,y,z&gt; &lt;rotation matrix&gt;<br />
<br />
This will tell the Library (and any other program that wants to use it) to adjust the rotation/position of a part before rendering it. This will allow for patterns or stickers that would otherwise not be shown in the default rendering to be shown (for example <a href="https://library.ldraw.org/parts/search/suffix?basepart=14718" target="_blank" rel="noopener" class="mycode_url">https://library.ldraw.org/parts/search/s...part=14718</a> ). This meta will only be included if the position adjust is not zero and the rotation matrix is not unity.<br />
<br />
A couple of notes: <br />
 - I'm already doing this internal to the Library software but it's part of the general site settings and only editable by me. This will allow authors/header editors to adjust the image without my help, persist the settings through updates, and could be useful to other software as well.<br />
 - As this is for display purposes only, a hold for for this meta would not be appropriate<br />
 - I'm not invested in "!IMAGE_ADJUST" if you have a better suggestion]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Request for new material]]></title>
			<link>https://forums.ldraw.org/thread-28335.html</link>
			<pubDate>Sun, 14 Jul 2024 19:45:09 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=5">Willy Tschager</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-28335.html</guid>
			<description><![CDATA[Guys,<br />
<br />
please read:<br />
<br />
<a href="https://forums.ldraw.org/thread-28300.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-28300.html</a><br />
<br />
I guess a new dull <a href="https://www.ldraw.org/article/299.html#material" target="_blank" rel="noopener" class="mycode_url">MATERIAL</a> Fabric will do the job.<br />
<br />
w.]]></description>
			<content:encoded><![CDATA[Guys,<br />
<br />
please read:<br />
<br />
<a href="https://forums.ldraw.org/thread-28300.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-28300.html</a><br />
<br />
I guess a new dull <a href="https://www.ldraw.org/article/299.html#material" target="_blank" rel="noopener" class="mycode_url">MATERIAL</a> Fabric will do the job.<br />
<br />
w.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[New meta in LDConfig for default category icon in editors]]></title>
			<link>https://forums.ldraw.org/thread-28258.html</link>
			<pubDate>Tue, 14 May 2024 13:23:56 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=5">Willy Tschager</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-28258.html</guid>
			<description><![CDATA[Dear LSB,<br />
<br />
please read:<br />
<br />
<a href="https://forums.ldraw.org/thread-28231.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-28231.html</a><br />
<br />
and have your say.<br />
<br />
w.]]></description>
			<content:encoded><![CDATA[Dear LSB,<br />
<br />
please read:<br />
<br />
<a href="https://forums.ldraw.org/thread-28231.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-28231.html</a><br />
<br />
and have your say.<br />
<br />
w.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Call for Votes: Complementary conditional lines]]></title>
			<link>https://forums.ldraw.org/thread-27024.html</link>
			<pubDate>Wed, 18 Jan 2023 03:02:16 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=11">Travis Cobbs</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-27024.html</guid>
			<description><![CDATA[Please vote on replacing the second paragraph of the <a href="https://www.ldraw.org/article/512.html#overlaps" target="_blank" rel="noopener" class="mycode_url">overlaps section</a> of the "LDraw.org Official Parts Library Specifications" document with the following:<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>All or part of a conditional line (line type 5) may not overlap all or part of any other conditional line (line type 5), with the exception of complementary conditional lines for curved primitives. Complementary conditional lines are placed at the end of curved primitives where those curved primitives may join with either a continuation of the curve, or with other geometry. In this case, the control points that are off of the edge of the curved primitive are placed so they are tangent to the curve.<br />
<br />
If two such curves are placed next to each other (for example to turn a quarter cylinder into a half cylinder), the conditional lines on the edge of each primitive will overlap exactly, and their control points will complement each other such that at most one will be rendered at any given time, and one of the two will always be rendered when appropriate. When other geometry is placed against such a curved primitive, nothing needs to be done if the geometry is tangent to the curve. If it is sloped further, then a complementary conditional line will be placed on the edge of that geometry, with the control points past the edge of the geometry configured to be tangent to the curve, and the two end points of the conditional placed to exactly overlap the complementary conditional line on the edge of the curved primitive.<br />
<br />
Example:<br />
<br />
The first and last conditional lines in a cyli primitive have a control point that is tangent to the cylinder. When two such cyli primitives join, the two conditional lines complement each other, like so:<br />
<br />
<!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forums.ldraw.org/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=9089" target="_blank" title="">comp cond 1.png</a> (Size: 13.6 KB / Downloads: 545)
<!-- end: postbit_attachments_attachment --></blockquote>
]]></description>
			<content:encoded><![CDATA[Please vote on replacing the second paragraph of the <a href="https://www.ldraw.org/article/512.html#overlaps" target="_blank" rel="noopener" class="mycode_url">overlaps section</a> of the "LDraw.org Official Parts Library Specifications" document with the following:<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>All or part of a conditional line (line type 5) may not overlap all or part of any other conditional line (line type 5), with the exception of complementary conditional lines for curved primitives. Complementary conditional lines are placed at the end of curved primitives where those curved primitives may join with either a continuation of the curve, or with other geometry. In this case, the control points that are off of the edge of the curved primitive are placed so they are tangent to the curve.<br />
<br />
If two such curves are placed next to each other (for example to turn a quarter cylinder into a half cylinder), the conditional lines on the edge of each primitive will overlap exactly, and their control points will complement each other such that at most one will be rendered at any given time, and one of the two will always be rendered when appropriate. When other geometry is placed against such a curved primitive, nothing needs to be done if the geometry is tangent to the curve. If it is sloped further, then a complementary conditional line will be placed on the edge of that geometry, with the control points past the edge of the geometry configured to be tangent to the curve, and the two end points of the conditional placed to exactly overlap the complementary conditional line on the edge of the curved primitive.<br />
<br />
Example:<br />
<br />
The first and last conditional lines in a cyli primitive have a control point that is tangent to the cylinder. When two such cyli primitives join, the two conditional lines complement each other, like so:<br />
<br />
<!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="https://forums.ldraw.org/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=9089" target="_blank" title="">comp cond 1.png</a> (Size: 13.6 KB / Downloads: 545)
<!-- end: postbit_attachments_attachment --></blockquote>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Complementary conds]]></title>
			<link>https://forums.ldraw.org/thread-27005.html</link>
			<pubDate>Tue, 10 Jan 2023 09:25:14 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=5">Willy Tschager</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-27005.html</guid>
			<description><![CDATA[Guys,<br />
<br />
please read Travis' proposal:<br />
<br />
<a href="https://forums.ldraw.org/thread-26711-post-48604.html#pid48604" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-26711-po...l#pid48604</a><br />
<br />
have a look at:<br />
<br />
<a href="https://forums.ldraw.org/thread-26711-post-48665.html#pid48665" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-26711-po...l#pid48665</a><br />
<br />
and:<br />
<br />
<a href="https://forums.ldraw.org/thread-24262-post-39346.html#pid39346" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-24262-po...l#pid39346</a><br />
<br />
and ratify. <br />
<br />
And since you're there please say if you're okay with Gerald's pictures:<br />
<br />
<a href="https://forums.ldraw.org/thread-26711-post-48633.html#pid48633" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-26711-po...l#pid48633</a><br />
<br />
w.]]></description>
			<content:encoded><![CDATA[Guys,<br />
<br />
please read Travis' proposal:<br />
<br />
<a href="https://forums.ldraw.org/thread-26711-post-48604.html#pid48604" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-26711-po...l#pid48604</a><br />
<br />
have a look at:<br />
<br />
<a href="https://forums.ldraw.org/thread-26711-post-48665.html#pid48665" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-26711-po...l#pid48665</a><br />
<br />
and:<br />
<br />
<a href="https://forums.ldraw.org/thread-24262-post-39346.html#pid39346" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-24262-po...l#pid39346</a><br />
<br />
and ratify. <br />
<br />
And since you're there please say if you're okay with Gerald's pictures:<br />
<br />
<a href="https://forums.ldraw.org/thread-26711-post-48633.html#pid48633" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-26711-po...l#pid48633</a><br />
<br />
w.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Sticker Shortcut Description]]></title>
			<link>https://forums.ldraw.org/thread-26562.html</link>
			<pubDate>Thu, 14 Jul 2022 20:50:26 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2">Orion Pobursky</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-26562.html</guid>
			<description><![CDATA[I'd like to add the following to the Sticker Shortcuts section of the library spec<br />
<a href="https://www.ldraw.org/article/512.html#sticker_shortcuts" target="_blank" rel="noopener" class="mycode_url">https://www.ldraw.org/article/512.html#s..._shortcuts</a><br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>The description for sticker shortcuts should be in the following format:<br />
<span style="font-style: italic;" class="mycode_i">&lt;base part description&gt;</span> with <span style="font-style: italic;" class="mycode_i">&lt;sticker description&gt;</span> Sticker<br />
<br />
Where:<br />
<span style="font-style: italic;" class="mycode_i">&lt;base part description&gt;</span> is the base part description verbatim<br />
<span style="font-style: italic;" class="mycode_i">&lt;sticker description&gt;</span> is the sticker description after "Sticker &lt;dimensions&gt;|&lt;shape&gt;"<br />
<br />
Example:<br />
Base Part 11477: Slope Brick Curved  2 x  1<br />
Sticker 6142622m: Sticker  1.9 x  0.8 with Black Headlamp on Yellow Background Right<br />
Sticker Shortcut: Slope Brick Curved  2 x  1 with Black Headlamp on Yellow Background Right Sticker</blockquote>
]]></description>
			<content:encoded><![CDATA[I'd like to add the following to the Sticker Shortcuts section of the library spec<br />
<a href="https://www.ldraw.org/article/512.html#sticker_shortcuts" target="_blank" rel="noopener" class="mycode_url">https://www.ldraw.org/article/512.html#s..._shortcuts</a><br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>The description for sticker shortcuts should be in the following format:<br />
<span style="font-style: italic;" class="mycode_i">&lt;base part description&gt;</span> with <span style="font-style: italic;" class="mycode_i">&lt;sticker description&gt;</span> Sticker<br />
<br />
Where:<br />
<span style="font-style: italic;" class="mycode_i">&lt;base part description&gt;</span> is the base part description verbatim<br />
<span style="font-style: italic;" class="mycode_i">&lt;sticker description&gt;</span> is the sticker description after "Sticker &lt;dimensions&gt;|&lt;shape&gt;"<br />
<br />
Example:<br />
Base Part 11477: Slope Brick Curved  2 x  1<br />
Sticker 6142622m: Sticker  1.9 x  0.8 with Black Headlamp on Yellow Background Right<br />
Sticker Shortcut: Slope Brick Curved  2 x  1 with Black Headlamp on Yellow Background Right Sticker</blockquote>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Sticker number clarification]]></title>
			<link>https://forums.ldraw.org/thread-26402.html</link>
			<pubDate>Thu, 26 May 2022 14:23:43 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2">Orion Pobursky</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-26402.html</guid>
			<description><![CDATA[I'm going to add some clarification to the sticker numbering section of the Part Number Spec to state that if the stickers are numbered on the sheet then the corresponding letter (e.g. 1 = a, 2= b) should be used as the letter suffix. I don't think this constitutes a material and, therefore, votable change but we can vote if either of you would like.]]></description>
			<content:encoded><![CDATA[I'm going to add some clarification to the sticker numbering section of the Part Number Spec to state that if the stickers are numbered on the sheet then the corresponding letter (e.g. 1 = a, 2= b) should be used as the letter suffix. I don't think this constitutes a material and, therefore, votable change but we can vote if either of you would like.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Change to the Official Library Spec for Pattern Naming]]></title>
			<link>https://forums.ldraw.org/thread-26036.html</link>
			<pubDate>Sun, 13 Feb 2022 20:26:51 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=2">Orion Pobursky</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-26036.html</guid>
			<description><![CDATA[Based on a discussion on the PT forum, I'd like to proposed the following change to the Official Library Spec.<br />
<br />
<a href="https://www.ldraw.org/article/512.html#pattern_desc" target="_blank" rel="noopener" class="mycode_url">https://www.ldraw.org/article/512.html#pattern_desc</a><br />
(changes in bold)<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>The description of a patterned part should in the following format:<br />
&lt;base part description&gt; with &lt;pattern description&gt; Pattern<br />
<br />
Where:<br />
<ul class="mycode_list"><li>    &lt;base part description&gt; is the description of the non-patterned version of the part. <span style="font-weight: bold;" class="mycode_b">Note: For parts with mold variants (e.g. tiles with or without groove), the additional qualifier for the mold is only required if the same pattern is printed on more than one variation. Example: "Minifig Head with Solid Stud with ... Pattern" can be shortened to "Minifig Head with ... Pattern" if the pattern being modeled only appears on the "Solid Stud" variation.</span><br />
</li>
<li>    &lt;pattern description&gt; is a reasonably detailed description of the pattern. If unsure, use of the description on other inventory websites is encouraged.<br />
</li>
</ul>
</blockquote>
]]></description>
			<content:encoded><![CDATA[Based on a discussion on the PT forum, I'd like to proposed the following change to the Official Library Spec.<br />
<br />
<a href="https://www.ldraw.org/article/512.html#pattern_desc" target="_blank" rel="noopener" class="mycode_url">https://www.ldraw.org/article/512.html#pattern_desc</a><br />
(changes in bold)<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>The description of a patterned part should in the following format:<br />
&lt;base part description&gt; with &lt;pattern description&gt; Pattern<br />
<br />
Where:<br />
<ul class="mycode_list"><li>    &lt;base part description&gt; is the description of the non-patterned version of the part. <span style="font-weight: bold;" class="mycode_b">Note: For parts with mold variants (e.g. tiles with or without groove), the additional qualifier for the mold is only required if the same pattern is printed on more than one variation. Example: "Minifig Head with Solid Stud with ... Pattern" can be shortened to "Minifig Head with ... Pattern" if the pattern being modeled only appears on the "Solid Stud" variation.</span><br />
</li>
<li>    &lt;pattern description&gt; is a reasonably detailed description of the pattern. If unsure, use of the description on other inventory websites is encouraged.<br />
</li>
</ul>
</blockquote>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Define a standard for helper parts]]></title>
			<link>https://forums.ldraw.org/thread-24865.html</link>
			<pubDate>Fri, 13 Aug 2021 11:18:23 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=5">Willy Tschager</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-24865.html</guid>
			<description><![CDATA[Guys,<br />
<br />
in response to this post:<br />
<br />
<a href="https://forums.ldraw.org/thread-24732.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-24732.html</a><br />
<br />
the majority of the SteerCo is in favour to add helper parts to the library but before a final vote we would like you to define a standard for these parts such as:<br />
<br />
Naming convention<br />
Category<br />
Edges Yes/No on 2D helpers<br />
Edges Yes/No on 3D helpers<br />
<br />
The general idea would be to add these to the main library as the separate Alias and Physical parts library hasn't worked very well. In addition these parts shouldn't go through the PT for certification but be usable in all editors. Any input from your side is welcome.<br />
<br />
Some example of helpers can be found here:<br />
<br />
<a href="http://www.holly-wood.it/ldraw/helper-en.html" target="_blank" rel="noopener" class="mycode_url">http://www.holly-wood.it/ldraw/helper-en.html</a><br />
<br />
w.]]></description>
			<content:encoded><![CDATA[Guys,<br />
<br />
in response to this post:<br />
<br />
<a href="https://forums.ldraw.org/thread-24732.html" target="_blank" rel="noopener" class="mycode_url">https://forums.ldraw.org/thread-24732.html</a><br />
<br />
the majority of the SteerCo is in favour to add helper parts to the library but before a final vote we would like you to define a standard for these parts such as:<br />
<br />
Naming convention<br />
Category<br />
Edges Yes/No on 2D helpers<br />
Edges Yes/No on 3D helpers<br />
<br />
The general idea would be to add these to the main library as the separate Alias and Physical parts library hasn't worked very well. In addition these parts shouldn't go through the PT for certification but be usable in all editors. Any input from your side is welcome.<br />
<br />
Some example of helpers can be found here:<br />
<br />
<a href="http://www.holly-wood.it/ldraw/helper-en.html" target="_blank" rel="noopener" class="mycode_url">http://www.holly-wood.it/ldraw/helper-en.html</a><br />
<br />
w.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Call for Votes: Sticker spec clarifications 2]]></title>
			<link>https://forums.ldraw.org/thread-24823.html</link>
			<pubDate>Tue, 10 Aug 2021 01:50:19 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=11">Travis Cobbs</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-24823.html</guid>
			<description><![CDATA[Please vote on adding the following clarifications to the <a href="https://www.ldraw.org/article/512.html" target="_blank" rel="noopener" class="mycode_url">LDraw.org Official Parts Library Specifications</a>. The quoted text would be added verbatim.<br />
<br />
<br />
Clarification to <span style="font-weight: bold;" class="mycode_b"><a href="https://www.ldraw.org/article/512.html#sticker_geo" target="_blank" rel="noopener" class="mycode_url">Sticker Geometry</a>:</span><br />
<blockquote class="mycode_quote"><cite>Quote:</cite>For stickers printed on a transparent medium, the type 1, 3, and 4 lines that comprise the pattern shall be preceded by a 0 BFC NOCLIP statement. If there is non-pattern geometry after the pattern geometry, the pattern geometry shall be ended by a 0 BFC CLIP statement.<br />
<br />
The sticker should be oriented such that the top of the pattern aligns with the +Z axis. Exceptions to this rule may be made on a case by case basis.</blockquote>
<br />
New <span style="font-weight: bold;" class="mycode_b">Sticker !KEYWORDS Entry</span> section immediately following the <span style="font-weight: bold;" class="mycode_b"><a href="https://www.ldraw.org/article/512.html#sticker_desc" target="_blank" rel="noopener" class="mycode_url">Sticker Description</a></span> section:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>All stickers and sticker shortcuts should, at a minimum, include at least one !KEYWORDS entry in the form of <span style="font-style: italic;" class="mycode_i">Set &lt;set number&gt;</span> where &lt;set number&gt; is the number of an official LEGO set in which that sticker appears. Only one set need be listed, but more may be if desired.</blockquote>
]]></description>
			<content:encoded><![CDATA[Please vote on adding the following clarifications to the <a href="https://www.ldraw.org/article/512.html" target="_blank" rel="noopener" class="mycode_url">LDraw.org Official Parts Library Specifications</a>. The quoted text would be added verbatim.<br />
<br />
<br />
Clarification to <span style="font-weight: bold;" class="mycode_b"><a href="https://www.ldraw.org/article/512.html#sticker_geo" target="_blank" rel="noopener" class="mycode_url">Sticker Geometry</a>:</span><br />
<blockquote class="mycode_quote"><cite>Quote:</cite>For stickers printed on a transparent medium, the type 1, 3, and 4 lines that comprise the pattern shall be preceded by a 0 BFC NOCLIP statement. If there is non-pattern geometry after the pattern geometry, the pattern geometry shall be ended by a 0 BFC CLIP statement.<br />
<br />
The sticker should be oriented such that the top of the pattern aligns with the +Z axis. Exceptions to this rule may be made on a case by case basis.</blockquote>
<br />
New <span style="font-weight: bold;" class="mycode_b">Sticker !KEYWORDS Entry</span> section immediately following the <span style="font-weight: bold;" class="mycode_b"><a href="https://www.ldraw.org/article/512.html#sticker_desc" target="_blank" rel="noopener" class="mycode_url">Sticker Description</a></span> section:<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>All stickers and sticker shortcuts should, at a minimum, include at least one !KEYWORDS entry in the form of <span style="font-style: italic;" class="mycode_i">Set &lt;set number&gt;</span> where &lt;set number&gt; is the number of an official LEGO set in which that sticker appears. Only one set need be listed, but more may be if desired.</blockquote>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Call for votes: Sticker spec clarifications]]></title>
			<link>https://forums.ldraw.org/thread-24745.html</link>
			<pubDate>Wed, 21 Jul 2021 15:57:00 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://forums.ldraw.org/member.php?action=profile&uid=11">Travis Cobbs</a>]]></dc:creator>
			<guid isPermaLink="false">https://forums.ldraw.org/thread-24745.html</guid>
			<description><![CDATA[Please vote on adding the following clarifications to the <a href="https://www.ldraw.org/article/512.html" target="_blank" rel="noopener" class="mycode_url">LDraw.org Official Parts Library Specifications</a>. The quoted text would be added verbatim. (Note that I made minor tweaks to Orion's original text.)<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Clarification to <a href="https://www.ldraw.org/article/512.html#sticker_geo" target="_blank" rel="noopener" class="mycode_url">Sticker Geometry</a>:</span><br />
<blockquote class="mycode_quote"><cite>Quote:</cite>For stickers printed on a transparent medium, the type 1, 3, and 4 lines that comprise the pattern shall be preceded by a 0 BFC NOCLIP statement and ended by a 0 BFC CLIP statement.<br />
<br />
The pattern should be oriented such that the top of the pattern aligns with the +Z axis. Exceptions to this rule may be made on a case by case basis.</blockquote>
<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Clarification to <a href="https://www.ldraw.org/article/512.html#sticker_shortcuts" target="_blank" rel="noopener" class="mycode_url">Sticker Shortcuts</a>:</span><br />
- Require a !KEYWORDS entry with text similar to <a href="https://www.ldraw.org/article/512.html#pattern_key" target="_blank" rel="noopener" class="mycode_url">Pattern !KEYWORDS Entry</a>:<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>A sticker shortcut should, at a minimum, include at least one !KEYWORDS entry in the form of <span style="font-style: italic;" class="mycode_i">Set &lt;set number&gt;</span> where &lt;set number&gt; is the number of an official LEGO set in which that sticker appears. Only one set need be listed, but more may be if desired.</blockquote>
]]></description>
			<content:encoded><![CDATA[Please vote on adding the following clarifications to the <a href="https://www.ldraw.org/article/512.html" target="_blank" rel="noopener" class="mycode_url">LDraw.org Official Parts Library Specifications</a>. The quoted text would be added verbatim. (Note that I made minor tweaks to Orion's original text.)<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Clarification to <a href="https://www.ldraw.org/article/512.html#sticker_geo" target="_blank" rel="noopener" class="mycode_url">Sticker Geometry</a>:</span><br />
<blockquote class="mycode_quote"><cite>Quote:</cite>For stickers printed on a transparent medium, the type 1, 3, and 4 lines that comprise the pattern shall be preceded by a 0 BFC NOCLIP statement and ended by a 0 BFC CLIP statement.<br />
<br />
The pattern should be oriented such that the top of the pattern aligns with the +Z axis. Exceptions to this rule may be made on a case by case basis.</blockquote>
<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Clarification to <a href="https://www.ldraw.org/article/512.html#sticker_shortcuts" target="_blank" rel="noopener" class="mycode_url">Sticker Shortcuts</a>:</span><br />
- Require a !KEYWORDS entry with text similar to <a href="https://www.ldraw.org/article/512.html#pattern_key" target="_blank" rel="noopener" class="mycode_url">Pattern !KEYWORDS Entry</a>:<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>A sticker shortcut should, at a minimum, include at least one !KEYWORDS entry in the form of <span style="font-style: italic;" class="mycode_i">Set &lt;set number&gt;</span> where &lt;set number&gt; is the number of an official LEGO set in which that sticker appears. Only one set need be listed, but more may be if desired.</blockquote>
]]></content:encoded>
		</item>
	</channel>
</rss>