Deleted some jp pages that were outdated

[ferafiks]

My motivation behind removing them was that I think it's better to have increased gaps in the translation than to have documentation that keeps going more out of date with time. I also moved the docs changelog from manual's index to includes - that way the Japanese manual will also have the most recent changelog.

Additional note: I ran all media files through my own "unlinked media destroyer" script to keep the images that are referenced by other jp pages intact.

[VaclavElias]

@xen2 this needs your approval, including there is incoming big #545, so JP docs will be even more out of sync.

Maybe it is the time to ask again, shall we keep JP docs?

[ferafiks]

Maybe it is the time to ask again, shall we keep JP docs?

My 3 cents: I'm generally for having resources like these available, but the JP docs aren't really evolving. If we were to remove them, they would still be available via the version switch in the docs, so nothing would be lost. The main reason to keep them would be in case someone would become interested in maintaining them in the future, but looking at how much the English docs are changing, it would probably be easier to just start translating them from scratch.

[xen2]

Agree. It seems nobody is going to work on it in the foreseeable future.
Also I want English doc to keep its recent momentum and JP doc is deadweight in that regard.

BTW, are machine translation viable? I thought with recent improvements, it might be possible?
One could even give very useful context (i.e. game studio menu .pot translation so that technical words are always translated the same, etc.)
If yes, it might be worth opening a discussion later (whenever needed).

[VaclavElias]

If machine translation works well, we can do a Discord poll to choose which language to add? 🤔

[ferafiks]

I would wait for now with additional languages (even if automatic) while the docs are still evolving. I can list hundred random things that are wrong or outdated and having them be in another language that has less resources and less support wouldn't make a good experience. Probably better to push for specific regions on all fronts at the same time.

I don't have much against using AI for translation (accessibility is probably one of the best use-cases for AI), but I'm struggling to see the difference between blindly translated official docs and someone translating the English docs in their browser (which is a common feature). Maybe it would produce a better result, but I wouldn't be surprised if google or other browser companies would introduce better translator models making this point outdated. I guess it could also make it more accessible for people that don't have that in their browser or don't know how to use it, but at that point maybe it would be better to have a button to automatically translate a page to whatever language someone would want than to host translated copies.

[xen2]

I was also asking because it strengthen the case for dropping JP translation for now.
We can see later about other languages, let's keep it simple and focus on english, until there's actual demand.