Dear Holger Levsen and Wolfgang Schweer, CC: Debian Edu team > On Wed, Jun 05, 2019 at 02:13:01AM +0900, [email protected] wrote: > > Deep sub-section titles are too small > > ====================================== > > > > e.g.) 6.3.2.1. foobar > > > > These 4 depth titles are rendered smaller than main paragraph fonts. > > I think it better to increase those rendering sizes. > > (at least in HTML) > > I've seen you commited this change to git (fine), I'd just like Wolfgang > to review the results and decide whether to keep this or adjust further. > > if we keep 61a709d1efee41c9e96024277e8a141b79c69a46 in d-e-doc.git this > change also needs to be documented in d/changelog.
Sorry about the important changelog, and thank you for reviewing and adding. > > Sub units > > ========== > > > > Especially in Hardware requirement section, > > there are mixed usage of MiB/MB and GiB/GB. > > > > I think those do not have to be so precise; GB and MB seems fine. > > I actually would prefer to always use KiB, MiB and GiB consistently. > > or, use KB, MB and GB consistently. just mixing them is definitly > wrong/sub-optimal. I agree. As you pointed, I think there would be at lease three options. 1. Separate those use. * Ki/Mi/Gi: for general IT related sub units. * k/M/G: for storage device amount (and CPU freq?). It is because storage amounts are written in KB/MB/GB traditionally, causing 1,000 and 1,024 sub unit mixing problems, as you know. The problem is CPU freqs; I'm not sure those are 1,000 radix or 1,024 radix. (It seems 1,000...?) 2. Make it simple (SI subunit, 1,000 radix only) * k/M/G: for all. This would be nice, considering it is Debian "Edu" doc, the world of general science, SI unit, 1,000 radix world. 3. Make it simple (1,024 subunit only) * Ki/Mi/Gi: for all. This would be preferable since it is about IT tech doc. In short, I'm confused. Perhaps #3 is easy and nice. > > GOsa2 section ja translation > > ============================= > > > > As I said once, GOsa2 Web UI itself has no ja translation, > > and I think it's rather fine. At least I have no capability to > > translate GOsa2 and related LDAP po files properly. > > I do think its a bug to tackle in the long run, but not now. Absolutely; and I need time for this obviously. > > Now I'm considering GOsa2 section's entry names be back to en, > > to avoid confusion; eg. "Base", "newstudent", etc. > > (to make them matched with the screenshots and actual UI) > > I think this makes perfect sense (for now). Thank you for your comment. Since I made my hardware (storage) replacements, I'll check clean-install "main server" again in the near future, and then make those entry names be back in English (for the time being). Regards.
