Both BLEU and METEOR are meant to evaluate the overall translation quality. METEOR shows a slightly better correlation with human judgment than BLEU, however, it relies on n-gram alignment between the translation hypothesis and reference that needs language-specific paraphrase tables. The quality of the table heavily influences the evaluation quality. I think BLEU was preferred because of its simplicity and language independence. Nowadays, there are many evaluation metrics that correlate much better with human judgment (such as BLEURT, BertScore, or COMET) and they start to be preferred in the MT community (cf. papers: Tangled up in BLEU: Reevaluating the Evaluation of Automatic Machine ranslation Evaluation Metrics, To Ship or Not to Ship: An Extensive Evaluation of Automatic Metrics for Machine Translation).
BLEU score is an average of n-gram precisions, weighted by the so-called brevity penalty that penalizes short high-precision, but low-recall hypotheses.
METEOR computes both precision and recall. Here, the precision corresponds to a proportion of words that are in the hypothesis and are correct. The recall is a ratio of how many words from the translation hypothesis appeared in the hypothesis. To do so, we need to somehow decide which words are correct. This is done by n-gram alignment between the hypothesis and the reference. If there is no exact match between the two, a table of paraphrases is used. To penalize sentences that contain the correct words, but in the wrong order, there is a reordering penalty term that penalizes such sentences.
Both metrics measure the same aspects of the translation, but slightly differently:
Precision
- BLEU: directly via n-gram precision
- METEOR: directly in the alignment graph
Recall
- BLEU: indirectly via including the brevity penalty
- METEOR: directly in the alignment graph
Fluency
- BLEU: directly by considering longer n-grams
- METEOR: indirectly from the properties of the alignment graph