Wiktionary:Votes/pl-2013-03/Japanese Romaji romanization - format and content

Hello, you have come here looking for the meaning of the word Wiktionary:Votes/pl-2013-03/Japanese Romaji romanization - format and content. In DICTIOUS you will not only get to know all the dictionary meanings for the word Wiktionary:Votes/pl-2013-03/Japanese Romaji romanization - format and content, but we will also tell you about its etymology, its characteristics and you will know how to say Wiktionary:Votes/pl-2013-03/Japanese Romaji romanization - format and content in singular and plural. Everything you need to know about the word Wiktionary:Votes/pl-2013-03/Japanese Romaji romanization - format and content you have here. The definition of the word Wiktionary:Votes/pl-2013-03/Japanese Romaji romanization - format and content will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofWiktionary:Votes/pl-2013-03/Japanese Romaji romanization - format and content, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.

Japanese romaji romanization - format and content

  • Voting on: Constraining the content of romaji entries. In particular:
    1. A headings that, for an English entry, usually contains a part of speech should, for romaji entries, be "Romanization" rather than a part of speech. These are level 3 headings.
    2. In each romaji entry, there should only be cross-reference links output by a template. Examples would look like "# See: ちゅうけい" or "# Romanization of ちゅうけい".
    3. In each romaji entry, there should be no glosses following the links. Thus, chūkei, would look like "# See: ちゅうけい" or "# Romanization of ちゅうけい", rather than "# See: ちゅうけい: delay; abbreviation of relay broadcast; ceremonial folding fan; younger of two elder brothers".
The ultimate goal is that each Japanese romaji entry will be no more than a cross-reference to the corresponding hiragana, katakana, or mixed-script forms. This is intended to allow for easier automatic generation of romaji entries, and to eliminate the maintenance overhead required in the past whenever a gloss or other information was added to a romaji entry but not to the corresponding kana entry, or vice versa.
  • A typical example, this proposal only affects romaji entries, which had the same information as in hiragana entries:
  1. romaji: dentaku (links to でんたく), no definition) - a disambiguation entry (here, only one kana equivalent exists)
  2. hiragana: でんたく (links to 電卓 (or any other kanji with the same hiragana reading) with PoS and short definitions); no link if the term is only written in hiragana.
  3. kanji: 電卓 - a complete entry
  • Vote starts: 00:01, 30 March 2013 (UTC)
  • Vote ends: 23:59, 28 April 2013 (UTC)

Support constraining romaji entries

  1. Support --Anatoli (обсудить/вклад) 03:48, 30 March 2013 (UTC)
  2. Support --Haplology (talk) 13:10, 30 March 2013 (UTC)
  3. Support --Ultimateria (talk) 13:15, 30 March 2013 (UTC)
  4. Support just to add my support, even though I am tempted to boycott like Angr. —Μετάknowledgediscuss/deeds 17:45, 31 March 2013 (UTC)
    Support (voting due to tactical considerations). - -sche (discuss) 21:25, 8 April 2013 (UTC) - -sche (discuss) 18:28, 17 May 2013 (UTC)

Oppose constraining romaji entries

  1. Oppose We have two formats of romanization entries to serve as a precedent, Chinese and Gothic. Creating a third format without any reason is a thoughtless disregard for the readability of this reference. How can editors argue that this is so thoroughly designed and call a vote about “format” while refusing to explain its essential form? And who uses a colon to write a two-word imperative statement? —Michael Z. 2013-04-02 15:28 z
    Michael. Pinyin, Gothic and Romaji were all developed independently and they don't even belong to the same supercategory (like "Romanizations by language") and I don't know if they ever could. As I explained multiple times, pinyin entries can't have a limited number of parameters because of homophones. The choice of the word "See" was a result of a consensus of JA contributors, my opinion on whether we should use Romanization of (Gothic), See (Romaji) and nothing (Pinyin) is weak but why should we follow Gothic if Japanese may have several lines of Romanization of, which will look ugly. We ended up having See but I don't know anything about how Gothic standards came up to be so. There are inconsistencies in Gothic romanisation entries. Template:ja-romaji doesn't allow such inconsistencies.
    We don't have to stick to formats of Chinese and Gothic. Gothic and Pinyin examples were only used in the discussion to show that romanisation entries can serve as links, they are not meant to have definitions, and not as a means to stop the work on the Japanese romaji. There's perfect readability of both the result and the code and it's very to use.
    I have removed the colon after See.
    Re: "...while refusing to explain its essential form...". Please clarify what is still not clear.
    Re: "..call a vote about “format”". The name of the vote was chosen by Dan Polansky.
    You seem to have jumped from tentative support to opposition (if I understand correctly). As you yourself pointed out Wiktionary:ELE#Definitions doesn't say must have definitions. Is it because we still use the wording "See" despite your protest? --Anatoli (обсудить/вклад) 04:56, 3 April 2013 (UTC)
    Yes, I am opposing this just because the design/copywriting details don’t appear to be thought through. We don’t have to stick to, e.g., the Gothic format, but if we diverge from it then we should articulate some reason justifying it.
    How many links can a romaji entry have? I was under the impression that it is only one or up to two, for katakana and hiragana. —Michael Z. 2013-04-03 14:19 z
    What is "copywriting details"? The design was thought, discussed and agreed on. Where were you? The reasons are already articulated many times. What has Gothic to do with Japanese? I didn't know Gothic romanisation entries exist before I was told. But what is different? Wording? Originally we had Hiragana: or Katakana:, then we changed to See: to allow for mixed scripts (hiragana/katakana/Roman letters, numerals). The definition line question was already explained. Gothic romanisation could be done the same way as Japanese with less parameters.
    Maximum 6. "zu" has 4 links. Combinations like ああ, あー, アア, あー will all give "ā". Romaji with ō may be linked to hiragana おお, おう, おー, katakana オオ, オウ, オー. Small　つ (tsu) - っ may be silent at the end of a word after vowels, thus giving more variants. --Anatoli (обсудить/вклад) 22:31, 3 April 2013 (UTC)
    Yes, copy=wording of the text used in entries, like “Romanization of” vs. “See:” vs. “See”. Now we know about Gothic, and the question of consistency needs to be addressed.
    Where was I? Why? Look, Anatoli, I wasn’t involved in a big conversation about romaji. Now it has become evident that this is relevant to the design of entries in three or more languages, and that it is a controversial edge case not covered perfectly clearly by our guidelines. Don’t imply that I don’t have a right to give my input. We all make an investment here, and I recognize your amazing contribution, but that doesn’t mean any of us owns some part of this project. —Michael Z. 2013-04-04 00:50 z
    IMO, this is not "relevant to three or more languages" (it only affects Japanese, obviously), and not that "controversial" (note that you are the only editor to vote against the new format). I ask too — where were you? If you had voiced your concerns earlier, it might not be a problem now. You have a right to give your input, but waiting for the vote after much discussion is not as helpful. —Μετάknowledgediscuss/deeds 02:17, 4 April 2013 (UTC)
    A new design pattern being implemented for romanization entries does not only affect Japanese. This vote came up and I chose to participate in it. I voiced my concerns as soon as I became aware and informed about the issue. —Michael Z. 2013-04-07 17:47 z
    You seem to be either misled or misleading, but I can't tell which. "A new design pattern being implemented for romanization entries" describes WT:V#Romanization and definition line perfectly, but this is a different vote. This one is just about Japanese. —Μετάknowledgediscuss/deeds 18:18, 7 April 2013 (UTC)
    That vote is about wikitext. It doesn’t affect the design of the entries at all. —Michael Z. 2013-04-07 19:06 z
    I meant that you can't say it wasn't thoroughly thought if the discussion lasted a month before a consensus and a decision was made in a very visible area. You criticise me for some implications but what are you implying? That we should consult Dan Polansky and yourself before making any change in any language because you don't take part in the discussion and language policy pages like WT:AJA are not on your watchlist? A decision on individual type of entries such as romanisation is not a common thing, so we didn't have a standard on how design them. They don't belong to any common category and exist independently.
    Having said this, I took the liberty and changed {{got-romanization of}} to display See and suggested to CodeCat to use a similar format to romaji where a definition line is generated by the template. We'll see if there is any negative reaction. I still don't get it why it should be dependent on Gothic or other languages. Pinyin, Gothic and Romaji existed independently for a long time and nobody cared. --Anatoli (обсудить/вклад) 01:27, 4 April 2013 (UTC)
    No you don’t have to consult Dan Polansky and me about everything. Likewise, I am not obligated to read every single Beer Parlour discussion in realtime, or to stay out of discussions if I have not.
    I am glad to see consideration being given to harmonizing these romanization templates. —Michael Z. 2013-04-07 17:47 z
  2. Oppose It appears that this new format caused an admin to block the Autoformat bot because it violates WT:ELE regulations. That is completely unacceptable, we need that bot. As such, I cannot accept this change. -- Liliana • 14:27, 8 April 2013 (UTC)
    @Liliana, I'm afraid I don't understand -- the Autoformat bot was violating WT:ELE? The format of {{ja-romaji}} violates WT:ELE? It's unacceptable that the bot was blocked? It's unacceptable that the bot or the template violates WT:ELE?
    And what precisely do you oppose -- the simplification of romaji entries in general? Or the current format of {{ja-romaji}}?
    It's also not entirely clear whether {{ja-romaji}} violates WT:ELE. CodeCat and I have been going back and forth about that a bit recently; I suspect the problem is partly that the writing in WT:ELE allows for more than one interpretation. -- Eiríkr Útlendi │ Tala við mig 21:44, 8 April 2013 (UTC)
I have already explained to Liliana-60 that the Autoformat is still running and romaji entries don't get picked up by it because they don't violate the format. Liliana-60 doesn't seem to pay attention to answers. No admin has blocked the Autoformat bot, to my knowledge. Are you implying that one of the JA developers did it? --Anatoli (обсудить/вклад) 23:00, 8 April 2013 (UTC)

I'm also very concerned by an apparent change yesterday (2013-04-07) to KassadBot's programming that specifically targets all entries using {{ja-romaji}}, adding {{defn}} notices.

This is a particularly troublesome change for a number of reasons:

  1. KassadBot did not previously analyze these entries as problematic.
    I suspect this was due to how KassadBot was programmed, and the kind of markup that KassadBot was analyzing. Depending on various parameters, bots can view the raw wikitext (same as what an editor sees), or expanded wikitext (an intermediary format, after templates are transcluded in; similar to manually subst-ing all the templates), or final HTML, among other possible formats. (See Special:ApiSandbox to poke around, if you're interested). Viewing the expanded wikitext would result in KassadBot seeing separate def lines, each starting with #, as produced by the template; viewing the raw wikitext would result in KassadBot seeing no def lines, as the template's effects are only visible once expanded.
    Since nothing changed in the format of {{ja-romaji}}, KassadBot's programming must have been adjusted.
  2. We're in the middle of two different votes related to the format of Japanese romanization entries, and the format output by {{ja-romaji}}.
    • Wiktionary:Votes/pl-2013-03/Japanese_Romaji_romanization_-_format_and_content (this vote)
    • ]
    Both of these votes include discussion about whether we need a separate line with a separate template call, or whether it's acceptable to have the template do that. Changing bot behavior with regard to this issue before the votes conclude is bad form, and could be viewable as either a willful nuisance or an attempt at strong-arming.
  3. The crux of this issue appears to be WT:ELE.
    Some editors are of the opinion that WT:ELE lays out strict requirements for separate lines in the wikitext starting with #, while other editors have made the point that WT:ELE doesn't actually say that this is a requirement. But again, changing bot behavior while these discussions are ongoing is not appropriate.

I'd like to thank -sche for blocking KassadBot until these votes and discussions can be sorted out. -- Eiríkr Útlendi │ Tala við mig 22:12, 8 April 2013 (UTC)

Did -sche really do it? If he did, was it to accommodate romaji entries? I don't think KassadBot would get romaji entries as badly formatted. We had one single instance, if you remember, when the template had * instead of # on a new line. --Anatoli (обсудить/вклад) 23:06, 8 April 2013 (UTC)
See Special:Contributions/KassadBot. -- Eiríkr Útlendi │ Tala við mig 23:08, 8 April 2013 (UTC)
I see. Thank you, Eirikr. I missed that development. So there may be some messing with KassadBot to undermine this project? Can we see if there was any change to coding or is it invisible? --Anatoli (обсудить/вклад) 23:21, 8 April 2013 (UTC)
  • Bots run based on client-side code, so any changes to bot code would be invisible to everyone except the bot owner. Liliana is KassadBot's owner, so I have asked her about the change in behavior over at User_talk:Liliana-60#Japanese_romaji.
It's possible that KassadBot depends on other code, such that the change in KassadBot's behavior on 7 April might have been due to a change not in KassadBot's own code, but instead in some other code that KassadBot calls. I have no idea if this is the case, but it is a possibility, so I have asked Liliana about that too. -- Eiríkr Útlendi │ Tala við mig 18:15, 9 April 2013 (UTC)

Abstain

  2. Abstain. Consensus has already been achieved; this vote is superfluous. —Angr 08:02, 31 March 2013 (UTC)

  3. Abstain. This whole thing has been a muddle since shortly after the JA editors arrived at consensus. I'm even muddled about whether it would be better to write here in the ====Abstain==== section, or below in the ====Oppose having this vote==== section. At any rate, it seems like there's already agreement amongst all the folks who might be working on JA romaji entries. Let my post here then count as Opposed to voting on largely settled issues, and Opposed to setting things in stone when discussion and consensus building should suffice (and so far had sufficed).

    @Michael, it sounds like your opposition is to the format of romaji entries, and not to the general idea of reducing romaji entries to limited stub content. Is that a correct interpretation of your comments above? -- Eiríkr Útlendi │ Tala við mig 15:42, 2 April 2013 (UTC)

    Yes, quite. It’s all part of the extended discussion. —Michael Z. 2013-04-02 16:04 z
  4. Abstain --Dan Polansky (talk) 20:30, 24 April 2013 (UTC)
  5. Abstain. I have no idea what's going on. It seems there are a few things that have happened outside the context of this vote that I am not fully aware of. I suggest tidying up those issues first and make a new vote that I can actually understand. Jamesjiao → T ◊ C 22:13, 28 July 2013 (UTC)

Oppose having this vote

  1. Oppose - -sche (discuss) 17:50, 31 March 2013 (UTC)
    Can I vote here as well as above? If we're going to have an unwanted, badly executed vote, it might as well be clear... —Μετάknowledgediscuss/deeds 17:55, 31 March 2013 (UTC)
    I don't see why not. I will find it funny if this vote shows that there's consensus to make a change, yet explicitly rejects codifying that consensus... but (if I may preach to the choir) if this vote establishes some format for romaji entries, it sets that format in stone, such that editors will have to run more time-consuming policy votes any time some detail of romaji formatting needs to be updated. Hence, I reject the idea of voting upon the issue, and prefer to let consensus on a format be reached by discussion. - -sche (discuss) 18:29, 31 March 2013 (UTC)
    @Metaknowledge: I don't know what -sche intended by this section heading, but nothing prevents you from writing "I don't want this vote", "I support the voted-on proposal but I object to having this vote" or the like as part of your support vote. In general, you can write in your vote comment anything that you think is related to what is being voted on. --Dan Polansky (talk) 18:36, 31 March 2013 (UTC)
  2. Oppose —Μετάknowledgediscuss/deeds 21:49, 31 March 2013 (UTC)
  3. Oppose Consensus was had, and any who might oppose on this vote should have discussed there first.--Prosfilaes (talk) 06:28, 1 April 2013 (UTC)
  4. Oppose This is becoming ridiculous. Lack of understanding, accusations, unproductive comments. New development - was KassadBot messed with?--Anatoli (обсудить/вклад) 23:08, 8 April 2013 (UTC)

Decision

  • Vote canceled for lack of quorum. (We don't have any specific requirement for quorum, but this vote-page shows as many people objecting to this vote's existence as supporting the most popular of the listed options.) —RuakhTALK 14:32, 2 September 2013 (UTC)
    Declaring the vote canceled seems wise, but, frankly, I cannot detect any issue with quorum. The number of people who cast a vote in at least one of the sections is 12. The number of people opposing the vote while apparently supporting the vote's proposal is 4 or 3, depending on whether you count what looks like -sche's retracted vote. Either way, at least 8 people cast a vote while avoiding the section "Oppose having this vote", which is a supermajority.

    That said, the vote seems hard the close and the proposed closure seems reasonable. By counting "oppose having this vote" as opposes, this vote fails, but it is clear that the proposal actually has a consensual support, so informally, the vote passes. Formally, the vote does not pass, as there are enough people who have decided to obstruct the vote's passing. --Dan Polansky (talk) 19:34, 7 September 2013 (UTC)

Wikious
Boobota
Sagapedia