JMdictDB - Japanese Dictionary Database

Entries

Search | Advanced Search | New Entry | Submissions | Help
Login for registered editors
Username:
Password:
jmdict 1000000 Active (id: 2289196)

1. [unc]
▶ repetition mark in katakana
Cross references:
  ⇔ see: 2213380 一の字点 1. kana iteration mark



History:
6. A 2024-01-19 20:26:41  Jim Breen <...address hidden...>
5. A* 2024-01-19 04:15:46  Stephen Kraus <...address hidden...>
  Comments:
I think we're now only using the [expl] tag for "untranslatable" Japanese words that are glossed with transliterations.
It doesn't seem necessary for [unc] entries.
  Diff:
@@ -10 +10 @@
-<gloss g_type="expl">repetition mark in katakana</gloss>
+<gloss>repetition mark in katakana</gloss>
4. A 2020-04-05 00:29:27  Jim Breen <...address hidden...>
  Comments:
If the display of an entry in the database WWW page has:
  <= headword, etc.
it means that the indicated entry has a cross-reference TO the entry you are viewing. It is 
purely informational.
  => means there is a cross-reference FROM this entry.
  <=> means there are cross-references in both directions.
There is no actual automatic cross-referencing.
HTH
3. A* 2020-04-04 16:35:00  Rob Harwood <...address hidden...>
  Refs:
https://jisho.org/word/ヽ (no back-references visible without explicit back-ref included in ヽ entry data)
  Comments:
Just a little house-keeping tidy up. Adding back-references to 2213380・一の字点, so that people can find all related kana repetition marks from a single one. 

[To be explicit: Jisho.org does not seem to implement automatic generation of back-references, so while you can find ヽ from 一の字点 (since ref is in 一の字点 data), you can't automatically find 一の字点 from ヽ (since back-ref not explicitly in ヽ data).

After checking confirmation page, I notice that there are two 'See also' links on that page, one of which is the one I just added, and the other seems to be automatically generated by this JMDICT software (but it is not actually included in the data entry for ヽ). This indicates to me that the local JMDICT software automatically generates such references, but *not* in the data, leaving such automatic back-referencing to be re-implemented in any software that uses JMDICT data.

So, I wonder, what is the current policy for how to handle such automatic vs. manual cross-referencing/back-referencing? 

Has it been decided that client software should implement their own back-referencing, and so manual back-references should be avoided?

Or, has it been decided that manual back-referencing is optional; allowed, but not automatically supported? Or is it encouraged? Or has there not yet been a discussion/consensus on this? Just hoping for some sort of guidance here.

Instead of going ahead with multiple edits to other entries, along the same lines, I'll await a response on this one to see what policy I should be following. Cheers!]
  Diff:
@@ -8,0 +9 @@
+<xref type="see" seq="2213380">一の字点</xref>
2. A 2018-01-31 02:18:02  Jim Breen <...address hidden...>
(show/hide 1 older log entries)

View entry in alternate formats: jel | edict | jmdict xml | jmnedict xml | jmdictdb xml