not a big fan of excluding ISO enters from the base kit. Might want to remove the ansi enters from the base kit and make a separate enter kit making the base kit even cheaper but also decreasing the cost of ISO user
As previously explained, this is not possible. MW has a significant child kit MOQ for all child kits that have a color that is not in the base kit. Therefore the accent colors are mandatory in base if Tweec wants to work with this manufacturer. While he could include colors that aren't on the accent esc and enters (possibly the best solution here is to put them on the bottom row as bottom row accents) if Tweec doesn't want bottom row accents I can't see a great solution to this issue.
I asked John out of curiosity and he does not think that MW standard packaging can hold 5 iso enters - that means new, unique packaging would need to be purchased, greatly increasing the cost of the set.
Thank you for explaining! By having those accents in base, it is more likely that the accent kits is possible. Though there's always a possibility of removing the ANSI accents from base if there is a lot of interest.
Nobody said they don't want any accents in base. We're telling you that if you're putting ANSI accents in base then there should also be ISO accents in base. Otherwise it's a completely different aesthetic for the 2 layouts. Why would I need to buy 4 child kits for my ISO keyboard just to have the same thing ANSI already has in the base kit alone?
It's clear that the criticism is that ansi is receiving preferential treatment in this kitting, no one is denying or ignoring that.
However, the solution is not clear. The accent colors must go
somewhere in the base it. Here are a few potential solutions I was able to brainstorm while discussing with other designers.
1) Remove esc and ansi enter accents from base, replace them with bottom row accents. Pros: removes preferential treatment, Cons: may create an aesthetic the designer doesn't want.
2) Remove ansi enter accents from base but keep escs. Pros: removes preferential treatment, cons: feels weird af to just offer random escs but no enters at all to pair them with, defeating the purpose of the accents entirely.
3) Remove accent ansi and esc from base, replace them with random keys, like F row or nav keys. Same pros and cons as #1.
4) Remove
some ansi enters and replace them with iso enters in those colors. Pros: removes preferential treatment between ansi and iso, cons: creates preferential treatment between specific colors.
There are some other possible solutions but they all feel worse than the 4 I just presented so I'll omit them for now. I hope I've made clear that the solution to the problem isn't just "put all the accent isos in base" because that's not possible. IMO #1 is the cleanest solution but idk if Tweec wants that.
