Can I make a html and css style with Korean docs?

[이예원]

Hello,

My name is Yewon, and I'm a Korean user of this library.

While browsing the official documentation (Korean version), I noticed that it currently lacks proper styling. I believe that adding a clean and consistent style would greatly improve the readability and accessibility of the documentation for Korean users.

I’d love to contribute by designing and applying CSS and HTML styling to the Korean docs, if you would allow it. Could you please let me know if this is possible, and how I might be able to submit my work once it's complete?

Thank you very much for your time and consideration.

Best regards,  
Yewon

[leonardr]

Hello, Yewon,

Thanks for your offer of help. I think there is something you can do to help, if you're interested, but it's a bit more complicated than changing the CSS styling.

The Korean translation looks the way it does because it used to be hosted on the translator's personal website, which went down in 2019. I rescued it using the Wayback Machine and added it to the Beuatiful Soup code repository.

The original English documentation and the other translations are stored in reStructured Text format, which makes it easy to create versions in different formats. It's clear from the formatting that the Korean translation was also originally stored as reStructured Text, but I was never able to contact the translator to get a copy of it. I was only able to recover the bare HTML and a basic CSS file.

If you could convert the existing Korean translation back to reStructured Text, it'd be on the same level as the other translations. This would have two advantages:

1. The HTML version of the Korean translation would have the same styling as the other translations, because it would be built by the same tools. It would also have improved presentation features like an automatically generated table of contents.

2. It would become practical to update the Korean translation.

The second one is the really important one for me, because the Korean translation is dated November 2012. It should still be accurate, but so many things have been added to Beautiful Soup in the last thirteen years, that I think it's less useful to a Korean-speaking developer than a machine translation of the current English documentation. But it's not reasonable to expect someone to update the Korean translation when they'd have to directly edit an HTML file.

If you want to modify the index.css file currently used with the Korean translation, I'll accept the contribution and update the repository, but I think the styling is just a symptom of the translation's complicated history. I think it'd be healthier for the future of the Korean translation if you or someone else could reverse-engineer a reStructured Text version of the HTML file.

Leonard

[이예원]

Hello Leonard,

Thank you so much for your thoughtful reply and for explaining the history of the Korean translation. I’m very sorry for the delayed response — I was caught up finishing a personal project and wasn’t able to get back to you sooner.

I’m really happy to hear there’s a meaningful way I can contribute. I’d love to help convert the existing Korean translation back into reStructured Text format as you suggested. It sounds like an important step for making the documentation more maintainable and accessible for Korean developers, and I’m excited to be part of that effort.

Could you please let me know how I should get started? If there’s any specific workflow, guidelines, or repository structure I should follow, I’d appreciate it if you could point me in the right direction.

For your reference, my GitHub username is <yewonlee1211>, and my associated email is <yewonl...@korea.ac.kr>.

Thank you again for the opportunity — I’m looking forward to contributing!

Best regards,  

Yewon

2025년 6월 26일 (목) 오후 8:18, leonardr <leonard.r...@gmail.com>님이 작성:

--
You received this message because you are subscribed to the Google Groups "beautifulsoup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beautifulsou...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/beautifulsoup/82d33b61-bc31-4cc5-a373-24e4df61013fn%40googlegroups.com.