Deck will export as Anki Collection Package but not Anki Deck Package

ixti · July 3, 2022, 12:51am

I’ve created a deck that will export successfully as an Anki Collection Package, but not as an Anki Deck Package. When I try and export this deck as an Anki Deck Package the error I get is:

Card template 2 in notetype ‘01 IPA’ has a problem. The front side is identical to card template 1.

I have no idea what to do to get around this.

The problem deck otherwise seems to work when I get it successfully into Anki using an Anki Collection Package.

I’ve included a DropBox link that allows downloading of an Anki Collection Package that contains two decks, one of which is the problem deck, if an agent wouldn’t mind downloading it and taking a look.

I have no idea what to do to get around this.

https:–www.dropbox.com-t-nH4seUtUMVw6aNx5

The DropBox link will expire 2022 July 09. I can renew it.

The two decks contained in the Anki Collection Package are “01 IPA deck information” and “02 IPA”. The deck I am having problems with is “02 IPA”.

BlackBeans · July 3, 2022, 6:11am

This error message means your note type is has a problem, which is that you have two card templates (in your case, card template 1 and card template 2) that have the same front side. This is a problem because either:

Their back side are identical too, in which case you are duplicating cards, which will bypass Anki’s evaluation of your memorization.
Their back side are different, in which case when you are prompted for that front side, you can’t know which answer to give, because two cards with the same front side but expecting different answers exist.

The solution is quite easy: remove the second card template (you probably created it by mistake anyways). To do so, Browse, then select a note of type 01 IPA, then click on Cards, and at the top you should see the list of the card templates. Select the card template your want to remove, the Options > Remove Card Template.

ixti · July 5, 2022, 6:29pm

I checked out what I’ve got going on with the cards of the Note Type associated with the deck that is having the problems. Simply deleting Card Types does not seem to be a solution for me. If having Card Types with identical front sides is a problem, I’m not sure how I will resolve the situation.

The Note Type that is an issue has 6 Card Types. Within these Card Types front sides and back sides are duplicated, but no Card Type is identical if you consider both back and front sides.

I currently have five files of distinct coding for this Note Type.

front card - glyph first

front card - name first

back card - vowels

back card - consonants

back card - other symbols

The six cards of the Note Type in question combine the card coding as follows:

    FRONT CARD       BACK CARD

1// … 1. glyph first — + — 3. vowels
2// … 1. glyph first — + — 4. consonants
3// … 1. glyph first — + — 5. other symbols

4// … 2. name first — + — 3. vowels
5// … 2. name first — + — 4. consonants
6// … 2. name first — + — 5. other symbols

So, if front sides or front and back sides of cards being in duplicate is a problem, how would I get around the current problem. For my situation duplication works with respect to what I need to happen, but if Anki does not accept any card side duplication, what should I do? Would sticking some nonsense coding that doesn’t get read break the duplication problem? Or would I want some conditional coding in each body of coding to differentiate the Note information allowing me to reduce the number of cards? This last option seems potentially difficult to do.

BlackBeans · July 5, 2022, 6:35pm

Could you post the actual front templates? Besides, if two card templates are actually identical, there is an issue.

ixti · July 5, 2022, 7:00pm

Here is the coding for the front card when you want to display the glyph on the front card.

**<!****================================================**

**IPA FRONT CARD**

**glyph first**

**=================================================****>**

<!DOCTYPE html>

<html>

**<head>**

<meta name= "viewport" content= "width=device-width, initial-scale=1.0" >

**</head>**

**<body>**

<!------------------------------------------------------------------------------------------------------>

<!__________________________________________________

**FRONT CARD LANDSCAPE VIEW**

___________________________________________________>

<div style= "font-family: times; font-size: 25vw; text-align: center; padding: 2vw 0 2vw 0 " class= "port timesreg midlime" > {{symbol}} </div>

<!__________________________________________________

**FRONT CARD PORTRAIT VIEW**

___________________________________________________>

<div style= "font-family: times; font-size: 50vw; text-align: center; padding: 2vw 0 1vw 0 " class= "land timesreg midlime" > {{symbol}} </div>

<!------------------------------------------------------------------------------------------------------>

**</body>**

</html>

<!__________________________________________________>

<!__________________________________________________>

Here is the coding for the front card when you want to display the glyph name on the front card.

**<!****================================================**

**IPA FRONT CARD**

**name first**

**=================================================****>**

<!DOCTYPE html>

<html>

**<head>**

<meta name= "viewport" content= "width=device-width, initial-scale=1.0" >

**</head>**

**<body>**

<!------------------------------------------------------------------------------------------------------>

<!__________________________________________________

**FRONT CARD LANDSCAPE VIEW**

___________________________________________________>

<div style="font-family: segl;" class= "segl f6 cyan txtcenter pad_7p5_3_7p5_3 port" > {{name}} </div>

<!__________________________________________________

**FRONT CARD PORTRAIT VIEW**

___________________________________________________>

<div style="font-family: segl;" class= " segl f12 cyan txtcenter pad_30_3_30_3 land" > {{name}} </div>

<!------------------------------------------------------------------------------------------------------>

**</body>**

</html>

<!__________________________________________________>

<!__________________________________________________>

ixti · July 5, 2022, 7:19pm

I forgot to send the Styling Card coding which you may want.

I learned HTML and CSS just to be able to create nicer Anki cards. I’m quite a novice.

I created one standard or template body of coding for the Styling Card to cover all possibilities and to be used with any Anki Decks I create. Since I’m not creating Anki decks often, I’ve actually forgotten a lot of how the coding works.

/*==============================
MY ANKI STYLING STANDARD

/* begun 2018-10-17w
 
this version is current as of :
2020 Nov 27 Friday
==============================*/

































































































/* MARGIN */

/* This removes default margins at the sides as well as eliminating to some degree a margin at the top of the view area. */
.card {margin: -1vw 0 0 0;}

/* FURTHER NOTE FOR MARGIN 
The coding under MARGIN on this page is useful if you have tables on cards. It minimizes spaces at the edge of the screen to let any table fit the screen more completely. If you don't have tables, you might want to get rid of the coding under MARGIN. */
/* NOTE: 
Line breaks will work for HTML coding but page breaks will not. */
























/* TO CAUSE <PRE> ELEMENT TO TEXT WRAP 
The <pre> element allows content as it is written in coding, with spaces and line spacing, to appear that way in the output. 

This coding will cause content in the <pre> element to also wrap, which it does not do otherwise.*/

pre {
    white-space: pre-wrap;
    white-space: -moz-pre-wrap;
    white-space: -pre-wrap;
    white-space: -o-pre-wrap;
    word-wrap: break-word;
}
 






/* PADDING */

/* This defines the convention used for padding. */

/* ORDER OF SIDES :
top  right  bottom  left */


{padding: 0 0 0 0;}

{padding: #vw #vw #vw #vw;}

{padding: #.#vw #.#vw #.#vw #.#vw;}














/* TABLE FORMATTING */

/* This automatically collapses the double borders of all tables in HTML.*/

table, th, td { border-collapse: collapse;}





/*TABLE OF CONTENTS
 
Margin  1
Table Formatting  1
 
TABLE OF CONTENTS  1
 
Width  2
Minimum Width  2
Height   2
Minimum Height  2
Maximum Height  2
Body Background Color  3
 
Background Color  3
--- Black, White and Greys  3
--- Beige  4
--- Brown  4
--- Miscellaneous  4
--- Bright Colors  4
 
Vertical Border Between Table Cells  6
 

 
Font Color  6
--- Black and White  6
--- Greys  6
--- Beige  7
--- Brown  7
--- Miscellaneous  7
--- Bright Colors  7
 
Font Embedding  9
Font Family  9
Font Sizes  10
Text Alignment  10
 
Padding  10
--- bottom  10
--- bottom and sides 10
--- top  10
--- top and bottom 10
--- top bottom and sides  10
 
Centering in Viewing Area  10
--- Horizontal and Vertical  10
--- Vertical  10
 


Media Query
--- ignore landscape  10
--- ignore portrait  10 */











































/* WIDTH */

{width: #vw;}
{width: #.#vw;}


/* MINIMUM WIDTH */

{min-width: #vw;}
{min-width: #.#vw;}


/* HEIGHT */

{height: #vw;}
{height: #.#vw;}









/* MINIMUM HEIGHT */

/* NOTE ON TABLE ROW HEIGHTS: If you want to specify a minimum height for table rows, you don't have to use the min-height command. You can just use the regular height command and if there is a larger size or amount of text in any of the row's cells, the row will expand to accommodate the text. You don't need the min-height command. */

{min-height: #vw;}
{min-height: #.#vw;}


/* MAXIMUM HEIGHT */

/* I've created this to keep the height of heading rows the same across a table. */

{max-height: #vw;}
{max-height: #.#vw;}












































































/* BODY BACKGROUND COLOR */

/* BODY BACKGROUND */
/* Background color for body which means the entire pane surface. This may automatically apply to the output. */

/* body background black HSV-0.0.0 */
body {background-color: black;}



/*  BACKGROUND COLOR */

/* BLACK, WHITE AND GREYS */

/* HSV
Black, white and greys are named numerically based on the Value parameter of HSV color space notation. White is 100, black is 000 and greys range between 100 and 0.
H  = hue  S = saturation V = value (lightness)
Each HTML color notation code will represent about 4 decimal places with the HSV V values of greys. HTML 1a1a1a will work for HSV value of 10.0 to 10.3.

HSL and HCL are similar color space systems with the L in HSL representing lightness (value) and the C in HCL representing colorfulness (saturation).


/* GREYS */
 
/* background white 100 HSV-0.0.100 */
.bgwhite {background-color: #ffffff;}

/* background grey 95 HSV-0.0.95 */
.bgrey95 {
background-color: #f2f2f2;}

/* background grey 90 HSV-0.0.90 */
.bggrey90 {background-color: #e6e6e6;}

/* background grey 85 HSV-0.0.85 */
.bgrey85 {background-color: #d9d9d9;}

/* background grey 80 HSV-0.0.80 */
.bggrey80 {background-color: #cccccc;}

/* background grey 75 HSV-0.0.75 */
.bgrey75 {background-color: #bfbfbf;}
/* background grey 70 HSV-0.0.70 */
.bggrey70 {background-color: #b3b3b3;}

/* background grey 65 HSV-0.0.65 */
.bgrey65 {background-color: #a6a6a6;}

/* background grey 60 HSV-0.0.60 */
.bggrey60 {background-color: #999999;}

/* background grey 55 HSV-0.0.55 */
.bgrey55 {background-color: #8c8c8c;}
/* background grey 50 HSV-0.0.50 */
.bggrey50 {background-color: #808080;}

/* background grey 45 HSV-0.0.45 */
.bgrey45 {background-color: #xxxxxx;}

/* background grey 40 HSV-0.0.40 */
.bggrey40 {background-color: #666666;}

/* background grey 35 HSV-0.0.35 */
.bgrey35 {background-color: #595959;}
/* background grey 30 HSV-0.0.30*/
.bggrey30 {background-color: #4d4d4d;}

/* background grey 25 HSV-0.0.25 */
.bggrey25 {background-color: #404040;}

/* background grey 20 HSV-0.0.20 */
.bggrey20 {background-color: #333333;}

/* background grey 15 HSV-0.0.15 */
.bggrey15 {background-color: #262626;}

/* background grey 12.5 HSV-0.0.10
.bggrey12p5 {background-color: #202020;}

/* background grey 10 HSV-0.0.10 */
.bggrey10 {background-color: #1a1a1a;}

/* background grey 8 HSV-0.0.8 */
.bggrey8 {background-color: #141414;}

/* background grey 5 HSV-0.0.5 */
.bggrey5 {background-color: #0d0d0d;}
/* background grey 3 HSV-0.0.3. This is too dark for my cell phone. */
.bggrey3 {background-color: #080808;}

/* background black 000 HSV-0.0.0 */
.bgblack {background-color: #000000;}


/* BEIGE */

/* background beige HSV-42.19.69. My first more vivid beige. */
.bgbeige {background-color: #b1a78f;}

/* background beige dark HSV-43.15.49. Similar to beige a but a bit darker. */
.bgbeigedk {background-color: #91866b;}

/* background beige grey 1. Similar to beige a but less saturation. HSV-42.12.65 */
.bgbeigegr1 {background-color: #a6a092;}

/* background beige grey dark 1. Similar to beige c but darker. HSV-42.20.50 */
.bgbeigegr1dk {background-color: # 807866;}


/* BROWN */

/* background yellowy-mid-brown from MS Word HSV-45.100.75 */
.bgbrownyel {background-color: #c09100;}
/* background mid-brown from MS Word HSV-45.100.50 */
.bgbrownmed {background-color: #806000;}
/* background darker brown 1 HSV-45.100.25 */
.bgbrowndk1 {background-color: #403000;}
/* background darker brown 2 HSV-45.100.12 */
.bgbrowndk2 {background-color: #1f1700;}






/* MISCELLANEOUS */

/* background my blue violet HSV-237.66.100 */
.bgviolet {background-color: #575fff;}

/* background mid-turquoise HSV-175.100.65 */
.bgmidturq {background-color: #00a698;}

/* background mid-lime HSV-75.100.80 */
.bgmidlime {background-color: #99cc00;}

/* background sap HSV-86.54.51 */
.bgsap {background-color: #64823c;}

/* background brown sap HSV-56.76.38 */
.bgbrsap {background-color: #615c17;}

/* background pink HSV-320.60.100 */
.bgpink {background-color: #ff66cc;}

/* background peach HSV-10.60.100 */
.bgpeach {background-color: #ff8066;}
/* background pastel turquoise HSV-10.60.100. This might get called baby blue. */
.bgturqpast {background-color: #8cffec;}



/* BRIGHT COLORS */

/* background red HSV-0.100.100 */
.bgred {background-color: #00ffff;}

/* background dark red or burgundy HSV-0.100.65 */
.bgreddk {background-color: #a60000;}

/* background red-orange HSV-15.100.100 */
.bgorangered {background-color: #ff4000;}

/* background orange HSV-30.100.100 */
.bgorange {background-color: #ff7f00;}

/* background orange bright HSV-45.100.100. Like the orange in MS Word. */
.bgorangebr {background-color: #ffbf00;}

/* background yellow dark HSV-53.100.100. This is a bit darker—more on the orange side. Maybe a canary yellow. */
.bgyellow {background-color: #ffe100;}

/* background yellow HSV-60.100.100. This is more like lime yellow. */
.bgyellowbr {background-color: #ffff00;}

/* background lime brighter 3 HSV-67.100.100 */
.bglimebr3 {background-color: #e1ff00;}

/* background lime bighter 2 HSV-75.100.100 */
.bglimebr2 {background-color: #bfff00;}

/* background lime brighter 1 HSV-82.100.100 */
.bglimebr1 {background-color: #a2ff00;}

/* background lime HSV-90.100.100 */
.bglime {background-color: #7fff00;}

/* background green HSV-120.100.100. This is quite a bright green. */
.bggreen {background-color: #00ff00;}

/* background turquoise green HSV-150.100.100 */
.bgturqgr {background-color: #00ff7f;}

/* background turquoise HSV-165.100.100 */
.bgturq {background-color: #00ffbf;}

/* background cyan HSV-180.100.100 */
.bgcyan {background-color: #00ffff;}

/* background dark cyan HSV-195.100.100 */
.bgcyandk {background-color: #00bfff;}

/* background azure HSV-210.100.100. This might be like a bright cerulean blue. */
.bgazure {background-color: #007fff;}

/* background dark azure HSV-225.100.100 */
.bgazuredk {background-color: #0040ff;}

/* background blue HSV-240.100.100. This is like an ultramarine blue which is fairly dark. */
.bgblue {background-color: #0000ff;}
/* background navy blue HSV-240.100.65. */
.bgnavyblue {background-color: #0000a6;}

/* background purple blue HSV-248.100.100. Some people might call this violet or indigo. */
.bgbluepurp {background-color: #2200ff;}

/* background purple dark 2 255-180.100.100. This might be considered a standard darker purple although it doesn't fall on the 30 multiple for hue. */
.bgpurpledk2 {background-color: #4000ff;}

/* background purple dark 1 HSV-263.100.100. This is a third tier color, neither a 30 or 15 hue multiple but can almost seem more middle of the road than purple at 270. */
.bgpurpledk1 {background-color: #6200ff;}

/* background purple HSV-270.100.100. This color is a 30 multiple hue but could almost seem more of a magenta purple. */
.bgpurple {background-color: #7f00ff;}
/* background magenta HSV-285.100.100. This is a second tier hue at a 15 hue multiple but seems to be a pretty good magenta candidate. */
.bgmagenta {background-color: #bf00ff;}

/* background magenta bright HSV-300.100.100. The chart calls this magenta but I think it might be more like a hot pink. */
.bgmagentabr {background-color: #ff00ff;}

/* background pink red HSV-330.100.100 */
.bgredpink {background-color: #ff007f;}


















/* VERTICAL BORDER BETWEEN TABLE CELLS */

/* This is the border placed at the right end of cells in some tables. These tables usually have thick dark grey borders and this is for vertical borders that divide cells.
The numbers correspond to the V of the HSV color space. */ 


/* vertical border grey 7p-1 */
/* This grey works with a PC but with the mobile it is too dark. */
.vbgrey1 {border-right-style: solid;
border-right-width: 7px;
border-right-color: #030303;}

/* vertical border grey 7p-7 */
.vbgrey7 {border-right-style: solid;
border-right-width: 7px;
border-right-color: #0d0d0d;}

/* vertical border grey 7p-20 */
.vbgrey20 {border-right-style: solid;
border-right-width: 7px;
border-right-color: #333333;}



/* vertical border grey 7p-1 */
/* This grey works with a PC but with the mobile it is too dark. */
.vbgrey7p-1 {border-right-style: solid;
border-right-width: 7px;
border-right-color: #030303;}

/* vertical border grey 7p-7 */
.vbgrey7p-7 {border-right-style: solid;
border-right-width: 7px;
border-right-color: #0d0d0d;}

/* vertical border grey 7p-20 */
.vbgrey7p-20 {border-right-style: solid;
border-right-width: 7px;
border-right-color: #333333;}

/* vertical border black 10p */
.vbgrey10px-bl {border-right-style: solid;
border-right-width: 10px;
border-right-color: #000000;}

/* vertical border black 15p */
.vbgrey15px-bl {border-right-style: solid;
border-right-width: 15px;
border-right-color: #000000;}
/* vertical border black 20p */
.vbgrey20px-bl {border-right-style: solid;
border-right-width: 20px;
border-right-color: #000000;}
 
/* FONT COLOR */

/* BLACK AND WHITE */

/* white 100 HSV-0.0.100 */
.white {color: white;}

/* black 000 HSV-0.0.0. */
.black {color: black;}

/* GREYS */

/* white 100 HSV-0.0.100 */
.grey100 {color: #ffffff;}

/* grey 95 HSV-0.0.95 */
.grey95 {color: #f2f2f2;}

/* grey 90 HSV-0.0.90 */
.grey90 {color: #e6e6e6;}

/* grey 85 HSV-0.0.85 */
.grey85 {color: #d9d9d9;}

/* grey 80 HSV-0.0.80 */
.grey80 {color: #cccccc;}

/* grey 75 HSV-0.0.75 */
.grey75 {color: #bfbfbf;}
/* grey 70 HSV-0.0.70 */
.grey70 {color: #b3b3b3;}

/* grey 65 HSV-0.0.65 */
.grey65 {color: #a6a6a6;}

/* grey 60 HSV-0.0.60. grey for headings */
.grey60 {color: #999999;}

/* grey 55 HSV-0.0.55 */
.grey55 {color: #8c8c8c;}

/* grey 50 HSV-0.0.50 */
.grey50 {color: #808080;}

/* grey 45 HSV-0.0.45 */
.grey45 {color: #737373;}

/* grey 40 HSV-0.0.40 */
.grey40 {color: #666666;}

/* grey 35 HSV-0.0.35 */
.grey35 {color: #595959}

/* grey 30 HSV-0.0.30*/
.grey30 {color: #4d4d4d;}

/* grey 25 HSV-0.0.25 */
.grey25 {color: #404040;}
/* grey 20 HSV-0.0.20 */
.grey20 {color: #333333;}

/* grey 15 HSV-0.0.15 */
.grey15 {color: #262626;}

/* grey 10 HSV-0.0.10 */
.grey10 {color: #1a1a1a;}

/* grey 8 HSV-0.0.8 */
.grey8 {color: #141414;}

/* grey 5 HSV-0.0.5 */
.grey5 {color: #0d0d0d;}

/* grey 3 HSV-0.0.3. This is too dark for my cell phone. */
.grey3 {color: #080808;}

/* black 000 HSV-0.0.0. This is too dark for my cell phone. */
.grey0 {color: #000000;}







/* BEIGE */

/* beige HSV-42.19.69. My first more vivid beige. */
.beige {color: #b1a78f;}

/* beige dark HSV-43.15.49. Similar to beige a but a bit darker. */
.beigedk {color: #91866b;}

/* beige grey 1. Similar to beige a but less saturation. HSV-42.12.65 */
.beigegr1 {color: #a6a092;}

/* beige grey 1 dark. Similar to beige c but darker. HSV-42.20.50 */
.beigegr1dk {color: # 807866;}

/* BROWN */

/* yellowy-mid-brown from MS Word HSV-45.100.75 */
.brownyel {color: #c09100;}

/* mid-brown from MS Word HSV-45.100.50 */
.brownmed {color: #806000;}

/* darker brown 1 HSV-45.100.25 */
.browndk1 {color: #403000;}
/* darker brown 2 HSV-45.100.12 */
.browndk2 {color: #1f1700;}

/* MISCELLANEOUS */

/* my blue violet HSV-237.66.100 */
.violet {color: #575fff;}

/* mid-turquoise HSV-175.100.65 */
.midturq {color: #00a698;}

/* mid-lime HSV-75.100.80 */
.midlime {color: #99cc00;}

/* sap HSV-86.54.51 */
.sap {color: #64823c;}
 
/* brown sap HSV-56.76.38 */
.brsap {color: #615c17;}

/* pink HSV-320.60.100 */
.pink {color: #ff66cc;}

/* peach HSV-10.60.100 */
.peach {color: #ff8066;}

/* pastel turquoise HSV-10.60.100. This might get called baby blue. */
.turqpast {color: #8cffec;}

/* light pale blue HSV-190.20.76 */
.bluepllt {color: #e7fbff;}

/* medium pale blue HSV-190.9.100*/
.blueplmed {color: #9bbcc2;}


/* BRIGHT COLORS */

/* red HSV-0.100.100 */
.red {color: #00ffff;}

/* dark red or burgundy HSV-0.100.65 */
.reddk {color: #a60000;}

/* red-orange HSV-15.100.100 */
.orangered {color: #ff4000;}

/* orange HSV-30.100.100 */
.orange {color: #ff7f00;}

/* orange brighter HSV-45.100.100. Like the orange in MS Word. */
.orangebr {color: #ffbf00;}

/* yellow darker HSV-53.100.100. This is a bit darker—more on the orange side. Maybe a canary yellow. */
.yellow {color: #ffe100;}

/* yellow HSV-60.100.100. This is more like lime yellow. */
.yellowbr {color: #ffff00;}

/* lime brighter 3 HSV-67.100.100 */
.limebr3 {color: #e1ff00;}
/* lime bighter 2 HSV-75.100.100 */
.limebr2 {color: #bfff00;}

/* lime brighter 1 HSV-82.100.100 */
.limebr1 {color: #a2ff00;}

/* lime HSV-90.100.100 */
.lime {color: #7fff00;}

/* green HSV-120.100.100. This is quite a bright green. */
.green {color: #00ff00;}

/* turquoise green HSV-150.100.100 */
.turqgr {color: #00ff7f;}

/* turquoise HSV-165.100.100 */
.turq {color: #00ffbf;}

/* cyan HSV-180.100.100 */
.cyan {color: #00ffff;}

/* dark cyan HSV-195.100.100 */
.cyandk {color: #00bfff;}

/* azure HSV-210.100.100. This might be like a bright cerulean blue. */
.azure {color: #007fff;}

/* dark azure HSV-225.100.100 */
.azuredk {color: #0040ff;}

/* blue HSV-240.100.100. This is like an ultramarine blue which is fairly dark. */
.blue {color: #0000ff;}

/* navy blue HSV-240.100.65. */
.navyblue {color: #0000a6;}
/* purple blue HSV-248.100.100. Some people might call this violet or indigo. */
.bluepurp {color: #2200ff;}

/* purple dark2 255-180.100.100. This might be considered a standard darker purple although it doesn't fall on the 30 multiple for hue. */
.purpledk2 {color: #4000ff;}





/* purpledark1 HSV-263.100.100. This is a third tier color, neither a 30 or 15 hue multiple but can almost seem more middle of the road than purple at 270. */
.purpledk1 {color: #6200ff;}

/* purple HSV-270.100.100. This color is a 30 multiple hue but could almost seem more of a magenta purple. */
.purple {color: #7f00ff;}

/* magenta HSV-285.100.100. This is a second tier hue at a 15 hue multiple but seems to be a pretty good magenta candidate. */
.magenta {color: #bf00ff;}

/* magenta bright HSV-300.100.100. The chart calls this magenta but I think it might be more like a hot pink. */
.magentabr {color: #ff00ff;}
/* pink red HSV-330.100.100 */
.redpink {color: #ff007f;}



























































/* FONT EMBEDDING */
 
/* This part references font files of the specified font families that have been embedded into the Anki Deck in the collection.media folder.

NOTE: To call up these fonts you don't use the class attribute. Rather, you have to use the style attribute in the form of:  style="font-family: segl;" 

I tried including Segoe UI Semilight, but no matter what I tried, in Anki flashcards II would seem to call up a serif font similar to Times New Roman.*/
 
/* Segoe UI Light */
@font-face {font-family: segl; src: url('_01 segoeuil.ttf');}
 
/* Segoe UI */
@font-face {font-family: segr; src: url('_02 segoeui.ttf');}

/* Times New Roman */
@font-face {font-family: times; src: url('_03 times new roman.ttf');}

 

/* FONT FAMILY */

/* These references you do call up with the class attribute.

Currently, the reference for Times New Roman may be working effectivel. I'm not so sure what is happening with the other font families in this section.

NOTE: If you don’t include any font family references in the coding for cards, you will get a sans-serif font that is fairly good. It looks like Segoe UI.
*/


/*arial */
.arial {font-family: arialreg, arial, helvetica, sans-serif;}

/*arial narrow */
.arialnar {font-family: “arial narrow”, arialreg, arial, helvetica, sans-serif;}

/* segoe ui light */
.segl {font-family: segoeuil, “segoe ui light”, “segoe ui semilight”, “segoe ui”, sans-serif}

/* segoe ui semilight */
.segsl {font-family: “segoe ui semilight”, segoeuil; “segoe ui light”, “segoe ui”, sans-serif}

/* segoe ui */
.segr {font-family: “segoe ui”, “segoe ui semilight”, segoeuil; “segoe ui light”, sans-serif}

/* times new roman */
.timesreg {font-family: timesreg, “times new roman”, times, serif}

/* no mention */















































/* FONT SIZES */

 {font-size: #vw;}
{font-size: #.#vw;}


/* TEXT ALIGNMENT */

/* HORIZONTAL */

{text-align: left;}

{text-align: center;}

{text-align: right;}

/* VERTICAL */

{vertical-align: top;}

{vertical-align: middle;}

{vertical-align: bottom;}




/* CENTERING IN VIEWING AREA*/
/* Horizontal and Vertical */
/* This is more useful if you have tables. If you don't have tables you might want to get rid of this. */

.centrhz {
    position: absolute;
    top: 50%;
    left: 50%;
    -moz-transform: translateX(-50%) translateY(-50%);
    -webkit-transform: translateX(-50%) translateY(-50%);
    transform: translateX(-50%) translateY(-50%);
}

/* Vertical */

.centrvt {
    position: absolute;
    top: 50%;
    -moz-transform: translateY(-50%);
    -webkit-transform: translateY(-50%);
    transform: translateY(-50%);
}
/* MEDIA QUERY */

/* coding constrained for landscape mode */
/* .land will cause elements to not display */

@media only screen and (orientation:landscape) {
.land {
display: none;
   }
}

/* coding constrained for portrait mode */
/* .port will cause elements to not display */

@media only screen and (orientation:portrait) {
.port {
display: none;
   }
}

<!--------------------------------------------------->

Rumo · July 6, 2022, 7:03am

Could you explain how your cards work from a learner’s perspective? I understand the ‘question’ is an IPA symbol or its name. What is the ‘answer’? In other words, for a given IPA symbol, what are the ‘vowels’, ‘consonants’ and ‘other symbols’ you need to remember?

dae · July 8, 2022, 12:17am

Anki won’t let you do this, because it doesn’t make sense to do so. Bear in mind that cards will appear in a random order once reviewed. When you see a question appear, you will have no way of knowing which answer you are supposed to provide, unless your question side is unique.

ixti · July 8, 2022, 3:28am

SUMMARIZING THE PROBLEM

. . . the deck in question, the IPA deck, works as far as I can tell in so far as you can study with it. It does what I want it to do. The problem is that I can export it as an Anki Collection Package (*colpkg), but it won’t export properly as an Anki Deck Package (*apkg). The error I get, as mentioned above, is:

Card template 2 in notetype ‘01 IPA’ has a problem. The front side is identical to card template 1.

The problem with this arrangement is that when anyone goes to upload the Anki Deck saved in the working Anki Collection Package, they can’t do it without getting all decks that are open (in whatever Profile you have open) in Anki deleted.

Apparently, having in one Note Type two or more Card Types with identical front sides is responsible for the problem that I am dealing with.

EXPLAINING THE DECK FURTHER

Earlier on, Rumo asked me for more info as to how the deck in question is organized. Hopefully, this will help in getting someone to help me figure out a way to correct the problem.

To begin with, IPA is an acronym for International Phonetic Alphabet. This is the most widely used and recognized phonetic alphabet that allows one to transcribe any language into a standard and fairly accurate script. It’s used in many dictionaries and in Wikipedia for translating words into a phonetic script equivalent.

I’ve grouped the symbols of the IPA into three main groups:

vowels
consonants
other symbols

:which are treated in separate decks. The main groups also get divided into further subdecks as shown in the deck structure shown in the below image.

I want the order of study to go in two directions: one direction where you are prompted with an image of the letter, and the other where you are prompted with the name of the letter.

Clipboard Image

The above image shows the deck structure as it is seen in the Anki deck list. All folders and subfolders are displayed. The recommendation is that people try and keep deck structures simple and that you fine-tune searches by using filters. Creating filters can be a bit inconvenient and maybe a bit learning-curve steep. I’ve preferred to make a more extensive deck structure for quicker access to the card type that is needed.

CARD TYPES IN THE NOTE TYPE FOR THE DECK

The deck is accommodated by one Note Type which has six Card Types or Card Templates to produce the six different card types that I want. The following, also shown earlier, illustrates the arrangement of the cards, where the words represent a body of unique coding.

    FRONT CARD       BACK CARD

1// … 1. glyph first — + — 3. vowels
2// … 1. glyph first — + — 4. consonants
3// … 1. glyph first — + — 5. other symbols

4// … 2. name first — + — 3. vowels
5// … 2. name first — + — 4. consonants
6// … 2. name first — + — 5. other symbols

In this arrangement I have, front card templates are duplicated in first one group of three card templates, and secondly in the remainder group of three card templates. There also are three groups of two back cards that are duplicates. I get the impression that duplicates in back card templates might not be a problem, but I’m not sure.

I JUST HAD AN IDEA

To get around the problem that I’m having, what if I created three Note Types to replace the one Note type I currently have, and divide the existing card types amongst them, dispersing the card types in such a way that no Note Type will have duplicate front cards. For example:

Note Type 1

    FRONT CARD      BACK CARD

1// … 1. glyph first — + — 3. vowels
4// … 2. name first — + — 3. vowels

Note Type 2

    FRONT CARD      BACK CARD

2// … 1. glyph first — + — 4. consonants
5// … 2. name first — + — 4. consonants

Note Type 3

    FRONT CARD      BACK CARD

3// … 1. glyph first — + — 5. other symbols
6// … 2. name first — + — 5. other symbols

And if having duplicate back cards between any Card Types in any one NoteType is a problem, I suppose I could then create 6 Note Types, each containing one of the 6 Card Types. The question is whether Anki will go for this.

EXAMPLES OF CARDS IN IMAGES

Here are examples of images of the cards as they appear when studying. I only include the horizontal view and not the vertical view. The coding includes some conditional thing where you get displayed different formats for a horizontal screen and a vertical screen. The vertical screen view is more ideal for cell phone use.

The back cards for vowels, consonants, and other symbols, though similar are different.

card 1

1// … 1. glyph first — + — 3. vowels

front card

back card

card 2

2// … 1. glyph first — + — 4. consonants

front card

back card

card 3

3// … 1. glyph first — + — 5. other symbols

front card

back card

card 4

4// … 2. name first — + — 3. vowels

front card

back card

card 5

5// … 2. name first — + — 4. consonants

front card

back card

card 6

6// … 2. name first — + — 5. other symbols

front card

back card

Rumo · July 8, 2022, 9:11am

Thank you for explaining. Your approach doesn’t make sense to me, though. Say you add a note with the symbol p. Then 6 cards will be generated, only 2 of which by card types you associate with consonants. E.g. you’ll have 3 cards with ‘p’ on the front and ‘voiceless bilabial plosive’ on the back.

If you mean to categorise your notes, you’ll need to take a different approach. Either:

Use different notetypes as you’ve described above. This will involve the most maintanence work and only really makes sense if you want the cards to look or behave very differently depending on their category.
Add a Category field to your notetype and fill in the category for each note. However, Anki has a better way to achieve the same thing:
Tag your notes with e.g. IPA::Consonant, IPA::Other, IPA:Vowel respectively.

I guess what I’m saying is: Delete 4 of your card types and do no. 3.

Topic		Replies	Views
Importing error with card template Anki Desktop	8	994	May 1, 2023
Can't share the deck over Ankiweb Syncing & AnkiWeb	19	1126	May 1, 2023
Issues with importing decks Anki Desktop	3	360	August 4, 2023
Errors when Importing A Deck with Duplicate Cards Card Design	2	469	July 23, 2023
Shared anki decks Anki Desktop	3	285	December 28, 2022

Deck will export as Anki Collection Package but not Anki Deck Package

Related Topics