Edge Rewrite
// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a44a8fe8fa753524

Jump to content

Talk:Ketohexokinase

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 4 days ago by Jeffrey34555 in topic Requested move 21 September 2026

Requested move 21 September 2026

[edit]
The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: moved. (closed by non-admin page mover) Jeffrey34555 (talk) 19:56, 28 September 2026 (UTC)Reply


Hepatic fructokinase → Ketohexokinase – The proposed title is the accepted name for EC 2.7.1.3 in the IUBMB enzyme nomenclature database and the official full name of the human KHK gene in the NCBI Gene record, where it is attributed to HGNC. It is also the name used in the article's infoboxes and throughout the text. "Hepatic fructokinase" is narrower than the article's actual scope, which covers both KHK-A and KHK-C rather than only a liver-specific enzyme. The proposed title is therefore more precise and consistent with authoritative nomenclature under WP:AT, while also clearly distinguishing this enzyme from Fructokinase (EC 2.7.1.4). The existing Ketohexokinase redirect can be reversed, with Hepatic fructokinase retained as a redirect. Potentialmotion (talk) 18:51, 21 September 2026 (UTC)Reply

I support: Ketohexokinase is also the uniprot recommended protein name which is the usual default choice based on MOS:MCB Pabnau (talk) 01:24, 23 September 2026 (UTC)Reply
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.