Name Games

This blog introduces another aspect of the problem of properly translating names into English. After that, Story Grid updates, 3d design status, watch dates and a headline review.

The Elizabeth Problem

Last week I introduced a problem dealing with how various Paleo names are translated in different ways in stock English Bibles. This is particularly true with New Testament names. In that blog I used Elizabeth as a good example. English readers think of that name as being unique to 1 person. In fact, she was named for the wife of Aaron. The spelling used for those women's names is exactly the same.

English readers for 500+ years have been unable to build a mental connection that the text is actually making. This is but 1 simple example. There are many others. For want of a better term, I am just calling it the "Elizabeth Problem."

Mechanical Translation

For many years I have had a strong conviction that whenever possible, the English translation of an ancient text should maintain a 1-to-1 match between the underlying original language term and the English.

This is so that English readers can build a mental map of the text based on English, but which matches a mental map that someone would build when reading in the original language. Elizabeth is a prime example of this problem. This example affirms my conviction in how translations should be done.

In recent lexicon work, we stumbled on another important example. Ryan found this when he was updating the BRB. He had gone in to remove Elizabeth from the BRB and replace that name with the name of Aaron's wife. That update goes live as this blog goes out. This is not full coverage of this problem in the BRB, but it is a reminder of this class of name related translation problems.

So let me show you another, related problem.

Yo-Ve-Ne and Yo-Ve-Ne-Yo-Wa

Yo-Ve-Ne is the root, while Yo-Wa is a common ending that indicates a place name. The Yo-Wa, is 2 letters. Yo is a hand, so many fingers, and Wa is a common ending meaning "the." Together these mean "the many." As an ending on a name, it often puts the emphasis on the people of a place or the collective set of heirs of an ancestor.

English translations of places and peoples are generally sloppy when it comes to exactly matching the Paleo endings to modern English. But the grammar is capable of precision. I would currently guess the editors were sloppy. So this is not fully fixable until audit.

Strictly translating the long form of this word into English we get Ionia. Yo often becomes 'I', the Ve often becomes 'o'. So this is a conventional translation of Yo-Ve-Ne-Yo-Wa.

The link above is to the Wikipedia article for that particular location. It is/was located on the western coast of modern day Turkey.

What is most important is how the sailors from this area eventually sailed the entire Aegean Sea. As a place name it gives rise to the original ancient name for what is now Greece. Greeks occupied this area until the Turks drove them out several hundred years ago.

The history of this place is part of the history of Constantinople, so Haggai Sophia and Orthodox Christianity. It is also part of the history of the modern nation of Greece.

Translate? Transliterate?

This is an example of yet another translation related vocabulary word problem. Translating names is someones done by following transliteration rules. Ionia, as I have described above, is a transliteration. If a modern translator uses Greek, or Greece, then the translator is performing a translation on the name.

If we are strict about this Paleo word, we would want to see Ionia in the English. But, this would mean nothing to modern readers. You can see why Ionia is conventionally translated into Greece.

Is substituting a modern place name for an ancient name a good practice?

I don't like it. But I am still surveying the problem.

I might rather see Ionia, and then be forced to learn how to exchange this name in my head. With electronic versions of the text, this could also be handled using a setting. The reader could decide, instead of the translator. Does the reader want to see the real, ancient, name? Or do they want to see the modern place name? Maybe they want to see both?

My current preference is to solve this problem using a setting. But, there are still more complications.

Javan

There are other transliteration rules for Yo and Ve. Yo can become 'J' in English. Ve can become 'v' in English. So Yo-Ve-Ne can be transliterated into English as Javan.

This is actually done in most Bibles when Yo-Ve-Ne is found in the post-flood table of nations.

This is an example of the Elizabeth problem, where translators do not always translate the same underlying word using the same rules all of the time.

Did you know Greece is one of the nations in the table of nations?

Neither did I.

What other nations might be similarly listed, but hidden, in that post-flood table of nations?

I don't know. I am still feeling along the side of this elephant. Good translation tools would make this question fast and easy to answer.

Why These Name Games?

Using Greece sometimes, Javan other times, and never Ionia, is a result of a translator game. We are now touching on how the modern heirs of our 6 villainous editors are still active with the text.

This seems to be driven, in part, by a Zionist desire to hide much of the content of the text. They remain in the game of narrative formation. They remain in the game of fooling Eve and her heirs over what did Joshua really say.

In this case, we can begin to build up a motive for when and why they would shift how they translate specific instances of original names.

Greece is one of the original colonies of Noah. So Greece and Greeks have a superior claim over Israel itself. Modern Iran is using a similar claim when they remind the world of 5000+ years of their own cultural history.

So Zionist translators hide the name Greece from the post-flood table of nations using a translator's trick. As a community, those translators ultimately fear superior claims.

Remember, Rome is also, in part, thought to be a colony of Greece. So Rome, so Europe, has a superior claim over Israel too.

You can see why this class of study is always hidden from most readers of the Bible. You can begin to see why there would be an Armenian genocide. You can see why they want to use the Ukraine war to burn down Europe.

More Tricks

There is another entire class of translation problems involving the name Yo-Ve-Ne. It is best explained by starting with the English side of this example. Then we will return and explain what someone in Paleo could actually infer about the story.

Whip In Temple

The link here is to John 2:13 in the BRB. This is John's telling of the story where Joshua has gone to the temple and overturns the tables of the money changers. In this particular version, he uses a whip. So this is the most emotional version of the story. Variations are told in all 4 gospels.

Joshua does this because he finds men who are selling animals for sacrifice. He also finds money changers with their tables. The parallel versions are simpler. They usually pick up on the issue of at least selling doves.

In all versions of this story, Joshua ends on the point that "his house" shall be called a house of prayer for all nations. This idea does not fall by filter rules, but you can see why an editor would like Joshua's endorsement of the Jerusalem temple in some general sense.

This final point is where we normally focus because there is the open question. Is this house, originally built by Solomon, something that Joshua might make a positive statement about?

We would generally think no, that Joshua has no real use for the temple. It was built, in part, because the heirs of Jacob asked for a king so they could be like all the other nations.

But let me explore the other side of this question. Could Joshua endorse at least some type of large religious building?

House of Prayer?

If this is inspired at all, Joshua may be allowing that any large, religious, building is acceptable to him if and when it is ONLY a house of prayer.

Money changing, but especially sacrifice, would thus be his major source of trouble. Sacrifice is the most serious problem. If the place is built for sacrifice, it would be out by Acts 15 rules.

If big houses of prayer are generally acceptable, then that temple would be an example, provided of course, the leaders of the temple cleaned up their act.

Other acceptable examples would be big modern places like Saint Peters in Rome. It would be acceptable to him to the extent it is also a house of prayer.

This might make some sense if what Joshua wants is people to start calling out in prayer. He sees all prayer, and can answer when he so chooses. So a place that encourages prayer is perhaps interesting to him.

The current Dome of the Rock, located at that same location, could be tested by this same standard. Most modern church buildings could be tested the same way. Is some building ultimately a house of prayer? Then that place is probably acceptable to Joshua.

In the Matthew telling of this story, see Matthew 21:12, we only get the details of selling doves, changing money, and a house of prayer. So the essential points of this story are those 3.

So, far, all of this is fine. We can debate many of these details. We can dispute which, if any, of the versions of this story might be inspired. We can debate what it might mean in terms of application to other large religious buildings.

Lexicon Complexity

As English language readers, we have missed an essential detail that might change how we interpret this general story. Even exposing this next problem, at all, also seriously complicates the conceptual design of the Paleo Lexicon. So this has serious technical implications.

Let me start with the Lexicon side of the problem then return to what may have really made Joshua so angry in the temple.

That Yo-Ve-Ne term, "Greek," can also be translated, just as easily, as "dove."

Only an original language reader can see this. Translators, and original language readers, must use context to select what meaning, so what English, to use when reading this word.

So the software problem of trying to enforce a mechanical translation stumbles badly on this particular vocabulary word. Not only is there a problem of what grammatical form of Greek to use, but also if it should be translated as a name at all.

The associated lexicon entry cannot be cleanly marked as a "names lexicon" entry or else a standard lexicon entry. Yo-Ve-Ne needs to be in both. To be more technically correct, Yo-Ve-Ne needs to be a single entry that shows both meanings. When displayed in a lexicon it needs to list off dove as well as Greek as possible English words that come from this single root.

For an original language reader, it is the presence of nearby words that drives the meaning. A dove flies in the sky. So if that Yo-Ve-Ne term is seen in the sky or flying or landing, then it is a dove.

Other contexts, like buying and selling, are not at all as simple to determine if dove or Greek is the intended meaning.

What Was Being Sold?

Because Yo-Ve-Ne is also what was being sold in the temple, there is an alternative interpretation that is completely lost in English.

In this particular story, there are no particular nearby vocabulary words that force this to be interpreted as a dove. Those doves were not flying, landing, cooing or similar. We only presume they were being used for sacrifice. We have villainous translators who would want nothing else. So we must keep our guard up for translator games.

But, maybe, something else was going on in the temple. Maybe the Jews were selling Greeks?

This is the obvious question that only an original language reader can ask.

Debate It

Imagine this as a subject for a college debating team. One side debates this word as dove. The other debates this word as Greek.

The dove side of the debate says this was for sacrifice. The building was for sacrifice. Visitors were there to sacrifice. They used their foreign money to buy doves so they could sacrifice. So this fits.

The Greek side of the debate says Solomon, who built the temple, had 1000 women. Why? Perhaps 700 of those women were to work the temple.

The Jebusites who started Jerusalem, and first built this temple, were following patterns of Sodom and Gomorrah. How does that manifest in the temple of Joshua's era? Through the buying and selling of Greeks.

The Greek side can point out that Solomon's Divine name, Yahweh, still has serious sexual connotations known to all well educated Jews. So the temple must also have serious sexual connections.

So the Greek side of the debate can claim that modern translators indicate "doves" were sold to those who did not otherwise know what was going on.

The Greek side of the debate can also claim the temple was like an Epstein Island, a front for a house of prostitution, about like most hotels in Vegas.

The Greek side of the debate can then explain certain design details of the building itself. It had 3 floors of upstairs bedrooms around the exterior walls. Those rooms suddenly have a knowable purpose.

This view also sets up for human sacrifice, which Joshua's crucifixion also supports.

The Greek side of the debate can easily go much further, but I try and keep this blog family friendly.

Why Was Joshua So Angry?

Which side of this debate would have the superior claim on what made Joshua so angry? Was it a den of robbers? Or is that word tampered too?

I certainly do not know which side wins this debate. As the budding translator, I don't want to stand in the way of discovering that such a debate exists at all in this story.

There must be some easy tooling that can be used to discover that Greek and dove are the same word. And, that tooling needs to warn English readers that conventional uses of the word dove can be modern Zionist translators covering for an inspired use of the word Greek. There may have been a different reason as to why Joshua was so angry.

Dove As A Class

Yo-Ve-Ne is not going to be the only example of this problem across the text. This "dove" problem is like the "Elizabeth" problem. Each stands in for a class of problems that are going to be sprinkled around the text.

Other names will have spelling that matches other standard vocabulary words. Probably no other examples make Joshua as angry as he was here.

So for now, I am back to 3d design work until I settle down enough to return later to these complex and subtle Paleo lexicon problems.

Diary Updates

Many years ago I was told prophetically to keep a written diary. Eventually that became a software project. I have diary files and a diary app. I am using them for long-running studies on how personal timelines actually work.

Earlier this year I added a system for carefully tracking personal watch dates. I had been doing this for awhile, but with by-hand calculations. Those updates added diary markup to automate the calculation and creation of future personal watch dates. This is very much less error prone.

Joshua clearly orders our days. With the correct tooling it is possible to see how this actually works. What we perceive as minor things he still cares about.

I have now added a life calendar timeline into that same diary app. I am working my way towards studies on the question of how much individuals run prophetic time lines. The first step is to lay out the measuring line.

An example of this is how Joseph was 17 when he was sold into Egypt. I showed in a recent blog how Joshua was 17 when he left Nazareth for Capernaum. In Joshua's case he was following Noah. So, Joseph was following the same life pattern. Both men were following the historical timeline.

Do many other people follow the same pattern?

I don't have enough documented personal history from the early years of my life to fully study these questions, but I am working on the theoretical tooling in order to study the problem as best as I can.

Birthdays

Once I added a personal life calendar to the diary app, I could immediately see where my Paleo Birthday falls in time. That was at least a first lesson.

My Gregorian birthday is at the end of October. But my Paleo birthday just passed a couple weeks ago. Fun. There are currently 2 years of difference in age because of how birthdays offset and how Gregorian vs. Paleo age is expressed. 2 year differences was something I would not have expected.

In doing this work I found an issue in the main timeline library which created an update this week to the Calendar app. Let me explain.

Calendar App

This week the Calendar app was updated. The basic calendaring library is setup for use in timelines. A simple use of that library handles the Calendar.

What has changed this week is that my personal diary app now sees personal history as a timeline. So I am now pushing the library into a strange timeline use case.

The library itself sets the flags that show up as the colored bars at the tops of the day boxes in the calendar app. Most days have nothing special. Sabbaths, New Months and Holidays trigger colored bars of various types. This impacts the label in the calendar box and the color of the bar above the box.

Conceptually, there are places where there are conflicts over how those bar colors are selected. New Months, Sabbaths, and various Holidays can at times collide on various days in the calendar. So the library prioritizes what should be displayed when there is a collision.

In particular, the days inside the weeks of Unleavened Bread and Tabernacles were previously considered lower priority than Sabbath days. The update this week was to shift holiday mid-week days to a higher priority than Sabbath days.

This was done because personal diary timelines do not carry around a weekly Sabbath cycle. So Sabbaths are naturally lower priority than everything else.

You will see the change in the Calendar app as updated this week. The Sabbath day labels and Color bars are replaced in all cases when that Sabbath lies within a holiday week.

Story Grid

This week Ryan has put considerable attention into updates for the Paul Letters I row in the Story Grid. This starts from story 550. This is the Ta row in the grid.

This week's changes are a result of both of us reading through those letters. We were looking for what might be added as a result of Ananias and his band of editors.

Ahead of Tabernacles week, Ryan had expanded some of the material in this section in order to allow us to find material that he would have otherwise left out. Since our reads are running late, that material has lingered in the Story Grid, Sabbath Reads and TT apps. Most of that type of material has been removed, at least as far as we have currently read.

The 2 main topics that have been dropped from Paul are 1) pretty much anything dealing with theology, especially the Holy Spirit. Also, 2) anything dealing with detailed church practices, like what to wear. Ananias was creating theology, and he was presuming an audience like that seen in his synagogues.

Christian theology seems to be the creation of Ananias. Joshua had to be written out of the New Testament whenever he spoke to people after his ascension. This is the same as the way Joshua was written out in the Old Testament. In the Old Testament case, names like Yahweh and Elohim were used instead. In the New Testament, "Holy Spirit" or just "Spirit" are the replacements for Joshua.

Joshua's view of his meetings are also not quite like what we know. It looks like there is a set of educational functions. These are built on most of the exhibits. They teach how the text is constructed. They teach how to read. The other function, the upper room function, is more like a modern Bible Study where a group of people gather for problem solving. They have a full library, larger than a Bible. They have a full timeline. They also have a star field, so they can consider off-world problems. None of this is sitting in church pews.

Paul's Contributions

The result of this week's updates is that Paul is generally on the topic of watching out for influences of Jews. In particular, being careful not to let them impact any sort of meetings and being careful to not let them impact how we are to think.

Paul reiterates the problem of circumcision, which is what started the Acts 15 council. He warns of false brothers who pretend to have faith in Joshua but do not.

Paul uses himself as a general example of what it means to follow Joshua. In particular he elaborates on his various troubles, like imprisonment. These are being used as examples of what it means to follow Joshua. This changes the tone of Paul's writings. It is much more demanding of a serious walk of faith.

Paul also encourages his readers to take matters to Joshua in prayer. This is more important that learning a set of rules. Paul does not give rules for how to solve every little thing. He is not telling his readers how to conduct meetings.

Ryan and I still have more reading ahead. We are still way behind on our Tabernacles reading schedule. We have been overwhelmed by what we are learning.

Shop Work: Sower

The first major new 3d design was finished this week. It is a large format copy of the Sower. This uses the new code for scaling models to any size. When finished it will stand about 2.5 feet tall, pushing 3 feet with the base.

This model fully sections all parts in the sower. At this scale, breaking the model into parts is now feasible. So it prints essentially without supports. Every part is printed flat on the bed of the 3d printer. Every part basically prints perfect, without support related surface burrs.

This will require assembly. I am experimenting with using a limited amount of glue for this model. This prevents the need to cover over bolt heads.

I am doing a draft in white plastic to test design and assembly. A finished copy will be done in silver plastic. Gloss silver plastic is fussy, but the correct color. Flat bed printing of that plastic will make the models better.

This scale of model needs a different set of model making tools for doing the assembly. Primarily a few larger clamps for gluing.

By lucky coincidence, a scaling factor of 3, creates a parts set which just barely fit on the stock 3d printer beds used in the shop.

By the time this blog goes out, about 1/2 of the parts will have been 3d printed. Watch for pics on Telegram.

Shop Work: Printer

Feedback from last week's blog was clear. Get a new printer ordered while ordering such things is still even possible and before inflation hits. Order went in this week. It should ship in November provided the world stays stable.

Match Dates

We appear to have made it to October 2, 2026, without anyone setting off a nuclear weapon in battle. Nice.

Note that we had a M4.2 earthquake in the Seattle area a few days ago. It was maybe 30 miles from the house. It had a sudden initial shock and then a shaking that followed. The M4.1 in Lebanon would have been similar. The Seattle quake was natural. The epicenter was in a forested area west of Puget Sound, east of Hood Canal, south of the known military bases in the region. The Lebanon quake was created with Israeli explosives, probably a small nuke as the prophetic stories would want to see.

This week the USA dispatched a 3rd aircraft carrier to the Middle East. There have been reports of the USA moving other equipment in preparation for resumed war with Iran. Iran continues to regulate what little oil leaves Hormuz. Ansar Allah continues to regulate what little oil leaves Saudi Arabia. Diesel shortages are expected to become severe in the western world in weeks ahead. Europe is particularly at risk of shortages and rationing.

Debate is centering on how war with Iran might impact Republican control of Congress. Current consensus is the Republicans will likely loose at least the House of Representatives. The real question is how many states voting systems are controlled by Zionists. This question cannot be easily answered, voting results themselves will provide some evidence.

War in Ukraine continues as it has for many months. The Russians continue to retaliate for Ukraine targeting critical Russian infrastructure. Most heavy industry and most energy in Ukraine is expected to be destroyed by Russia before snow falls in Ukraine.

Watch Dates

The day this blog goes out, 2026-10-02, Friday, is the replay of the last year of Azariah's reign. The following day, 2026-10-03, Saturday, is the start of Jotham's reign.

Note these prophetic dates also passed in August of 2002. The main headlines at the time was Saddam Hussein parading his "Jerusalem Army" basically a threat against Israel, which is why Iraq was later invaded. Also at this date, the USA opened a new military base in Qatar.

So the USA just pulled the last troops out of Iraq. So this is the other end of the war started because of Saddam's threats on Israel.

Iran has driven most US Bases out of the Persian Gulf, also a similar reverse of the 2002 headline of a new base in Qatar.

The current issue for Iran is modeled by Saddam's Iraq. Iran must conquer Israel. If not, Israel will conquer Iran. There is no possible peace until one of these outcomes is achieved. Iran is fighting for survival. Iran is much better prepared than Saddam. Is this enough?

Headline Review

The following caught my attention this week.

Pope In France

This post on Telegram has more photos of the Pope in France. This time at Lourdes, a well known pilgrimage location. Large, unscheduled, gatherings like this are important to note.

Assassination Details

This post on Telegram details events surrounding the February 28, 2026, assassination of Iran's supreme leader. His son was also injured. The Zionists bombed the hospital were his son was being treated. The son escaped, but with injuries. So the Zionists were willing to bomb civilians in order to kill the heir.

Prometheus At Star Base, Texas

Someone from France is building a big bronze statue and putting it up along the road into Star Base, Texas. This is almost certainly a masonic idol. It usually represents a standing curse against the subject. Clueless members of the public have no idea what is going on. Someone in France wants SpaceX to fail.

US Troops Leave Iraq

This link is to the Reuters report on the last US troops leaving Iraq.

Petrol Thieves

There was a strange arrest this week near a major US Airbase in the UK. 5 men were arrested, then released on bail. This was initially explained as an Iranian attack against the USA in the UK. Note the satellite photo shows these guys were not on base. Seems they were smuggling diesel, and found a spot off the main road to get out of traffic. But, the Zionist rule is simple, never let a good crisis go to waste.

Celebrations in Iraq

This link is to a PressTV post on Telegram reporting on the celebrations in Iraq over the departure of US troops. Various militias are still not disarming because there is still much US influence in that country.

Trucking Company Bankruptcies

Only a few weeks into diesel shortages in the USA and 16 American trucking companies have filed for bankruptcies. These apparently mostly ship food. Presumably more to come.

Swiss Neutrality

The link here is to a post on X detailing the national vote in Switzerland to end national neutrality.

This is a very big deal. This is the lost tribe of Levi. They were not to go to war. Modern neutrality is a marker for that tribe. That marker was lost in a national referendum. So when nuclear war comes, they, too, will go up in smoke. A sad day.

Unclear if this was via media propaganda or via ballot stuffing. The blame for the smoke shifts some based on the real cause for the outcome of this vote. If it was ballot stuffing, more Swiss might survive.

A Year to Recover

This link is to a post on X detailing a FED survey of 100 oil companies in the USA. Should supply return to normal, it will take at least 4 full quarters, so a full year, for the diesel market to recover to normal in the USA.

This is a huge issue. Much of the economy built on diesel fuels will be broken by then.

Pentagon Technical Dominance

So the Pentagon wants Musk, Gingrich and Palmer to take 120 days and report back about how the Pentagon can achieve technical dominance in the battle field.

This reminds me of various fairy tale movies from the 1930s. Someone want's Musk to wave a magic wand and make everything better.

The real issue is how to curry Joshua's favor. This is not a time in history for Zionist rulers in the Pentagon to be wishing for such a thing.

Sexual Meaning of Yahweh

This post on X by Brother Nathanael explains the Torah's understanding of the spelling of Solomon's god term, Yahweh. This post provides the Greek side of the debate with high octane evidence that it was not doves being sold in the temple.

More Later,

Phil