Inquiry About Multilingual Support and Future Research Plans

#3
by gunoh - opened

Hello,

I am a researcher currently evaluating OvisOCR2 on Korean-language documents.

I have observed cases where the source document clearly contains Korean Hangul text, but the model outputs Chinese characters with the same or a similar meaning instead.

I analyzed the token embeddings and the decoder hidden state at the relevant generation steps. Although the Hangul token showed higher cosine similarity to the decoder hidden state, the Chinese-character token had a larger dot product and was consequently selected as the final output.

I would appreciate your thoughts on the following questions:

  1. Is it possible to mitigate this issue by adjusting the decoding or sampling strategy, without additional fine-tuning?
  2. I understand that the Alibaba Token Hub team has adopted a synthetic data strategy. Are there any plans to invest additional resources in expanding OvisOCR2’s multilingual capabilities in future releases?
  3. Would it be possible to share the source code or pipeline used to generate the synthetic training data? I would be interested in using it to perform post-training and extend the model to additional language domains myself.

Thank you for sharing such a valuable model and for your excellent research.
스크린샷 2026-07-20 09.57.13

Just sharing a personal thought:
cosine-based decoding may mitigate this issue, but it carries a risk of degrading overall performance because the model was trained using dot-product logits.
A less aggressive option would be partial norm correction:
部分归一化的点积
This would still require careful multilingual evaluation, while Korean-focused post-training would likely be more reliable.

Sign up or log in to comment