<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 334: Mailmark 2D postcode format.</title><link href="https://sourceforge.net/p/zint/tickets/334/" rel="alternate"/><link href="https://sourceforge.net/p/zint/tickets/334/feed.atom" rel="self"/><id>https://sourceforge.net/p/zint/tickets/334/</id><updated>2026-03-20T14:46:55.164000Z</updated><subtitle>Recent changes to 334: Mailmark 2D postcode format.</subtitle><entry><title>#334 Mailmark 2D postcode format.</title><link href="https://sourceforge.net/p/zint/tickets/334/?limit=25#a009" rel="alternate"/><published>2026-03-20T14:46:55.164000Z</published><updated>2026-03-20T14:46:55.164000Z</updated><author><name>Git Lost</name><uri>https://sourceforge.net/u/gitlost/</uri></author><id>https://sourceforge.netabd35199bc0e847b357f60a1bb1da7a6d59bb3ae</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>#334 Mailmark 2D postcode format.</title><link href="https://sourceforge.net/p/zint/tickets/334/?limit=25#6659" rel="alternate"/><published>2025-04-08T23:22:16.939000Z</published><updated>2025-04-08T23:22:16.939000Z</updated><author><name>Git Lost</name><uri>https://sourceforge.net/u/gitlost/</uri></author><id>https://sourceforge.netcb0be9472d9caed90b6b8130f43005754f067583</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks Milton, hopefully commit &lt;a class="alink" href="/p/zint/code/ci/182c84fa4d348d63b43b0305a9bca0f712666e0f/"&gt;[182c84]&lt;/a&gt; has addressed this. There's a later document available at &lt;a href="https://www.royalmail.com/sites/royalmail.com/files/2024-12/Mailmark-Barcode-definition-document-181224-v1_5-final.pdf" rel="nofollow"&gt;https://www.royalmail.com/sites/royalmail.com/files/2024-12/Mailmark-Barcode-definition-document-181224-v1_5-final.pdf&lt;/a&gt;, but it doesn't change the DPS/RTS stuff, all the best, Martin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Mailmark 2D postcode format.</title><link href="https://sourceforge.net/p/zint/tickets/334/" rel="alternate"/><published>2025-04-08T03:46:41.995000Z</published><updated>2025-04-08T03:46:41.995000Z</updated><author><name>Milton Neal</name><uri>https://sourceforge.net/u/miltonneal/</uri></author><id>https://sourceforge.neta63d951a22c64366209c3331fba3f9a2e0d41912</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Looking at the code for generating Mailmark 2D barcodes, the Destination post code +  Destination Point format checking uses the same peice code as for Mailmark  4 state(CL) check.  According to to &lt;a href="https://www.royalmailwholesale.com/mint-project/uploads/337237901.pdf" rel="nofollow"&gt;https://www.royalmailwholesale.com/mint-project/uploads/337237901.pdf&lt;/a&gt;&lt;br/&gt;
Mailmark 2D uses different post code formats, and also appears not to used the reduced alpha set&lt;br/&gt;
(–C,I,K,M,O or V).  Also according to this document, the Return To Sender post code only 7 characters, ie no DPS. The Zint code adds a dummy DPS then varifies it with the same code as for Mailmark  4 state(CL). The above document is dated 25/09/2020, so its reasonably recent, or is there another document I should be referencing?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Mailmark 2D postcode format.</title><link href="https://sourceforge.net/p/zint/tickets/334/" rel="alternate"/><published>2025-04-08T03:46:41.995000Z</published><updated>2025-04-08T03:46:41.995000Z</updated><author><name>Milton Neal</name><uri>https://sourceforge.net/u/miltonneal/</uri></author><id>https://sourceforge.neta930fc3b1488dffb01b267d1592e02b93f506351</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 334 has been modified: Mailmark 2D postcode format.&lt;br/&gt;
Edited By: Git Lost (gitlost)&lt;br/&gt;
Status updated: 'open' =&amp;gt; 'closed'&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>