A problem I had recently with one of my designs has me wondering, should technical terms be encouraged or discouraged when designing?
The situation at hand is a design for a gown, and (having studied fashion for a few years) I included the term 'darts' in the description. For those of you who might not be aware, darts are folds tucked into the fabric and stitched shut to provide shape for a garment, most specifically around the bust line. "A sweeping shoulder line leads to princess sleeves, and darts around the armpit and waist accentuate the bust without overly drawing attention." However, it was returned with a note only works under the assumption that 'darts' is viewed as the verb form rather than the noun. Note that this is not the only inclusive fashion terminology in the sentence, princess sleeves might escape the layman and be seen as some vague image (though easily remedied by a Google search). Context would, I think, clue that nothing is moving about erratically within the gown.
Now, my query is this: Is this a problem that is only encountered in tailoring? Do jewellers, forgers, or chefs have the same issue? Should we remove terminology that the Average Joe might not understand and replace it with clearer phrasing about what we're trying to say? If ease of reading is the purpose, is it better to have a blocky two or three line sentence instead of one?
(Note, the Charites did fix the problem, and the design went through, I'm looking for player thought and feedback.)
Comments
Estarra the Eternal says, "Give Shevat the floor please."
Using special terms just means that occasionally you might get a misunderstanding in the review process, like you did, if the person reviewing is unfamiliar with that terminology. But the Charites are pretty good about resolving those issues, too. My advice is just be able to back up whatever term you use with a source, just in case!
Estarra the Eternal says, "Give Shevat the floor please."
Ixion tells you, "// I don't think anyone else had a clue, amazing form."
That's the real risk with using technical terms. If a person doesn't know the technical meaning they can probably get a general idea from context, so in a lot of cases it's fine. The problem is with cases like this specific example where the word also has common meanings. When that happens the meaning that you intend and the meaning that a person is most likely to understand are not the same thing.