Skip to content

Commit

Permalink
[FIX] fix rst syntax in readme fragments
Browse files Browse the repository at this point in the history
  • Loading branch information
huguesdk committed Jan 23, 2024
1 parent c80aded commit 1468640
Show file tree
Hide file tree
Showing 4 changed files with 18 additions and 18 deletions.
12 changes: 6 additions & 6 deletions member_card/README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -30,8 +30,8 @@ Create a member card and link it to a partner.
- Creating a card generates a barcode, witch is then displayed on the member card
- The "Force Barcode" option allows to set a specific barcode instead
- A partner's barcode is computed from the last active member card
- Adds a field `member_card_logo` on the company allowing to upload an image
- The card template displays the `member_card_logo` image
- Adds a field ``member_card_logo`` on the company allowing to upload an image
- The card template displays the ``member_card_logo`` image
- A boolean "Print Member card?" allows to flag partners for whom you need to print new cards.
- The wizards "Request member card printing" and "Set member card as printed" allow to mass check and uncheck the "Print Member Card?" flag.
- If the point of sale is installed, the generated barcode matches customer pattern rule.
Expand All @@ -53,14 +53,14 @@ Known issues / Roadmap
- factor out wizards "request member card printing" and "set member card as printed"

- it was used to request a batch of card to print but has no link to the actual template
- use `barcodes_generator_abstract` from the OCA to generate barcodes
- use ``barcodes_generator_abstract`` from the OCA to generate barcodes

**Customer Barcodes**

- odoo/base adds `barcode` field on `res.partner`.
- member_card also adds `barcode` but defines it as computed and stored.
- odoo/base adds ``barcode`` field on ``res.partner``.
- member_card also adds ``barcode`` but defines it as computed and stored.

On `member_card` install, odoo will compute the values for barcode field and **erase pre-existing values**.
On ``member_card`` install, odoo will compute the values for barcode field and **erase pre-existing values**.
It will also make it impossible to load data on that field.

Bug Tracker
Expand Down
4 changes: 2 additions & 2 deletions member_card/readme/DESCRIPTION.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ Create a member card and link it to a partner.
- Creating a card generates a barcode, witch is then displayed on the member card
- The "Force Barcode" option allows to set a specific barcode instead
- A partner's barcode is computed from the last active member card
- Adds a field `member_card_logo` on the company allowing to upload an image
- The card template displays the `member_card_logo` image
- Adds a field ``member_card_logo`` on the company allowing to upload an image
- The card template displays the ``member_card_logo`` image
- A boolean "Print Member card?" allows to flag partners for whom you need to print new cards.
- The wizards "Request member card printing" and "Set member card as printed" allow to mass check and uncheck the "Print Member Card?" flag.
- If the point of sale is installed, the generated barcode matches customer pattern rule.
Expand Down
8 changes: 4 additions & 4 deletions member_card/readme/ROADMAP.rst
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
- factor out wizards "request member card printing" and "set member card as printed"

- it was used to request a batch of card to print but has no link to the actual template
- use `barcodes_generator_abstract` from the OCA to generate barcodes
- use ``barcodes_generator_abstract`` from the OCA to generate barcodes

**Customer Barcodes**

- odoo/base adds `barcode` field on `res.partner`.
- member_card also adds `barcode` but defines it as computed and stored.
- odoo/base adds ``barcode`` field on ``res.partner``.
- member_card also adds ``barcode`` but defines it as computed and stored.

On `member_card` install, odoo will compute the values for barcode field and **erase pre-existing values**.
On ``member_card`` install, odoo will compute the values for barcode field and **erase pre-existing values**.
It will also make it impossible to load data on that field.
12 changes: 6 additions & 6 deletions member_card/static/description/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -377,8 +377,8 @@ <h1 class="title">Member Card</h1>
<li>Creating a card generates a barcode, witch is then displayed on the member card</li>
<li>The “Force Barcode” option allows to set a specific barcode instead</li>
<li>A partner’s barcode is computed from the last active member card</li>
<li>Adds a field <cite>member_card_logo</cite> on the company allowing to upload an image</li>
<li>The card template displays the <cite>member_card_logo</cite> image</li>
<li>Adds a field <tt class="docutils literal">member_card_logo</tt> on the company allowing to upload an image</li>
<li>The card template displays the <tt class="docutils literal">member_card_logo</tt> image</li>
<li>A boolean “Print Member card?” allows to flag partners for whom you need to print new cards.</li>
<li>The wizards “Request member card printing” and “Set member card as printed” allow to mass check and uncheck the “Print Member Card?” flag.</li>
<li>If the point of sale is installed, the generated barcode matches customer pattern rule.</li>
Expand Down Expand Up @@ -406,14 +406,14 @@ <h1><a class="toc-backref" href="#toc-entry-1">Known issues / Roadmap</a></h1>
<li>it was used to request a batch of card to print but has no link to the actual template</li>
</ul>
</li>
<li>use <cite>barcodes_generator_abstract</cite> from the OCA to generate barcodes</li>
<li>use <tt class="docutils literal">barcodes_generator_abstract</tt> from the OCA to generate barcodes</li>
</ul>
<p><strong>Customer Barcodes</strong></p>
<ul class="simple">
<li>odoo/base adds <cite>barcode</cite> field on <cite>res.partner</cite>.</li>
<li>member_card also adds <cite>barcode</cite> but defines it as computed and stored.</li>
<li>odoo/base adds <tt class="docutils literal">barcode</tt> field on <tt class="docutils literal">res.partner</tt>.</li>
<li>member_card also adds <tt class="docutils literal">barcode</tt> but defines it as computed and stored.</li>
</ul>
<p>On <cite>member_card</cite> install, odoo will compute the values for barcode field and <strong>erase pre-existing values</strong>.
<p>On <tt class="docutils literal">member_card</tt> install, odoo will compute the values for barcode field and <strong>erase pre-existing values</strong>.
It will also make it impossible to load data on that field.</p>
</div>
<div class="section" id="bug-tracker">
Expand Down

0 comments on commit 1468640

Please sign in to comment.