If I understand the question correctly, the goal is to think about the total time spent working, and to apportion that time to each of several different languages based on the extent to which you used them for a project.
For example, let's pretend you were assigned to do a Java project for 2 months. After the 2 months ended, you were given a second project to be completed using C++, but your Java project kept going at the same pace. So after another two months, you might say you have effectively done 3 "work-months" of Java programming and 1 "work-month" of C++.
But 'experience' with a programming language is not simply the stated amount of time that you actively performed a work function with that language. In this example, just because you weren't directly doing Java for 1/2 the time in that last stretch does not mean you weren't learning about it, becoming better at it, even osmotically from the C++ experience.
Most of the time, once you have begun to use a programming language for serious projects, then your cumulative life experience with that language starts counting from that point on. Even if a few months go by when you don't use the language at all, you might still answer some Stack Exchange questions about it, read an article about it, review old code that you wrote, or teach someone else how to extend your old code to have new features. All of these activities (and many more) count as "experience" with the language, even if at the time you were more focused on using a different language, or your stated projects at work listed different tools.
To summarize, I would treat each language in isolation from the others. Ask when you first began performing serious programming tasks with that language and count your experience as starting at that time. If you feel you are especially rusty or out of the loop in a particular language, just estimate how much experience time to knock off of your estimate so that recruiters and hiring managers have a clear picture of your self-appraisal of your abilities. But do not try to intensely calculate the precise amount of dedicated work hours that technically went into one language versus another. Few, if any, recruiters or managers will even care about that level of specificity anyway.