From The Document Foundation Wiki
- Hi Dennis,
- Actually, This two pages has different means.
- Translating LibreOffice/ja is a Japanese translation of the global page Translating LibreOffice, and JA/Translation/ page describes Japanese NPL's local rules, so they are hard to merge I guess.
- Did I answer enough your question?
- Naruoga (talk) 2014-08-13T08:35:46 (UTC)
- sry for the late response,
- well yes and no: both pages are about translating libo. althughone is about the process and the second is about /how to do it/ both go hand in hand I think a) they could be merged (esp. for easier finding) on one page as they aren't long enough and b) should get moving at a place where they are in an international context (all l10n teams do need to describe the the functionality he same place so any lage like l10n/langage_code might be useful for such pages...)
- Dennis Roczek (talk) 2014-10-05T00:37:48 (UTC)
- Hi Dennis,
- Hmm... I agree that every important rules (such as translation) should be easy to find out, and the localized global page (e.g. Translating LibreOffice/ja ) might be a good entry point.
- And sorry, I had confessed. I might remember some different page, instead of Translating LibreOffice. Yes, we can merge them. Please forget my answer below.---Naruoga (talk) 2014-10-10T07:14:58 (UTC)
And I change my mind little, that is, Translating LibreOffice/ja does NOT has important information for Japanese users/translators at that time, because the page describes how to create NEW language project, but we already have our own project, so we can just remove, not merge. My idea is to change (1)Translating LibreOffice/ja as a just redirect to (2)JA/Translation/, and add comment in the head of (2), for example "This page is describes local rules to translate LibreOffice to Japanese. If you want to know how to create your new language project, please see Translating LibreOffice(in English)." What do you think that idea? --Naruoga (talk) 2014-10-10T07:01:48 (UTC)