We can only use overflow-wrap: anywhere; on item links and it solves wrapping problem without breaking table layout.

When value input removed it gives another error as well.

I think everything is merged now.

It seems like difference between desktop and mobile was because of the order and content of language codes array sent to Termbox renderer and right now it's already solved. Editing workflow on mobile can be changed within a day, IMO.

I couldn't reproduce the order in "In more languages" section (desktop and mobile has the same order of items, both logged out). After talking with @ItamarWMDE, we decided to take a deeper look into fallback algorithm and terms. Then we can talk about edit mechanism in mobile termbox.

There is no need to add additional documentation, we have both of them in both example CSV file and the documentations.

Oh, that's great! I'll proceed like you said then, thanks a lot!

In T288511#8385726, @Lydia_Pintscher wrote:

I believe we said the meta_wikidata_value column should always be present but it can be empty. Does that address your concern @HasanAkgun_WMDE?

We should allow CSV files without meta_wikidata_value column because we are adding it as optional and it's not good for backward compatibility. However, we have another optional column in our CSV files, external_url and unlike meta_wikidata_value, the CSV file should have that column even there is no value for the external_url field. I think we should treat there columns same because they have similar attributes: we should allow CSV files without external_url column just like with meta_wikidata_value. Otherwise we have two optional columns but one is not so optional compared to the other one. I wonder if you agree @Lydia_Pintscher?

In T304943#8274994, @Lucas_Werkmeister_WMDE wrote:

I think we should use the existing RegexValidator error reporting, just with a custom error code instead of the default 'malformed-value'.

Here is the final form of the merged ontology file @Lydia_Pintscher @danshick-wmde, I don't know how to update current one that's why I'm adding it to here.

@Lucas_Werkmeister_WMDE I think we can add problematic part of a property as a parameter to the API response? UI can also highlight the issue with the input as well. I don't know if it's a good idea to add it as a parameter though.

In T314360#8262594, @abian wrote:

You may want to check https://oops.linkeddata.es. It won't tell you about all the possible issues, but it will give you an idea of some (so-called) common pitfalls that still need to be resolved. By doing so you may also be solving T210337. 0:-)

You can visualize the result at https://service.tib.eu/webvowl/#iri=http://wikiba.se/ontology-1.0.owl or http://vowl.visualdataweb.org/webvowl-old/webvowl-old.html#iri=http://wikiba.se/ontology-1.0.owl.

As discussed on gerrit, there is an uncertainty about lexemes having languages and the way we define them, or should we define them at all.

I have added the final form of ontology file as attachment, I don't know where to add it tbh :)

We have talked about "Lexemes having spelling variant" with @Lucas_Werkmeister_WMDE and I suppose forms have spelling variants instead of lexemes and I'm not sure if it's relatable anymore. Other than that, it should be ready for review.

When I checked the escapeHtmlAllowEntities and the signature of htmlspecialchars function, it seems like it doesn't matter if you put or remove ENT_QUOTES | ENT_SUBSTITUTE as flags, because it's the default value anyway.

@Dzahn no I realize that it's way more complicated than I think, so let's cancel the task and pretend like it never happened?

Hello, I just signed the agreement.

@WMDE-leszek @Dzahn Actually the problem with creating new user process was kernel username, I couldn't remove that from the old user so I couldn't add it to the new one. If you can provide a proper way to make this happen, I can create the new user for sure.

As the WMF-Legal project tag was added to this task, some general information to avoid wrong expectations:
Please note that public tasks in Wikimedia Phabricator are in general not a place where to expect feedback from the Legal Team of the Wikimedia Foundation due to the scope of the team and/or nature of legal topics. See the project tag description.
Please see https://meta.wikimedia.org/wiki/Legal for when and how to contact the Legal Team. Thanks!