Hi everyone.
In Japanese, many are translated. There are parts that have not been tagged. Also please give us a translatable tag below as well: Recommendations for mobile friendly articles on Wikimedia wikis. This document seems to be important for actual efforts. If Japanese documents are prepared, Japanese version templates will change as well.
I finished translating to japanese, most of the important documents.
I think this project is a very necessary improvement for usability improvement of mobile.
Question
What does MobileFrontEnd read? What do we need to prepare in Japanese Wikipedia?
For example "hide-when-compact" class.
I think you have the first part correct. Use the class in templates to control what appears in the mobile view. I'm not sure on the second.
@Jdlrobson could you help with this question?
> ommon.css requires a class name in each wiki. In order to hide this we need CSS designation for each wiki. I do not understand this part. Or, we do not need to edit common.css (etc).
I'm not 100% sure on the context here, but if we are referring to Recommendations_for_mobile_friendly_articles_on_Wikimedia_wikis#Use_standardized_class_names_in_HTML_markup_for_components_in_templates_across_projects the word "common" here is more to do with using a "standardized" class name (not common.css). One challenge we have with standardising displays across wiki is the class attribute usage in HTML markup.
For instance
<div class="m-elephant"></div>
In Chinese/Japanese might be
<div class="m-大象"></div>
To avoid having to localise class names, we're attempting to standardise on a single class across all the wikis.
So in the above case if m-elephant is the "standard", the markup for Japanese/Chinese might become:
<div class="m-elephant m-大象"></div>
Thanks, CKoerner, Jdlrobson.
I try using unique class names. I will experiment when I have time. It seems to be activated just. : Tech/News/2018/51
To avoid complicated clutter. It would be better for MobileFrontEnd to determine a single unique class name. Furthermore, it is easier when MobileFrontEnd outputs the corresponding CSS.
"m-elephant" is OK as "m-elephant".
HTML and CSS are originally in English. We do not need to use kanji for this. The use of kanji is not practical.
sorry for adding to the confusion. This is exactly what we are doing. I wasn't suggesting to use kanji. I was trying to explain the idea that in certain wikis you may want to use both classes.
To provide a more concrete example hatnotes in german wikipedia do not use the .hatnote class in Template:Begriffsklärungshinweis but have classes "noprint navigation-not-searchable". The germand could use the hatnote class along with those existing classes and attributes to become more mobile compatible
E.g. "noprint navigation-not-searchable hatnote"
It could also use a class begriffsklaringshinweis if it wanted to but that would be ignored by Minerva skin.
